Скачать презентацию e Gov TC Washington DC July 2004 Naming Скачать презентацию e Gov TC Washington DC July 2004 Naming

e24e0df9da538fceb385e3a8d404125f.ppt

  • Количество слайдов: 30

e. Gov TC, Washington DC, July 2004. Naming Conventions and OASIS CAM Resources: http: e. Gov TC, Washington DC, July 2004. Naming Conventions and OASIS CAM Resources: http: //www. oasisopen. org/committees/cam http: //www. jcam. org. uk Copyright OASIS, 2004 David RR Webber Chair OASIS CAM TC http: //drrw. net [email protected] net

Two world views – programmer v modeller • Programmer wants efficient structures – <bz. Two world views – programmer v modeller • Programmer wants efficient structures – • Production manager wants efficient throughput and low transaction exchange costs • Modeller wants semantic relevant names • Business analyst wants domain relevant names Copyright OASIS, 2004

e. Business XML parsing - mission profile • Working with vocabularies and naming systems e. Business XML parsing - mission profile • Working with vocabularies and naming systems • Opening up business integration rules • Handling local context drivers • Validating content with semantics • How does W 3 C XSD schema help? • What does OASIS CAM provide? • How do you create efficient payload Copyright OASIS, 2004

Topics • Naming Convention Systems – Understanding Elements / Attributes / Data types / Topics • Naming Convention Systems – Understanding Elements / Attributes / Data types / Namespaces – Using Vocabularies / Legacy Semantics – Deployment / Business Context Mechanism – Alignment of Industry Vocabularies • Summary Copyright OASIS, 2004

Naming Convention Systems • Content Assembly Techniques Copyright OASIS, 2004 Naming Convention Systems • Content Assembly Techniques Copyright OASIS, 2004

Conceptual: Data Elements build Transactions Name Address email Phone # Company Name Address email Conceptual: Data Elements build Transactions Name Address email Phone # Company Name Address email Phone # Cost Company Party ID Party Line Item PO # Invoice CONTEXT Copyright OASIS, 2004

Example #1 - Core Components Context Providing supply chain messaging using CC Domain: Matl Example #1 - Core Components Context Providing supply chain messaging using CC Domain: Matl Mgmt Industry: Auto Create Long Term Contract • Ship Notice Prod. Id Regulatory: Safety Change Lvl Forecast Component Requirements Part Number Send Planning Document Customer Container Supplier Place Order Ship Materials Serialized ID Ship’d Qty Arrange Payment Copyright OASIS, 2004

Example #2 - Context Affects “Person” depending on “Role”. CORE COMPONENT (PERSON) Police Officer Example #2 - Context Affects “Person” depending on “Role”. CORE COMPONENT (PERSON) Police Officer knows he is a WITNESS L'officier de police sait qu'il est un TÉMOIN Police Investigator thinks He is a SUSPECT L'investigateur de police pense qu'il est un SUSPECT Judge calls him a DEFENDANT Le juge l'appelle un DÉFENDEUR Corrections call him a INMATE / CRIMINAL Les corrections l'appellent un DÉTENU/CRIMINEL NPB calls him a PAROLEE NPB l'appelle un LIBÉRÉ SUR PAROLE ENGLISH FRENCH Copyright OASIS, 2004

How do you put this all together? Where / Who Action How Information What How do you put this all together? Where / Who Action How Information What Event When Rule Why Event When Action How Information What Event When Rule Why Copyright OASIS, 2004

Combination of Components Naming conventions Logical Components Definitions Registry Definitions CAM template Content References Combination of Components Naming conventions Logical Components Definitions Registry Definitions CAM template Content References Linkage Layer XSD Structure components XML instances Instances Local usage terms Copyright OASIS, 2004

Separation of tagging from logical use • XSD defines structure and tag names • Separation of tagging from logical use • XSD defines structure and tag names • Registry holds semantic definitions of nouns in vocabulary • CAM template provides linkage between vocabulary and XML instance • Context allows specialization and localization to be applied Copyright OASIS, 2004

Capturing Noun Semantics Can use Designer Tools to automatically generate from XSD model • Capturing Noun Semantics Can use Designer Tools to automatically generate from XSD model • Draft layout for storing noun details in registry See: OASIS Registry Semantic Content Management sub-committee work (SCM SC) Copyright OASIS, 2004

Reference Nouns from CAM template • Using the UID reference, and Registry alias mechanisms Reference Nouns from CAM template • Using the UID reference, and Registry alias mechanisms – associate content in the schema layout with noun semantic reference Define Registry Alias Associate structure item Noun semantics referencing Copyright OASIS, 2004

Example : Person Scenario Details in Real World Context Key: UID: RCMP 023079: 00 Example : Person Scenario Details in Real World Context Key: UID: RCMP 023079: 00 USAGE CONTEXT CORE COMPONENT Geo-Political Context: English or French Legislative Context: Narcotics Legistation Industry Context: NAICS 9221 Process Context: HC 3515 Process Role Context: Police Chief Supporting Role Context: RCMP Investigator Product Context: Case Management Systems Capabilities Context: XML Schema 1. Example: AGE BUSINESS INFORMATION ENTITY 2. Becomes: PERSON. BIRTH. DATE of Suspect Syntax Independent Syntax Bound SYNTAX BIE EXPRESSION English or French Text Document HTML 3. Is expressed in an XML Schema XML schema fragment PDF e. Forms Copyright OASIS, 2004

Elements / Attributes / Data types • While these are at the heart of Elements / Attributes / Data types • While these are at the heart of XML syntax, they are also in many ways an odd-ball trio. • If you ask ten people about these, you will get ten different views, or more! • How do you get to consistency of use and sensible use standards? • How do you apply versioning and reuse? • CAM allows you to treat structure elements and attributes consistently and apply robust data typing and validations to them equally as nouns. Copyright OASIS, 2004

Aligning Terminology and Usage • XML allows for freeform naming of content tags • Aligning Terminology and Usage • XML allows for freeform naming of content tags • CAM provides the means to link those tag names to standard industry terms and definitions within a formal vocabulary • This also means that multi-lingual support is built-in • You can also version those references • Registry SCM team is defining noun semantics Copyright OASIS, 2004

Noun Semantics Summary • CAM uses a simple unique identifier system (UID) tailored to Noun Semantics Summary • CAM uses a simple unique identifier system (UID) tailored to the target domain – such as ISO 11179, UDEF, Rosetta. Net, FIX, legacy EDI and more. • With a neutral logical labelling system you decouple away from dependency on explicit human readable names – and can resolve possible collisions. • Facilitates a system of nouns and constructing a vocabulary that provides consistent semantic use. • Enables libraries of structure parts and OASIS, 2004 Copyright

More thoughts : Names and Namespaces • Is this a solution looking for a More thoughts : Names and Namespaces • Is this a solution looking for a problem? • How much irresolvable collision of names really happens in a given XML instance? • Local and global declarations – Can you just include a piece of XML into another XML structure and it always work? • Can you work smart and build XML that is self-defining and always locally unambiguous? • What we really need is a way of establishing logical identifiers that link consistent semantics – regardless of Copyright OASIS, 2004 the

Namespaces – when to use them? • CAM itself uses namespaces. • The most Namespaces – when to use them? • CAM itself uses namespaces. • The most coherent reason to use them is not to apply prefixes to every piece of content – that is wasteful, confusing and prevents easy content reuse! • CAM uses namespaces to denote a stream of markup within markup. In other words – markup that is there only to direct how the main markup is to be used - e. g. inline predicates and assertion rules. • This use of namespaces is simple and clear. • A namespace prefix may also denote Copyright OASIS, 2004

Elements / Attributes Summary • CAM facilitates the use of simple XML V 1. Elements / Attributes Summary • CAM facilitates the use of simple XML V 1. 0 based structure definitions that provide very stable interoperability and compatibility • The CAM template provides the means to express the semantics around the content in the target XML structure • The cardinality and logic statements in CAM provide the means to assemble together a clear structure instance schema • Removes the need to use namespaces to avoid naming collisions. • The next section looks at the techniques and examples Copyright OASIS, 2004

Aligning Industry Vocabularies Tools that support the development of industry vocabularies for noun semantics Aligning Industry Vocabularies Tools that support the development of industry vocabularies for noun semantics and legacy transaction integration. Copyright OASIS, 2004

Noun Semantics – common foundation • Need consistent way of expressing noun definitions across Noun Semantics – common foundation • Need consistent way of expressing noun definitions across industry domains • Registry SCM provides path to that • Existing industry domain vocabularies can be easily populated into Registry using the noun semantics layout • Once loaded Registry provides powerful set of tools to aid alignment – associations, classification, ontologies, discovery Copyright OASIS, 2004

Registry Roles Information Engine “A semantic registry is the key foundation block upon which Registry Roles Information Engine “A semantic registry is the key foundation block upon which global electronic business exchanges will be built”. Business Analyst Administration Distribution Web Interface Interchange Program Level Semantics Software Developers XML Industry Business Standards Registry Protocol Standards eb. XML, ISO 11179, OASIS, OAGi, Rosetta. Net, UBL, UDEF Information Profiles CAM Copyright OASIS, 2004

Example : Managing Process / Transactions Logical business transaction can have more than one Example : Managing Process / Transactions Logical business transaction can have more than one structure layout BPM Step transaction XML instance structure(s) template Content Assembly Template can add inline rules directly into structure Simple Declarative Statements Business context rules + Content Reference rules + Data Validation rules + External Mapping rules make. Optional() exclude. Tree() item type="noun" name="Agency/@Agency. ID" UIDReference="ukt 000910" Copyright OASIS, 2004

Summary Resources and Planning Copyright OASIS, 2004 Summary Resources and Planning Copyright OASIS, 2004

Summary: The Holy Grail of e. Business • Automatic information integration has been the Summary: The Holy Grail of e. Business • Automatic information integration has been the Holy Grail of e-Business systems since before XML was conceived. • Lesson learned - three needs are paramount: – the ability to design transactions consistently, – the ability to document their usage in a clear way and then – the ability to drive software that can apply rules and test information content to ensure correct compliance. • CAM approach provides three critical abilities: – documentation of business interchange Copyright OASIS, 2004

Next Steps • Work in progress: – Formal Publication of OASIS Specification – Continue Next Steps • Work in progress: – Formal Publication of OASIS Specification – Continue development of j. CAM processor – Library of CAM templates by industry – Integration with OASIS Registry assembly – Building of noun semantic dictionaries Copyright OASIS, 2004

Available Components / Resources • j. CAM component – http: //jcam. org. uk • Available Components / Resources • j. CAM component – http: //jcam. org. uk • Visual. Script editor for CAM templates – http: //www. visualscript. com • JAXE editor with CAM XSD – http: //www. jaxe. org • OASIS CAM TC – http: //www. oasis-open. org Copyright OASIS, 2004

Get involved in OASIS CAM • Download the specs from www. oasisopen. org • Get involved in OASIS CAM • Download the specs from www. oasisopen. org • Open source resources www. jcam. org. uk • Encourage your industry group to adopt CAM templates for their standards • Specify CAM-compliance from providers Copyright OASIS, 2004

OASIS – Content Assembly Mechanism April 2004 Thank You http: //www. oasisopen. org/committees/cam www. OASIS – Content Assembly Mechanism April 2004 Thank You http: //www. oasisopen. org/committees/cam www. oasis-open. org xml. coverpages. org www. xml. org Copyright OASIS, 2004