Re: [office-metadata] Groups - MetaData-Examples_07-06-21(MetaData-Examples_07-06-21.odt) uploaded

[Svante Schubert <Svante.Schubert@Sun.COM>]

Bruce,

Bruce D'Arcus wrote:
> Guys,
>
> Looks really good! Nice work.
Thanks! Of course still room for improvement...
>
> I have a couple of suggested changes and things to keep in mind for 
> discussions with the TC (based on discussions with Svante today).
>
> First, this:
>
>> In this scenario the document editor associates part of the document 
>> with metadata.
>
> I really, really think we need to avoid using vague statements like 
> "metadata" when we can instead use more specific terms like "resource 
> description" or "resource property." The reason is because I think 
> people will get confused.
Agree that we should be as precise as possible, on the other hand we 
should be as well consistent with our vocabulary.
Just to be sure, is for you the term "resource description" similar to 
the RDF object and "resource property" the RDF property (predicate)?

>
> Also, this example has a bunch of problems:
>
> <med:patient rdf:about="http://ex-hospital-DB/patients/ID98765";>
>     <ex:hasID rdf:resource="ID98765"/>
>     <ex:hasVitals>
>         <med:vitalData 
> rdf:about="http://hospital-DB/medical-note-cc1593";>
>             <rdf:type 
> rdf:resource="http://docs.oasis-open.org/opendocument/meta/package#Element"/> 
>
>         </rdf:Description>
>     </ex:hasVitals>
> </med:patient>
>
> First, note that this is not well-formed XML.
>
> Second, resources should be capitalized.
Obviously there is a copy-paste issue, the example should read:

<med:patient rdf:about="http://ex-hospital-DB/patients/ID98765";>
    <ex:hasID rdf:resource="ID98765"/>
    <ex:hasVitals>
       <med:vitalData rdf:about="http://hospital-DB/medical-note-cc1593"/>
    </ex:hasVitals>
</med:patient>
>
> Third, as I mentioned before, I think this nested RDF/XML obscures 
> what's going on with the graph, and should be:
Bruce, you must admit it is only human taste to nest it or use an IRI 
placeholder. One way or the other no parser will be obfuscated by this.
>
> <med:Patient rdf:about="http://ex-hospital-DB/patients/ID98765";>
>    <ex:hasID rdf:resource="ID98765"/>
>    <ex:hasVitals rdf:resource="http://hospital-DB/medical-note-cc1593"/>
> </med:Patient>
>
> <med:VitalData rdf:about="http://hospital-DB/medical-note-cc1593";>
>    <rdf:type 
> rdf:resource="http://docs.oasis-open.org/opendocument/meta/package#Element"/> 
>
> </med:VitalData>
>
> Finally, surely the rdf:type statement there is wrong, or at least 
> unnecessary?
Some problem, as mentioned above. The med:VitalData is as in content 
data by default of type xs:string and therefore not of type odf:Element.

Svante