IT in general

The COEL Specification provides a clear and robust framework for implementing a distributed system capable of capturing data relating to an individual as discrete events. It facilitates a privacy-by-design approach for personalised digital services, IoT applications where devices are collecting information about identifiable individuals and the coding of behavioural attributes in identity solutions.The COEL Specification contains an extensive and detailed taxonomy of human behaviour. The taxonomy allows data from different systems to be encoded in a common format, preserving the meaning of the data across different applications.This ability to integrate universally at the data level, rather than just the technology level, is known as semantic harmonisation and provides full data portability. The communication protocols needed to support system interoperability across a wide range of implementations are also included.

This standard specifies conformance clauses in accordance with the OASIS TC Process ([TC-PROC] section 2.2.6 for the KMIP Specification [KMIP-SPEC] for a KMIPserver or KMIP client through profiles that define the use of KMIP objects, attributes, operations, message elements and authentication methods within specific contexts of KMIP server and client interaction.These profiles define a set of normative constraints for employing KMIP within a particular environment or context of use. They may, optionally, require the use of specific KMIP functionality or in other respects define the processing rules to be followed by profile actors.

The XACML architecture promotes a loose coupling between the component that enforces decisions, the policy enforcement point (PEP), and the component that decides based on XACML policies, the policy decision point (PDP). The XACML standard defines the format of the request and the response between thePEP and the PDP. As the default representation of XACML is XML and is backed by a schema, the request and response 8are typically expressed as XML elements or documents. With the rise in popularity of APIs and its consumerization, it becomes important for XACML to be easily understood in order to increase the likelihood it will be adopted. This profile aims at defining a JSON format for the XACML request and response. It also defines the transport between client (PEP) and service (PDP).

This specification defines a profile for the use of the OASIS eXtensible Access Control Markup Language (XACML), versions 3.0 [XACMLv3]and earlier. Use of this profile requires no changes or extensions to the XACMLstandard. This specification assumes the reader is somewhat familiar with XACML. XACML can be used for controlling access within a single application.This removes hard-coded security constraints from the application code, making it easier to change them. It also makes it possible to use a standard Policy Decision Point (PDP), so that organizations can make a proper make-or-buy decision. For virtually all organizations, authorization is not their core business, so being able to use an off-the-shelf product is appealing. Although these are substantial benefits, XACML really shines when authorizationis completely externalized from the application. Policies can then be reused across many applications, each using the same PDP. This leads to greater consistency of access control rules and improved efficiency in maintaining them.

While industry-specific data formats have the advantage of maximal optimization for their busines scontext, the existence of different formats to accomplish the same purpose in different business domainsis attended by a number of significant disadvantages as well.  The OASIS Universal Business Language (UBL) is intended to help solve these problems by defininga generic XML interchange format for business documents that can be restricted or extended to meet the requirements of particular industries.

Recommendation ITU-T Y.3508 provides an overview and high-level requirements for distributed cloud. This Recommendation introduces the concept of the distributed cloud, and identifies the characteristics of distributed cloud. Based on concept and characteristics, configuration models are illustrated. Deployment considerations of distributed cloud are provided in perspective of infrastructure, network, service, management and security. From use cases, high-level requirements of the distributed cloud are derived.

Standardization of basic characteristics, test methods and other related items of products such as 2D and 3D Printers/Scanners, Copiers, Projectors, Fax and Systems composed of their combinations, excluding such interfaces as user system interfaces, communication interfaces and protocols.

SC 28 is one of the few product or hardware oriented subcommittees in the JTC 1 community. As such fundamental output of this group has been standards on product specification descriptors, methods for measurement of productivity of hardcopy devices, quality of hardcopy output and yield of consumables (ink and toner cartridges). SC 28 will continue the expansion of measurement methods for consumables and productivity. SC 28 will also extend the image quality assessment to support print permanence and durability. In 2015, due to the changing nature of market needs for office equipment and related technologies with increasing usage of 3D technology in the office environments, SC 28 enlarged its scope with including 3D Printers/Scanners. SC 28 will continue to monitor developments for 3D printers/scanners in the office/home space to identify areas for potential development to address customer needs. Not only 3D area, SC 28 starts to align its work program for IoT and accessibility with JTC 1 strategic directions where applicable.

SC 31 continues to deliver technically rigorous standards that meet user requirements. Looking ahead in 2016 SC31 will deliver three standards of note. One jointly developed with SC 17 will measure the quality of OCR Characters used on passports significantly improving the readability of the characters (ISO/IEC 30116). The second will establish the first quantitative method for test and evaluation of localization systems aiding the first responder community and public safety (ISO/IEC 18305). The third is a method for uniquely identifying devices and items touching the Internet of Things (ISO/IEC 29161). In 2016 SC31 will commence a joint effort with the ISO Conformance Assessment Organization (CASCO) focusing on use of an “eLabel” to replace traditional conformance markings on electronic devices.

Standardization in the area of Internet of Things and related technologies.

1. Serve as the focus and proponent for JTC 1's standardization programme on the Internet of Things and related technologies, including Sensor Networks and Wearables technologies.
2. Provide guidance to JTC 1, IEC, ISO and other entities developing Internet of Things related applications.

The OASIS Cyber Threat Intelligence (CTI) TC was chartered to define a set of information representations and protocols to address the need to model, analyze, and share cyber threat intelligence. In the initial phase of TC work, three specifications will be transitioned from the US Department of Homeland Security (DHS) for development and standardization under the OASIS open standards process: STIX (Structured Threat Information Expression), TAXII (Trusted Automated Exchange of Indicator Information), and CybOX (Cyber Observable Expression).

The OASIS CTI Technical Committee will:

• define composable information sharing services for peer-to-peer, hub-and-spoke, and source subscriber threat intelligence sharing models
• develop standardized representations for campaigns, threat actors, incidents, tactics techniques and procedures (TTPs), indicators, exploit targets, observables, and courses of action
• develop formal models that allow organizations to develop their own standards-based sharing architectures to meet specific needs

For more information on the CTI TC, see the TC Charter.

The OASIS MQTT TC is producing a standard for the Message Queuing Telemetry Transport Protocol compatible with MQTT V3.1, together with requirements for enhancements, documented usage examples, best practices, and guidance for use of MQTT topics with commonly available registry and discovery mechanisms. The standard supports bi-directional messaging to uniformly handle both signals and commands, deterministic message delivery, basic QoS levels, always/sometimes-connected scenarios, loose coupling, and scalability to support large numbers of devices. Candidates for enhancements include message priority and expiry, message payload typing, request/reply, and subscription expiry.

As an M2M/Internet of Things (IoT) connectivity protocol, MQTT is designed to support messaging transport from remote locations/devices involving small code footprints (e.g., 8-bit, 256KB ram controllers), low power, low bandwidth, high-cost connections, high latency, variable availability, and negotiated delivery guarantees. For example, MQTT is being used in sensors communicating to a broker via satellite links, SCADA, over occasional dial-up connections with healthcare providers (medical devices), and in a range of home automation and small device scenarios. MQTT is also ideal for mobile applications because of its small size, minimized data packets, and efficient distribution of information to one or many receivers (subscribers).

For more information on the MQTT TC, see the TC Charter.

This specificationis a component of version three (v3) of the Common Information Model(CIM) architecture. CIM v3 is a major revision of CIM. CIM v3 preserves the functionality of CIM v2, but it is not backwards compatible. The DMTF continuesto support the specifications that define CIM v2. However, new CIM v3 architectural features may not be added to CIM v2 specifications. This standard describes the Common Information Model (CIM) Meta model version 3, which is based on the Unified Modeling Language: Superstructure specification. CIM schemas represent object-oriented models that can be used to represent the resources of a managed system, including their attributes, behaviors,and relationships. The CIM Metamodelincludes expressions for common elements that must be clearly presented to management applications (for example, classes, properties, methods, and associations).