Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Person-with-address Example Context Ontology"
m (Example Context Ontology moved to Person-with-address Example Context Ontology) |
|||
| Line 1: | Line 1: | ||
Let's imagine a Context whose domain involved things (or more precisely [[Digital Subject]]s) called Persons. Each Person has a surname, first name and a postal address. And let's say that this postal address is something that could be described in XML schema as: | Let's imagine a Context whose domain involved things (or more precisely [[Digital Subject]]s) called Persons. Each Person has a surname, first name and a postal address. And let's say that this postal address is something that could be described in XML schema as: | ||
| − | <xsd:complexType name="postalAddress"> | + | <xsd:complexType name="postalAddress"> |
<xsd:sequence> | <xsd:sequence> | ||
<xsd:element name="streetAddress" type="xsd:string" /> | <xsd:element name="streetAddress" type="xsd:string" /> | ||
| Line 13: | Line 13: | ||
For the sake of simplicity, we are going to side-step best practice and not model what in IdAS is called the "source" of these attributes. As far as we are concerned these attributes came out of thin air. | For the sake of simplicity, we are going to side-step best practice and not model what in IdAS is called the "source" of these attributes. As far as we are concerned these attributes came out of thin air. | ||
| − | The first thing a Context Provider needs to do is declare the ontology that will provide the language in which to describe instances of Persons along with their associated simple attributes (surname and first name) and compound attributes (postal address). | + | The first thing a Context Provider needs to do is declare the ontology that will provide the language in which to describe instances of Persons along with their associated simple attributes (surname and first name) and compound attributes (postal address). |
| − | + | You'll notice that like all Context ontologies, it includes near the top an "import" statement that imports the required base higgins.owl ontology. This "person-with-address" ontology is so long and tedious, that instead of including it inline, we show a couple of pretty pictures: | |
| − | |||
| − | Context Providers are also responsible for being able to export the Contexts they manage. Here is an example of an export to RDF of a Context that contains one Person ( | + | Context Providers are also responsible for being able to export the Contexts they manage. Here is an example of an export to RDF of a Context that contains one Person (Mary) and conforms to the person-with-address ontology. |
| − | + | <rdf:Description rdf:about="urn:address"> | |
| − | + | <pwa:city>Provo</pwa:city> | |
| − | + | <pwa:country>USA</pwa:country> | |
| − | + | <pwa:postalCode>12345</pwa:postalCode> | |
| − | + | <pwa:state>Utah</pwa:state> | |
| − | + | <pwa:streetAddress>123 Main St.</pwa:streetAddress> | |
| − | + | <rdf:type> | |
| − | + | <rdf:Description rdf:about="#PostalAddress"/> | |
| − | + | </rdf:type> | |
| − | + | </rdf:Description> | |
| − | + | <rdf:Description rdf:about="urn:mary"> | |
| − | + | <pwa:postalAdress> | |
| − | + | <rdf:Description rdf:about="urn:address"/> | |
| − | + | </pwa:postalAdress> | |
| − | + | <rdf:type> | |
| − | + | <rdf:Description rdf:about="#Person"/> | |
| − | + | </rdf:type> | |
| − | + | </rdf:Description> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 18:03, 29 September 2006
Let's imagine a Context whose domain involved things (or more precisely Digital Subjects) called Persons. Each Person has a surname, first name and a postal address. And let's say that this postal address is something that could be described in XML schema as:
<xsd:complexType name="postalAddress"> <xsd:sequence> <xsd:element name="streetAddress" type="xsd:string" /> <xsd:element name="city" type="xsd:string" /> <xsd:element name="state" type="xsd:string" /> <xsd:element name="postalCode" type="xsd:integer" minOccurs="0" /> <xsd:element name="country" type="xsd:string" minOccurs="0" /> </xsd:sequence> </xsd:complexType>
For the sake of simplicity, we are going to side-step best practice and not model what in IdAS is called the "source" of these attributes. As far as we are concerned these attributes came out of thin air.
The first thing a Context Provider needs to do is declare the ontology that will provide the language in which to describe instances of Persons along with their associated simple attributes (surname and first name) and compound attributes (postal address).
You'll notice that like all Context ontologies, it includes near the top an "import" statement that imports the required base higgins.owl ontology. This "person-with-address" ontology is so long and tedious, that instead of including it inline, we show a couple of pretty pictures:
Context Providers are also responsible for being able to export the Contexts they manage. Here is an example of an export to RDF of a Context that contains one Person (Mary) and conforms to the person-with-address ontology.
<rdf:Description rdf:about="urn:address"> <pwa:city>Provo</pwa:city> <pwa:country>USA</pwa:country> <pwa:postalCode>12345</pwa:postalCode> <pwa:state>Utah</pwa:state> <pwa:streetAddress>123 Main St.</pwa:streetAddress> <rdf:type> <rdf:Description rdf:about="#PostalAddress"/> </rdf:type> </rdf:Description> <rdf:Description rdf:about="urn:mary"> <pwa:postalAdress> <rdf:Description rdf:about="urn:address"/> </pwa:postalAdress> <rdf:type> <rdf:Description rdf:about="#Person"/> </rdf:type> </rdf:Description>