IT-tillämpningar

Kommittébeteckning: SIS/TK 448 (Teknik och stödsystem för personlig identifiering)
Källa: ISO
Svarsdatum: den 15 dec 2018
Se merSe mindre
 

This part of ISO/IEC 19785 specifies the procedures to be followed by the Biometric Registration Authority (RA) in preparing, maintaining, and publishing registers of identifiers for biometric organizations and biometric objects. ISO/IEC JTC 1 shall not interfere with the operations of the RA, which shall be a separately managed entity.

Kommittébeteckning: SIS/TK 448 (Teknik och stödsystem för personlig identifiering)
Källa: ISO
Svarsdatum: den 15 dec 2018
Se merSe mindre
 

This part of ISO/IEC 19785 specifies and publishes registered CBEFF patron formats defined by the CBEFF

patron ISO/IEC JTC 1/SC 37, and specifies their registered CBEFF patron format types (see ISO/IEC 19785-

1:2015) and resulting full ASN.1 Object Identifiers.

Kommittébeteckning: SIS/TK 448 (Teknik och stödsystem för personlig identifiering)
Källa: ISO
Svarsdatum: den 15 dec 2018
Se merSe mindre
 

The proposed standard will specify an interface of a BioAPI C++ framework and BioAPI C++ BSP which will

mirror the corresponding components specified in ISO/IEC 30106-1.The semantic equivalence of this

standard will be maintained with ISO/IEC 30106-2 (Java implementation) and ISO/IEC 30106-3 (C#

implementation). In spite of the differences in actual parameters passed between functions, the names and

interface structure are the same.

Kommittébeteckning: SIS/TK 323 (Geodata)
Källa: ISO
Svarsdatum: den 18 dec 2018
Se merSe mindre
 

This part of ISO 19150 sets a framework for geographic information service ontology and the description of geographic information Web services in OWL.

The Web Ontology Language (OWL) is the language adopted for ontologies.

This part of ISO 19150 will make use of service metadata (ISO 19115-1) and service definition (ISO 19119) whenever appropriate

This part of ISO 19150 does not define semantics operators, rules for ontologies, and does not develop any application ontology.

In reference to ISO 19101-1:2014, Clause 6.2, this part of ISO 19150 defines and formalizes the following purpose of the ISO geographic information reference model:

* geographic information service components and their behaviour for data processing purposes over the Web, and

* OWL ontologies to cast ISO/TC 211 standards to benefit from and support the Semantic Web.

In reference to ISO 19101-1:2014, Clause 8.3, this part of ISO 19150 addresses the Meta:Service foundation of the ISO geographic information reference model.

Kommittébeteckning: SIS/TK 448 (Teknik och stödsystem för personlig identifiering)
Källa: ISO
Svarsdatum: den 19 dec 2018
Se merSe mindre
 

This document specifies

* rules and guidelines for defining biometric data interchange formats that are extensible without invalidating previous data structures,

* the meaning of common data elements for use in biometric data interchange formats,

* common data structures for tagged binary data formats based on an extensible specification in ASN.1,

* common data structures for textual data formats based on an XML schema definition, and

* conformance testing concepts and methodologies for testing the syntactic conformance of biometric data blocks.

Kommittébeteckning: SIS/TK 450 (IT-standarder för Lärande)
Källa: ISO
Svarsdatum: den 8 jan 2019
Se merSe mindre
 

1.1.1 Scope of 24751

ISO/IEC 24751 is a multi-part standard that defines an AccessForAll framework to enable: 

•Individuals to discover, explore, refine, prioritize and request their personally unique preferences, for a given context, and

•AccessForAll services to satisfy the individual preferences by delivering a match (e.g, finding, assembling, developing, recruiting or using other strategies to deliver products,services, configurations or environments that match the preferences [herein referred to as AfA resources])

AccessForAll is in large part motivated by the goal of addressing currently unmet or poorly met preferences (where the term ‘preferences’ encompasses the range from critical needs to preferences). This goal is in part satisfied by registries, which are open to any individual or organization, to register possible preference concepts (as AccessForAll Preference Concepts), including concepts associated with unanticipated, emerging or new preferences. These registered AccessForAll Preference Concepts might then be used to express individual preferences within a broad diversity of AccessForAll implementing services. An AccessForAll Concept Registry is intended to register possible preference concepts; it is not used for individuals to declare or store personal preferences or personal preference sets (AfA Preference Statement), this is achieved through AccessForAll services that support discovery, exploration, refinement, prioritization and matching of Individual Preference Statements. (An AccessForAll Preference Concept might itself be able to represent a preference or it may require qualification and/or combination with other  preference concepts to form a preference through an AfA Preference Statement).

1.1.2 Future Parts

This International Standard is designed to accommodate developments in technology and implementations and supports the addition of more parts in the future.

1.2 Scope of Part 1 of 24751

Part 1 specifies the basic principles of an AccessForAll approach and the specifications for AccessForAll (AfA) registries.

This part defines:

•a framework and basic principles to support matching of individually unique preferences (that may vary according to the context, including the user goal) to resources that satisfy the preferences.

•specifications for AccessForAll (AfA) registries to register AfA Preference Concepts

In order to make it easier for users and developers to understand and use AfA Preference Concepts, this part supports registration of multiple names and descriptions for a given AfA Preference Concept. It aims to enable users, developers, and others to use their chosen names and descriptions, in their chosen natural language, and yet have them interoperate within many systems.

AccessForAll Preference Concepts will be used by AccessForAll services to:

•enable individuals to create AfA Preference Statements (3.5) or requests, (this includes discovering, exploring, evaluating and refining an understanding of the preferences that work best for them in a given context to achieve a given goal),

•identify resources that match AfA preference concepts (including, but not limited to, through the application of resource metadata)

•match resources to personally declared AfA Preference Statements

Kommittébeteckning: SIS/TK 543 (Dokumentbevarande)
Källa: ISO
Svarsdatum: den 14 jan 2019
Se merSe mindre
 

This part of ISO/IEC 19757 specifies Schematron, a schema language for XML. This part of ISO/IEC 19757 establishes requirements for Schematron schemas and specifies when an XML document matches the patterns specified by a Schematron schema.

Kommittébeteckning: SIS/TK 445 (Teckenrepresentation och användargränssnitt)
Källa: ISO
Svarsdatum: den 20 jan 2019
Se merSe mindre
 

This document defines multi-point gestures for common system actions used in information and communication technology (ICT) systems. It specifies movements for clear and classified gestures recognized by the systems and applications. The multi-point gestures are performed using an input device (e.g. multi-touch pad, multi-touch screen, etc.) or body parts (e.g. fingertips, hands, etc.). These multi-point gestures are intended to operate in a consistent manner regardless of systems, platforms or applications.

The gestures for common system actions denote system level functions and common functions across applications of ICT systems. The system level functions are executed at a system or a platform level. They include initiation, resume, restart and termination of an application, etc. The common functions across applications are commonly executed among applications of a system or a platform. The functions include navigation of menus, opening an object, closing an object, etc.

NOTE ICT systems include, but are not limited to, digital televisions, set-top boxes, video game consoles, communication devices, internet devices, entertainment devices, and personal computers (PCs).

Kommittébeteckning: SIS/TK 448 (Teknik och stödsystem för personlig identifiering)
Källa: ISO
Svarsdatum: den 21 jan 2019
Se merSe mindre
 

This document specifies interindustry commands that may be used for security operations. This

document also provides informative directives on how to construct security mechanisms with

ISO/IEC 7816-4 defined commands.

The choice and conditions of use of cryptographic mechanism in security operations may affect card

exportability. The evaluation of the suitability of algorithms and protocols is outside the scope of this

document. It does not cover the internal implementation within the card and/or the outside world.

Kommittébeteckning: SIS/TK 255 (Vägtrafikinformatik)
Källa: CEN
Svarsdatum: den 1 feb 2019
Se merSe mindre
 

1.1 General Scope of the Standard

The main objective of the present document is to present the Reference Data Model for Public Transport, based on:

— the Reference Data Model, EN 12896, known as Transmodel V5.1;

— EN 28701:2012, Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896— 1:2016 and EN 12896— 2:2016) following their successful publication.

incorporating the requirements of

— EN 15531— 1 to — 3 and TS 15531— 4 and — 5: Service interface for real— time information relating to public transport operations (SIRI);

— TS 16614— 1 and 2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation.

Particular attention is drawn to the data model structure and methodology:

— the data model is described in a modular form in order to facilitate the understanding and the use of the model;

— the data model is entirely described in UML.

The following functional domains are considered:

— Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.

— Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type— related vehicle schedules)

— Passenger Information (planned and real— time)

— Fare Management (fare structure, sales, validation, control)

— Operations Monitoring and Control: operating day— related data, vehicle follow— up, control actions

— Driver Management:

— Driver Scheduling (day— type related driver schedules),

— Rostering (ordering of driver duties into sequences according to some chosen methods),

— Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance).

— Management Information and Statistics (including data dedicated to service performance indicators).

The data modules dedicated to cover most functions of the above domains will be specified.

Several concepts are shared by the different functional domains. This data domain is called "Common Concepts".

1.2 Functional Domain Description

The different functional domains (enumerated above) taken into account in the present document, and of which the data have been represented as the reference model, are described in EN 12896-1:2016 "Public Transport Reference Data Model – Part 1: Common Concepts".

1.3 Particular Scope of this Document

The present European Standard entitled "Reference Data Model for Public Transport – Part 4: Operations Monitoring and Control" incorporates the following data packages:

— Dated Production Components MODEL;

— Call MODEL;

— Production Plan MODEL;

— Detecting and Monitoring MODEL;

— Control Action MODEL;

— Event and Incident MODEL;

— Messaging MODEL;

— Situation MODEL; and

— Facility Monitoring and Availability MODEL.

The data structures represented in this part form descriptions of data that are specific to operations for an operational day (as opposed to those planned for day types). They reference to structures as described in EN 12896-1:2016, such as version frames or generic grouping mechanisms, but also to EN 12896-2:2016 and EN 12896-3:2016.

This document itself is composed of the following parts:

— Main document (normative) presenting the data model for the domain Operations Monitoring and Control;

— Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions;

— Annex B (normative), providing a complement to EN 12896-1:2016, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model;

— Annex C (informative), indicating the data model evolutions; and

— Annex D (informative), providing a mapping between the Situation Publication model of DATEX II (CEN/TS 16157, Situation Publication Data Model 2.2, 2013), SIRI Situation Exchange (CEN/TS 15531-5:2016) and SIRI Facility Monitoring (CEN/TS 15531-4:2011).

Kommittébeteckning: SIS/TK 255 (Vägtrafikinformatik)
Källa: CEN
Svarsdatum: den 1 feb 2019
Se merSe mindre
 

1.1 General Scope of the Standard

The main objective of the present standard is to present the Reference Data Model for Public Transport, based on:

- the Reference Data Model, EN 12896, known as Transmodel V5.1;

- EN 28701:2012, Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication.

incorporating the requirements of

- EN 15531-1 to -3 and CEN/TS 15531-4 and -5: Service interface for real-time information relating to public transport operations (SIRI);

- CEN/TS 16614-1 and 2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation.

Particular attention is drawn to the data model structure and methodology:

- the data model is described in a modular form in order to facilitate the understanding and the use of the model;

- the data model is entirely described in UML.

The following functional domains are considered:

- Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.

- Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules)

- Passenger Information (planned and real-time)

- Fare Management (fare structure, sales, validation, control)

- Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions

- Driver Management:

- Driver Scheduling (day-type related driver schedules),

- Rostering (ordering of driver duties into sequences according to some chosen methods),

- Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance).

- Management Information and Statistics (including data dedicated to service performance indicators).

The data modules dedicated to cover most functions of the above domains will be specified.

Several concepts are shared by the different functional domains. This data domain is called “Common Concepts”.

1.2 Functional Domain Description

The different functional domains (enumerated above) taken into account in the present standard, and of which the data have been represented as the reference model, are described in EN 12896-1:2016 “Public Transport Reference Data Model – Part 1: Common Concepts”.

1.3 Particular Scope of this Document

The present European Standard entitled “Reference Data Model for Public Transport – Part 5: Fare Management” addresses Fare Information for Public Transport and incorporates the following data packages:

- Fare Structure

- Access Right Assignment

-  Fare Pricing

-  Sales Description

-  Sales Transaction

-  Fare Roles

-  Validation and Control

-  Explicit Frames for Fares

This document itself is composed of the following parts:

-  Main document (normative) representing the data model for the concepts shared by the different fare domains covered by Transmodel,

-  Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions,

-  Annex B (normative), providing a complement to the "Common Concepts" domain, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model.

-  Annex C (informative), indicating the data model evolutions from previous versions of Transmodel (EN 12896:2016).

Kommittébeteckning: SIS/TK 255 (Vägtrafikinformatik)
Källa: CEN
Svarsdatum: den 1 feb 2019
Se merSe mindre
 

The main objective of the present document is to present the Reference Data Model for Public Transport, based on:

— the Reference Data Model, EN12896, known as Transmodel V5.1;

— EN 28701:2012, Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication,

incorporating the requirements of:

— EN 15531-1 to −3 and CEN/TS 15531-4 and −5: Service interface for real-time information relating to public transport operations (SIRI);

— CEN/TS 16614-1 and -2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation.

Particular attention is drawn to the data model structure and methodology:

— the data model is described in a modular form in order to facilitate the understanding and the use of the model;

— the data model is entirely described in UML.

The following functional domains are considered:

— Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places;

— Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules);

— Passenger Information (planned and real-time);

— Fare Management (fare structure, sales, validation, control);

— Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions;

— Driver Management:

— Driver Scheduling (day-type related driver schedules),

— Rostering (ordering of driver duties into sequences according to some chosen methods),

— Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance);

— Management Information and Statistics (including data dedicated to service performance indicators).

The data modules dedicated to cover most functions of the above domains will be specified.

Several concepts are shared by the different functional domains. This data domain is called "Common Concepts".

Kommittébeteckning: SIS/TK 255 (Vägtrafikinformatik)
Källa: CEN
Svarsdatum: den 1 feb 2019
Se merSe mindre
 

The main objective of the present document is to present the Reference Data Model for Public Transport, based on:

— the Reference Data Model, EN 12896, known as Transmodel V5.1;

— EN 28701:2012, Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication.

incorporating the requirements of

— EN 15531-1 to −3 and CEN/TS 15531-4 and −5: Service interface for real-time information relating to public transport operations (SIRI);

— CEN/TS 16614-1 and 2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation.

Particular attention is drawn to the data model structure and methodology:

— the data model is described in a modular form in order to facilitate the understanding and the use of the model;

— the data model is entirely described in UML.

The following functional domains are considered:

— Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.

— Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules)

— Passenger Information (planned and real-time)

— Fare Management (fare structure, sales, validation, control)

— Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions

— Driver Management:

— Driver Scheduling (day-type related driver schedules),

— Rostering (ordering of driver duties into sequences according to some chosen methods),

— Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance).

— Management Information and Statistics (including data dedicated to service performance indicators).

The data modules dedicated to cover most functions of the above domains will be specified.

Several concepts are shared by the different functional domains. This data domain is called "Common Concepts".

Kommittébeteckning: SIS/TK 115 (Språk och terminologi)
Källa: ISO
Svarsdatum: den 9 feb 2019
Se merSe mindre
 

This International Standard specifies general, i.e. implementation- and use-case-independent

terminology database design for enabling maximum efficiency and quality in the field of terminology

work and, thus, in creating, processing, and using high quality terminology. The intended audiences

of this document are terminologists, translators, technical writers, language planners, subject field

experts, and terminology management system developers. However, the standard can also be used to

evaluate the conformance and suitability of terminology databases.

This International Standard describes a maximum approach, i.e. terminology database design for

distributed, multilingual terminology management environments. Nevertheless, it can also be used for

designing smaller solutions by just subsetting the proposed data model.

Kommittébeteckning: SIS/TK 115 (Språk och terminologi)
Källa: ISO
Svarsdatum: den 9 feb 2019
Se merSe mindre
 

This International Standard specifies essential features to be supported by terminology management systems regardless of specific software engineering paradigms, user interface and user assistance design principles, and specific data models for enabling maximum efficiency and quality in the field of terminology work and, thus, in creating, processing, and using high quality terminology. The intended audiences of this standard are software engineers/developers as well as terminologists, technical writers, translators, language planners, and subject field experts. However, the standard can also be used to evaluate the conformance and suitability of terminology management systems.

This International Standard describes all features needed for recording, editing, maintaining, exchanging, and presenting terminological data. Term extraction features used to identify new terms are out of scope from this standard.

Kommittébeteckning: SIS/TK 323 (Geodata)
Källa: ISO
Svarsdatum: den 16 feb 2019
Se merSe mindre
 

This document defines the structure and content of a text string implementation of the abstract model

for coordinate reference systems described in ISO 19111:2018. The string defines frequently needed

types of coordinate reference systems and coordinate operations in a self-contained form that is easily

readable by machines and by humans. The essence is its simplicity; as a consequence there are some

constraints upon the more open content allowed in ISO 19111. To retain simplicity in the well-known

text (WKT) description of coordinate reference systems and coordinate operations, the scope of this

document excludes parameter grouping and pass-through coordinate operations. The text string

provides a means for humans and machines to correctly and unambiguously interpret and utilise a

coordinate reference system definition with look-ups or cross references only to define coordinate

operation mathematics. A WKT string is not suitable for the storage of definitions of coordinate

reference systems or coordinate operations because it omits metadata about the source of the data and

may omit metadata about the applicability of the information.