[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-metadata] Groups - Metadata SC meeting added
Svante and I had a long chat yesterday, and we agreed (I think!) that we really have a handful of different kinds of cases we need to deal with. I want to suggest we think of them like this: 1. adding custom metadata to describe the document (the simplest; already done, no controversy) 2. add custom metadata to document content, either to describe: a. the document (may include references to non-document resources) b. some non-local resource In general, the enhanced search use case is an example of 1. The citation use case is an example of 2a. John's medical use case and Elias' demo are examples of 2b. The primary technical issue is in general the "2" cases. So I really suggest we focus on just two cases: Elias' demo and the simple split object literal that Michael presented. If Svante's still wants to persist with an approach which does not allow some metadata attributes in content, then write up some code (document fragments + XSLT) that shows how you'd do those two use cases. I also want to mention that I put up examples about six weeks ago. <http://wiki.oasis-open.org/office/Metadata_Examples> I even created a separate page for people to add those examples recast using Svante's idea: <http://wiki.oasis-open.org/office/Metadata_Examples_Package- Only_Alternative> I still don't see anything there though ;-) Bruce PS - An XSLT to read RDF triples from the content file using the hybrid approach Elias and I have advocated would be brain-dead simple. Think of a template like: <xsl:template match="*[meta:property]"> <rdf:Description rdf:about="{@meta:about}"> <xsl:element name="{@meta:property}"> <xsl:value-of select="."/> </xsl:element> </rdf:Description> </xsl:template>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]