ONTOLOGY GROUP

1. INFS 770 ONTOLOGY GROUP Members: Riki Morikawa Alan Blair Kevin Vasquez Jeunghyun Cho Inja Youn My Huong Nguyen

2. Ontology, Economics, Semantic Web • It is a Shared Common Understanding Across People and Applications • Ontologies are Knowledge Representations that reduce Cognitive Load and Lower Transaction Costs • Ontologies Lower the Costs of Constructing New Services • Computers are Active Partners in Ontologies, their Ability to Process Content is Key to the Semantic Web Market-Based Ontologies • Create List of Emerging Ontologies • Note: High Failure Rate

3. Products/Services E-Commerce Core Digital Product/ Service Machine Mediated Ontology Traditional Commerce Machine Mediated Ontology Economic Players Human Mediated Ontology Physical Product/ Service Digital Process Machine Mediated Ontology Human Mediated Ontology Physical Process Economic Players Physical Agent Digital Agent

4. Create Industry Structure Explicit Knowledge Externalization (T-to-E) Combination (E-to-E) Prices Socialization (T-to-T) Tacit Knowledge Internalization (E-to-T) Formal Ontology Individual Group Organization B2B B2C C2C Inter-organization Administrative Processes Market Processes (Buy/Sell Justified True Belief)

5. Electronic Commerce and Security • 1987 SABRE Airline Reservation System • 1977 SWIFT (Society of Worldwide Interbank Financial Telecommunications) • 1982 EDI (ANSI X12 Standard) • 1987 EDIFACT (ISO 9735) • Today, E-Commerce security solutions include technologies such as: XML, SSL, X.509 certificates, etc. to provide confidentiality, integrity, non-repudiation, and authentication. • XML enables a high level of encryption granularity within an XML document. • XML Signature (W3C and IETF) and XML Encryption (W3C) • XML Key Management System (XKMS)

6. The Semantic WEB “The Semantic Web is an extension of the current web in which information is given well-defined meaning, better enabling computers and people to work in cooperation.” - Tim Berners-Lee, James Handler, Ora Lassila • The Semantic Web will contain contents and services that are understood by computers and software agents, and will be based upon XML, RDF, and WSDL. • Will most likely consist of several specialized ontologies connected by pointers and data populated by users. • Provides an infrastructure that enables the use of remote, mobile software agents. • While XML Schemas can provide the strong data typing, RDF can provide the meaning.

7. The Semantic WEB • XML Linking Language (XLink) - describes a standard way to link XML data and documents together. • expresses information on the nature and behavior of the link, support multiple destinations, allow link authors to define endpoints and traversal rules, backward compatible • “link definition” defines the relationship between the items to the linked • “participating resources” items connected together • “traversal rules” or “arcs” direction of traversal between pairs • XML Path Language (XPath) – enables hierarchical nodes sets to be created that consist of a root, elements, attributes, namespaces, processing instructions, and comments. • Namespaces – provides meaning to attributes and elements within an XML document. Schemas can have their own namespaces in which all declarations are unique and have their own meanings. This helps to deconflict attributes that have different meanings.

8. Resource Description Framework (RDF) Definition • World Wide Web Consortium (or W3C) in 1999 as a universally established carrier for metadata • RDF employs the XML language to exchange descriptions of Web resources – but does not have to be XML based RDF Model • A simple model for describing interrelationships among resources in terms of labeled properties and values • Includes: • Uniform Resource Identifiers (URI’s) • Triples • Literals • Uniformity within the RDF Model

9. Uniform Resource Identifiers (URI’s) Are URI’s with an optional fragment identifier, allowing the URI to send back a property of the information resulting from a given retrieval action Triples Occurs when one resource, known as the subject, is linked to another resource, known as the object, by means of an arc that possesses the title of a third resource, known as the predicate. http://.purl.org/DC/Creator http://MrX.gmu.edu/index.html mailto:MrX@gmu.edu

10. Literals Uniformity within the RDF Model Allow an individual to be able to write text directly to an RDF graph, as opposed to having to store it in another resource URI can be used as a node and as an arc label, which provides for a great deal of self-reference and reification when using the language RDF Syntax • necessary in enabling the creation and exchange of metadata • uses the Extensible Markup Language (XML) • Includes: • RDF Documents – Descriptions • RDF Containers • Distributed descriptions

11. RDF Documents – Descriptions • The definition of an RDF document • contained within an RDF document, for the most part pertaining to one resource, as well as containing a registry of properties. RDF Containers • classified as a part of the XML syntax - represented by a particular element with one of the following names: • rdf:Alt • rdf:Bag • rdf:Seq

12. Distributed Descriptions • distributing a given description over a set of resources exists 1. rdf:aboutEach's - value must be a container's URI; the corresponding description applies to every component of the container. 2. rdf:aboutEachPrefix's - value is a string; the parallel explanation pertains to any resource whose URI begins with the respective string. Reification of Asserted Statements • a means to reify declared statements • a single arc can be reified by appending an rdf:ID attribute to the property element, which will define the URI of the reified statement.

13. DAML+OIL OIL Sharing and exchange of ontologies to support the unequivocal shring of semantics Frame-based Representations, Description Logics, and Web based language  DAML Developed to support the limitation of XML as an extension Allows to describe RDF data, adds more semantics to the data DAML + OIL Builds on existing Web technologies based on a collection of RDF triples Provide a rich set of constructs to create ontologies and to markup information Disjoint Domain of object classes from domain of datatypes

14. XML Registry and Repository Data management system to provide services for XML artifacts Support the supply chain and business partnerships The benefits of XML registry and repository ebXML registry enable business to share information between two partners to allow e-business collaboration The types of objects Four basic states needed UDDI containing a directory of reference to Web services information rather than the objcets The best conjunction with ebXML

15. Authoring • XML editors • Allows authors to choose a root element and to markup the documents • Text editor • Support all the features of the XML language • Do not offer any real function to support in use • Document Conversion • Require the use of a particular set of markup rules

16. Collaboration • Business relationship is built on the foundation of trust • Supply Chain Management (SCM) • Achieved in many different stages automatically • Requirements to build collaboration • Keep developing an open standard

17. DATABASE - ERD

18. DATABASE - RELATIONSHIP

19. DATABASE – CLASS DIAGRAM

20. RELATIONSHIPOFIMPLEMENTATIONDATABASE

21. Architecture of Ontology System “Humans construct knowledge through experience” –Jean Piaget “Knowledge is like inputting to be processed and stored by users” (Computer metaphor) • Ontology Catalog System is a human cognitive thinking meta-search agent system. • To keep good ontology. • To keep organizational search. • To help human/computer processes aid search. • Desirable Ontology Catalog System. • Obstacles-Time limitation and Hard Coding-Time consuming. • For instance: Main problem is the establishment Soap Server such as Soap Toolkit 2.0 and MSXML 3.0 SP1 on the Ontology System. • Data Flow Diagram (DFD).

22. Architecture of Ontology System - DFD

23. Architecture of Ontology System • Desirable Ontology Catalog System (Con’t) • Implementation in Java coding • 1. Created “makeSelectQuery”method that includes three input • parameters: • String lev1Description, String lev2Description, & Stringlev3Description. • 2. Created “main” method that generates three output SQL statements. • A. If lev3Description is not Null, generate the below SQL statement forlev3. • Type description string: Desk Lamps • Type level # (1-3): 3 • SLECT • Cat4.Product_SKU,Lev1.Description AS Level1_ID, • Lev2.Description AS Level2_ID,Lev3.Description AS Level3_ID, • Cat4.Product_Name,Cat4.Product_Description,Cat4.Unit_Cost,Cat4.Quantity, • Cat4.Unit_Weight, S.Supplier_ID,S.Supplier_Name ,Cat4.Zip_Code • FROM iyoun.Catalog_level4 Cat4 • LEFT OUTER JOIN iyoun.Supplier S • ON S.Supplier_ID = Cat4.Supplier_ID • LEFT OUTER JOIN iyoun.level3_catagory Lev3 • ON Cat4.Level3_ID = Lev3.Category_ID • LEFT OUTER JOIN iyoun.level2_category Lev2 • ON Cat4.Level2_ID = Lev2.Category_ID • LEFT OUTER JOIN iyoun.level1_category Lev1 • ON Cat4.Level1_ID = Lev1.Category_ID • WHERE (Lev3.Description LIKE 'Desk Lamps%');

24. Architecture of Ontology System • In the below two cases, the outputs are like the sample shown in the previous • slide (B.If lev3Description is Null and lev2Description is not Null C.If • lev3Description is Null and lev2Description is Null and levDescription1 is not Null.) • Current Ontology Catalog System • Ontology Catalog System physical configuration: • Portable laptop(Intel celeron, 256 MB RAM, 1.5 GB, Web Server (IIS 5.0) with XP, SQL Server, and Application Servers. • Implemented as a working ASP prototype without SOAP Server. • Looks Like general search engines like google.com • Includes searchresult.asp, showxml.asp, showitem.asp, connection.asp, • and ontology.asp. • Connects SQL DB with ASP: SQLOLEDB • Shows OntologyResponse in XML format, according to UI’s Request_ID, • Level1, Level2, and Level3. • Simulates Ontology prototype with dynamic search in Demo section.

25. Thank You