1 / 18

Ontoprise: B 3 - Semantic B2B Broker

Ontoprise: B 3 - Semantic B2B Broker. whitepaper review. CSCI 8350, Spring 2002,UGA. Bernhard Schueler. Overview. Aim of Ontoprise Problem: interoperability Previous approaches Using ontologies Using RDF Remarks. The aim of Ontoprise is to provide ontology-based B2B-applications.

thai
Download Presentation

Ontoprise: B 3 - Semantic B2B Broker

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ontoprise: B3 - Semantic B2B Broker whitepaper review CSCI 8350, Spring 2002,UGA Bernhard Schueler

  2. Overview Aim of Ontoprise Problem: interoperability Previous approaches Using ontologies Using RDF Remarks

  3. The aim of Ontoprise is to provide ontology-based B2B-applications. Those applications should make the semantics of business information machine-processable. Aim of Ontoprise

  4. Example: Product Catalogues The seller’s product catalogue is transformed into an electronic data format. Programmers write transformation programs to generate different formats and views required by buyers. This process requires human resources and time.

  5. Seller and buyer have catalogues, which are structured differently. Seller’s catalogue: a printer has an attribute type with values laser, ink or matrix. Buyer’s catalogue:there is a subclass laser printer. Example computer dealer

  6. How can the data formats automatically be mapped between the catalogues? Mapping is necessary to create and update the buyer’s catalogue. It is expensive to program those mappings. Solution:automate the creation of mappings, which can automate creation and update of the catalogue. Problem: Mapping

  7. EDIFACT provides a standardized electronic format to exchange data between sellers and buyers, allows the specification of standards for application areas. The standards cover the semantics of different application areas. Previous approaches - EDIFACT

  8. XML-specifications provide a semi-structured description of products, orders, … . DTDs or XML-schema specifications define the structure of the data. Previous approaches – XML

  9. Readable for non-experts, Integrated with other document/data exchange standards, DTDs, XML-schema enable generation of tools like form editors, Designed for the web. Advantages of XML over EDIFACT

  10. <article><articleid>a_5634</articleid><category>printer</category><type>laser</type><article><articleid>a_5634</articleid><category>printer</category><type>laser</type> </article> <article><articleid>a_5634</articleid><category>laserprinter</category> </article> XML Description, Example:

  11. Implicit agreement on meaning of tags is necessary. Validation of XML using DTDs is only syntactic. The labeled tree structure is checked. There can’t be semantic constraints, e.g. The price of a mouse may only be 1/100 of the price of a computer system. There is no inheritance. Deficiencies of XML – 1

  12. Transformations:They are purely syntactical, using XSLT and DTDs.Therefore they would have to bee hand-coded. Queries:XQL and XML-QL allow to query the document structure.Give me all printers for which cartridges are available that last for more than 5000 pages.Can be done. But it’s very cumbersome and overloaded with syntactic aspects. Deficiencies of XML – 2

  13. Ontologies define a domain and provide a shared vocabulary. “leight-weight” ontologies model concepts with properties and relationships, which are embedded in an is-a-hierarchy.They are comparable to database schemata. “heavy-weight ontologies also contain rules and constraints. Ontologies

  14. Ontology Ontologies in B3 Ontology OntoMap DTD Maker OntoLift DTD DTD Custom DTD XML documents DTD XML documents

  15. Ontology Ontologies in B3 - with RDF Ontology OntoMap RDF documents RDF documents

  16. OntoEdit, OntoFact,generates forms for attributes and relations of instances (of concepts of an ontology), OntoAnnotate,allows the user to add meta information to HTML, Word, PDF. The B3 B2B Broker – Basic tools

  17. OntoLift, provides means to identify concepts and relationships from an XML-DTD or XML-schema, DTDMaker, OntoMap, semi-automated creation of mapping rules, OntoCompile,creates a set of XSLT transformations. The B3 B2B Broker – Advanced tools

  18. By the time the paper was published not all of the tools had been implemented. By now, data would rather be stored using RDF than pure XML. A means to create forms, views and web content form RDF might be more interesting. Remarks

More Related