DOCSLIB.ORG

Metadata Standards Directory WORKING GROUP

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Metadata Standards Directory WORKING GROUP Metadata Standards Directory WORKING GROUP Metadata Standards Directory Alex Ball University of Bath RDA Europe Webinar 16 February 2016 Outline Motivation: Why use metadata standards, and why many don’t Prior work: Finding a perfect match Methodology: The Working Group Results: The Metadata Standards Directory Next steps: The Metadata Standards Catalog Acknowledgements Why should I use a metadata standard? Better discovery versus Better context versus Better reuse | versus | Better ecosystem É Less working things out from scratch É More complete metadata É Benefits of practising É Better documentation of the standards É Concentration of development attention and effort É Better time-saving tools É etc., etc. So why doesn’t everyone use a metadata standard? 1 2 3 No suitable standard? None 56.1% My lab 22.1% ISO 8.0% Open GIS 8.0% EML 7.9% FDGC 7.9% Other 6.8% DC 2.2% Metadata standards used DwC 1.7% DIF 1.0% 0 100 200 300 400 500 600 700 Responses (N = 1205/1329) Figure: Metadata for scientific data (Source: Tenopir et al. 2011) Back Forward Too many standards? (Source: cbn Randall Munroe) ‘The nice thing about standards is that you have so many to choose from’ — Tanenbaum (1988) Back Forward Isn’t that, like, really hard? Just fill out this simple form… <mods xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-4.xsd"> <titleInfo> <title> Title goes here </title> </titleInfo> <name type="personal"> <namePart>Author name goes here</namePart> <role> <roleTerm type="text">Author</roleTerm> </role> </name> <typeOfResource>dataset</typeOfResource> <genre>Dataset</genre> <originInfo> <publisher>Publisher name goes here</publisher> </originInfo> <language> <languageTerm type="text">Language name</languageTerm> <languageTerm type="code" authority="iso639-2b">ISO 639-2b code</languageTerm> </language> <physicalDescription> <internetMediaType>MIME type goes here, repeat as necessary</internetMediaType> <digitalOrigin>born digital</digitalOrigin> <extent>Number of records in your database, or size of file in bytes</extent> </physicalDescription> <abstract> Abstract goes here </abstract> <subject authority="scheme name goes here"> <topic>Keyword goes here, repeat as necessary</topic> <cartographics>Spatial coordinates<cartographics/> <temporal>Temporal extente</temporal> <geographic>Spatial extent in words</geographic> </subject> <identifier>ID goes here</identifier> <location> <url usage="primary display" access="object in context">Location of record</url> <url access="raw object">Location for download</url> </location> <accessCondition type="useAndReproduction"> Usage restrictions or permissions </accessCondition> <relatedItem ID="relatedMaterials"> <location> <url usage="primary display" access="object in context">Record of related item</url> </location> </relatedItem> <note type="citation"> Sample citation goes here </note> <note type="software">Required software goes here</note> <subject ID="location" displayLabel="Description of spatial extent again"> <cartographics> <coordinates> List of coordinates, comma separated </coordinates> </cartographics> <topic>Type of coordinates goes here</topic> </subject> </mods> Back Forward Science Data Literacy Project http://sdl.syr.edu/?page_id=32 Scientific Data Application Profile Scoping Study http:// www.ukoln.ac.uk/ Scientific Data Application Profile Scoping Study Report projects/sdapss/ Document details Author: Alexander Ball, UKOLN, University of Bath Date: 3rd June 2009 Version: 1.1 Document Name: sdapss.pdf Notes: Changes from version 1.0: Typographical corrections made. References added. Conclusions expanded. Seeing Standards ta a ata d usical MaterialsScholarly Texts ata ual Reso Visual Resources Musica Mo Musica Sc ving Scholarly Texts Sch Mov h Musical Materials olarly Te Imag ov Scholarly Texts l Ma Visual Resources Geospatial Data u ing Imagesl Ma Visual Resour ing Images M Visual Resources ogy olarly Texts oving Images Geos es y teria teria Musical MaterialsSch patial Data olled Vocabulary Visual Reso rmat Datasets Geospatial Data Visual Re Moving Images ls xts ces Musica Musical Materials olarly rolled Vocabulary Cultural Objects ls Geospatial Data rd Fo Scholarly Text RD Contr Datasets Cont tural Objects Sch Moving Images ControlledReco Vocabular Content StandardRecord Format Mov Archives es Datasets ContentRecord Standard Format Structure Standard Cultural Objects Structure Standard Structure Standard Geospatial Data Texts Technical Metadata LCSHDescrip l Ma olarly mat Str Cultural Objects ry Str QDC uctur Technical Metadata ing Images ONIXDescrip uctur DescripRights Metadata Industry Rights Metadata brari Archives urces bula Archives al Metadata Industry MARCRights MetadataStr sourc al Metadata es Mu Descrip uctur Geospatial Data on Li ies al Metadata Geospatial Data teria Datasets Framework/TechnolRecord For ti Museums Texts Industry Information tive Metad Archives ar s Content Standard brari Datasets Controlled Voca Libraries tive Metad Museums tive Metad Libr ls e Record Format Cultural Objects Libraries OAI-PMHDescrip Righ tion Industry Li tive Metad s Record Format Cultural Objects Structure Standard Informa Dat aset s Structure Standard Technical Metadata ts Met MODSRights Meta Archives Information Cultural Objects Descrip Str uctur adat Informa Archives al Metadata ata METS tive Metad a Me da ata Structural Metadata ta ata Weak ata Archives tadata Wrappe Libraries Information IndustryLibrariesMuseums Museums tive Metad Museums Information Industry CanCore, GEM, IEEE/LOM, MIX, ata MuseumDat, TGN, XMP Libraries Markup rs ata Semi-Weak Language AGLS, APPM, Atom, CIDOC/CRM, DACS, EAC-CPF, EAD, SGML, XML ISAAR(CPF), ISAD(G), MPEG-7, OAI-ORE, Musical Framework/ Semi-Strong RSS, SCORM, Topic Maps MathML, MIX AACR2, DCAM, DDC, Materials Technology indecs, ISBD, LCC, Linked CanCore, Seeing Standards: KML, Data, MADS, MARC, MARC EAC-CPF, EAD, GEM, NewsML Relator Codes, MARCXML, METS IEEE/LOM, ISAAR(CPF), Rights, MODS, OAI-PMH, OAIS, ISAD(G), MARCXML, ODRL, AACR2, AES Core Controlled Atom, RSS, Audio, CCO, DC, ODRL, PREMIS, RAD, RDA, RDF, Ontology for Media EAC-CPF, EML, SKOS Resource, SCORM, TGN, IEEE/LOM, MIX, MODS, RELAX NG, Sears List of Subject NewsML, ODRL, ONIX, PB Headings, SGML, SKOS, SMIL, SRU, AACR2, Topic Maps Core, RAD, RDA, Vocabulary A Visualization of the TextMD, XrML XOBIS, XQuery, XrML AGLS, Atom, Scholarly BISAC, DACS, DCAM, GEM, METS DDC, FRBR, indecs, LCC, Rights, QDC, EAD, EML, ADL, AES Core Audio, VRA Core DCAM, Linked Data, MADS, MARC, MARC Weak GML, AES Process History, Texts DTD, Linked Data, Relator Codes, METS Rights, MODS, Metadata Universe eak MathML, DC, DTD, FRBR, ID3, PREMIS, PRISM, RDF, RELAX NG, CDWA, DC, GILS, OAI-ORE, OAI-PMH, ISAD(G), ISBD, MARC, MEI, LCSH, MEI, METS, MO, RSS, Sears List of Subject AGLS, APPM, MARCXML, MODS, Semi-W PRISM OpenURL, RDF, QDC, TEI, VRA Core Music- MPEG-21 DIDL, DC, DTD, Headings, SGML, SKOS, XMP, Atom, DACS, AGLS, RELAX NG, SGML, XOBIS, XQuery, XrML EAC-CPF, EAD, CanCore AAT, BISAC, DDC, MusicXML, MXF, ISBD, LCSH, MESH, DDC, FRBR, SRU, Topic ISAAR(CPF), LCC Semi-Strong LCC, LCSH, MARC Ontology for Media METS, MPEG-21 DIDL, ISAD(G), LCSH, Maps, XML, Content: Jenn Riley Relator Codes, MESH, Resource, PB Core, OAI-ORE, OAI-PMH, MARC, XML Schema, AACR2, CanCore, MARCXML, Sears List of Subject QDC, XML, XML OAIS, ONIX, OpenURL, Design: Devin Becker XPath, CIDOC/CRM, DCAM, GEM, OAI-ORE, RSS, Content Standard Headings, TGM I, TGM II, Schema, XPath, QDC, SRU, SWAP, TEI, IEEE/LOM, indecs, ISBD, Linked Data, SCORM, Sears Strong XQuery TextMD, XML, XML AAT, CCO, MADS, MARC Relator Codes, METS List of Subject TGN, ULAN , Z39.50 Headings, Topic XSL Schema, XPath, CDWA, CDWA Lite, Rights, MODS, MPEG-7, MuseumDat, Work funded by the Indiana University Librariesí Maps CDWA, MPEG-21 IEEE/LOM, AACR2, APPM, Z39.50 NewsML, ODRL, PREMIS, RAD, White Professional Development Award DIDL, VRA Core XSLT, Z39.50 DC, DIG35, DTD, METS, ISAD(G), CCO, DACS, RAD, RDA RDA, RDF, RELAX NG, SGML, MIX, MPEG-21 DIDL, OAI-PMH, NewsML, ISAAR(CPF), ISBD, RDF SKOS, SMIL, XMP, XOBIS, Visual SKOS OAIS, Ontology for Media Resource, PB XQuery, XrML Core, QDC, SRU, TGM I, TGM II, TGN, ULAN, CIDOC/CRM, FRAD, FRBR, FRSAD, VRA Core, XML, XML Schema, XPath, XSLT, Z39.50 Resources Conceptual Model indecs, OAIS, VSO Data Model OAIS GML EML, MEI, MusicXML, Atom, KML, MathML, RSS Copyright 2009-2010 Jenn Riley NewsML, SGML, XML AACR2, AAT, AGLS, APPM, Atom, DC, DCAM, BISAC, CanCore, CCO, CDWA, CDWA Lite, CIDOC/CRM, AAT, CCO, CDWA, CDWA Lite, CIDOC/CRM, AACR2, AES Core FOAF, indecs, MuseumDat, SPECTRUM, TGN, ULAN` Audio, AES Process DACS, DC, DCAM, DDC, DIF, DIG35, DwC, EAC-CPF, EAD, EML, AACR2, AGLS, DTD, OAI-PMH, VRA Linked Data, MIX, History, APPM, Data MODS, OAI-ORE, CanCore, DACS, FGDC/CSDGM, FOAF, FRAD, FRBR, FRSAD, GEM, GILS, GML, ID3, Core, XML, DDC, DwC, This work is licensed under a Creative Commons CQL, DDC, FRAD, Attribution-Noncommercial-Share Alike 3.0 United States License XMLSchema, XPath, OAIS, PREMIS, EAC-CPF, EAD, IEEE/LOM, indecs, ISAAR(CPF), ISAD(G), ISBD, ISO 19115, LCC, QDC, RDF, RSS, FGDC/CSDGM, <http://creativecommons.org/licenses/by-nc-sa/3.0/us/>. FRBR, FRSAD, GILS, XQuery, XSLT FRBR, GEM, LCSH, Linked Data, MADS, MARC, MARC Relator Codes, ISBD, LCC, LCSH, SGML, SKOS, IEEE/LOM, TGM I, ISAAR(CPF), ISAD(G), MARCXML, MESH, MO, MODS, MPEG-7, MuseumDat, ISO 19115, KML, LCC, MADS,
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.
    [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]