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] ODF 1.2 Single-Level Conformance and Floor << CeilingAlready


On 01/20/09 00:46, Dennis E. Hamilton wrote:
> I forgot something, if I want to make an application/xml document (and
> whether this is required and what else is permitted, like a <!DOCTYPE ...>
> is a bit vague in the ODF specifications, since the XML specification allows
> both and requires neither):


If the XML specification allows both and requires neither, you can use 
neither or both. Why should the ODF specification be more specific than 
the XML specification? What problem would that solve? Or, what is the 
issue with not being more restrictive than XML itself?

Michael




> 
> 	-	-	-	-	-	-	-
> 
> <?xml version="1.0" encoding="UTF-8" ?>
> <!-- Minimum Required ODF 1.0/1.1 Text Document
>      There is one for each of the main document
>      types.  There is a package equivalent that
>      has the same office:body in an office:document-
>      content element in content.xml and has the MIMETYPE 
>      in the special first-item of the package.
>      For a text template, just change the mimetype.
>      -->
> 
> <o:document 
>       xmlns:o="urn:oasis:names:tc:opendocument:xmlns:office:1.0"
>       o:mimetype="application/vnd.oasis.opendocument.text"
>       >
>    <o:body>
>       <o:text />
>    </o:body>
>       <!-- Singing: I ain't got no body, no body have I ... -->
> </o:document> 
> 
> 	-	-	-	-	-	-	- 
> 
> -----Original Message-----
> From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] 
> Sent: Monday, January 19, 2009 15:19
> To: robert_weir@us.ibm.com
> Cc: office@lists.oasis-open.org; Bart Hanssens
> Subject: RE: [office] ODF 1.2 Single-Level Conformance and Floor << Ceiling
> Already
> 
> [ ... ] 
> 
> The following example is ridiculous (and Bart Hanssens will raise his
> eyebrows), but it points out the most (or least, depending on perspective)
> that any ODF processor has to deal with.  Acceptance of all sorts of
> additional content must be acceptable, but support for it at the processing
> or semantic level is not.  This is a far bigger deal for interoperability
> than whether or not foreign elements are allowed, with or without some
> proviso that the reduction to a conformant document be benign.  Keeping in
> mind that the world is a mostly-practical, often-realistic, place, and no
> one could get a way with this, here is all that the letter of the ODF law
> requires.
> 
> [ ... ]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
> 


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

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]