OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [office] Rules for handling parsing errors (was: proposal forODF1.2: extension of verticalrelationvaluesfor certain anchor types)


Florian Reuter wrote:
> Well just put them on the agenda. If we don't have time -- fine. As long as they are "in the loop" its OK for me.

I have added this to the agenda, but the best way to actually track this 
idea would be to create a proposal wiki page for this. We may then 
schedule the discussion of your idea in the same way as that of any 
other proposal.

The page does not have to be very detailed at the start. It should be 
sufficient if it states what you have said already. This would allow us 
to have a first discussion of the topic that allows you to figure out if 
you want to further elaborate the idea, or just cancel its discussion.


> And I guess an answer to that question is quite important for Olivers proposal.
> ~Florian
>>>> Michael Brauer - Sun Germany - ham02 - Hamburg <Michael.Brauer@Sun.COM> 07/04/08 12:00 PM >>>
> Hi Florian,
> I haven't set up the agenda for the next call, but we have already a lot 
> of topics on the agenda. Some of them are waiting for a discussion for a 
> long time already, and you have requested the discussion of several 
> proposals, too.
> We won't have the time to discuss all of these things in the next call. 
> I will keep this in the loop of agenda items, but ask for your 
> understanding if this will have to be scheduled for a later call.
> One more remark below.
> Thank you
> Michael
> Florian Reuter wrote:
>> Hi Michael,
>> Well lets discuss this in the next TC call then. 
>> Wrt. to Olivers proposal the interresting question is what do we expect todays readers to do with it... 
>> When I read the current ODF spec it seems to me that the document is simply not conformant and thus everything can happen....
>> Anyway: Was just curious whether we say something somewhere in the spec about invalid values already.
>> You may wanna take a look at "Rules for handling parsing errors" of the CSS spec:
>> http://www.w3.org/TR/2007/CR-CSS21-20070719/syndata.html#parsing-errors
>> It would be great to have something similar in ODF.
>> E.g. when we would use the CSS rules for handling parsing errors the answer to the backward compatiblity question of Olivers proposal would be very easy:
>> <quote>Illegal values. User agents must ignore a declaration with an illegal value.</quote>
> If my understanding of Oliver's proposal is correct, then all values are 
> valid values. It is only the combination of particular attributes and 
> their values that was not permitted. So, stating that user agents must 
> ignore a declaration with an illegal value won't help in this case.

Michael Brauer, Technical Architect Software Engineering
Sun Microsystems GmbH             Nagelsweg 55
D-20097 Hamburg, Germany          michael.brauer@sun.com
http://sun.com/staroffice         +49 40 23646 500

Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
	   D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]