[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-metadata] Content duplication and ODF related RDF vocabulary
On Dec 19, 2006, at 8:44 PM, Svante Schubert wrote: > Let me write the content.xml as I assume it would like it in an > xml:id-alone approach. > The content.xml using the xml:id-only approach, as Model independent > View without awareness of any metadata > > <!-- some text metadata refer on from the content.xml --> > <text:span style:name="s2" xml:id="_1">CG7217</text:span> > <text:span style:name="s2" xml:id="_2"> is a gene product. </text:span> > <text:span style:name="s2" xml:id="_3">It was introduced on > </text:span> > <text:span style:name="s2" xml:id="_4">GENCON Conference</text:span> > <text:span style:name="s2" >.</text:span> The RDF could be: _:some_anonymous_id a ex:GeneProduct ; rdf:value "CG7217" ; ex:introductionVenue "GENCON Conference" . So three triples. [note: the event could also be a resource itself] Options I would be fine with: 1) RDFa approach, with triples in-content. <text:p meta:about="http://ex.net/1" meta:class="ex:GeneProduct"> <text:span meta:property="rdf:value">CG7217</text:span> is a gene product. <text:span style:name="s2">It was introduced on </text:span> <text:span style:name="s2" meta:property="ex:introductionVenue">GENCON Conference</text:span> </text:p> 2) RDFa approach, with triples in-package. <text:p meta:about="http://ex.net/1"> <text:span>CG7217</text:span> is a gene product. <text:span style:name="s2">It was introduced on </text:span> <text:span style:name="s2">GENCON Conference</text:span> </text:p> All that content gets duplicated in RDF/XML, and properties do not get marked as such in content: <ex:GeneProduct rdf:about="http://ex.net/1"> <rdf:value>CG7217</rdf:value> <ex:introductionVenue>GENCON Conference</ex:introductionVenue> </ex:GeneProduct> Using xml:id to identify the subject would work, too, but they are different. 3) RDFa approach, using a style abstraction: <text:p meta:about="http://ex.net/1" style:name="Gene Product"> <text:span style:name="value">CG7217</text:span> is a gene product. <text:span style:name="s2">It was introduced on </text:span> <text:span style:name="introductionVenue">GENCON Conference</text:span> </text:p> ... where the styles contain the appropriate property and class URIs instead. 1 and 3 are essentially equivalent. I dislike the xml:id approach to achieve those outcomes because it adds too much complexity while leaving the content pretty much opaque. I would prefer to scale back functionality than do this. Bruce
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]