Continuity of Care (CCD) Suitability Analysis

Total Page:16

File Type:pdf, Size:1020Kb

Continuity of Care (CCD) Suitability Analysis NIST GCR 11-941 Continuity of Care (CCD) Suitability Analysis Lantana Consulting Group NIST GCR 11-941 Continuity of Care (CCD) Suitability Analysis Prepared for National Institute of Standards and Technology Gaithersburg Md 20899-8202 By Lantana Consulting Group May 2011 U.S. Department of Commerce Rebecca M. Blank, Acting Secretary National Institute of Standards and Technology Patrick D. Gallagher, Under Secretary for Standards and Technology and Director Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. Continuity of Care Document (CCD) Suitability Analysis May 2011 Prepared by Lantana Consulting Group for National Institute of Standards and Technology © 2011 Lantana Consulting Group All rights reserved. Lantana Consulting Group P.O. Box 177 East Thetford, VT 05043 www . lantanagroup . com Bob Dolin, MD President and CMO bob . dolin @ lantanagroup . com Liora Alschuler Chief Executive Officer liora . alschuler @ lantanagroup . com Rick Geimer Chief Technology Officer rick . geimer @ lantanagroup . com Gaye Giannone Dolin Senior Nurse Informaticist gaye . dolin @ lantanagroup . com Kate Hamilton Senior Information Analyst kate . hamilton @ lantanagroup . com Susan Hardy Senior Technical Editor susan . hardy @ lantangroup . com Yan Heras Senior Medical Informaticist yan . heras @ lantanagroup . com Jingdong Li Chief Architect jingdong . li @ lantanagroup . com Brett Marquard Senior Interoperability Consultant brett . marquard @ lantangroup . com Sean McIlvenna Senior Software Architect sean . mcilvenna @ lantangroup . com Tim Stevens Technical Writer tim . stevens @ lantanagroup . com Lauren Wood Senior Project Manager lauren . wood @ lantanagroup . com Acknowledgments This analysis was produced and developed by Lantana Consulting Group for the National Institute of Standards and Technology (NIST) under contract number SB134110CN0039, CCD Definition. SNOMED CT® ( http :// www . ihtsdo . org / snomed - ct / ) is a registered trademark of the International Health Terminology Standard Development Organisation (IHTSDO). LOINC® ( http :// loinc . org ) codes, LOINC table, and LOINC panels and forms file are copyright © 1995-2010, Regenstrief Institute, Inc., and the Logical Observation Identifiers Names and Codes (LOINC) Committee and are available at no cost under the license at http :// loinc . org / terms - of - use. Table of Contents 1 Executive Summary 8 2 Introduction 9 2.1 Purpose 9 2.2 Audience9 2.3 Approach 9 2.4 Organization of This Document 10 3 Healthcare Conformance Requirements and Their Testability 11 3.1 Conformance Statements 11 3.1.1 Conformance Statements vs. Prose Guidance 11 3.1.2 Conformance Verbs 12 3.1.3 Types of Conformance Statements 12 3.1.3.1 Parent-to-child Constraints 12 3.1.3.2 Document Tree Conditional Constraints 13 3.1.3.3 Template-specific Vocabulary Constraints 13 3.1.3.4 Non-XML Syntax Constraints 13 3.1.3.5 Data Integrity Checks 14 3.1.3.6 Business Rules 14 3.1.3.7 Guidance on Data Recording and Accuracy 14 3.1.3.8 CDA Extensions 14 3.1.3.9 Compound Conformance Statements15 3.1.4 Templates 15 3.2 Base Standard Constraints 16 3.2.1 Data Types 16 3.2.2 Narrative Block 16 3.2.3 Identifiers 16 3.2.3.1 OIDs 16 3.2.3.2 UUIDs 17 3.2.4 Base Standard Vocabularies 17 3.2.5 XML Structure 18 3.2.5.1 Syntax Validation 18 3.2.5.2 Attributes and Elements 18 3.2.5.3 Cardinality and Conformance Verbs 18 3.2.5.4 Namespaces 19 3.2.5.5 XML Schema and XSI-Type 19 3.3 External Constraints 20 3.3.1 HITSP/C32 20 3.3.2 Meaningful Use 21 4 Test Technologies 22 4.1 Ranking Criteria 22 4.2 Currently Used Technologies 22 4.2.1 CDA.xsd XML Schema 22 4.2.2 Constrained Schemas 23 4.2.3 Schematron 24 4.2.4 XPath 25 4.2.5 Model-Driven Validation 26 4.2.6 Terminology Service Validation 28 4.2.7 Human Validation 29 4.3 Potential Technologies 29 4.3.1 RELAX NG 29 4.3.2 Web Ontology Language 30 4.3.3 Custom Validation Code 31 4.4 Test Technology Application 32 5 Conclusions and Recommendations 34 5.1 Recommendations for Standards Developers 34 5.2 Test Technology Recommendations 35 5.2.1 General Recommendations to NIST 35 5.2.2 Applicable Technologies for Constraint Types 35 6 References 37 Appendix A — Acronyms and Abbreviations 39 Appendix B — CCD Test Data Coverage 41 Table of Figures Figure 1: Parent-to-child cardinality constraint example 12 Figure 2: Document tree conditional constraint example 13 Figure 3: Static value set example 13 Figure 4: Dynamic value set example 13 Figure 5: Syntax constraint example 13 Figure 6: Data integrity check example 14 Figure 7: Business-rule constraint example 14 Figure 8: Data recording constraint example 14 Figure 9: CDA extension example 15 Figure 10: Compound conformance statement example 15 Figure 11: CCD template example 15 Figure 12: C32 template example 15 Figure 13: Namespace declaration example 19 Figure 14: xsi:type example 19 Table of Tables Table 1: Use of Conformance Verbs 12 Table 2: CDA.xsd XML Schema Analysis 23 Table 3: Constrained Schemas Analysis 24 Table 4: Schematron Analysis 25 Table 5: Model-driven Validation Analysis 27 Table 6: Terminology Service Validation Analysis 28 Table 7: Human Validation Analysis 29 Table 8: RELAX NG Validation Analysis 30 Table 9: Test Technology Application Examples 32 Table 10: Applicable Technologies for Validation 36 Table 11: CCD Conformance Statement Coverage 42 1. Executive Summary The advent of widespread dependence on electronic exchange of health information has highlighted the importance of interoperability standards and the testability of those standards. Several established and effective test tools and methods are in use; however, the relative merits and, more critically, limitations of different test methods have not been anlaysed or defined. This paper explores test methods for the Health Level Seven (HL7) Continuity of Care Document (CCD); some of our findings and recommendations apply generally to the testing and validation of HL7 Clinical Document Architecture (CDA) instances of all types. The paper reviews the expression of conformance requirements for Meaningful Use of CCD, categorizes these, and then catalogs the CCD conformance statements. We assess ten methods ranging from fully automated to human inspection for their ability to validate the different categories of conformance requirements. The analysis indicates that the methods in use are reasonably effective, where combined with a cleaner definition of conformance requirements and descriptions on the limits of each method. Thus, the paper contains recommendations to standards developers on the expression of conformance requirements that could improve the clarity of current test methods and tools. We give most attention to those methods currently in use: XML Schema, Schematron, and model- driven validation. We also examine potentially useful technologies not widely used for CDA validation at this time, such as RELAX NG and OWL (Web Ontology Language). 2. Introduction 1. Purpose This document analyzes Health Level Seven’s (HL7) Continuity of Care Document (CCD) specification from the perspective of validation, looking at the limits of automated testing and assessing the differential impact of various approaches to it. This document describes common concepts, structures, and data types within the specification and the extent to which they can be tested through automated processes. It assesses the relevance of testing technologies to CCD and recommends those technologies deemed appropriate for CCD validation. It provides an audit of CCD conformance statements, identifying which test technologies apply. Finally, this document provides recommendations for fully and semi- automated processes to generate test files. Note that this assessment also provides recommendations to the standards community on construction of conformance requirements to make them more manageable for automated testing; however, the emphasis here is on evaluation of test technologies against an established set of conformance requirements. Ultimately, this document clearly defines what portions of the HL7 CCD specification are testable and to what extent they will be included in the test data deliverable for this contract. This report contains the names of commercial products and organizations. Any mention of commercial products or organizations is for information only; it does not imply recommendation or endorsement by Lantana or NIST. 2. Audience The audience for this document includes NIST staff, standards developers interacting with CCD, and implementers interested in the available means to validate their documents. 3. Approach Our approach to analyzing CCD coverage consisted of these components: 1. Review of formal conformance requirements 2. Review of validation methods 3. Assessment of validation methods for different types of conformance requirements 4. Analysis of results We reviewed conformance requirements by describing how these requirements are conveyed and by developing categories of conformance requirements. We then cataloged and categorized all 549 CCD conformance requirements. This review encompassed the conformance requirements of the base standard, CDA, the CCD itself, and the layered constraints added by Integrating
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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • NISO RP-2006-01, Best Practices for Designing Web Services in The
    NISO RP-2006-01 Best Practices for Designing Web Services in the Library Context by the NISO Web Services and Practices Working Group A Recommended Practice of the National Information Standards Organization July 2006 Published by the National Information Standards Organization Bethesda, Maryland Published by NISO Press Copyright © 2006 by the National Information Standards Organization. All rights reserved under International and Pan-American Copyright Conventions. For noncommercial purposes only, this publication may be reproduced or transmitted in any form or by any means without prior permission in writing from the publisher. All inquiries regarding commercial reproduction or distribution should be addressed to: NISO Press 4733 Bethesda Avenue, Suite 300 Bethesda, MD 208114 Telephone: 301-654-2512 Email: [email protected] About NISO Recommended Practices A NISO Recommended Practice is a recommended "best practice" or "guideline" for methods, materials, or practices in order to give guidance to the user. Such documents usually represent a leading edge, exceptional model, or proven industry practice. All elements of Recommended Practices are discretionary and may be used as stated or modified by the user to meet specific needs. © 2006 NISO Best Practices for Designing Web Services in the Library Context Contents Foreword......................................................................................................................................ii Purpose and Scope..................................................................................................................
    [Show full text]
  • Iso/Iec 13250-3:2007(E)
    This is a preview - click here to buy the full publication INTERNATIONAL ISO/IEC STANDARD 13250-3 First edition 2007-03-15 Information technology — Topic Maps — Part 3: XML syntax Technologies de l'information — Plans relatifs à des sujets — Partie 3: Syntaxe XML Reference number ISO/IEC 13250-3:2007(E) © ISO/IEC 2007 ISO/IEC 13250-3:2007(E) This is a preview - click here to buy the full publication PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. © ISO/IEC 2007 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.
    [Show full text]
  • Iso/Iec 23007-3:2011(E)
    This is a preview - click here to buy the full publication INTERNATIONAL ISO/IEC STANDARD 23007-3 First edition 2011-07-15 Information technology — Rich media user interfaces Part 3: Conformance and reference software Technologies de l'information — Interfaces d'utilisateur au support riche — Partie 3: Conformité et logiciel de référence Reference number ISO/IEC 23007-3:2011(E) © ISO/IEC 2011 ISO/IEC 23007-3:2011(E) This is a preview - click here to buy the full publication COPYRIGHT PROTECTED DOCUMENT © ISO/IEC 2011 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from 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.org Published in Switzerland ii © ISO/IEC 2011 – All rights reserved This is a preview - click here to buy the full publication ISO/IEC 23007-3:2011(E) Contents Page Foreword ............................................................................................................................................................iv Introduction.........................................................................................................................................................v 1 Scope ......................................................................................................................................................1
    [Show full text]
  • The Emergence of ASN.1 As an XML Schema Notation
    The emergence of ASN.1 as an XML schema notation John Larmouth <[email protected]>> Abstract This paper describes the emergence of ASN.1 as an XML schema notation. Use of ASN.1 as an XML schema notation provides the same functionality as use of W3C XML Schema (XSD), but makes compact binary representations of the data available as well as XML encodings. ASN.1 also provides a clear separation of the specification of the information content of a docu- ment or message from the actual syntax used in its encoding or representation. (Examples of representation differences that do not affect the meaning - semantics - being communicated are the use of an attribute instead of an element in an XML encoding, or of space-separated lists instead of repeated elements.) Examples are given of ASN.1 specification of an XML document, and some comparisons are made with XSD and RELAX NG Table of Contents 1. Brief historical background ........................................................................................................... 1 2. Relevant documents .................................................................................................................... 3 3. The concept and value of an abstract syntax notation ......................................................................... 3 4. The need for XML Encoding Rules for ASN.1 ................................................................................. 3 5. The development of the ASN.1 XML Encoding Rules - BASIC-XER ..................................................
    [Show full text]
  • Towards Conceptual Modeling for XML
    Towards Conceptual Modeling for XML Erik Wilde Swiss Federal Institute of Technology Zurich¨ (ETHZ) Abstract: Today, XML is primarily regarded as a syntax for exchanging structured data, and therefore the question of how to develop well-designed XML models has not been studied extensively. As applications are increasingly penetrated by XML technologies, and because query and programming languages provide native XML support, it would be beneficial to use these features to work with well-designed XML models. In order to better focus on XML-oriented technologies in systems engineering and programming languages, an XML modeling language should be used, which is more focused on modeling and structure than typical XML schema languages. In this paper, we examine the current state of the art in XML schema languages and XML modeling, and present a list of requirements for a XML conceptual modeling language. 1 Introduction Due to its universal acceptance as a way to exchange structured data, XML is used in many different application domains. In many scenarios, XML is used mainly as an exchange format (basically, a way to serialize data that has a model defined in some non- XML way), but an increasing number of applications is using XML as their native data model. Developments like the XML Query Language (XQuery) [BCF+05] are a proof of the fact that XML becomes increasingly visible on higher layers of the software architec- ture, and in this paper we argue that current XML modeling approaches are not sufficient to support XML in this new context. Rather than treating XML as a syntax for some non-XML data model, it would make more sense to embrace XML’s structural richness by using a modeling language with built-in XML support.
    [Show full text]