OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office-metadata] Suggestion for next version of ODF-OWL


Hi again,

I also want to share with you a manifest.rdf file example (using my alternate syntax suggestion, sorry) that I think demonstrates where I think the real utility of the manifest would come in. Here it is, then some comments:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rdf:RDF [
<!ENTITY uuid "urn:uuid:" >
<!ENTITY pkg "&uuid;a4bcb5e0-5ce1-11dc-a5f7-0002a5d5c51b" >
]>

      <owl:Ontology rdf:about="&pkg;">
            <owl:imports rdf:resource="http://docs.oasis-open.org/opendocument/meta/package/common"/>
      </owl:Ontology>
      <common:Package rdf:about="&pkg;">
            <!-- Here, we indicate the enterprise's web address for this package -->
            <owl:sameAs rdf:resource="&this;"/>
            <!--  -->
             <!-- and here, we give some versionInfo about this package -->
            <owl:versionInfo>last edited by Ben Franklin on July 4, 1776</owl:versionInfo>
            <!--  -->
            <common:hasPart rdf:ID="this_Content">
                  <odf:ContentFile rdf:about="&pkg;/content.xml">
                        <common:hasPart>
                              <odf:Element rdf:about="&pkg;/content.xml#this_patient">
                                    <!-- Here we make an assertion we want to publicly expose in the manifest about our patient, namely that our patient is a Person as defined by the eBiquity person.owl ontology -->
                                    <rdf:type rdf:resource="http://ebiquity.umbc.edu/ontology/person.owl#Person"/>
                                    <!--  -->
                                    <!-- Here we make an assertion to publicly expose the fact that our patient is the same as the Smith Hospital patient with the Smith hospital ID of "S45678" -->
                                    <owl:sameAs>
                                          <!-- We use a blank node identifier here, because we are literally going to say that our patient is "the same as something that has the Smith Hospital patient ID of "S45678" -->
                                          <rdf:Description rdf:nodeID="_12345">
                                                <!-- We obligingly use Smith Hospital's ontology to reference their patientID -->
                                                <smith:patientID xmlns:smith="http://www.smithHospital.com/enterpriseOntology#">S45678</smith:patientID>
                                          </rdf:Description>
                                    </owl:sameAs>
                                    <!--  -->
                              </odf:Element>
                        </common:hasPart>
                  </odf:ContentFile>
            </common:hasPart>
      </common:Package>
</rdf:RDF>


So basically, my point here is that I think we ought to make apparent to potential users that the benefit of the manifest is fourfold (at least):

(1) simply to list the metadata files that are attached

(2) to provide versioning info about the metadata files in a machine readable way, using owl:versionInfo and related properties

(3) possibly most important to me, to expose certain odf:Elements to RDF aggregators in an easy way

(4) to expose publicly some useful assertions about the elements that were exposed in (3), particulary using owl:sameAs, owl:differentFrom and owl:AllDifferent, in conjunction with references to other ontologies.


John



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]