Results for area 10.2 Data, data dictionaries and registers
data element that cannot be further subdivided meaningfully within the context of ASN.1
data about a living individual, identified or identifiable, as determined by the privacy laws and conventions of a political jurisdiction
set of data grouped together for transmission
occurrence of a message containing the actual values for the data elements and, in some cases, data about the message
registration process to store data definitions, characterized in a consistent manner, as determined according to the provisions of ISO 14817, used for a specific purpose (in this case ITS/TICS)
NOTE The data registration process provides a determination of the ITS Data Dictionary items accepted into the ITS/TICS Data Registry. The Data Registry contains not only data about data concepts in terms of their names and representational forms but also substantial data about the semantics or meaning associated with the data concepts. A Data Registry may contain data that assists information interchange and reuse, both from the perspective of human users and for machine-interpretation of data concepts. The Data Registry is comprised of items only from ITS/TICS Data Dictionaries, showing their source; however, not all ITS/TICS Data Dictionary items shall necessarily be submitted for inclusion, or accepted, into the Data Registry.
organized and constructed (electronic data base) compilation of descriptions of data concepts that provides a consistent means for documenting, storing and retrieving the syntactical form (i.e. representational form) and the meaning and connotation of each data concept
any of a group of data structures (i.e. object class, property, value domain, data elements, message, interface dialogue, association) referring to abstractions or things in the natural world that can be identified with explicit boundaries and meaning and whose properties and behaviour all follow the same rules
description of the organization of data in a manner that reflects an information structure
NOTE See also information model.
data concept; grouping of data elements primarily for the purpose of referring to the group with a single name, and thereby efficiently reusing groups of data elements that commonly appear together (e.g. ASN.1 SEQUENCE, SEQUENCE OF, SET, SET OF or CHOICE) in a message specification
NOTE This data concept type may be used to specify groups of data elements for other purposes as well.
acceptable standard of accuracy of personal data
prevention of misuse of computer data: legal safeguards to prevent misuse of information stored on computers, particularly information about individual people
data concept; an expression of the inherent concept embodied in a data element without regard to the value domain(s) by which it can be physically represented.
NOTE A data element concept is represented by an object class and a property of that object class.
individual occurrence of a data concept
meaning, including concept(s), associated with a given data concept
structure of expressions in a language and the rules governing the structure of a language
process by which data is formally described and provided to an approved location in the Data Registry
NOTE This process is effected under the control of the ITS/TICS data registrar, in accordance with the requirements of ISO 14817.
organizational element or an individual appointed by ISO/TC 204 to undertake the day-to-day management of the Data Registry process
limits to the collection of personal data
types defined by directly specifying the set of its values
<XML> create new types (both simple and complex)
NOTE 1 to entry: It is additional information about a piece of data (element). Often attributes are used to pass information about the element and hence can be said to provide metadata for the element. An attribute is a value indicator (=) and the attribute value is specified within the tag (i.e. <H3 align=”centre”>). Attribute in XML is a name=”value” pair that can be placed in the start tag of an element. For XML, all values have to be quoted with single or double quotes.
any documenting characteristic of a data concept
indexical term used by humans as a means of identifying data elements and other data concepts
data type (or type for short) that represents in a formalised way a class of information (for example, numerical, textual, still image or video information); the representation is conformant to definitions given in ISO/IEC 8824-1
type definition that does not conform to ISO/IEC 8824
definition of the content and structure of data using an ASN.1 type definition
type which is used only for defining the value and subtype notation for a type
NOTE Associated types are defined when it is necessary to make it clear that there may be a significant difference between how the type is defined in ASN.1 and how it is encoded. Associated types do not appear in user specifications.
one or more instances of the use of the ASN.1 notation for type, value, value set, information object class, information object, and information object set (as well as the parameterized variant of those), encapsulated using the ASN.1 module notation [ISO/IEC 8824)
set of rules for encoding electronic documents define by the World Wide Web Consortium W3C
NOTE Although developed for documents, it is today widely used for data exchange in general, usually in conjunction with an XML Schema Definition
atomic constituent of the UML model logical data structure within an XML document, a piece of data within a file [XML]
NOTE An XML element consists of a start tag, and end tag, and the information between the tags, which is often referred to as the contents. Start tags and end tags show the beginning and end of an element. A schema that can provide a description of the structure of the data describes elements used in an XML file.
a formal description of the allowed content of an XML document that claims compliance to the schema; XML Schema Definitions allow for formal validation of syntactical compliance of instance documents
<XML> processor that reads an XML document and determines the structure and properties of the data
Note 1 to entry: If the parser goes beyond the XML rules for conformance and validates the document against an XML schema, the parser is said to be a “validating” parser. A generalized XML parser reads XML files and generates a hierarchically structured tree, then hands off data to viewers and other applications for processing.
A validating XML parser also checks the XML syntax and reports errors.
really simple syndication comprises a Web feed format used to publish frequently updated sources of information
<XML> set of unique identifiers
NOTE 1 to entry: Namespace is a mechanism to resolve naming conflicts between elements in an XML document when each comes from a different vocabulary. It allows the commingling of like tag names from different namespaces. A namespace identifies an XML vocabulary defined within a URN. An attribute on an element, attribute, or entity reference associates a short name with the URN that defines the namespace; that short name is then used as a prefix to the element, attribute, or entity reference name to uniquely identify the namespace.
Namespace references have scope. All child nodes beneath the node that specifies the namespace inherit that namespace. This allows nonqualified names to use the default namespace.
<XML> short name to uniquely identify the namespace profile
<UML> stereotyped package that contains model elements, which have been customized for a specific domain or purpose using extension mechanisms, such as stereotypes, tagged definitions and constraints
Note 1 to entry: A profile may also specify model libraries on which it depends and the metamodel subset that it extends.
<XML> identification of element types and structure within a document
NOTE 1 to entry: The mark-up is not actually part of the content, but identifies the components and their roles.
<UML> explicit definition of a property as a name-value pair
NOTE 1 to entry: Certain tags are predefined in the UML; others MAY be user defined. Tagged values are one of three extensibility mechanisms in UML.
NOTE 2 to entry: In a tagged value, the name is referred as the tag.
<UML> endpoint of an association, which connects the association to a classifier
instance of some information object class, being composed of a set of fields which conform to field specification of the class; graphical representation that logically organizes various data concepts by depicting key relationships among the data concepts
EXAMPLE An information model might specify that a Vehicle may be described by a variety of properties, such as: Make, Model, Year, and Vehicle Identification Number. Likewise a Collision might be described by properties such as Time of Occurrence, Severity, and Number of Vehicles Involved. Finally, the model might depict that a Collision has a many-to-many relationship to a Vehicle.
NOTE Information models can be depicted using UML Class Diagrams.
<UML> description of a set of objects that share the same attributes, operations, methods, relationships, and semantics
set of fields, forming a template for the definition of a potentially unbounded collection of information objects, the instances of the class
simple type whose values are the set of all object identifiers allocated in accordance with the rules of the ISO/IEC 9834 series
semantic relationship between classes
association where the target class is an aggregate; therefore the source class is a part
NOTE 1 to entry This characteristic is expressed in UML with an attribute named “aggregation” on the target side Association End being set to “aggregate”
association that connects exactly two classes
<UML> endpoint of an association, which connects the association to a classifier
association where the target class is a composite; therefore the source class is a part that is strongly owned by the composite and may not be part of any other composite
NOTE This characteristic is expressed in UML with an attribute named “aggregation” on the target side Association End being set to “composite”.
dependency states that the implementation or functioning of one or more elements requires the presence of one or more other elements
data type whose range is a list of predefined values, called enumeration literals
element of the run-time extension of an Enumeration data type
NOTE It has no relevant substructure, that is, it is atomic. The enumeration literals of a particular Enumeration data type are ordered.
instance of an object identifier type which relates to an associated module
NOTE In ISO/IEC 8824 a module identifier is defined as: ModuleIdentifier::= modulereference DefinitiveIdentifier If the "DefinitiveIdentifier" is not empty, the denoted object identifier value unambiguously and uniquely identifies the module being defined. No defined value may be used in defining the object identifier value.
reference identifiers which relate to prescribed Sub Modules determined in subordinate Standards
<UML> new type of modelling element that extends the semantics of the metamodel
NOTE 1 to entry: Stereotypes have to be based on certain existing types or classes in the metamodel. Stereotypes may extend the semantics, but not the structure of pre-existing types and classes. Certain stereotypes are predefined in the UML, others may be user defined. Stereotypes are one of three extensibility mechanisms in UML.
NOTE 2 to entry: The stereotype may specify additional constraints and tag definitions that apply to model elements. In addition, a stereotype may be used to indicate a difference in meaning or usage between two model elements with identical structure.
<XML> enable elements and attributes with specific names and types (both simple and complex) to appear in document instances
<UML> diagram that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships
data concept; collection of all the temporal sequences of messages, including variants such as multiple responses, that are used to accomplish the services that the interface dialogue provides
rights of an invididual to have access to personal data held about the individual and ability to challenge and correct such data
<XML> set of valid literals for a data type
<UML> semantic condition or restriction
NOTE 1 to entry: Certain constraints are predefined in the UML, others may be user defined. Constraints are one of three extensibility mechanisms in UML.
limits to the purposes which personal data can be used
policy of openness about developments, practices and policies with respect to personal data
formal set of production rules that comprise a grammar defining language, such as XML
language for defining interfaces to CORBA objects which is independent of platform, operating system and programming language
IRI compact string of characters for identifying an abstract or physical resource
globally unique identifier that is unique in space and time, i.e. no other object will ever have the same identifier at any other place and at any time
protocol for transmitting private information via the Internet by using public and private keys to encrypt data
inter ORB protocol that defines the message formats between ORBs in a distributed environment
inter ORB protocol that allows ORBs to use the Internet as a communications bus by mapping inter ORB messages onto TCP/IP
NOTE This is an implementation of GIOP.
data concept; expression of a specific and explicit representation of some information about something of interest within the ITS/TICS domain
XML based specification for the interoperable exchange of metadata
NOTE It is today most commonly used to exchange UML models between UML tools. XMI is specified in ISO/IEC 19503:2005.
characteristic of information, which prevents the possibility to determine directly or indirectly the identity of the data subject
process by which personal information (PI) is irreversibly altered in such a way that an Individual or a legal entity can no longer be identified directly or indirectly either by the controller alone or in collaboration with any other party
personal information that has been subject to a process of anonymisation and that by any means can no longer be used to identify an Individual or legal entity
transfer of PI from the controller to a processor in the context of a commissioned work
individual's or legal entity's (data subject) explicitly or implicitly freely given agreement to the processing of its PI in the course of which the data subject has been in advance completely informed about the purpose, the legal basis and the third parties, receiving data subject’s PI, and all these in a comprehensible form
any natural or legal person, public authority, agency or any other body which alone or jointly with others collect and/or process and determine the purposes and means of the processing of PI, independently whether or not a person uses the PI by themselves or assigns the tasks to a processor; where the purposes and means of processing are determined by national or Community laws or regulations, the controller or the specific criteria for his nomination may be designated by national or Community law
conditions which result in a data subject being identified, directly or indirectly, on the basis of a given set of PI
establishes the link between a data subject and its PI or a set of PI
set of attributes which makes it possible to identify, contact or locate the data subject
any data or information related to an individual or legal entity or an association of person or individuals by which the individual or legal entity or association of persons could be identified
NOTE 1 to entry: The EU-Dir 95/48/EC names in its Art 2 lit. (a) the personal information as “personal data” and defines it as: “any information relating to an identified or identifiable natural person (‘data subject’); an identifiable person is one who can be identified, directly or indirectly, in particular by reference to an identification number or to one or more factors specific to his physical, physiological, mental, economic, cultural or social identity”.
natural person or legal entity or organization that processes personal information (PI) on behalf of and in accordance with the instructions of a PI controller and if it use PI only for the commissioned work
privacy stakeholder that processes PI on behalf of and in accordance with the instructions of a PI processor
any operation or set of operations which is performed upon personal data, whether or not by automatic means, such as collection, recording, organization, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, blocking, erasure or destruction
any personal information related to a natural person revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, health data or sex life; its processing is prohibited except for closing circumstances
action that circumvents all kinds of operations with the set of PI or certain elements of it meaning both processing of PI and transmission of PI to a third party
any person or legal entity receiving PI of a data subject other than the data subject itself or the controller or the processor
transfer of personal information to recipients other than the data subject, the controller or a processor, in particular publishing of data as well as the use of data for another application purpose of the controller