office-collab — archive

[Patrick Durusau]

Dennis, On 10/19/2011 11:46 PM, Dennis E. Hamilton wrote: Funny, I don't think an ODF producer should be required to pay attention to the RDF at all, except maybe the embedded RDFa. But not manifest.rdf and any other *.rdf components in the package. Curious what you mean by "...required to pay attention to RDF at all...." ? Producers would be the components that produce RDF, whether in the manifest or RDFa. Did you mean consumers? There's nothing in the ODF specification for dealing with RDF package parts in any way whatsoever. It is a no-man's land. Change tracking seems a very messy business, especially since it has to deal with incoming references to xml:id fragment identifiers in parts of the content.xml. Without knowing what the semantics of the incoming reference is, it is not clear what is appropriate "change-tracking." The treatment of package parts does need to be beefed up, I will find the time to open a series of issues for RDF in 1.3. It also isn't clear what you mean by: Change tracking seems a very messy business, especially since it has to deal with incoming references to xml:id fragment identifiers in parts of the content.xml. "incoming"? From where? There seems to be some confusion about the nature of change tracking in ODF. At least in my opinion it isn't about tracking changes in the ODF XML. It is about tracking changes to the document instance, changes that are represented in XML so the next application in line knows what changes were made, accepted or rejected, etc. Yes, we have to make reference to ODF elements and attributes as part of recording changes, because that is how the changes will be manifested to the next application but isn't diffing the XML as though we were editing the XML. To put it another way, ODF isn't about editing XML, it is about XML representing an editing process and/or product for interchange. Not the same thing. Hope you are at the start of a great day! Patrick