Data technologies

ISO/IEC 29794-1:2016, for any or all biometric sample types as necessary, establishes the following:

- terms and definitions that are useful in the specification and use of quality metrics;
- purpose and interpretation of biometric quality scores;
- encoding of quality data fields in biometric data interchange formats;
- methods for developing biometric sample datasets for the purpose of quality score normalisation;
- format for exchange of quality algorithm results;
- methods for aggregation of quality scores.

This standard was last reviewed and confirmed in 2017. Therefore this version remains current.

ISO/IEC 19795-6:2012: provides guidance on the operational testing of biometric systems; specifies performance metrics for operational systems; details data that may be retained by operational systems to enable performance monitoring; and specifies requirements on test methods, recording of data, and reporting of results of operational evaluations.

ISO/IEC 29197:2015 addresses

• fundamental requirements for planning and execution of environmental performance evaluations for biometric systems based on scenario and operational test methodologies,
• specifications to define, establish, and measure specific conditions to assess, including requirements for equipment,
• requirements for establishing a baseline performance in order to compare the influence of environmental parameters,
• a specification of the biometric evaluation including requirements for test population, test protocols, data to record, and test results, and
• procedures for carrying out the overall evaluation.

ISO/IEC TR 24722:2015 contains descriptions of and analyses of current practices on multimodal and other multibiometric fusion, including (as appropriate) references to more detailed descriptions. ISO/IEC TR 24722:2015 contains descriptions and explanations of high-level multibiometric concepts to aid in the explanation of multibiometric fusion approaches including multi-characteristic-type, multiinstance, multisensorial, multialgorithmic, decision-level and score-level logic.

01.080.50 Graphical symbols for use on information technology and telecommunications technical drawings and in relevant technical product documentation
35.240.15 Identification cards. Chip cards. Biometrics

The OASIS BDXR TC advances an open standards framework to support public e-procurement and e-invoicing. The group defines specifications for a lightweight and federated messaging infrastructure that supports a 4-corner model for the secure and reliable exchange of electronic documents. Wherever possible, the TC specifications are based on profiles of existing standards from OASIS and elsewhere. BDXR TC members also coordinate the submission of new requirements as use cases for expanded functionality.
 
The original OASIS BDX TC was formed to advance the messaging portion of PEPPOL. Subsequently, the decision was made to broaden the scope of the TC to include global requirements and use cases from government and industry and to support an ongoing technical convergence between PEPPOL and other European Large Scale Pilots (LSPs), resulting in the rechartered OASIS BDXR TC.
 
All those involved in e-procurement and e-invoicing are invited to participate in the BDXR TC, including public and private sector agencies, enterprises, solution providers, consultants, and researchers. E-payment actors including financial institutions, associations and payment networks should also be represented in this work.

The LegalCiteM TC develops an open standard for machine-readable tagging of legal citations based upon a formalized conceptual model, vocabulary, metadata definitions, and prescribed syntax. The goal of the standard is to support rich tagging of citations while leaving the visible text of the citation undisturbed. The markup is intended to work for a broad variety of legal content types — including court cases, legislation, regulations, parliamentary documents, and legal treatises. It supports citations as used in different countries and jurisdictions, and allows other metadata to be associated with citations for purposes beyond just linking. The TC also defines use cases, overviews, sample data sets, and such other non-normative content to help guide implementers and users in adopting the standard.
 
The TC is affiliated with the OASIS LegalXML Member Section. For more information on the LegalCiteM TC, see the TC Charter.

The purpose of the XDI TC is to define a format and protocol for semantic data interchange using a standard addressable semantic graph model serialized in JSON.
 
For more information, see the TC Charter and FAQ.
 
The TC operates under a standing rule approved 17 July 2008 under which the TC does not hold regular official meetings and conducts all business by electronic ballot only. Unofficial weekly meetings are held to enable discussion among members but no business is conducted nor actions taken at those meetings.

The mission of the Automotive Working Group is to develop Open Web Platform specifications for application developers, including but not limited to HTML5/JavaScript, enabling Web connectivity through in-vehicle infotainment systems and vehicle data access protocols. The API is agnostic with regard to the connection used.
 
This group will develop service specifications for exposing vehicle data and other information around vehicle centric functions.
 
A common pattern will be described to unify the style the different service interfaces are using.
 
The specification(s) produced by this Working Group will include security and privacy considerations.
 
Members of the Working Group should review other working groups' deliverables that are identified as being relevant to the Working Group's mission.
 
Services may include but are not limited to

• Vehicle Data
  • vehicle brand, model, year, fuel type, transmission type, steering wheel position, tire pressure, oil level, wiper position, lights, doors, windows and seat settings as well as navigation, trip computer data, climate control data, speed, RPMs, acceleration, gears, …
• media
  • media control, track lists, …
• navigation
  • route manipulation, points of interests, …

The mission of the Dataset Exchange WG is to: 1. Revise the Data Catalog Vocabulary, DCAT, taking account of related vocabularies and the extensive work done in developing a number of its application profiles. 2. Define and publish guidance on the use of application profiles when requesting and serving data on the Web.
 
DCAT is formulated as an RDF vocabulary and is expected to remain so, however, the working Group is agnostic about data formats. Methods for expressing DCAT in other (existing) formats are in scope.
 
Government data, scientific research data, industry/enterprise and cultural heritage data, whether shared openly or not, are all explicitly in scope.

The current practice of the exchange of business documents by means of telecommunications – 65 usually defined as e-Business presents a major opportunity to improve the competitiveness of 66 companies, especially for Small and Medium Enterprises (SME).

The purpose of this document is to define globally consistent invoicing processes for the worldwide supply chains, using the UN/CEFACT Modelling Methodology (UMM) approach and Unified Modelling Language to describe and detail the business processes and transactions involved.

Since its original publication in 2014 by the RDF 1.1 Working Group, JSON-LD 1.0 has become an essential format for describing structured data on the World Wide Web. It is estimated to be used by between 10% and 18.2% of all websites. This is due largely to its adoption as a recommended format by schema.org. It has been adopted by several Recommendations including those from the Social Web, Web Annotation, and Linked Data Platform Working Groups, and current Working Groups have expressed interest in alignment of their specifications, such as the Publishing and Web of Things Working Groups. It has provided a much-needed bridge between communities that need rich semantics, and those that desire an intuitive and easily usable format (see separate wiki page for more details).
 
The mission of the JSON-LD Working Group is to update the JSON-LD 1.0 specifications to address specific usability or technical issues based on the community’s experiences, implementer feedback, and requests for new features.
 
The JSON-LD Working Group will update the JSON-LD 1.0 Recommendation to take into account new features and desired simplifications that have become apparent since its publication. The group will also extend the JSON-LD 1.0 Processing Algorithms and API Recommendation to update the existing APIs corresponding to changes in the JSON-LD Recommendation. Additionally, the group will move the Framing API CG specification to W3C Recommendation.
 
A summary of syntax changes proposed for inclusion by the JSON for Linking Data Community Group can be found on a wiki and in slides used at TPAC 2017.
 
The work must be consistent with principles expressed in the Data on the Web Best Practices Recommendation. All changes must preserve backward compatibility for JSON-LD 1.0 documents. This means that, when processing existing JSON-LD documents, JSON-LD 1.1 processors generate the same expanded output, unless that output is subject to errata in JSON-LD 1.0 or is otherwise an unspecified implementation detail.