DOCSLIB.ORG

Universal Business Language: Realizing Ebusiness XML

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Universal Business Language: Realizing Ebusiness XML Universal Business Language: Realizing eBusiness XML Mark Crawford, LMI UBL Vice Chair Why Are We Talking About UBL • UBL fulfills the promise of XML for business by defining a standard cross-industry vocabulary • UBL is the ebXML missing link • UBL plus ebXML enables the next generation of EDI – Cheaper, easier, Internet-ready – Extends benefits of EDI to small businesses – Fits existing legal and trade concepts – Allows re-use of data • UBL can provide the XML payload for a wide variety of other web-based business frameworks Overview 11 Evolution & Success of Business Standards 22 The Role of ebXML Relationship with ebXML 3 3 & Core Components 44 UBL Overview 55 The XML Stuff 66 The Business Standards Stuff 77 Working with Liaisons 88 Summary Goals for Successful eBusiness Services • Web-enable existing fax- and paper-based business practices • Allow businesses to upgrade at their own pace • Preserve the existing investment in EDI • Integrate small and medium-size businesses into existing EDI-based supply chains The standardization of XML business documents is the easiest way to accomplish these goals. Can’t We Just Do It? OpenTag Markup W3C Specifications Documentation Metadata - PICS Document Definition Markup Language (DDML) Text Encoding Initiative (TEI) MIX - Mediation of Information Using XML WEBDAV (IETF 'Extensions for Distributed Authoring and Versioning on the Web') Channel Definition Format, CDF (Based on XML) CDIF XML-Based Transfer Format DAV Searching and Locating (DASL) RDF Rich Site Summary (RSS) Synchronized Multimedia Integration Language (SMIL) Graphic Communications Association - GCA 'Paper' DTD Open Content Syndication (OCS) Precision Graphics Markup Language (PGML) DocBook XML DTD W3C Document Object Model (DOM), Level 1 Specification Vector Markup Language (VML) Tutorial Markup Language (TML) Web Collections using XML WebBroker: Distributed Object Communication on the Web International Development Markup Language (IDML) Meta Content Framework Using XML (MCF) Web Interface Definition Language (WIDL) Call Processing Language (CPL) XML-Data XML/EDI - Electronic Data Interchange Call Policy Markup Language (CPML) Namespaces in XML XML/EDI Repository Working Group VoiceXML Forum (Voice Extensible Markup Language Forum) Resource Description Framework (RDF) European XML/EDI Pilot Project VoxML Markup Language Australia New Zealand Land Information Council (ANZLIC) - Metadata EEMA EDI/EC Work Group - XML/EDI Telephony Markup Language (TML) Alexandria Digital Library Project ANSI ASC X12/XML and DISA SABLE: A Standard for Text-to-Speech Synthesis Markup ATLA Serials Project (ATLAS) Information and Content Exchange (ICE) Java Speech Markup Language (JSML) XML Metadata Interchange Format (XMI)-Object Management Group (OMG) CommerceNet Industry Initiative SpeechML OMG Common Warehouse Metadata Interchange (CWMI) Specification eCo Interoperability Framework Specification TalkML Object Management Group XML/Value RFP BizTalk Framework XML and VRML (Virtual Reality Modeling Language) - X3D MDC Open Information Model (OIM) eCo Framework Project and Working Group XML for Workflow Management [NIST] Educom Instructional Management Systems Project (IMS) Commerce XML (cXML) SWAP - Simple Workflow Access Protocol Metadata Specification RosettaNet XML-Based Process Management Standard: Wf-XML Structured Graph Format (SGF) Open Catalog Protocol (OCP) Theological Markup Language (ThML) Legal XML Working Group and UELP vCard Electronic Business Card LitML: A Liturgical Markup Language XML Court Interface (XCI) iCalendar XML DTD XML-F ('XML for FAX') Georgia State University Electronic Court Filing Project XML Encoded Form Values Extensible Forms Description Language (XFDL) Web Standards Project (WSP) Capability Card: An Attribute Certificate in XML XML Forms Architecture (XFA) HTML Threading - Use of HTML in Email Telecommunications Interchange Markup (TIM, TCIF/IPI) Broadcast Hypertext Markup Language (BHTML) Open Software Description Format (OSD) aecXML Working Group - Architecture, Engineering and Construction IEEE LTSC XML Ad Hoc Group XLF (Extensible Log Format) Initiative Product Data Markup Language (PDML) IEEE Standard DTD Apache XML Project Product Definition Exchange (PDX) Open Settlement Protocol (OSP) - ETSI/TIPHON WAP Wireless Markup Language Specification Electronic Component Information Exchange (ECIX) and Directory Services Markup Language (DSML) HTTP Distribution and Replication Protocol (DRP) Pinnacles Component Information Standard (PCIS) WDDX - Web Distributed Data Exchange Chemical Markup Language ECIX QuickData Specifications Business Rules Markup Language (BRML) Molecular Dynamics [Markup] Language (MoDL) ECIX Component Information Dictionary Standard (CIDS) Common Business Library (CBL) Bioinformatic Sequence Markup Language (BSML) ECIX Timing Diagram Markup Language (TDML) Open Applications Group - OAGIS BIOpolymer Markup Language (BIOML) Encoded Archival Description (EAD) Schema for Object-oriented XML (SOX) Virtual Hyperglossary (VHG) UML eXchange Format (UXF) XMLTP.Org - XML Transfer Protocol Weather Observation Definition Format (OMF) XML Data Binding Specification The XML Bookmark Exchange Language (XBEL) Open Financial Exchange (OFX/OFE) Translation Memory eXchange (TMX) Simple Object Definition Language (SODL) and XMOP Service Interactive Financial Exchange (IFX) P3P Syntax Specification Simple Object Access Protocol (SOAP) FinXML - 'The Digital Language for Capital Markets' Scripting News in XML XML and Music Extensible Financial Reporting Markup Language (XFRML) InterX.org Initiative Clinical Trial Data Model Open Trading Protocol (OTP) NuDoc Technology Human Resource Management Markup Language (HRMML) Financial Products Markup Language (FpML) Coins: Tightly Coupled JavaBeans and XML Elements HR-XML Consortium Mortgage Bankers Association of America XML Workgroup DMTF Common Information Model (CIM) XML-HR Initiative - Human Resources Digital Property Rights Language (DPRL) Universal Plug and Play Forum ECMData - Electronic Component Manufacturer Data Sheet Inventory Specification XML Digital Signature (Signed XML - IETF/W3C) Process Interchange Format XML (PIF-XML) Bean Markup Language (BML) Digital Receipt Infrastructure Initiative Ontology and Conceptual Knowledge Markup Languages The Koala Bean Markup Language (KBML) Digest Values for DOM (DOMHASH) XOL - XML-Based Ontology Exchange Language Jigsaw XML Format (JXML) Signed Document Markup Language (SDML) Procedural Markup Language (PML) Chinese XML Now! FIXML - A Markup Language for the FIX Application Message Layer QAML - The Q&A Markup Language MOS-X (Media Object Server - XML) Bank Internet Payment System (BIPS) LACITO Projet Archivage de données linguistiques FLBC (Formal Language for Business Communication) and KQML smartX ['SmartCard'] Markup Language (SML) sonores et textuelles [Linguistic Data Archiving Project] ISO 12083 XML DTDs Real Estate Transaction Markup Language (RETML) Astronomical Markup Language Extensible User Interface Language (XUL) OpenMLS - Real Estate DTD Design Astronomical Instrument Markup Language (AIML) User Interface Markup Language (UIML) ACORD - XML for the Insurance Industry GedML: [GEDCOM] Genealogical Data in XML Process Specification Language (PSL) and XML Customer Profile Exchange (CPEX) Working Group Newspaper Association of America (NAA) - Standard for XML DTD for Phone Books Customer Support Consortium Classified Advertising Data 5.5 Using XML for RFCs XML for the Automotive Industry - SAE J2008 News Industry Text Format (NITF) Schools Interoperability Framework (SIF) XML.ORG - The XML Industry Portal XMLNews: XMLNews-Story and XMLNews-Meta Guideline XML (gXML) X-ACT - XML Active Content Technologies Council NewsML and IPTC2000 Extensible Protocol Electronic Business XML Initiative (ebXML) Notes Flat File Format (NFF) XML Belief Network File Format (Bayesian Networks) Portal Markup Language (PML) Java Help API Predictive Model Markup Language (PMML) EDGARspace Portal Cold Fusion Markup Language (CFML) The Data Documentation Initiative (DDI) DII Common Operating Environment (COE) XML Registry Document Content Description for XML (DCD) XML and CORBA Open eBook Initiative XSchema Mathematical Markup Language OpenMath Standard The Problem Is Repetition of Repetition of „Tower„Tower of of Babel“ Babel“ SameSame mistakes mistakes as as EDI EDI Reengineering the Standards Process TODAY TOMORROW (informal description) (rigorous and formal description) BusinessBusiness W BUSINESS AnalysisAnalysis H MODELS RequirementsRequirements Analysis Example Validation Y Analysis Information rules OrderToBuyOrSell flow TRANS- Usage Format ACTIONS Usage TradeCondition InstructingParty ExecutingParty Trade guidelines specs -TradeDate: Date -SWIFTIdent: BIC-SWIFTIdent: BIC -Security: ISIN -PriceCondition: Real -Action: {Buy/S rules -OrderedQty: Real Field W LogicalLogical Analysis specs Scope H Analysis Message Message COMPONENTS A Design T Design Purchase Order Purchase Order Sender Recipient ________ ________ Sender Recipient ________ ________ ________ ________ DOCUMENTS ________ ________ Technical ________ ________ H Technical ________ ________ Position Design Business __ ________ ________ Position __ ________ ________ Design __ ________ ________ __ ________ ________ O __ ________ ________ Documents __ ________ ________ Technical __ ________ ________ __ ________ ________ __ ________ ________ Technical __ ________ ________ Account Summary W Implementation ________ ______ __ Implementation Account Summary ________ ______
Load more

Recommended publications
  • Using the UML for Architectural Description?
    Using the UML for Architectural Description? Rich Hilliard Integrated Systems and Internet Solutions, Inc. Concord, MA USA [email protected] Abstract. There is much interest in using the Unified Modeling Lan- guage (UML) for architectural description { those techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. IEEE P1471, the Recommended Practice for Architectural Description, represents an emerging consensus for specifying the content of an architectural descrip- tion for a software-intensive system. Like the UML, IEEE P1471 does not prescribe a particular architectural method or life cycle, but may be used within a variety of such processes. In this paper, I provide an overview of IEEE P1471, describe its conceptual framework, and investigate the issues of applying the UML to meet the requirements of IEEE P1471. Keywords: IEEE P1471, architectural description, multiple views, view- points, Unified Modeling Language 1 Introduction The Unified Modeling Language (UML) is rapidly maturing into the de facto standard for modeling of software-intensive systems. Standardized by the Object Management Group (OMG) in November 1997, it is being adopted by many organizations, and being supported by numerous tool vendors. At present, there is much interest in using the UML for architectural descrip- tion: the techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. Such techniques enable architects to record what they are doing, modify or ma- nipulate candidate architectures, reuse portions of existing architectures, and communicate architectural information to others. These descriptions may the be used to analyze and reason about the architecture { possibly with automated support.
    [Show full text]
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial 25 June 2007
    OMG Systems Modeling Language (OMG SysML™) Tutorial 25 June 2007 Sanford Friedenthal Alan Moore Rick Steiner (emails included in references at end) Copyright © 2006, 2007 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Status • Specification status – Adopted by OMG in May ’06 – Finalization Task Force Report in March ’07 – Available Specification v1.0 expected June ‘07 – Revision task force chartered for SysML v1.1 in March ‘07 • This tutorial is based on the OMG SysML adopted specification (ad-06-03-01) and changes proposed by the Finalization Task Force (ptc/07-03-03) • This tutorial, the specifications, papers, and vendor info can be found on the OMG SysML Website at http://www.omgsysml.org/ 7/26/2007 Copyright © 2006,2007 by Object Management Group. 2 Objectives & Intended Audience At the end of this tutorial, you should have an awareness of: • Benefits of model driven approaches for systems engineering • SysML diagrams and language concepts • How to apply SysML as part of a model based SE process • Basic considerations for transitioning to SysML This course is not intended to make you a systems modeler! You must use the language. Intended Audience: • Practicing Systems Engineers interested in system modeling • Software Engineers who want to better understand how to integrate software and system models • Familiarity with UML is not required, but it helps 7/26/2007 Copyright © 2006,2007 by Object Management Group. 3 Topics • Motivation & Background • Diagram Overview and Language Concepts • SysML Modeling as Part of SE Process – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework • Transitioning to SysML • Summary 7/26/2007 Copyright © 2006,2007 by Object Management Group.
    [Show full text]
  • Pivotpoint-Sparx Partnership Promotes Model-Based Systems
    PivotPoint-Sparx Partnership Promotes Model-Based Systems Engineering with SysML PivotPoint Technology and Sparx Systems today announced a technology partnership that will combine their complementary strengths in SysML training and tools for systems engineers. PivotPoint announced that its “SysML Distilled™ with Enterprise Architect™” workshop is immediately available, and will use Sparx’s new MDG Technology for SysML™ product. Fallbrook, California (PRWEB) - October 9, 2006 -- PivotPoint Technology and Sparx Systems today announced a technology partnership to promote model-based systems engineering with the Systems Modeling Language (SysML). SysML is the new domain-specific modeling language for systems engineering applications that was adopted by the Object Management Group as OMG SysML™ in July 2006, and is attracting users among systems engineers worldwide. Under the agreement, PivotPoint will be Sparx’s primary partner for training and consulting services that use Sparx’s new SysML product (MDG Technology for SysML™), which was released last week. PivotPoint showed its readiness to partner by announcing the immediate availability of a new “SysML Distilled™ with Enterprise Architect™” workshop, which combines both SysML language and tool training. SysML extends the Unified Modeling Language (UML), the industry standard for specifying software-intensive systems, so that it can also specify hardware, processes, personnel, and facilities. Systems engineers who want to follow a model-based systems engineering process gain at least two important advantages in using SysML. First, SysML is a smaller language than UML 2.0 since it has fewer diagrams and constructs, so it is easier for engineers to learn and apply. Second, SysML adds to the semantic expressiveness of UML with two new diagrams for defining requirements and parametric constraints, which systems engineers need to fully specify complex systems.
    [Show full text]
  • 03-01-06 BPDM RFP.Pdf
    Business Process Definition Metamodel RFP Object Management Group First Needham Place 250 First Avenue, Suite 100 Needham, MA 02494 Telephone: +1-781-444-0404 Facsimile: +1-781-444-0320 Business Process Definition Metamodel Request For Proposal OMG Document: bei/2003-01-06 Letters of Intent due: June 16, 2003 Submissions due: August 18, 2003 Objective of this RFP This Request For Proposals solicits submissions that specify a business process definition metamodel, which is platform independent with respect to specific business process definition languages. This metamodel will define an abstract language for specification of executable business processes that execute within an enterprise (with or without human involvement); and may collaborate between otherwise- independent business processes executing in different business units or enterprises. The specification developed in response to this RFP is expected to achieve the following: • A common metamodel to unify the diverse business process definition graphical and textual notations that exist in the industry • A metamodel that complements existing UML metamodels so that business processes specifications can be part of complete system specifications to assure consistency and completeness bei/2003-01-06, January 31, 2003 1 Business Process Definition Metamodel RFP • The ability to integrate process models for workflow management processes, automated business processes, and collaborations between business units. • Support for the specification of choreography, describing the collaboration
    [Show full text]
  • Sysml, the Language of MBSE Paul White
    Welcome to SysML, the Language of MBSE Paul White October 8, 2019 Brief Introduction About Myself • Work Experience • 2015 – Present: KIHOMAC / BAE – Layton, Utah • 2011 – 2015: Astronautics Corporation of America – Milwaukee, Wisconsin • 2001 – 2011: L-3 Communications – Greenville, Texas • 2000 – 2001: Hynix – Eugene, Oregon • 1999 – 2000: Raytheon – Greenville, Texas • Education • 2019: OMG OCSMP Model Builder—Fundamental Certification • 2011: Graduate Certification in Systems Engineering and Architecting – Stevens Institute of Technology • 1999 – 2004: M.S. Computer Science – Texas A&M University at Commerce • 1993 – 1998: B.S. Computer Science – Texas A&M University • INCOSE • Chapters: Wasatch (2015 – Present), Chicagoland (2011 – 2015), North Texas (2007 – 2011) • Conferences: WSRC (2018), GLRCs (2012-2017) • CSEP: (2017 – Present) • 2019 INCOSE Outstanding Service Award • 2019 INCOSE Wasatch -- Most Improved Chapter Award & Gold Circle Award • Utah Engineers Council (UEC) • 2019 & 2018 Engineer of the Year (INCOSE) for Utah Engineers Council (UEC) • Vice Chair • Family • Married 14 years • Three daughters (1, 12, & 10) 2 Introduction 3 Our Topics • Definitions and Expectations • SysML Overview • Basic Features of SysML • Modeling Tools and Techniques • Next Steps 4 What is Model-based Systems Engineering (MBSE)? Model-based systems engineering (MBSE) is “the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases.” -- INCOSE SE Vision 2020 5 What is Model-based Systems Engineering (MBSE)? “Formal systems modeling is standard practice for specifying, analyzing, designing, and verifying systems, and is fully integrated with other engineering models. System models are adapted to the application domain, and include a broad spectrum of models for representing all aspects of systems.
    [Show full text]
  • Unifying Modeling and Programming with ALF
    SOFTENG 2016 : The Second International Conference on Advances and Trends in Software Engineering Unifying Modeling and Programming with ALF Thomas Buchmann and Alexander Rimer University of Bayreuth Chair of Applied Computer Science I Bayreuth, Germany email: fthomas.buchmann, [email protected] Abstract—Model-driven software engineering has become more The Eclipse Modeling Framework (EMF) [5] has been and more popular during the last decade. While modeling the established as an extensible platform for the development of static structure of a software system is almost state-of-the art MDSE applications. It is based on the Ecore meta-model, nowadays, programming is still required to supply behavior, i.e., which is compatible with the Object Management Group method bodies. Unified Modeling Language (UML) class dia- (OMG) Meta Object Facility (MOF) specification [6]. Ideally, grams constitute the standard in structural modeling. Behavioral software engineers operate only on the level of models such modeling, on the other hand, may be achieved graphically with a set of UML diagrams or with textual languages. Unfortunately, that there is no need to inspect or edit the actual source code, not all UML diagrams come with a precisely defined execution which is generated from the models automatically. However, semantics and thus, code generation is hindered. In this paper, an practical experiences have shown that language-specific adap- implementation of the Action Language for Foundational UML tations to the generated source code are frequently necessary. (Alf) standard is presented, which allows for textual modeling In EMF, for instance, only structure is modeled by means of of software systems.
    [Show full text]
  • Business Meeting of the Openmath Society 2018
    Business Meeting of the OpenMath Society 2018 Michael Kohlhase (President) Openmath Society http://openmath.org August 13. 2018, Hagenberg Kohlhase: Business Meeting of the OpenMath Society 2018 1 13. 8. 18, Hagenberg OpenMath 2018 Business Meeting (as required by Statutes) 1. Election of Chair of the meeting 2. Election of Secretary and two Minute Checkers (James is in Rio) 3. Annual Report 4. New Members? 5. Adoption of Balance Sheet and discharge of the Executive Committee 6. GDPR/Privacy issues for the Minutes 7. Election of the Executive Committee 8. Adoption of the second revision of the OM2 Standard 9. New OpenMath web site 10. OpenMath in JSON 11. OpenMath3 12. OMCD (management) Issues 13. Any Other Business (please come forward) Kohlhase: Business Meeting of the OpenMath Society 2018 2 13. 8. 18, Hagenberg Annual Report on Activities (2017-2018) I Last Open Business meeting, July 2017 in Edinburgh (internal ones in Spring to keep charter happy) I OM Repositories: Moved all digital assets to http://github.com/OpenMath I OM Web Site: deployed a new web site based on GH Pages (see below) I OM CD Submission Process: based on GitHub now, I OM Standard moved to separate repository, build process renovated, automated by travis. I OM2 Standard: thorough editing, more error fixing (OM binding) I OM3 Standard Effort: not started due to OM2e2 work Kohlhase: Business Meeting of the OpenMath Society 2018 3 13. 8. 18, Hagenberg New Members? I Anybody who has attended 3 OM Workshops or worked on OM for 6 months can become a member (will be generous) I please suggest new members (self-nominations encouraged) I New members proposed by OM Executive Committee I ???? Kohlhase: Business Meeting of the OpenMath Society 2018 4 13.
    [Show full text]
  • Generating Openmath Content Dictionaries from Wikidata
    Generating OpenMath Content Dictionaries from Wikidata Moritz Schubotz Dept. of Computer and Information Science, University of Konstanz, Box 76, 78464 Konstanz, Germany, [email protected] Abstract OpenMath content dictionaries are collections of mathematical sym- bols. Traditionally, content dictionaries are handcrafted by experts. The OpenMath specification requires a name and a textual description in English for each symbol in a dictionary. In our recently published MathML benchmark (MathMLBen), we represent mathematical for- mulae in Content MathML referring to Wikidata as the knowledge base for the grounding of the semantics. Based on this benchmark, we present an OpenMath content dictionary, which we generated auto- matically from Wikidata. Our Wikidata content dictionary consists of 330 entries. We used the 280 entries of the benchmark MathMLBen, as well as 50 entries that correspond to already existing items in the official OpenMath content dictionary entries. To create these items, we proposed the Wikidata property P5610. With this property, everyone can link OpenMath symbols and Wikidata items. By linking Wikidata and OpenMath data, the multilingual community maintained textual descriptions, references to Wikipedia articles, external links to other knowledge bases (such as the Wolfram Functions Site) are connected to the expert crafted OpenMath content dictionaries. Ultimately, these connections form a new content dictionary base. This provides multi- lingual background information for symbols in MathML formulae. 1 Introduction and Prior Works Traditionally, mathematical formulae occur in a textual or situational context. Human readers infer the meaning of formulae from their layout and the context. An essential task in mathematical information retrieval (MathIR) is to mimic parts of this process to automate MathIR tasks.
    [Show full text]
  • Semi-Automated Correction Tools for Mathematics-Based Exercises in MOOC Environments
    International Journal of Artificial Intelligence and Interactive Multimedia, Vol. 3, Nº 3 Semi-Automated Correction Tools for Mathematics-Based Exercises in MOOC Environments Alberto Corbí and Daniel Burgos Universidad Internacional de La Rioja the accuracy of the result but also in the correctness of the Abstract — Massive Open Online Courses (MOOCs) allow the resolution process, which might turn out to be as important as participation of hundreds of students who are interested in a –or sometimes even more important than– the final outcome wide range of areas. Given the huge attainable enrollment rate, it itself. Corrections performed by a human (a teacher/assistant) is almost impossible to suggest complex homework to students and have it carefully corrected and reviewed by a tutor or can also add value to the teacher’s view on how his/her assistant professor. In this paper, we present a software students learn and progress. The teacher’s feedback on a framework that aims at assisting teachers in MOOCs during correction sheet always entails a unique opportunity to correction tasks related to exercises in mathematics and topics improve the learner’s knowledge and build a more robust with some degree of mathematical content. In this spirit, our awareness on the matter they are currently working on. proposal might suit not only maths, but also physics and Exercises in physics deepen this reviewing philosophy and technical subjects. As a test experience, we apply it to 300+ physics homework bulletins from 80+ students. Results show our student-teacher interaction. Keeping an organized and solution can prove very useful in guiding assistant teachers coherent resolution flow is as relevant to the understanding of during correction shifts and is able to mitigate the time devoted the underlying physical phenomena as the final output itself.
    [Show full text]
  • The Utility of Openmath
    The Utility of OpenMath James H. Davenport? Department of Computer Science, University of Bath, Bath BA2 7AY England [email protected], WWW home page: http://staff.bath.ac.uk/masjhd Abstract. OpenMath [5] is a standard for representing the semantics of mathematical objects. It differs from ‘Presentation’ MathML [7] in not being directly concerned with the presentation of the object, and from ‘Content’ MathML in being extensible. How should these extensions be performed so as to maximise the utility (which includes presentation) of OpenMath? 1 What is OpenMath? “OpenMath is an emerging standard for representing mathematical objects with their semantics, allowing them to be exchanged between computer programs, stored in databases, or published on the worldwide web.”1. In particular, Open- Math is extensible, unlike MathML 2.02 [7]. It achieves this by having an exten- sible collection of Content Dictionaries. “Content Dictionaries (CDs) are used to assign informal and formal semantics to all symbols used in the OpenMath ob- jects. They define the symbols used to represent concepts arising in a particular area of mathematics” [5, section 1.3]. Notation 1 By an OpenMath CD we will mean any document conforming to the formal syntax of [5]. The status of an OpenMath content dictionary is one of the following [5, Section 4.2.1]: – official: approved by the OpenMath society according to the procedure defined in section 4.5 (of [5]); ? This paper owes much to some questions of Paul Libbrecht, when we were both at the IMA Workshop “The Evolution of Mathematical Communication in the Age of Digital Libraries” — December 8–9, 2006.
    [Show full text]
  • OMG Meta Object Facility (MOF) Core Specification
    Date : October 2019 OMG Meta Object Facility (MOF) Core Specification Version 2.5.1 OMG Document Number: formal/2019-10-01 Standard document URL: https://www.omg.org/spec/MOF/2.5.1 Normative Machine-Readable Files: https://www.omg.org/spec/MOF/20131001/MOF.xmi Informative Machine-Readable Files: https://www.omg.org/spec/MOF/20131001/CMOFConstraints.ocl https://www.omg.org/spec/MOF/20131001/EMOFConstraints.ocl Copyright © 2003, Adaptive Copyright © 2003, Ceira Technologies, Inc. Copyright © 2003, Compuware Corporation Copyright © 2003, Data Access Technologies, Inc. Copyright © 2003, DSTC Copyright © 2003, Gentleware Copyright © 2003, Hewlett-Packard Copyright © 2003, International Business Machines Copyright © 2003, IONA Copyright © 2003, MetaMatrix Copyright © 2015, Object Management Group Copyright © 2003, Softeam Copyright © 2003, SUN Copyright © 2003, Telelogic AB Copyright © 2003, Unisys USE OF SPECIFICATION - TERMS, CONDITIONS & NOTICES The material in this document details an Object Management Group specification in accordance with the terms, conditions and notices set forth below. This document does not represent a commitment to implement any portion of this specification in any company's products. The information contained in this document is subject to change without notice. LICENSES The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification.
    [Show full text]
  • Ontology Definition Metamodel
    Date: September 2014 Ontology Definition Metamodel Version 1.1 OMG Document Number: formal/2014-09-02 Standard Document URL: http://www.omg.org/spec/ODM/1.1/ Normative Machine Consumable Files: http://www.omg.org/spec/ODM/20131101/ODM-metamodels.xmi http://www.omg.org/spec/ODM/20131101/RDFProfile.xmi http://www.omg.org/spec/ODM/20131101/OWLProfile.xmi http://www.omg.org/spec/ODM/20131101/RDFLibrary.xmi http://www.omg.org/spec/ODM/20131101/XSDLibrary.xmi http://www.omg.org/spec/ODM/20131101/OWLLibrary.xmi Copyright © 2009-2014, 88Solutions Copyright © 2013-2014, ACORD Copyright © 2009-2014, Adaptive, Inc. Copyright © 2009-2014, California Institute of Technology. United States Government sponsorship acknowledged. Copyright © 2005-2012, Computer Sciences Corporation Copyright © 2009-2014, Deere & Company Copyright © 2005-2014, International Business Machines Corporation Copyright © 2013-2014, Institute for Defense Analyses Copyright © 2009-2014, Object Management Group, Inc. Copyright © 2011-2014, No Magic, Inc. Copyright © 2005-2012, Raytheon Company Copyright © 2005-2011, Sandpiper Software, Inc. Copyright © 2009-2014, Sparx Systems Pty Ltd Copyright © 2011-2014, Thematix Partners LLC USE OF SPECIFICATION - TERMS, CONDITIONS & NOTICES The material in this document details an Object Management Group specification in accordance with the terms, conditions and notices set forth below. This document does not represent a commitment to implement any portion of this specification in any company's products. The information contained in this document is subject to change without notice. LICENSES The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version.
    [Show full text]