1 / 47

New Working Ideas for MMFI4Ontology Registration

New Working Ideas for MMFI4Ontology Registration. 3. P 25. WANG Chong, HE Keqing, HE Yangfan, WANG Jian. State Key Laboratory of Software Engineering, Wuhan University, P.R.China. Background Introduction of MMFI4Onto NWI Ⅰ: Registration of Process Ontology

prem
Download Presentation

New Working Ideas for MMFI4Ontology Registration

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. New Working Ideas for MMFI4Ontology Registration 3 P 25 WANG Chong, HE Keqing, HE Yangfan, WANG Jian State Key Laboratory of Software Engineering, Wuhan University, P.R.China

  2. Background Introduction of MMFI4Onto NWI Ⅰ: Registration of Process Ontology NWI Ⅱ: Harmonization with other standards Future work Outline

  3. Background Introduction of MMFI4Onto NWI Ⅰ: Registration of Process Ontology NWI Ⅱ: Harmonization with other standards Future work Outline

  4. characterized with • rich semantics • heterogeneous structure • various representation • unsteady • …… hamper • knowledge sharing • effective utilization • …… Resources on web • information resource • service resource • infrastructure resource • ……

  5. Objective Registration Sharing and reuse Interoperation between human beings between human beings and machines between machines Resource management • Resolution • Ontology is used as the foundation of communication. • A common facility should be provided to register resources on semantic web.

  6. Ontology describes concepts and the relationship between them in the universe of discourse. has been identified as a knowledge representation mechanism for semantics. Ontology captures the semantics of information from various sources, gives them a concise, uniform and declarative description, and has gained significance in terms of the demands in academia and industry. From D. Fensel: Ontologies: A Silver Bullet for Knowledge Management and Electronic Commerce. Why Ontology

  7. Scalable, Compatible and Open • Extensible In a framework, the frozen spot implies the fixed and reusable part that we need not customize. A high reuse rate reduces the end-user's work in application development. Conversely, the hot spot implies the flexible part that we need to customize. • From Takeshi Chusho, Hiroshi Tsukui and Katsuya Fujiwara: • A Form-based and UI-Driven Approach for Enduser-Initiative Development of Web Applications Framework for resource registration (1/3)

  8. Scalable, Compatible and Open • Harmonization Framework for resource registration (2/3) • Coordinate with other existing standards • Build a bridge for interoperation between systems based on different registry mechanisms • Supplement with no change to the original structure of those registry models

  9. Scalable,Compatible and Open • Interoperation Framework for resource registration (3/3) • Extended hot spot should follow the specification of frozen spot. • Interoperation can be implemented among those extended parts.

  10. Ontologyis the key issue for semantic annotation; important for interoperation between various resources. In order to promote sharing and interoperation between resources, a framework is needed to register ontology and other resources on web. Summary of background Framework for Metamodel Interoperability: Metamodel for Ontology Registration(MMFI4Onto)is such a facility.

  11. Background Introduction of MMFI4Onto NWI Ⅰ: Registration of Process Ontology NWI Ⅱ: Harmonization with other standards Future work Outline

  12. MOF,ISO 11179(MDR) MMFI Core Model MMFI4Onto MMFI for Modeling Constructs MMFI for Mapping MMFI for Ontology Registration SKLSE(WHU) Metamodel Instance Interoperability, Exchanging Universe Of Domain MMFI & MMFI4Onto

  13. MMFI Core Model & MMFI4Onto

  14. Reference Ontology & Local Ontology (1/3) • Reference Ontology (RO) • specified by standard organizations • stable • Local Ontology (LO) • used by information systems • modification to RO • adding new component • adding new atomic construct • ……

  15. Frozen spot Reference Ontology (RO), Reference Ontology Component (ROC), Reference Ontology Atomic Construct (ROAC) Hot spot Local Ontology (LO), Local Ontology Component (LOC), Local Ontology Atomic Construct (LOAC) Reference Ontology & Local Ontology (2/3)

  16. For RO and its components, growing means adding new ROAC for RO versioning renaming for knowledge updating …… For LO and its components, growing means reusing constructs from some ROs adding new LOAC or LOC for specific demands …… Reference Ontology & Local Ontology (3/3)

  17. Metaclasses: Ontology is the super class of RO and LO. Ontology Component is the super class of ROC and LOC. Ontology Atomic Construct is the super class of ROAC and LOAC. Relations: Ontology consists of Ontology Component. Ontology Component consists of Ontology Atomic Construct. Other definitions in MMFI4Onto In MMFI4Onto specification, these three metaclasses are abstract classes. They can be regarded as the frozen spots without growing.

  18. OntologyLanguage 1 modelType 0..* Ontology Ontology Component OntologyAtomicConstruct 0..* 0..* 0..* 0..* sameAs sameAs ReferenceOntology ReferenceOntologyComponent ReferenceOntologyAtomicConstruct 0..1 0..1 sameAs sameAs 0..* 0..* Frozen spots without growing Hot spots Frozen spots with growing LocalOntology LocalOntologyComponent LocalOntologyAtomicConstruct Kernel Model of MMFI4Onto Frozen spot Hot spot

  19. Background Introduction of MMFI4Onto NWI Ⅰ: Registration of Process Ontology NWI Ⅱ: Coordination with other standards Future work Outline

  20. Web service one of the important resources characterized with dynamic features and processes. Current version of MMFI4Onto concentrates on the registration of static ontology, rather than process ontology and/or service ontology. Extending MMFI4Onto • Register process ontologies. • Govern the construction of customized services. • Reduce the cost of service development. Why registration for Process Ontology

  21. OWL-S (Services) SWRL (Rules) OWL([DLP], Light, DL, Full) RDFS (RDF Schema) RDF (Resource Description Framework) XML (Extensible Markup Language) Brief introduction of OWL-s (1/2)-- Layered approach to language development • OWL-s (W3C) • is an extended ontology language • a specific OWL profile for Web Service SWRL: Semantic Web Rule Language (W3C)

  22. OWL-s is used as a language for describing services, reflecting the fact that it provides a standard vocabulary that can be used together with the other aspects of the OWL description languages to create service description. OWL-s is meant to support categories of service. Brief introduction of OWL-s (2/2) (from W3C, OWL Web Ontology Language for Services (OWL-s) Specification)

  23. Upper Ontology of Service Ontology Ontology images compliments of Terry Payne, University of Southampton

  24. Selected classes and properties of the Service Profile IOPE

  25. Top level of the Process Ontology

  26. Ontology Process Ontology Ontology Component CompositeProcess ControlConstruct AtomicProcess Sequence Output Precondition Choice Split Input Postcondition Ontology Atomic Construct If-Then-Else Split+Join Repeat-While …… Any-Order Repeat-Until Iterate ProcessOnto Model in MMFI4Onto

  27. Reference Process Ontology (RPO) is fixed web services with wide acceptance and relevant applications Local Process Ontology (LPO) is for particular application domains generated by reusing sub-processes (atomic process and/or smaller composite process) from RPOs adding some new sub-processes RPO/LPO in ProcessOnto Model (1/2)

  28. Similarly, interoperation between LPOs is based on the common foundation provided by RPO. Interoperation between Process Ontology includes reuse matching automatic discovery automatic composition …… RPO/LPO in ProcessOnto Model (2/2)

  29. An example: service registration and interoperation based on ProcessOnto Model--BravoAir example from W3C, http://www.daml.org/services/owl-s/1.0/examples.html

  30. Registration Info of BravoAir reservation service …… - <process:CompositeProcess rdf:ID="BravoAir_Process"> <rdfs:label>This is the top level process for BravoAir</rdfs:label> - <process:composedOf> - <process:Sequence> - <process:components rdf:parseType="Collection"> <process:AtomicProcess rdf:about="#GetDesiredFlightDetails" /> <process:AtomicProcess rdf:about="#SelectAvailableFlight" /> <process:CompositeProcess rdf:about="#BookFlight" /> </process:components> </process:Sequence> </process:composedOf> </process:CompositeProcess> …… - <process:CompositeProcess rdf:ID="BookFlight"> - <process:composedOf> - <process:Sequence> - <process:components rdf:parseType="Collection">   <process:AtomicProcess rdf:about="#Login" />   <process:AtomicProcess rdf:about="#ConfirmReservation" />   </process:components>   </process:Sequence>   </process:composedOf>   </process:CompositeProcess> …… - <process:AtomicProcess rdf:ID="ConfirmReservation"> <process:hasInput rdf:resource="#ReservationID_In" /> <process:hasInput rdf:resource="#Confirm_In" /> <process:hasOutput rdf:resource="#PreferredFlightItinerary_Out" /> <process:hasOutput rdf:resource="#AcctName_Out" /> <process:hasOutput rdf:resource="#ReservationID_Out" /> <process:hasEffect rdf:resource="#HaveSeat" /> </process:AtomicProcess> - <process:Input rdf:ID="ReservationID_In"> <process:parameterType rdf:resource="&website#ReservationNumber" /> </process:Input> - <process:Input rdf:ID="Confirm_In"> <process:parameterType rdf:resource="&website#Confirmation" /> </process:Input> - <process:UnConditionalOutput rdf:ID="PreferredFlightItinerary_Out"> <process:parameterType rdf:resource="&website#FlightItinerary" /> </process:UnConditionalOutput> - <process:UnConditionalOutput rdf:ID="AcctName_Out"> <process:parameterType rdf:resource="&website#AcctName" /> </process:UnConditionalOutput> - <process:UnConditionalOutput rdf:ID="ReservationID_Out"> <process:parameterType rdf:resource="&website#ReservationNumber" /> </process:UnConditionalOutput> - <process:UnConditionalEffect rdf:ID="HaveSeat"> <process:ceEffect rdf:resource="&website#HaveFlightSeat" /> </process:UnConditionalEffect> …… • Ontology • BravoAirProcess • Ontology Component • AtomicProcess:GetDesiredFlightDetails • CompositeProcess:BookFlight • …… • Ontology Atomic Construct • hasInput:ReservationID_In • hasOutput:ReservationID_Out • Sequence • ……

  31. Service interoperation based on ProcessOnto Model Service Registration based on MMFI4Ontology Registration Reference Process Onto for e-business Online Service The same Atomic process …… AtomicProcess=#Login AtomicProcess =#ConfirmTypeOfCard …… …… AtomicProcess=#Login AtomicProcess =#ConfirmReservation …… Local Process Onto A Local Process Onto B Flight Reservation Service Bank Service

  32. Background Introduction of MMFI4Onto NWI Ⅰ: Registration of Process Ontology NWI Ⅱ: Harmonization with other standards Future work Outline

  33. MMF For Interoperability Role of MMFI

  34. Issue Ⅰ: Coordination with other standards

  35. MMFI MOF MMFI4Onto M3 Metamodel M2 MetaModel Metamodel Pattern : Model Model Stereotype : Modeling M1 Model Model Facility Template: Model Modeling Constructs M0 Universe of Discourse Abstraction Layer where MMFI Resides in

  36. MMFI specify the basic concepts and relations to register information models correspond to specific registry mechanisms MMFI4Onto supplement the capability of existing standards promote interoperation between them enable collaboration and harmonization How to coordinate?

  37. Issue Ⅱ: Implement MMFI4Onto for specific application

  38. Purpose Software Component (SC) Registry and Repository (R&R) based on ebXML describe complex attributes of SC with ontology register and query SC Implement MMFI4Onto register attribute ontology for knowledge sharing classify and register SC based on registered ontology Implement MMFI4Onto with OASIS/ebXML

  39. ebXML Registry Information Model (RIM) Overview of OASIS/ebXML RIM

  40. ClassificationNode instances are RegistryObject instances that are used to define tree structures under a ClassificationScheme, where each node in the tree is a ClassificationNode and the root is the ClassificationScheme. ClassificationNode ClassificationNode ClassificationScheme ClassificationScheme ClassificationNode ClassificationNode & Classification Scheme (from OASIS/ebXML Registry Information Model v2.1 )

  41. Basic idea： To establish the inheritance relationship between RIM and MMFI4Onto Solution： Ontology inherits ClassificationScheme Ontology Component inherits ClassificationScheme a part of ontology with certain structure Ontology Atomic Construct inherits ClassificationNode unit Implementation of MMFI4Onto (1/3)

  42. Registry Information Model from ebXML RegistryObject Classification ClassificationNode RegistryEntry Association ExtrinsicObject ClassificationScheme ClassificationScheme Ontology Atomic Construct Ontology Component Ontology Kernel Model from MMFI4Onto Implementation of MMFI4Onto (2/3)-- Extend RIM for MMFI4Onto Registry

  43. Evaluation supplement semantics support registration of complex resources no change to the original structure in RIM recognize registered instances by both MMFI4Onto and RIM realize interoperation between them Implementation of MMFI4Onto (3/3)

  44. Background Introduction of MMFI4Onto NWI Ⅰ: Registration of Process Ontology NWI Ⅱ: Harmonization with other standards Future work Outline

  45. MMFI4Onto Kernel Model, Evolution Information Model and Evolution Rule Model consistency preservation (algorithm, implementation, etc.) ProcessOnto Model detailed registration for Semantic Web Service algorithms for service matching, composition and decomposition, etc. Future work (1/2)

  46. Applications based on MMFI4Onto corresponding workbench Collaboration with the other standards UDDI …… Future work (2/2)

  47. Any Question?Thank You!wangchong_whu@yahoo.com.cnhekeqing@public.wh.hb.cnheyangfan927@hotmail.comwangjian_sd@163.com

More Related