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] Conformance Definition Proposal and Normative MIMETYPE

I think the normative MIME types should be in sections 1 or 2 just like
namespaces.  Also, the normative document structure uses the MIME types as
glue.  I think that has them belong in the body of the specification.

With regard to the appendix, it needs to be updated (since the types have
been registered for some time and the others should probably be deprecated
if ever used).  With regard to file extensions, I don't know if those are
normative or not.  MIMETYPE registration is not a registration of file
extensions in the same way (the file extensions in the registration are just
identified as being in use).  I have no idea what the intention of the ODF
TC or the specification is in the matter of file extensions.

 - Dennis 

-----Original Message-----
From: Michael.Brauer@Sun.COM [mailto:Michael.Brauer@Sun.COM] 
Sent: Tuesday, January 20, 2009 05:47
To: dennis.hamilton@acm.org
Cc: office@lists.oasis-open.org
Subject: Re: [office] Conformance Definition Proposal and Normative MIMETYPE


On 01/19/09 23:09, Dennis E. Hamilton wrote:
> Michael,
> Concerning what fits inside of "conformant" (whether there is a
loosely-conformant or not), I think there needs to be something about
normative MIMETYPE values for the office:mimetype attribute and for the
MIMETYPE item of an ODF package.  At the moment these are defined in a
non-normative appendix and apparently the package MIMETYPE item is optional
(or is in 1.1). 

If I remember it correctly, then the appendix is informative because 
when we approved ODF 1.0, the registration of MIME types was in 
progress, and we did not want to add normative MIMETYPE unless the 
registration was successful.

We may make the appendix normative now, but that's not related to the 
conformance clauses itself.
> For a conformant document, I think we must be more precise and normative,
especially with regard to anything that is covered in the <office:document>
schema directly or in its hypothetical synthesis from package items.
> In that regard, the requisite alignment of normative MIMETYPE and
<office:body> content elements needs to be spelled out normatively.  This is
not something that the schema can do on its own without supplemental
normative language about what MIMETYPEs require what <office:body> content

I agree that the MIMETYPE section currently does not explicitly say what 
the child element of <office:body> has to be for the individual 
MIMETYPEs, but I would not do so as part of the conformance clauses 
themselves, but as part of the MIMETYPE appendix.

Best regards


> Doesn't that make sense for (strict) compliance?
>  - Dennis
> -----Original Message-----
> From: Michael.Brauer@Sun.COM [mailto:Michael.Brauer@Sun.COM] 
> http://lists.oasis-open.org/archives/office/200901/msg00110.html
> Sent: Thursday, January 15, 2009 01:37
> To: office@lists.oasis-open.org
> Cc: Robert Weir
> Subject: [office] Conformance Definition Proposal
> Dear TC members,
> I would like to discuss the below proposal in the next TC call, in 
> particular whether we want to have something like a loose conformance.
> Since the current conformance definitions need to be modified, it would 
> be good if we could agree on one or the other alternative as basis for 
> any future work on the conformance definition, if required. If one of 
> the two proposals already is acceptable, then that's fine for me, too, 
> of cause.
> This would allow us to integrate the proposal into the specification, 
> and would allow us to work on further items that depend on the 
> conformance clauses. These are the schemas and the conformance clauses 
> for the other parts.
> Best regards
> Michael
> On 12/11/08 03:28 PM, Michael.Brauer@Sun.COM wrote:
> http://lists.oasis-open.org/archives/office/200812/msg00095.html
> [ ... ]
>> Document Description:
>> Conformance Definition Proposal
>> View Document Details:
>> http://www.oasis-open.org/committees/document.php?document_id=30360
>> Download Document:  
>> PLEASE NOTE:  If the above links do not work for you, your email
>> may be breaking the link into two pieces.  You may be able to copy and
>> the entire link address into the address field of your web browser.
>> -OASIS Open Administration
> [ ... ]
> ---------------------------------------------------------------------
> 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
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

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:

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