April 14, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club

ITGumbo: spicing IT up

IT Copywrite

Technology and application of technology.

ebizQ presents ITGumbo: a spicy blog network where vendors and IT professionals share ideas about creating Business Agility.

July 2007 Archives

Encoding normative metadata context

Here it is suggested that if normative metadata terms can be represented by alphanumeric codes defined by respective standards organization associated with the product, then this will simplify the web services development and make search more efficient. The Web Service Definition (WSD) and Functional Definition (FD) documents will then use this normative metadata code only. The translation and conversion of the natural language query to normative metadata code will be done by the thesaurus based context mediator.

Example:
Normative metadata term code - xxxyyyzzz
Standards organization identification - xxx
Product vocabulary identification - yyy
Metadata term identification – zzz

» Continue reading Encoding normative metadata context.

Normative metadata for services

Web users have diverse requirements and seek different information. In order to do this they form different phrases and try to get the best result from a search application. The search query that is composed with the same meaning as the question generally seeks the best result. To support these diverse requirements most text search engines have been built with the basic algorithm as: best match for the query pattern in the web content. Semantic technologies aim to provide accurate and fast objective results that will not only enhance customer satisfaction but also provide better business opportunities. A customer has to find an appropriate search application that can lead him/her to the best business solution available for his/her requirement. Once the business solution has been found then the online customer interface of the business must be able to answer the customer queries.

» Continue reading Normative metadata for services.

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>

» Continue reading Extensibility of normative metadata ontology.

Assimilation of semantics in web 3.0

A product may be sold online as a single item or as a retail item. Single item represents single instance of the product in one sale offer, retail item represents more than one instance of the same item available in one sale offer . The EPCglobal tag id filter value suggests whether the item is available as a single item or retail item. The fields of EPCglobal tag id may be added as members of a class in a normative metadata vocabulary provided by EPCglobal. Thus every product that has an RFID tag with embedded EPCglobal tag will be represented as a subClassOf this EPCglobal Class.

» Continue reading Assimilation of semantics in web 3.0.