1. SEMTECH - Semantic Technology & Business Conference November 30 th 2011 Cory Casanave

2. CEO, Model Driven Solutions Actionable Architectures & Agile Solutions Information Federation, SOA, EA and MDA Development Open Source Supporting a Model Driven Approach (ModelDriven.org) Object Management Group Board of Directors Standards work: UML, SoaML, BPMN, EDOC, AESIG, SIMF, Etc. GovDTF: Chair – Open Government Workgroup W3C Government Linked Data (GLD) Workgroup Government NIEM: Co-chair NIEM-UML PIM Submission Team CIO Council/DAS: Open Government Vocabularies Workgroup Introduction

3. Problem statement Federation (information sharing, interoperability, shared services, etc.) is the problem of this decade – it is costing productivity, lives and billions trillions of dollars annually. It is the pre-requisite to solving many problems in the large. It is a problem faced by most CIOs in government and industry. We are calling this the “data problem” A problem not solved… None of the standards we have directly target this problem. Not: UML, OWL, LoD, E/R, SOA, DoDAF, XML Schema, Common Logic or SBVR, etc. With all these solutions – we still have a pervasive problem! While not ideal, the standards above can and are used for federation, but, they are all built for other purposes and repurposed to solve the data problem. Experts can pull these technologies together to solve a specific problem, we want to make it easy to do so with an integrated and standardized approach supporting mainstream solutions and internet-scale federation. We can make a substantial dent in the data problem with new standards derived from current technologies and practices. This is the “SIMF” Initiative. Proposition

4. Stakeholders View of Federated Information Application Data Open Data Commercial Data Enterprise Data Partner Data Stakeholders & Systems Using Federated Data Federated Information SIMF Federation Semantic Links

5. Combining multiple independently conceived data sources and using them together for analytics and other purposes. Example: A sales department may want to combine public, internal and external information about prospect companies as part of their CRM system Key term: Independently conceived Different data sources may use different structures, technologies, vocabularies, identifiers or theories when expressing information about the same things. Sharing information between potentially independent organizations (and their independently conceived systems). Example: U.S. Government Information Sharing Environment (ise.gov) initiative to combat terrorism and other threats to the U.S. What is Information Federation?

6. Enabling collaborative processes that may cross organizational boundaries. Example: An agency wants to outsource human resources but needs to understand how the processes, services and information of their internal department can be satisfied by an external provider. Information federation is essential. Service Oriented Architecture Mediation and Brokering Example: U.S. States provide services to access healthcare information but each State’s service is different. The federal government as well as other states need to interact. Some level of mediation is required across these independently conceived services. Information exchange and federation is the essence of SOA. What is Information Federation?

7. Agility Componentized development Agile iteration Repurpose data & other assets Reuse Stakeholder centric design Cost Reduction Reduced time/cost to integrate systems Reduced time/cost to build and maintain systems Reduced time/cost to find and use data Life and death Combatting terrorism Joint forces acting safely and effectively on the same battlefield Situational awareness Intelligence Efficiency: Better decision making through analytics Shared Resources Shared Processes Shared Services Shared Information Importance of Information Federation This is a multi-billion (trillion?) dollar problem that has not received the dedicated attention it deserves!

8. Point-point structural transformation of data {Lets hack a solution point} Representations : XSD, XSLT, Copybooks, Code {Which are not accessible to most stakeholders} Standardized or centralized data structures or APIs {One size fits all} Representations: XSD, SQL-DD, UML, “Master Data Management” Service/API Definitions: WSDL, Corba, SoaML Canonical data model with proprietary/structural mapping {Convert to MY WAY} Representations: E/R, UML Classes, RDFS, Code/Proprietary, Data Warehouse Web data with point-point links {Publish now, federate later} Representations: RDFS+ (SEMWEB/LOD) Conceptual or logical models (sometimes) with logical links {Abstraction} Representations: Ontologies, Rules, UML (With Extensions), SBVR Federation - State of the art

9. The conceptual pivoting approach A common and growing approach to the data problem leverages abstraction: Defining a domain focused vocabulary with integrity rules and assertions as part of a conceptual model that captures domain semantics. Federation and integration is achieved by relating various logical and physical information structures to the conceptual model Information federation and integration is achieved via a “pivot” through this conceptual semantic layer This approach is used, in part, in existing standards such as CCTS (Core Components), ISO 20022 and is currently being utilized in OMG for finance. In the majority of cases the “tool” used to represent these common semantics and links is a spreadsheet, but UML and OWL are also used. Pivoting through a conceptual model

10. Cory Casanave 240 Excel UML XML There is an actual “Person”, Cory Casanave There is a concept of this person shared in this room, right now Here is one representation of him “Person” is a shared concept, independent of data structures There may also be shared agreement that Cory is a person and some other “facts” “Cory Casanave” is a name for this person He weighs 240 LBS There are multiple data representations about Cory Casanave which may or may not agree Those representations can be grounded in concepts (semantics), assisting federation Example of “Pivoting” through a conceptual model Concept of “Cory Casanave” Concept of a “Person”. Representations

11. We understand that all these representations and data structures are not “the thing” in the world But sometimes we loose site of this A conceptual domain model is a model of the things, not the data. You may also call this an ontology. A logical information model is a logical model of the data. So what is a data or information model? A model, for a specific purpose, of data about something else, that something else and that purpose are unstated. This is the root of the problem. Things Vs. Representations of Things “This is not a pipe” René Magritte Cory’s Pipe 0.02 This isn’t either

12. It must be easy to use and understand – suited to mainstream adoption! Does not require “deep” semantics, it does require well defined concepts No assumption of the same name or “matching” representations There can be any number of shared concept “theories”, no single “ring to bind them all” SIMF will be federated with other languages, so existing models in existing languages can also be federated How automated can it be? Some pivoting will be manual – but the manually asserted information saved Some will be assisted with “human in the loop” Some will be fully automatic There may be some tool variation in the automation, but not the representation Other semantic technologies will be needed to “project” the data based on the models and provide the federated information capability, completing a semantic mediation platform. There is no 100% solution – and that is not what we need. Even a minor improvement in federation capabilities could make an impact at the level of the gross national product*. More on Pivoting * Joe Bugajski, Visa International

13. Conceptual modeling with relations to structural models is not new It is done with a variety of representations UML, OWL, RDFS, E/R, Spreadsheets, FOL Ontologies, SBVR With a variety of linking and transformation mechanisms Code, XSLT, FOL, OWL, Rules, QVT, Proprietary What seems to work now – working with what we have Conceptual UML models with extensions for linking, transformed to RDF-LOD RDFS models with rules and a bit of OWL Structured English (i.e. SBVR) representations of conceptual models A bit of structural mapping, some proprietary solutions None of these approaches seem ideal for the task and all require substantial expertise, more than is practical for mainstream adoption. But, they can inform SIMF “built for purpose” standards and tools. Semantic Federation Today

14. A Draft RFP in OMG focused on Federation through Conceptual Modeling

15. SIMF Architecture Conceptual Domain Models Logical Information Models Physical Data Schema Kernel Subject focused conceptual models define the concepts, predicates, integrity rules and terms of a domain that can be related to each other SIMF Scope Solution focused logical information elements represent information structures and integrity rules that can use and extend other information Technology focused physical data schema are grounded in logical data models which define their context and semantics Model Bridging Relations

16. SIMF Language Definition SIMF Conceptual Model SIMF Notation Graphical + Textual SIMF Metamodel OMG MOF/SMOF OMG Diagram Definition Semantic Bridge Semantic Bridge Kernel Ontology Formal Logic Conceptual Domain Concepts Model Bridging Concepts Logical Information Concepts SIMF Kernel LIM CDM Defined Using Defined Using Defined Using Defined Using For Defined Using Grounds Represented In RDF Optional XML Defines

17. OWL Metamodel SIMF Language Federation SIMF Conceptual Model Semantic Bridge Semantic Bridge Conceptual Domain Concepts Model Bridging Concepts Logical Information Concepts XSD Metamodel SQL DDL Metamodel Semantic Bridge Semantic Bridge Semantic Bridge Semantic Bridge UML Metamodel Semantic Bridge Semantic Bridge E/R Metamodel Semantic Bridge Semantic Bridge SIMF Metamodel Semantic Bridge Semantic Bridge Abstraction of information modeling concepts found in more than one reference language

18. Conceptual Model of SIMF expressed in SIMF notation Conceptual Domain Model Logical Information Model Model Bridging Relations Grounding in formal logic (Common Logic Default) Textual and graphical notations Bridging to common information modeling languages ER, SQL DDL, XSD, UML, SBVR, OWL, RDFS Metamodel and exchange format for OMG-MOF and (Optionally) RDF Summary of SIMF Requirements

19. As a federation capability, “overlap” with other views of information, semantics and conceptual models is required and intended. So if your saying : We can do that with {OWL, Rules, UML, XSLT, CL, My Product…} we want to listen. It is expected that other standards will be proposed by submitters to fulfill requirements as part of the SIMF specification Since there are multiple choices for what to reuse and how these existing standards should be integrated into the SIMF solution, the choice of standards to leverage for the SIMF domain specific language is the purview of the submitter and not prescribed by the RFP. It is intended that SIMF build on existing languages! How does SIMF relate to…

20. MDA Federation Framework SIMF will describe the conceptual and logical model with mapping relations between them There are many options for how this is “implemented” into a federation solution Code or structural transformation could be generated (at design time or runtime) to fit into existing integration frameworks using various technologies Or, the model could be executed directly at runtime, perhaps using an inference engine This separation of concerns is the essence of “Model Driven Architecture” (MDA) SIMF and Model Driven Architecture Models Conceptual Domain Model(s) Logical Information Model(s) Model Execution Engine Code Generation Engine ESB or other Platform Model Bridging Model(s) Unfederated Data Federated Information

21. Linked data provides a platform for data to be ubiquitously available and linked The linking and semantics of the links is not well defined OWL has largely not proved successful for wide-scale federation of independently conceived data – it is fragile, lacks expressability and is not stakeholder friendly Linked Data (RDF) could become the delivery platform for data described using SIMF OWL and RuleML Semantics can contribute to SIMF semantics, perhaps also be used as part of an implementation XSD Data structures will be federated with the SIMF conceptual model RDF representation of SIMF models provide for a SEMWEB definition Perhaps this could become the design language for Semantically Linked Data (SDL)? SIMF and Linked Data

22. SoaML – Existing Standard for Services Services are also a part of the federation landscape, there are some existing solutions. SoaML is s OMG Standard for Modeling Service Oriented Architectures Adopted from the UML ® Profile for Modeling Services (UPMS) RFP SoaML supports the “A” in SOA Used for modeling SOA at the business, enterprise and technology levels Leverages Model Driven Architecture A “Profile” of the Unified Modeling Language™ Can be used with off-the-shelf UML tools as well as customized tooling Tool support & implementations already exist Tool support – making it easy to create services models MDA Implementations – provisioning web services, business artifacts and implementations from SoaML models Includes Service context, collaboration and composite services Services as conversations – not just request/reply SIMF can provide the data federation capability SoaML lacks

23. We don’t have to wait for new standards! “Just do it” approach to semantic federation There are existing tools and techniques we can use today, but they do require experts UML/MDA Focused Semantic Web Focused Experience with the approach, even without new tools and standards, can provide near-term benefits and build competence and models “Just do it” approach to SIMF tools and standards A group is forming to better define the approach and start on solutions (some part of which will be open source) May become a submitter group for the OMG effort Contact us to get involved Just Do It Model Driven Solutions can help you with either or integrating both!

24. In-Progress Standards Work: NIEM-UML Provide a UML representation of the National Information Exchange Model – a U.S. national controlled vocabulary approach Support the community Expand the community Reduce complexity and barriers to entry Leverage standards and standard based tooling Partner with industry Make NIEM accessible to business stakeholders Support the full life-cycle of information sharing Support multiple technology solutions Make it quick and inexpensive to share information and consume shared information Fit in with other initiatives and standards

25. NIEM-UML Profiles and Transforms NIEM-UML Vocabularies NIEM Vocabulary PIM Profile NIEM MPD PIM Profile Vocabulary Model For One or More Exchanges Platform Independent Model of a Specific MPD NIEM Core Vocabulary NIEM Domain Vocabularies Platform Specific Model of a Specific MPD A NIEM MPD NIEM PSM Profile Existing NIEM NDR and MPD Platform Specifications Extends & References Uses Includes Maps Between Transforms Between XML Primitive Types Uses Conforms to User’s UML NIEM Models Generated Based on NIEM-UML Model Libraries Transform Specification Mapping Specification Conforms to

26. NIEM-UML Profiles and Transforms NIEM-UML Vocabularies NIEM Vocabulary PIM Profile NIEM MPD PIM Profile Vocabulary Model For One or More Exchanges Platform Independent Model of a Specific MPD NIEM Core Vocabulary NIEM Domain Vocabularies Extends & References Uses Includes XML Primitive Types User’s UML NIEM Models NIEM-UML Model Libraries Platform Specific Model a NIEM Model in RDF A NIEM RDF Schema RDF Metamodel (ODM) RDF/S Maps Between Uses Conforms to Transform Specification Mapping Specification Conforms to Transforms Between Generated Based on NIEM-UML

27. Potential Advantages of NIEM-RDF Support for linking in NIEM Support for more open exchange specifications, less fragile than XSD RDF Schema partition in a NIEM-MPD Automatic conversion between NIEM-RDF and NIEM-XML Extensive NIEM vocabularies become useful for other LOD purposes I.E. Use NIEM reference vocabularies for LOD federation Ability to do SPARQL queries across NIEM data Connection between data.gov and NIEM

28. Still being worked on and socialized in OMG Expected to be issued next OMG meeting Could also become a W3C initiative Find more about SIMF here: http://tinyurl.com/SIMFrfp Email list and wiki are open (OMG membership not required) – get involved! Contact SIMF RFP Status