Template Wizard runtime configuration Library Object templates/Components design time Facets Questions / Data Technology Targeting Syntax specific production rules Partner / Component Interface Agreement builder + review / support / completion workflow 1 3 4 XML 2 Conceptual Factors Stored XML XML XML XML Solution Specific Syntax 5
Context is the pervasive driver to effective engineering
Drives dynamic process configuring and control
Ensures accurate information capture, packaging and delivery
Key to correct relationships between partners in a collaboration
Understanding about Context Lack of context control mechanisms is the most prominent reason why legacy business systems are difficult and complex to extend and support Date: circa 1568 1 : the parts of a discourse that surround a word or passage and can throw light on its meaning 2 : the interrelated conditions in which something exists or occurs
Interoperability absolutely requires the software to understand and apply context from the ground up in a consistent way that links to the external world functional needs – and that is not hard-coded into rigid software methods – but exposed across the information space
Role and context
Role is a convenient way to group together context and manage that for classes of functional users
Use based solutions
This determines how and what results are expected given role and context that allows users to perform their business use cases effectively without information issues.
Today’s SOA / Mashup’s have extended service model needs
Can I create a standard simple open format to describe my message structures and data content rules?
Can my partners validate their transactions in test BEFORE they send them?
How do people know what I will send them?
I want something that’s simple and standards based – leverages existing XML components
Can I generate HTML documentation that is readable by business analysts?
Defining Information Services Create Samples Rules Editor XML Analyst Templates Samples Develop Verify Structure Rules Context Vocabulary 3 2 Rules html XML Results html Publish 1 Detail Use Rules Test Rules on Samples 4 Share Results Enabling Agile Information Exchanges Structure + Vocabulary Rules + Context Templates Verify Template Outcomes
Configure the Business Exchange Content Assembly Template XML instance structure(s) Business context rules + Content Reference rules + Data Validation rules + External Mapping rules Logical business transaction can have more than one structure layout can relate rules directly with structure makeOptional () excludeTree() item type="noun" name="Agency/@AgencyID" UIDReference="ukt000910" <conditional expression="'//SupplierID' and lookup(value,'SGIRWSDL:supplierID_check')" <MapRule output="type" input="Sales/Company/Year/Qtr/Product@type"/> Simple Declarative Statements BPM Step transaction template OASIS Content Assembly Mechanism (CAM)
Opening up business integration rules so that partners can confirm their usage + validating
HTML reporting of rules and layouts
Processing content with open public specification and sharable rules base
OASIS Content Assembly Mechanism Specification: http://wiki.oasis-open.org/cam http://www.jcam.org.uk Organization for Advancement of Structured Information Standards
SOA, BPM and Data Services Transport Security Delivery Process 3 2 5 1 Data Services 4 C A M Internet Infrastructure Query / Response WSDL SOAP / http / https Vocabulary / Semantics Packaging / Encoding XML / edi Validation / Assembly Mapping / Transform XSD, CAM, Schematron Business Model Service Agreement Context / Roles Business Processes Description Msg Exchange Profile State & Context Addressing / Envelope Transactions Coordination Push / Pull
To effectively exchange information, there must be a common semantic understanding of data among participants, and the data must be formatted in a consistent manner that matches the business process context
Solve the business functional needs as the priority - ability for systems to accommodate each others functional requirements in a holistic and agile way so that users can maximize the business value obtained today and adapt that to tomorrows changing needs rapidly and easily
Predictability – when the mechanisms being used are using known, consistent and extensible methodology
Need to support semantically rich information (human), contextual mechanisms, and not just rigid lists of enforced content (machine)
Reduce collaboration and adoption costs by making exchanges quick and easy to build and self-adaptive – cost is barrier to interoperability
Ability to support routing and intermediary services with views of exchange content based on role and use context
How do you get there?
Example: NIEM XSD Reference Architecture Exchange xml *Exchange xsd *Extension xsd Namespace * Optional NIEM xsd subset *Constraint xsd IEPDs have their own target namespaces Constraint Validation Conformance Validation NIEM = National Information Exchange Model (www.niem.gov) for DOJ/DHS *Code list xsd XML Schema