Leveraging SET, OWL, CAM and Dictionary based tools to enabled automated cross-dictionary domain translations David Webber OASIS SET TC / CAM TC (with excerpts from iSURF presentation by Prof. Dr. Asuman Dogac, METU-SRDC, Turkey) OASIS SET TC Automating Intra-domain Mappings
29
Embed
David Webber OASIS SET TC / CAM TC (with excerpts from iSURF presentation by
OASIS SET TC Automating Intra-domain Mappings. Leveraging SET, OWL, CAM and Dictionary based tools to enabled automated cross-dictionary domain translations. David Webber OASIS SET TC / CAM TC (with excerpts from iSURF presentation by Prof. Dr. Asuman Dogac, METU-SRDC, Turkey ). Agenda. - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Leveraging SET, OWL, CAM and Dictionary based tools to enabled automated cross-dictionary domain translations
David WebberOASIS SET TC / CAM TC(with excerpts from iSURF presentation by Prof. Dr. Asuman Dogac, METU-SRDC, Turkey)
OASIS SET TC Automating Intra-domain Mappings
Agenda
Part I: Introduction – Intra-domain example use cases Challenges and Opportunities
Part II: Roadmap – CAM templates, OWL, XPath, Dictionaries, CCTS Using Dictionary based approach and SET Tools
for aligning structure components across syntax vocabularies within a domain
Part III: Summary – Next Steps
Part I: Intra-domain Example Use Cases
Information Exchange Interoperability Many common domains are using multiple
vocabularies that have arisen historically over time – e.g. banking, healthcare, supply chain1.
These may be weakly or strongly aligned depending on the domain and fragmentation / marketplaces within it
All domains share common components such as organisation, person, customer, vehicle, address.
Dictionary alignment task challenges Each domain can be inspected by comparing
the vocabulary dictionaries Creating dictionaries in a common reference
format has previously been complex and manual intensive process
Even within a domain implementation the vocabulary maybe fragmented and inconsistent because information models evolve over time
Opportunities and Potential
Creating a domain agnostic set of methods and tools that allow alignment within any domain to facilitate consistent information definitions
Leverage the approach to also support semi or fully automated mapping patterns and templates
Use open standards and open source tools Provide open public roadmap for tool vendors Allow standards groups to publish their exchanges in
an open non-proprietary syntax and rule system Enable SMBs to build once, exchange to many
Part II: Roadmap – CAM templates, OWL, XPath Dictionaries and CCTS
CAM templates, OWL and dictionaries Information components derive their meaning and
semantics from the context of their use pattern, not the physical name label, e.g. Customer/Account/Number Order/Item/Number
CAM templates and OWL terms share ability to express use patterns that can be inspected and equivalence deduced using software agents that traverse the exchange structure components
Matching is based on rules that can be tailored and reference to dictionaries of known properties
Allows automated generation of domain dictionaries
Dictionaries, UIDs, and CAM templates Within a dictionary each unique context of an item
can be assigned a UID label value These UID label values can then be inserted as
references into a CAM template Each UID couplet across exchange formats within a
domain can be marked as equivalent (aliases) or similar (rules associated)
For similar items, CAM supports transform rules1
The UID couplets allow automated mapping across CAM template definitions
1 - Using standard XPath syntax
Explicate semantics related with the different usages of document data types Different document standards use Data Types
differently For example, “Code.Type" in one standard is
represented by “Text.Type" in another standard and yet with “Identifier.Type" in another standard
This knowledge in real world is expressed through class equivalences so that not only the humans but also the reasoner knows about it Code.Type ≡ Text.Type Name.Type ≡ Text.Type Identifier.Type ≡ Text.Type Can cross-reference via UID as well as type
Dictionary Alignment Step Human / OWL inspectors Dictionary alignment report produces known
equivalents listing (confidence 100%), and then lesser equivalence rankings based on matching factors
Component compound relationships resolved using CAM template structure layouts
Human inspection then reviews and resolves and updates dictionary (using Excel spreadsheet workbook format)
New dictionary produced Iterative refinement over time can enhance alignment
along with common practices through industry agreements
From Dictionary to Runtime Mapping Once dictionary is available with UID
couplets for domain crosswalks – proceed to align Take templates of actual exchanges – and label
these with UID couplets Lookup UID couplets in dictionary and update
target template with UID from couplet Take completed templates – use to drive actual
Dictionary approach summary1. If the document components of two different domain standards
share the same semantic properties: Use this as an indication that they may be similar
2. Some explicitly defined semantic properties may imply further implicit semantic relationships:
Use a reasoner to obtain implicit relationships Align to dictionary definitions allowing crosswalk Create harmonized dictionary lookup Use abstract UID as common reference (linkage between
language specific named types/objects)3. Explicate semantics related with the different usages of document
data types in different document schemas to obtain some desired interpretations by means of such informal semantics
Determine similar/match relationships and rules for constraint alignment and compound component relationships (e.g. date-time vice date and time)
4. Provide dictionary structure format for managing relationships
Leverage existing OASIS CAM and ebXML Registry TC work
Part III: Summary – Next Steps
Value Proposition Mapping templates provide localization mechanism
to tailor input and outputs to patterns and scenarios
Domain mapping automation reduces burden on
participants to maintain multiple mappings
Removes issues surrounding versioning and
exchange transaction structure differences
Simplifies testing and setup
Allows alignment over time to coherent domain
reference dictionaries; mitigates collisions
Lowers costs of entry and participation
Tools needed
CAM Schema ingesting Dictionary builder
OWL Reasoner CAM dictionary to OWL generator Extend CAM dictionary format for couplets / rules Extend reasoner to update dictionary couplets
Mapping XSLT engine to read input, templates and create output
The above equivalences are labelled as couplets through the UID dictionary cross-references and can be stored back into CAM templates <Extensions> section for runtime crosswalk use.
Runtime crosswalks between template structure member items