Relax Ng to Json Schema
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Specification for JSON Abstract Data Notation Version
Standards Track Work Product Specification for JSON Abstract Data Notation (JADN) Version 1.0 Committee Specification 01 17 August 2021 This stage: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.html https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.pdf Previous stage: https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.html https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.pdf Latest stage: https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.html https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.pdf Technical Committee: OASIS Open Command and Control (OpenC2) TC Chair: Duncan Sparrell ([email protected]), sFractal Consulting LLC Editor: David Kemp ([email protected]), National Security Agency Additional artifacts: This prose specification is one component of a Work Product that also includes: JSON schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.json JADN schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.jadn Abstract: JSON Abstract Data Notation (JADN) is a UML-based information modeling language that defines data structure independently of data format. -
Darwin Information Typing Architecture (DITA) Version 1.3 Draft 29 May 2015
Darwin Information Typing Architecture (DITA) Version 1.3 Draft 29 May 2015 Specification URIs This version: http://docs.oasis-open.org/dita/dita/v1.3/csd01/dita-v1.3-csd01.html (Authoritative version) http://docs.oasis-open.org/dita/dita/v1.3/csd01/dita-v1.3-csd01.pdf http://docs.oasis-open.org/dita/dita/v1.3/csd01/dita-v1.3-csd01-chm.zip http://docs.oasis-open.org/dita/dita/v1.3/csd01/dita-v1.3-csd01-xhtml.zip Previous version: Not applicable Latest version: http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-csd01.html (Authoritative version) http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-csd01.pdf http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-csd01-chm.zip http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-csd01-xhtml.zip Technical committee: OASIS Darwin Information Typing Architecture (DITA) TC Chair: Kristen James Eberlein ([email protected]), Eberlein Consulting LLC Editors: Robert D. Anderson ([email protected]), IBM Kristen James Eberlein ([email protected]), Eberlein Consulting LLC Additional artifacts: This prose specification is one component of a work product that also includes: OASIS DITA Version 1.3 RELAX NG: http://docs.oasis-open.org/dita/dita/v1.3/csd01/schemas/ DITA1.3-rng.zip OASIS DITA Version 1.3 DTDs: http://docs.oasis-open.org/dita/v1.3/os/DITA1.3-dtds.zip OASIS DITA Version 1.3 XML Schemas: http://docs.oasis-open.org/dita/v1.3/os/DITA1.3-xsds.zip DITA source that was used to generate this document: http://docs.oasis-open.org/dita/dita/v1.3/ csd01/source/DITA1.3-source.zip Abstract: The Darwin Information Typing Architecture (DITA) 1.3 specification defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining, extending, and constraining document types. -
An Automated Approach to Grammar Recovery for a Dialect of the C++ Language
An Automated Approach to Grammar Recovery for a Dialect of the C++ Language Edward B. Duffy and Brian A. Malloy School of Computing Clemson University Clemson, SC 29634, USA feduffy,[email protected] Abstract plications developed in a new or existing language [12, 15]. Frequently, the only representation of a dialect is the gram- In this paper we present the design and implementa- mar contained in the source code of a compiler; however, a tion of a fully automated technique for reverse engineering compiler grammar is difficult to comprehend since parser or recovering a grammar from existing language artifacts. generation algorithms place restrictions on the form of the The technique that we describe uses only test cases and a compiler grammar [16, page 10]. parse tree, and we apply the technique to a dialect of the Another problem with language dialects is that there C++ language. However, given test cases and a parse tree has been little research, to date, addressing the problem for a language or a dialect of a language, our technique of reverse engineering a grammar or language specifica- can be used to recover a grammar for the language, in- tion for a language dialect from existing language arti- cluding languages such as Java, C, Python or Ruby. facts. Lammel¨ and Verhoef have developed a technique that uses a language reference manual and test cases to recover a grammar for a language or dialect [16]. How- 1. Introduction ever, their technique requires user intervention along most of the stages of recovery and some of the recovery process The role of programming languages in software devel- is manual. -
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. -
XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département D©Informatique Et De Recherche Opérationnelle Université De Montréal
XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/ XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 Abstract This tutorial gives a high-level overview of the main principles underlying some XML technologies: DTD, XML Schema, RELAX NG, Schematron, XPath, XSL stylesheets, Formatting Objects, DOM, SAX and StAX models of processing. They are presented from the point of view of the computer scientist, without the hype too often associated with them. We do not give a detailed description but we focus on the relations between the main ideas of XML and other computer language technologies. A single compact pretty-print example is used throughout the text to illustrate the processing of an XML structure with XML technologies or with Java programs. We also show how to create an XML document by programming in Java, in Ruby, in Python, in PHP, in E4X (Ecmascript for XML) and in Swift. The source code of the example XML ®les and the programs are available either at the companion web site of this document or by clicking on the ®le name within brackets at the start of the caption of each example. -
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. -
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. -
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. -
File Format Guidelines for Management and Long-Term Retention of Electronic Records
FILE FORMAT GUIDELINES FOR MANAGEMENT AND LONG-TERM RETENTION OF ELECTRONIC RECORDS 9/10/2012 State Archives of North Carolina File Format Guidelines for Management and Long-Term Retention of Electronic records Table of Contents 1. GUIDELINES AND RECOMMENDATIONS .................................................................................. 3 2. DESCRIPTION OF FORMATS RECOMMENDED FOR LONG-TERM RETENTION ......................... 7 2.1 Word Processing Documents ...................................................................................................................... 7 2.1.1 PDF/A-1a (.pdf) (ISO 19005-1 compliant PDF/A) ........................................................................ 7 2.1.2 OpenDocument Text (.odt) ................................................................................................................... 3 2.1.3 Special Note on Google Docs™ .......................................................................................................... 4 2.2 Plain Text Documents ................................................................................................................................... 5 2.2.1 Plain Text (.txt) US-ASCII or UTF-8 encoding ................................................................................... 6 2.2.2 Comma-separated file (.csv) US-ASCII or UTF-8 encoding ........................................................... 7 2.2.3 Tab-delimited file (.txt) US-ASCII or UTF-8 encoding .................................................................... 8 2.3 -
SWAD-Europe Deliverable 5.1: Schema Technology Survey
Sat Jun 05 2004 23:47:40 Europe/London SWAD-Europe Deliverable 5.1: Schema Technology Survey Project name: Semantic Web Advanced Development for Europe (SWAD-Europe) Project Number: IST-2001-34732 Workpackage name: 5. Integration with XML Technology Workpackage description: ☞http://www.w3.org/2001/sw/Europe/plan/workpackages/live/esw-wp-5.html Deliverable title: SWAD-Europe: Schema Technology Survey URI: ☞http://www.w3.org/2001/sw/Europe/reports/xml_schema_tools_techniques_report Authors: Stephen Buswell, Dan Brickley, Brian Matthews Abstract: This report surveys the state of schema annotation and mapping technology. It takes a practical approach by targeting the work to the needs of developers, providing background to support our attempts to answer frequently asked questions on this subject. The report first reviews previous work on 'bridging languages', giving an overview of the major approaches and uses that to motivate further technical work to progress the state of the art in this area. Status: Snapshot release for discussion and editorial work. Further revisions are planned during WP4. Comments on this document are welcome and should be sent to the ☞[email protected] list. An archive of this list is available at ☞http://lists.w3.org/Archives/Public/public-esw/ This report is part of ☞SWAD-Europe ☞Work package 5: Integration with XML Technology and addresses the topic of Schema annotation, and the relationship(s) between RDF and XML technologies. The variety of so-called 'schema languages' for the Web has caused some confusion. This document attempts to place them in context, and explore the state of the art in tools for mapping data between the different approaches. -
Understanding
Implementing UBL Mark Crawford UBL Vice Chair XML 2003 9 December 2003 Why Are We Talking About UBL • UBL fulfils 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 eBusiness exchanges – 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 1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability 4 Making UBL Happen 5 UBL Phase 2 6 Summary The promise of XML for e-business • Plug ‘n’ play electronic commerce – Spontaneous trade – No custom programming • Ubiquity on the Internet – Dirt-cheap tools – Complete platform independence – Enable true global market availability • Enable universal interoperability – Abandon existing EDI systems – Handle both "publication" document types and "transactional" documents 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 electronic business exchanges • Integrate small and medium-size businesses into existing electronic data exchange-based supply chains The standardization of XML business documents is the easiest way to accomplish -
Information Technology — Topic Maps — Part 3: XML Syntax
© ISO/IEC 2006 – All rights reserved ISO/IEC JTC 1/SC 34 Date: 2006-06-19 ISO/IEC FDIS 13250-3 ISO/IEC JTC 1/SC 34/WG 3 Secretariat: SCC Information Technology — Topic Maps — Part 3: XML Syntax Warning This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. Document type: International Standard Document subtype: Document stage: (50) Approval Document language: E ISO/IEC FDIS 13250-3 ii © ISO/IEC 2006 – All rights reserved ISO/IEC FDIS 13250-3 Copyright notice This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying, recording or otherwise, without prior written permission being secured. Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's member body in the country of the requester. ISO copyright office Case postale 56 · CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail [email protected] Web www.iso.ch Reproduction may be subject to royalty payments or a licensing agreement.