[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)
Dear TC members, 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. > > And I guess an answer to that question is quite important for Olivers proposal. > From my point of view the discussion of Florian's general request to define the reaction on unknown property values has no impact on my proposal regarding the extension of vertical relation values for certain anchor types. Regards, Oliver. > > ~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. > -- ======================================================================= Sun Microsystems GmbH Oliver-Rainer Wittmann Nagelsweg 55 Software Engineer - OpenOffice.org/StarOffice 20097 Hamburg Phone: (+49 40) 23 646 670 Germany Fax: (+49 40) 23 646 550 http://www.sun.de mailto:oliver-rainer.wittmann@sun.com ----------------------------------------------------------------------- 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 ======================================================================= Oliver-Rainer Wittmann (od) - OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]