Big Data Governance and Metadata Management: Standards Roadmap
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Thinkjs 2.0 Documentation
ThinkJS 2.0 Documentation ᳪفள᭛ Օᕨ ጱ Node.js MVC ຝֵ҅አ ES7 Ӿ async/await ҅ᘏ ES6ݎෛقThinkJS ฎӞֵྃአ ES6/7 ᇙ තԧࢵٖक़ռग़ຝጱᦡᦇቘஷޕӾጱ */yield ᇙବᥴ٬ԧ Node.js Ӿྍ્ॺጱᳯ̶᷌ݶ ṛප̶̵ܔᓌےNode.js ᶱፓๅ ݎమ҅ᦏ පሲ҅ฎ۠ಅࣁ̶ଚӬෛᇇጱ Node.js ES6 ᇙԞํԧݎᶱፓݢզय़य़ṛݎአ ES6/7 ᇙֵ Զᇙᬮဌํඪ೮҅Ԟݢզۗ Babel ᖫᦲඪ೮̶ํֵܨঅጱඪ೮҅ ᇙ ᶱፓݎአ ES6/7 ᇙֵ ᇇӧඪ೮̶੦ٌฎֵڹۗ Babel ᖫᦲ҅ݢզࣁᶱፓӾय़ᙦֵአ ES6/7 ಅํጱᇙ҅෫ᵱஞߺԶᇙ୮ አ async/await ᘏ */yield ᥴ٬ྍࢧ᧣ጱᳯ̶᷌ JavaScript //user controller, home/controller/user.js export default class extends think.controller.base { //login action async loginAction(self){ //ইຎฎget᧗҅ፗളดᐏጭ୯ᶭᶎ if(this.isGet()){ return this.display(); } ᬯ᯾ݢզ᭗ᬦpostොဩ឴ݐಅํጱහഝ҅හഝ૪ᕪࣁlogic᯾؉ԧ໊ḵ// let data = this.post(); let md5 = think.md5('think_' + data.pwd); ᯈහഝପӾԭጱፓ܃ݸጱੂᎱ݄ੂےአಁݷ// let result = await this.model('user').where({name: data.name, pwd: md5}).find(); ձ֜හഝ҅ᤒᐏአಁݷᘏੂᎱᲙکᯈ܃ইຎ๚// if(think.isEmpty(result)){ return this.fail('login fail'); } sessionفٟ௳מݸ҅ਖ਼አಁ௳מአಁک឴ݐ// await this.session('userInfo', result); return this.success(); } } ӤᶎጱդᎱ౯ժֵአԧ ES6 ᯾ጱ class , export , let զ݊ ES7 ᯾ጱ async await ᒵᇙ҅ Session ᮷ฎྍ֢҅֕ۗ async/await ҅դᎱ᮷ฎݶྍԡٟጱ̶๋ݸֵ فᡱᆐັᧃහഝପٟ አ Babel ᬰᤈᖫᦲ҅੪ݢզᑞਧᬩᤈࣁ Node.js ጱሾहӾԧ̶ ඪ೮ग़ᐿᶱፓᕮग़ᐿᶱፓሾह ̶ݎཛྷࣘཛྷୗᒵग़ᐿᶱፓᕮ҅ݢզჿ᪃ݱᐿᶱፓ॔ଶጱړཛྷࣘཛྷୗ̵ฦ᭗ཛྷୗ̵ܔᶱፓඪ೮ ἕᦊඪ೮ development ҅ testing prodution 3 ᐿᶱፓሾह҅ݢզࣁӧݶጱᶱፓሾहӥᬰᤈӧݶ ጱᯈᗝ҅ჿ᪃ࣁӧݶሾहӥጱᯈᗝᵱ҅ݶᬮݢզचԭᶱፓᵱᥝᬰᤈಘ̶ ඪ೮ӿጱහഝପ ThinkJS ඪ೮ mysql ҅ mongodb ҅ sqlite ᒵଉᥠጱහഝପ҅ଚӬᤰԧஉग़֢හഝପጱളݗ҅෫ᵱ ᚆ̶ۑᘶཛྷࣳᒵṛᕆى̵ۓᄋ၏̶ݶඪ೮Ԫقᒵਞفಋۖ೪ള SQL ݙ҅ᬮݢզᛔۖᴠྊ SQL ဳ դᎱᛔۖๅෛ Ԟӧአۗᒫӣ҅ۓNode.js ๐ ސኞප҅ӧአ᯿ܨදݸᒈץկ҅ګThinkJS ٖᗝԧӞॺդᎱᛔۖๅෛጱ ොཛྷ̶ࣘ ୌ REST ളݗڠᛔۖ ইຎమࣁ̶ݎݢਠ౮ REST API ጱܨୌ REST -
Metadata Demystified: a Guide for Publishers
ISBN 1-880124-59-9 Metadata Demystified: A Guide for Publishers Table of Contents What Metadata Is 1 What Metadata Isn’t 3 XML 3 Identifiers 4 Why Metadata Is Important 6 What Metadata Means to the Publisher 6 What Metadata Means to the Reader 6 Book-Oriented Metadata Practices 8 ONIX 9 Journal-Oriented Metadata Practices 10 ONIX for Serials 10 JWP On the Exchange of Serials Subscription Information 10 CrossRef 11 The Open Archives Initiative 13 Conclusion 13 Where To Go From Here 13 Compendium of Cited Resources 14 About the Authors and Publishers 15 Published by: The Sheridan Press & NISO Press Contributing Editors: Pat Harris, Susan Parente, Kevin Pirkey, Greg Suprock, Mark Witkowski Authors: Amy Brand, Frank Daly, Barbara Meyers Copyright 2003, The Sheridan Press and NISO Press Printed July 2003 Metadata Demystified: A Guide for Publishers This guide presents an overview of evolving classified according to a variety of specific metadata conventions in publishing, as well as functions, such as technical metadata for related initiatives designed to standardize how technical processes, rights metadata for rights metadata is structured and disseminated resolution, and preservation metadata for online. Focusing on strategic rather than digital archiving, this guide focuses on technical considerations in the business of descriptive metadata, or metadata that publishing, this guide offers insight into how characterizes the content itself. book and journal publishers can streamline the various metadata-based operations at work Occurrences of metadata vary tremendously in their companies and leverage that metadata in richness; that is, how much or how little for added exposure through digital media such of the entity being described is actually as the Web. -
Compiler Error Messages Considered Unhelpful: the Landscape of Text-Based Programming Error Message Research
Working Group Report ITiCSE-WGR ’19, July 15–17, 2019, Aberdeen, Scotland Uk Compiler Error Messages Considered Unhelpful: The Landscape of Text-Based Programming Error Message Research Brett A. Becker∗ Paul Denny∗ Raymond Pettit∗ University College Dublin University of Auckland University of Virginia Dublin, Ireland Auckland, New Zealand Charlottesville, Virginia, USA [email protected] [email protected] [email protected] Durell Bouchard Dennis J. Bouvier Brian Harrington Roanoke College Southern Illinois University Edwardsville University of Toronto Scarborough Roanoke, Virgina, USA Edwardsville, Illinois, USA Scarborough, Ontario, Canada [email protected] [email protected] [email protected] Amir Kamil Amey Karkare Chris McDonald University of Michigan Indian Institute of Technology Kanpur University of Western Australia Ann Arbor, Michigan, USA Kanpur, India Perth, Australia [email protected] [email protected] [email protected] Peter-Michael Osera Janice L. Pearce James Prather Grinnell College Berea College Abilene Christian University Grinnell, Iowa, USA Berea, Kentucky, USA Abilene, Texas, USA [email protected] [email protected] [email protected] ABSTRACT of evidence supporting each one (historical, anecdotal, and empiri- Diagnostic messages generated by compilers and interpreters such cal). This work can serve as a starting point for those who wish to as syntax error messages have been researched for over half of a conduct research on compiler error messages, runtime errors, and century. Unfortunately, these messages which include error, warn- warnings. We also make the bibtex file of our 300+ reference corpus ing, and run-time messages, present substantial difficulty and could publicly available. -
Mapping Topic Maps to Common Logic
MAPPING TOPIC MAPS TO COMMON LOGIC Tamas´ DEMIAN´ Advisor: Andras´ PATARICZA I. Introduction This work is a case study for the mapping of a particular formal language (Topic Map[1] (TM)) to Common Logic[2] (CL). CL was intended to be a uniform platform ensuring a seamless syntactic and semantic integration of knowledge represented in different formal languages. CL is based on first-order logic (FOL) with a precise model-theoretic semantic. The exact target language is Common Logic Interchange Format (CLIF), the most common dialect of CL. Both CL and TM are ISO standards and their metamodels are included in the Object Definition Metamodel[3] (ODM). ODM was intended to serve as foundation of Model Driven Architecture (MDA) offering formal basis for representation, management, interoperability, and semantics. The paper aims at the evaluation of the use of CL as a fusion platform on the example of TM. II. The Topic Maps TM is a technology for modelling knowledge and connecting this structured knowledge to relevant information sources. A central operation in TMs is merging, aiming at the elimination of redundant TM constructs. TopicMapConstruct is the top-level abstract class in the TM metamodel (Fig. 1). The later detailed ReifiableConstruct, TypeAble and ScopeAble classes are also abstract. The remaining classes are pairwise disjoint. Figure 1: The class hierarchy and the relation and attribute names of the TM metamodel. TopicMap is a set of topics and associations. Topic is a symbol used within a TM to represent exactly one subject, in order to allow statements to be made about that subject. -
Towards the Second Edition of ISO 24707 Common Logic
Towards the Second Edition of ISO 24707 Common Logic Michael Gr¨uninger(with Tara Athan and Fabian Neuhaus) Miniseries on Ontologies, Rules, and Logic Programming for Reasoning and Applications January 9, 2014 Gr¨uninger ( Ontolog Forum) Common Logic (ISO 24707) January 9, 2014 1 / 20 What Is Common Logic? Common Logic (published as \ISO/IEC 24707:2007 | Information technology Common Logic : a framework for a family of logic-based languages") is a language based on first-order logic, but extending it in several ways that ease the formulation of complex ontologies that are definable in first-order logic. Gr¨uninger ( Ontolog Forum) Common Logic (ISO 24707) January 9, 2014 2 / 20 Semantics An interpretation I consists of a set URI , the universe of reference a set UDI , the universe of discourse, such that I UDI 6= ;; I UDI ⊆ URI ; a mapping intI : V ! URI ; ∗ a mapping relI from URI to subsets of UDI . Gr¨uninger ( Ontolog Forum) Common Logic (ISO 24707) January 9, 2014 3 / 20 How Is Common Logic Being Used? Open Ontology Repositories COLORE (Common Logic Ontology Repository) colore.oor.net stl.mie.utoronto.ca/colore/ontologies.html OntoHub www.ontohub.org https://github.com/ontohub/ontohub Gr¨uninger ( Ontolog Forum) Common Logic (ISO 24707) January 9, 2014 4 / 20 How Is Common Logic Being Used? Ontology-based Standards Process Specification Language (ISO 18629) Date-Time Vocabulary (OMG) Foundational UML (OMG) Semantic Web Services Framework (W3C) OntoIOp (ISO WD 17347) Gr¨uninger ( Ontolog Forum) Common Logic (ISO 24707) January 9, 2014 -
Fundamentals of C Programming
Index Fundamentals of C Programming .............................................................................................. 3 Discrete Mathematics ............................................................................................................... 3 Fundamentals of Data Structures .............................................................................................. 5 Fundamentals of Logic and Computer Design ........................................................................... 7 Laboratory for Fundamentals of Logic and Computer Design ................................................ 10 Object-Oriented Programming (C++) ...................................................................................... 12 Database Systems .................................................................................................................... 14 Computer Organization ........................................................................................................... 14 Laboratory for Computer Organization ................................................................................... 16 Java Programming ................................................................................................................... 18 Principles of Database System ................................................................................................ 20 Advanced Data Structures and Algorithm Analysis ................................................................. 22 E-commerce Technologies ..................................................................................................... -
Metadata Standards
Chapter 3 METADATA STANDARDS This chapter lists the major metadata standards in use or under development. Standards are subdivided into six areas: general, transportation models, educa- tion, media-specific, preservation, and rights. Each standard lists its official URL, sponsoring agency, community of use, purpose and goals, description, potential for information organizations, and key projects. General metadata standards General metadata standards are the most common, well-known, and univer- sally accepted schemas to date. Some are general and meant to be used as universal or common-denominator standards; others are for specific communi- ties with specific information resources. Most of the metadata standards listed here have emerged as practical applications in use, or will probably emerge as the most commonly applied standards, due to broad international support, history and development, or industry application and acceptance. Dublin Core Metadata Initiative (DCMI) http://dublincore.org The Dublin Core Metadata Initiative (DCMI) is managed by an international board of trustees, but most of the direction and maintenance of the standard has been led by the Online Computer Library Center (OCLC) in Dublin, Ohio. Community of use Library Technology Reports Librarians, Web content providers, Web resource creators, metadata creators, and general public. Purpose and goals Dublin Core assists in the discovery and description of Web and electronic resources. It is designed to provide a simple descriptive metadata standard extensible to Web resources of any format or subject domain. Description www.techsource.ala.org Dublin Core is a set of 15 core elements that assist in simple description and discovery of electronic resources. The standards basic principles are the reasons for its success as a viable common-denominator metadata standard for elec- tronic resources. -
A Framework of Guidance for Building Good Digital Collections
A Framework of Guidance for Building Good Digital Collections 3rd edition December 2007 A NISO Recommended Practice Prepared by the NISO Framework Working Group with support from the Institute of Museum and Library Services 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. This recommended practice may be revised or withdrawn at any time. For current information on the status of this publication contact the NISO office or visit the NISO website (www.niso.org). Published by National Information Standards Organization (NISO) One North Charles Street, Suite 1905 Baltimore, MD 21201 www.niso.org Copyright © 2007 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, provided it is reproduced accurately, the source of the material is identified, and the NISO copyright status is acknowledged. All inquires regarding translations into other languages or commercial reproduction or distribution should be addressed to: NISO, One North Charles Street, Suite -
Interoperability As Desideratum, Problem, and Process
Interoperability as Desideratum, Problem, and Process Gary Richmond City University of New York [email protected] Copyright © by Aalborg University Press 2006 Abstract. In a global environment more and more influenced by the use of Internet technology in distributed settings, issues of interoperability have become crucial for business and governments, and in fact for all individuals and organizations employing it and increasingly dependent on it. We analyze three inter-related but distinct levels of interoperability, the syntactic, semantic and pragmatic, and discuss some of the interoperability issues related especially to the semantic and pragmatic levels. We briefly look at the relationship between philosophical Ontology and ontology as the term is used in AI, suggesting that especially the scientific metaphysics (Ontology) of Charles Peirce might be of value in helping KR workers generally and ontologists in particular to uncover possibly hidden ontological commitments. We then consider John Sowa’s Unified Framework (UF) approach to semantic interoperability which recommends the adoption of the draft ISO standard for Common Logic, and touch upon how CGs could be effectively employed within this framework. The promise of Service Oriented Architectures (SOA) in consideration of real world applications is remarked, and it is suggested how in a fast paced and continuously changing environment, loose coupling may be becoming a necessity—not merely an option. We conclude that, while the future of network interoperability is far from certain, our communities at least can begin to act in concert within our particular fields of interest to come to agreement on those “best in class” theories, methods, and practices which could become catalysts for bringing about the cultural change whereas interoperability, openness, and sharing are seen as global desiderata. -
Using Common Logic
Using Common Logic = Mapping other KR techniques to CL. = Eliminating dongles. = The zero case Pat Hayes Florida IHMC John Sowa talked about this side. Now we will look more closely at this side, using the CLIF dialect. Wild West Syntax (CLIF) Any character string can be a name, and any name can play any syntactic role, and any name can be quantified. Anything that can be named can also be the value of a function. All this gives a lot of freedom to say exactly what we want, and to write axioms which convert between different notational conventions. It also allows many other 'conventional' notations to be transcribed into CLIF directly and naturally. It also makes CLIF into a genuine network logic, because CLIF texts retain their full meaning when transported across a network, archived, or freely combined with other CLIF texts. (Unlike OWL-DL and GOFOL) Mapping other notations to CLIF. 1. Description Logics Description logics provide ways to define classes in terms of other classes, individuals and properties. All people who have at least two sons enlisted in the US Navy. <this class> owl:intersectionOf [:Person _:x] _:x rdf:type owl:Restriction _:x owl:minCardinality "2"^^xsd:number _:x owl:onProperty :hasSon _:x owl:toClass _:y _:y rdf:type owl:Restriction _:y owl:hasValue :USNavy _:y owl:onProperty :enlistedIn Mapping other notations to CLIF. 1. Description Logics Classes are CL unary relations, properties are CL binary relations. So DL operators are functions from relations to other relations. (owl:IntersectionOf Person (owl:minCardinality 2 hasSon (owl:valueIs enlistedIn USNavy))) (AND Person (MIN 2 hasSon (VAL enlistedIn USNavy))) ((AND Person (MIN 2 hasSon (VAL enlistedIn USNavy))) Harry) (= 2ServingSons (AND Person (MIN 2 hasSon (VAL enlistedIn USNavy)))) (2ServingSons Harry) (NavyPersonClassification 2ServingSons) (BackgroundInfo 2ServingSons 'Classification introduced in 2003 for public relation purposes.') Mapping other notations to CLIF. -
View, Laboratory Or Research Protocol
Uciteli et al. Journal of Biomedical Semantics 2011, 2(Suppl 4):S1 http://www.jbiomedsem.com/content/2/S4/S1 JOURNAL OF BIOMEDICAL SEMANTICS PROCEEDINGS Open Access An ontologically founded architecture for information systems in clinical and epidemiological research Alexandr Uciteli1*, Silvia Groß1,2, Sergej Kireyev1, Heinrich Herre1* From Ontologies in Biomedicine and Life Sciences (OBML 2010) Mannheim, Germany. 9-10 September 2010 * Correspondence: alexander. Abstract [email protected]; [email protected] This paper presents an ontologically founded basic architecture for information 1 Institute for Medical Informatics, systems, which are intended to capture, represent, and maintain metadata for various Statistics and Epidemiology (IMISE), University of Leipzig, Germany domains of clinical and epidemiological research. Clinical trials exhibit an important basis for clinical research, and the accurate specification of metadata and their documentation and application in clinical and epidemiological study projects represents a significant expense in the project preparation and has a relevant impact on the value and quality of these studies. An ontological foundation of an information system provides a semantic framework for the precise specification of those entities which are presented in this system. This semantic framework should be grounded, according to our approach, on a suitable top-level ontology. Such an ontological foundation leads to a deeper understanding of the entities of the domain under consideration, and provides a common unifying semantic basis, which supports the integration of data and the interoperability between different information systems. The intended information systems will be applied to the field of clinical and epidemiological research and will provide, depending on the application context, a variety of functionalities. -
Metadata for the Open Data Portals
Metadata for the open data portals Discussion Paper No. 6, December 2016, Joined-up Data Standards Project Beata Lisowska Data Scientist, Development Initiatives Contents Introduction .............................................................................................................................. 2 Platforms used for open data portals ...................................................................................... 3 Metadata standards .................................................................................................................. 4 Core metadata standards ........................................................................ 5 RDF Data Cube vocabulary .................................................................... 5 Dublin Core ............................................................................................ 5 Data Catalog Vocabulary (DCAT) ........................................................... 6 Other metadata standards ...................................................................... 6 Geographic metadata standards ............................................................. 6 ISO 19115 .............................................................................................. 6 Open data portals and metadata ............................................................................................. 8 Socrata and CKAN ................................................................................... 8 DKAN .......................................................................................................