[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office] Slides about OpenDocument and meta data
Hi Duane, I think there is a big difference between the support of ID and IDREF data types and a "transparent system" you are describing. Especially for event-based APIs like SAX such a "transparent ID/IDREF" mechanism would be a killer, since the event-based XML parser must find all the IDs, before it could issue the transparent events referenced by the IDREFs. Sorry for the confusion, but yes - RelaxNG supports the ID and IDREF data types with the associated semantic, that for each IDREF there must exists an ID and that IDs may occurs only once. But no, I am not aware of the transparent ID/IDREF mechanism you described. Sorry for the confusion, Best regards, Florian > Rob: > > I didn't see it in the spec either but had asked this on the last call > and was told the answer was "yes". Regardless, wherever it is, we > can use IDREF to point at its' new location. This would be totally > transparent to processors and 100% foolproof unless the document was > corrupt. All parsers essentially use a SAX method to parse XML, then > build a DOM tree by having custom handlers take actions when they > encounter certain items. When they encounter > element[namespace:foo;name:bar]; the handler turns it into a special > instruction before handing it over to the tree. > > The idea of using the existing <office:meta> element sounds > intriguing. I do not know enough about this and would like to hear > what others think. > > Duane > > > > robert_weir@us.ibm.com wrote: > >> >> Hi Duane, >> >> Thanks for the write up. I read it over, as well as the RDF slides >> Florian sent out earlier. Since I might not be able to make the call >> tomorrow, I thought I'd send along my questions in advance. >> >> First, is the Dublin Core meta data really located deterministically >> in existing files? Is this just the practice of the current OO >> implementation? Or is it specified so? I didn't see this called out >> in the spec. >> >> The 1.0 OO spec, page 65, section 3.3 "Custom Metadata" says: "In >> addition to the pre-defined metadata elements, applications should >> also preserve any additional content found inside the <office:meta> >> element. As there is no semantics specified for such foreign content, >> applications need not process this information other than to preserve >> it when editing the document." If I'm reading this right, wouldn't >> this allow you to simply put the RDF within the <office:meta> tag, >> allowing extensibility as well as backwards compatibility? Nothing >> would need to be moved. What am I missing? >> >> I'm a bit nervous with the idea of moving the DC, and just leaving a >> "forwarding address" in the form of IDREF. Do we have a sense of how >> transparent this would be for existing processors? Not just the big >> OO/KOffice applications, but also the small XSL stylesheets or simple >> SAX parsers that fill out the document processing ecosystem with >> viewers, indexers, etc. I'd feel better if someone could tell me >> that ID/IDREF processing is transparent among the XML parsers in >> common use. >> >> Regards, >> >> -Rob >> >> >> >> *Duane Nickull <dnickull@adobe.com>* >> >> 09/10/2005 05:25 PM >> >> >> To >> Florian Reuter <Florian.Reuter@Sun.COM> >> cc >> office@lists.oasis-open.org >> Subject >> Re: [office] Slides about OpenDocument and meta data >> >> >> >> >> >> >> >> >> >> I finished my action item and produced a first draft of an idea for >> supporting RDF and still being backwards compatible with DC and other >> metadata. Sorry for the Word doc ;-) >> >> TTYL (monday CC). >> >> Duane >> >> Florian Reuter wrote: >> >> > Hi, >> > >> > please find attached some slides about OpenDocument and meta data. I >> > post these slides as a preparation for the meeting at Monday. >> > >> > Best regards and nice weekend, >> > >> > Florian >> > >> >------------------------------------------------------------------------ >> >> > >> >--------------------------------------------------------------------- >> >To unsubscribe from this mail list, you must leave the OASIS TC that >> >generates this mail. You may a link to this group and all your TCs >> in OASIS >> >at: >> >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> > >> [attachment "RDF Proposal.doc" deleted by Robert Weir/Cambridge/IBM] >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. You may a link to this group and all your TCs >> in OASIS >> at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and 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]