[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [office] Conforming OpenDocument Text Document, etc.
1. I notice that the template cases are not included. Do you want to handle those? Would they be instances of the same Templates are a valuable tool in support of interoperability arrangements. I wonder if they can simply be included under the corresponding conforming document type? 2. You appear to have set a new ceiling, but there is no new floor within those constraints, other than the existing constraints on conformant documents. That makes sense, although I think we need to deal with other prospective exclusions (binary objects, applets?) When characterizing consumer, producer, and processor targets, shall we have preservation requirements on elements that a producer does not support/interpret or must a processor be capable of processing and producing all of its target class, rather than simply producing documents confined to the target? 3. I don't think a requirement to support all of OpenFormula will fly. What will be done about the different conformance levels for OpenFormula? 4. Do we need some way for a producer to assert the conformance target in the document so that a target-constraining consumer can confirm/reject the document accordingly? 5. I continue to think we should consider that the document type determination be a normative part of the specification, with the target having the additional requirements for what shall and shall not be supported. (I think of type determination as more like schema than interpretation, its just that we have attribute and package item values that determine the applicable schema.) 6. I also think this is a big deal. It looks like the details should be hammered out in wiki drafts until we feel we have surrounded the situation and understand the implications on normative language throughout the specification, what this may raise as an issue for implementers (and adopters), etc. I fear the law of unintended consequences biting us here. - Dennis -----Original Message----- From: robert_weir@us.ibm.com [mailto:robert_weir@us.ibm.com] Sent: Sunday, March 15, 2009 14:49 To: office@lists.oasis-open.org Subject: [office] Conforming OpenDocument Text Document, etc. [ ... ] These specialized document targets specify constraints on static factors like namespaces, mime types and syntax. It will be straightforward to add Producer and Consumer targets corresponding to each of these to constraints on runtime behavior. The Producer/Consumer targets will likely invoke the requirement to process and be consistent with the semantics defined for the elements and attributes which are allowed in that document type. I'll work on writing up these Producer/Consumer targets next. -Rob ------------------------------------------------------------------------ 1.4.2.3 Conforming OpenDocument Text Document [ ... ] (D3.1) The <office:document> element shall have an office:mimetype attribute with the value "application/vnd.oasis.opendocument.text". (D3.2) If the document is OpenDocument package then it shall contains a mimetype stream containing the string " application/vnd.oasis.opendocument.text". [ ... ] 1.4.2.4 Conforming OpenDocument Spreadsheet Document [ ... ] 1.4.2.5 Conforming OpenDocument Drawing Document [ ... ] 1.4.2.5 Conforming OpenDocument Presentation Document [ ... ] 1.4.2.5 Conforming OpenDocument Chart Document [ ... ] 1.4.2.5 Conforming OpenDocument Image Document [ ... ] --------------------------------------------------------------------- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]