July 4, 2007 12:56 PM
Extensibility of normative metadata ontology
Consider the following OWL ontology with normative metadata (assumed) provided by a standards organization, this ontology describes the characteristics of a product "Laptop":
|
<owl:Class rdf:ID="Laptop" /> <owl:Class rdf:ID="Speed" /> <owl:DatatypeProperty rdf:ID="LaptopProcessorNumber"> <rdfs:domain rdf:resource="#Laptop" /> <rdfs:range rdf:datatype="xsd:integer" /> </owl:DatatypeProperty> <owl:ObjectProperty rdf:ID="LaptopProcessorSpeed"> <rdfs:domain rdf:resource="#Laptop" /> <rdfs:range rdf:resource="#Speed" /> </owl:ObjectProperty> |
This ontology is extended by web 3.0 search application provider as follows:
|
<!DOCTYPE rdf:RDF [ <!ENTITY lapt "http://www.example.com/test/laptop#"> ]> <owl:DatatypeProperty rdf:about="lapt:LaptopProcessorNumber"> <rdf:type rdf:resource="owl:InverseFunctionalProperty" /> </owl:DatatypeProperty> <owl:ObjectProperty rdf:about="lapt:LaptopProcessorSpeed"> <rdf:type rdf:resource="owl:InverseFunctionalProperty" /> </owl:ObjectProperty> |
Different vendors of laptop may define the product laptop as given here and use the normative metadata terms associated with this class in WSD document or web content to assimilate the information into semantic web framework. The vendors may associate names with product range for a given processor.
|
<owl:Class rdf:ID="Vendor1ProductXYZ"> <rdfs:subClassOf rdf:resource="lapt:Laptop" /> </owl:Class> <owl:Class rdf:ID="Vendor2ProductXYZ"> <rdfs:subClassOf rdf:resource="lapt:Laptop" /> </owl:Class> |
The OWL Inverse Functional Property implies that if property P is applied to a <subject, object> tuple such that P<y,x> and P<z,x> then y=z. Here in this example a user query such as: "laptop with 2.0 GHz speed" may be converted to a search for the Laptop vendors with support for processor speed or corresponding processor number. The search for normative metadata terms LaptopProcessorNumber and LaptopProcessorSpeed will be converted to application of these Inverse Functional Properties on tuples <vendors, "Intel Core Duo Processor T2500" > and <vendors, "2.0 GHz">. Thus all web pages and web services found on the WWW for these properties (normative metadata terms) and the given values can be considered to describe "Laptop" product and may be returned in the query result. Example: all vendors found for LaptopProcessorNumber = T2500 will be considered as laptop vendors.
The product vendors may use different subset of normative metadata terms to describe the products. The web content provider can find the necessary normative metadata terms from the basic ontology provided by the standards organization. These ontologies may also be used by other agencies to define standards for products to be used within an organization. The web 3.0 search applications may have different search algorithms and hence define different ontologies for the normative metadata terms. The challenge for web 3.0 search application developers will be to define the most optimized and efficient algorithm and ontologies.
Conclusion: The provision of normative metadata terms by standards organization will provide the flexibility to define different ontologies with these normative metadata terms. In order to be able to do so the ontologies provided by the standards organization must provide the basic ontology for normative metadata that is extensible by the users of the ontology. The ontology can be extended by using "rdf:about attribute".
Note: Speed class may have properties as value and clock speed.



I am going to be blogging live from a couple of days of the
Leave a comment