1、American National StandardDeveloped byfor Information Technology Vocabulary Description and ManagementINCITS 532-2014INCITS 532-2014INCITS 532-2014American National Standardfor Information Technology Vocabulary Description andManagementSecretariatInformation Technology Industry CouncilApproved Augus
2、t 15, 2014American National Standards Institute, Inc.Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI
3、Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be mad
4、etowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the s
5、tandards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the Ameri
6、canNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National Standard
7、sInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican
8、National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2014 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI
9、, 1101 K Street NW, Suite 610, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developer
10、s nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims ha
11、ve been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.i Contents Page Foreword.iii Introduction v 1 Scope 1 2 Nor
12、mative references 1 3 Terms and definitions . 2 4 Vocabulary contents model . 3 4.1 Introduction 3 4.2 Assumptions 3 4.3 Model 4 4.4 Context . 8 5 Registry model . 8 5.1 Introduction: 8 5.2 Registration attributes: . 9 5.3 Registry Model . 13 6 Registration procedures . 18 6.1 Introduction 18 6.2 Co
13、ncept of Operations 19 6.2.1 Kinds of items to register . 19 6.2.2 Item identifiers . 19 6.2.3 Statuses 19 6.2.4 Quality Guidelines . 21 6.2.5 Procedures Overview 21 6.3 Roles and Responsibilities . 22 6.3.1 Introduction 22 6.3.2 Roles General 22 6.3.3 Role of Registration Authorities (RA) 22 6.3.4
14、Role of RA Registrar . 23 6.3.5 Role of RA Executive Committee . 23 6.3.6 Role of RA Control Committee . 23 6.3.7 Role of Stewards . 23 6.3.8 Role of Submitters . 23 6.3.9 Role of All Others 23 6.3.10 Role of Read-only User . 23 6.3.11 Responsibilities of Registration Authorities (RA) 23 6.3.12 Resp
15、onsibilities of Stewards . 24 6.3.13 Responsibilities of Submitters . 25 6.3.14 Responsibilities of Registrar 25 6.3.15 Responsibilities of Read-only Users . 26 6.3.16 Responsibilities of Control Committee . 26 6.3.17 Responsibilities of Executive Committee (ExCom) . 27 6.4 Procedures: 27 6.4.1 Revi
16、ew and Response. 27 6.4.2 Rejection Criteria . 28 6.4.3 Revision and Review Procedures General 28 ii 6.4.4 Revision and Review Procedures Revision . 28 6.4.5 Revision and Review Procedures Review . 28 6.4.6 Change Management Procedures . 29 7 Conformance . 29 LLiForeword (This foreword is not part o
17、f American National Standard INCITS 532-2014.)This standard addresses the description and management of open vocabularies. Themain purposes of this is to support data interchange and data interoperability acrossorganizations, systems, subject, time, and geography. This standard specifies threemain i
18、deas: - A model for the contents of a vocabulary (clause 4);- A model for a registry of vocabularies (clause 5); and- A set of procedures for managing a vocabulary registration process (clause 6).Requests for interpretation, suggestions for improvement or addenda, or defect re-ports are welcome. The
19、y should be sent to InterNational Committee for InformationTechnology Standards (INCITS), ITI, 1101 K Street, NW, Suite 610, Washington, DC20005.This standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not necessarily imply that all committe
20、e mem-bers voted for its approval. At the time it approved this standard, INCITS had thefollowing members:Philip Wennblom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems Inc. Scott FosheeSteve Zilles (Alt.)AIM Global, Inc. Steve HallidayMary Lou Bosco (Al
21、t.)Chuck Evanhoe (Alt.)Dan Kimball (Alt.)Apple Helene WorkmanMarc Braner (Alt.)David Singer (Alt.)Distributed Management Task Force John Crandall Jeff Hilland (Alt.)Lawrence Lamers (Alt.)EMC Corporation . Gary Robinson Stephen Diamond (Alt.)Farance, Inc Frank Farance Timothy Schoechle (Alt.)Futurewe
22、i Technologies, Inc. Yi ZhaoWilbert Adams (Alt.)Timothy Jeffries (Alt.)GS1GO. Frank SharkeyCharles Biss (Alt.)Hewlett-Packard Company Karen Higginbottom Paul Jeran (Alt.)IBM Corporation Steve HolbrookAlexander Tarpinian (Alt.)IEEE . Jodi HaaszChristy Bahn (Alt.)Noelle Humerick (Alt.)Don Wright (Alt.
23、)Intel Philip Wennblom Stephen Balogh (Alt.)Grace Wei (Alt.)Microsoft Corporation . Jim Hughes John Calhoon (Alt.)Laura Lindsay (Alt.)iYOrganization Represented Name of RepresentativeNational Institute of Standards example: car (whole) body, engine, wheels (parts); illustrated with line headed by tr
24、iangle Generic (type / sub-type) line with diamond shaped head; example: car (type) Ford, Fiat, Ferrari (sub-type); illustrated with line headed by diamond Associations illustrated with line Association classes illustrated by dotted line from relationship to class of attributes 4.3 Model The model i
25、s presented in parts, which build up the understanding from first principles. It is assumed that in any information system built to conform to this model, identifiers for each record (primary keys in relational databases) are used and references to objects in relationships (foreign keys in the relat
26、ional databases) are also used. They are not represented in these pictures. Figure 1 Objects Since objects (Figure 1) are anything perceivable or conceivable, and concepts are units of thought, they are conceivable objects. Other objects include the other things we need to keep track of: Concept Sys
27、tems, Namespaces, and Vocabularies. INCITS 532-2014 5 Figure 2 Concepts This model describes concepts (Figure 2). They require definitions, which take 2 basic forms (described in ISO 704): Intensional definition of a concept based on reference to a super-ordinate concept and the characteristics that
28、 distinguish it from that super-ordinate concept Extensional definition of a concept based on an enumeration of sub-ordinate concepts which partition its extension Signifiers, used to designate Concepts, are Concepts themselves. The Extension of a Signifier contains only perceivable Objects, and it
29、is these Objects which appear in print, on road signs, etc that people perceive. Here are two examples of a signifier, the numeral five: 5 and 5. Relations are also Concepts, and their Extensions contain Tuples (ordered sets see Figure 6) of other Concepts or Objects. This corresponds to the usual m
30、athematical definition of a relationship. Figure 3 Labels and Designations Labels (Figure 3) are how humans and machines refer to Objects and Concepts. A Designation (Figure 3) is a Label applied to a Concept. Identifiers and locators are also kinds of Labels, but they are not shown in this model.IN
31、CITS 532-2014 6 Figure 4 Designations Designations (Figure 4) have a parallel structure to Labels, and they are a kind of Label. NamespaceLabel0*0*+Contains+Contained inAggregateFigure 5 Namespaces A Namespace (Figure 5) is a set of Labels. This means that the elements of a Namespace are assumed to
32、refer to objects. They do not contain arbitrary collections of strings, say. A code set in statistics contains a Namespace the set of codes, each of which designates a concept. Concept systems (Figure 6) are sets of concepts structured by the relations among them. Hierarchies are kinds of concept sy
33、stems that have the additional feature of levels. Levels are ordered, and the concepts in adjacent levels are related by the same hierarchical relation. An example in the US is the Standard Occupational Classification (SOC) at http:/www.bls.gov/soc/. INCITS 532-2014 7 Figure 6 Concept Systems Every
34、label in a Namespace used by some vocabulary must be a designation of some concept in the related Concept System. Each concept may have more than one designation, either in the one Namespace or many.VocabularyConcept System0n1conceptsNamespace0n0ndesignations01 0nFigure 7 Vocabularies Vocabularies (
35、Figure 7) are Concept Systems with Designations for each concept provided. A Concept may have more than one Designation. INCITS 532-2014 8 The idea that a Concept System might be part of more than one Vocabulary is the same as realizing the codes used in a code set are replaceable, for instance cons
36、ider the alpha-2 and alpha-3 columns in ISO 3166-1 Country Codes. The United States of America may be designated as US (alpha-2) or USA (alpha-3) and Afghanistan may be designated AF (alpha-2) and AFG (alpha-3). Each set of codes has the same underlying meanings associated with them. 4.4 Context Con
37、text loosely refers to the circumstances or perspective that provides additional meaning to some concept. For instance, the idea of nearness means something different if one is describing people versus describing galaxies. For Open Vocabularies, the context of a Concept is manifested through the pos
38、ition a Concept holds within some Vocabulary (i.e., the relations that exist for that Concept) and the Vocabulary as a whole the concept resides in. For instance, the concept of a wheel means something slightly different when considering the exterior of an automobile versus the interior of one. In t
39、he exterior, wheel refers to the device on which a tire is mounted. On the other hand, within the interior, wheel refers to the device used to influence the left/right direction of the motion of the automobile. In both instances, the same basic idea is being conveyed, yet there are characteristics o
40、f each that are different. This has consequences for how to refer to a concept in applications. Two URIs must be used: URI for the concept URI for the vocabulary within which the concept resides The URI for the vocabulary is not necessarily implied by the URI for the concept. Take the “wheel” exampl
41、e described in the above paragraph. The base concept for wheel need not be defined in either the vocabulary for exterior of an automobile or for the interior. 5 Registry model 5.1 Introduction: This document contains a general description of registration for open vocabularies, comprised of a set of
42、registration attributes and a registry model. The modelling diagrams throughout this document use a Unified Modeling Language (UML) notational format, with underlying assumptions limited to those appearing elsewhere in this document. We offer the following semantic interpretation with respect to tha
43、t which is represented by these models: Boxes (look like UML classes) represent concepts and instances are objects in the extension of that concept. The lines representing relationships are instances of the relations defined in ISO 1087-1: Hierarchical (super-ordinate / sub-ordinate) relations Parti
44、tive (whole / part) line with triangle shaped head; example: car (whole) body, engine, wheels (parts); illustrated with line headed by triangle Generic (type / sub-type) line with diamond shaped head; example: car (type) Ford, Fiat, Ferrari (sub-type); illustrated with line headed by diamond INCITS
45、532-2014 9 Associations illustrated with line Association classes illustrated by dotted line from relationship to class of attributes 5.2 Registration attributes: This subclause contains a set of attributes for describing: a vocabulary as a set; a controlled list of possible vocabulary types; and a
46、list of high-level vocabulary subject headings. The attributes specified describe the vocabulary as a container but do not describe the contents. The description of the contents is detailed in the document titled “Open Government Vocabularies Content Model”. These attributes, which are similar to th
47、ose specified in the Dublin Core, should be used for cataloging vocabularies. These attributes are intended to be available to support searches and the high-level discovery of vocabularies. The attributes and their definitions are defined in Table 1 below. This is a list of attributes that shall be
48、filled out for submitting a vocabulary to a registry. Table 1 Vocabulary Registry Metadata Attributes Element URI Element Occurrence min,max Description Example Title 1,1 Official name of the vocabulary. Standard Occupational Classification Abbreviated Title 1,1 Short title or abbreviation by which
49、this vocabulary is popularly known. SOC Version 1,1 For vocabularies that are updated periodically, the number for this version. 2010 Description 1,1 Detailed explanation of the nature and purpose of it. See http:/www.bls.gov/opub/mlr/2010/08/art3full.pdf Submitter Contact Information 1,1 Submitter is entity responsible for presenting a vocabulary description for registration. Relevant attributes for specifying contact information are found in ISO/IEC 19773:2011 Clause 19 Entity-Person-Group Cont
