Information coding

The SAML V2.0 metadata specification [SAML2Meta] defines an XML schema and a set of basic processing rules intended to facilitate the implementation and deployment of SAML profiles, and generallyany profile or specification involving SAML. Practical experience has shown that the most complex aspects of implementing most SAML profiles, and obtaining interoperability between such implementations, are in the areas of provisioning federated relationships between deployments, and establishing the validity of cryptographic signatures and handshakes. Because the metadata specification was largely intended to solve those exact problems, additional profiling is needed to improve and clarify the use of metadata in addressing those aspects of deployment. The purpose of this profile is to guarantee that in a correct implementation, all security considerations not deriving from the particular cryptography used (i.e., algorithm strength, key sizes) can be isolated to metadata exchange and acceptance, and not affect the runtime processing of messages.

This standard defines a mapping of CIM-XML messages to the Hypertext Transfer Protocol (HTTP and HTTPS) so that implementations of CIM can operate in an open, standardized manner. It also defines the notion of conformance in the context of this mapping, and it describes the behavior animplementation of CIM shall exhibit to be a conforming CIM implementation.

CIM information could be represented within XML in many different ways. In the interest of interoperability between different implementations of CIM,there is an obvious requirement for standardization of this representation.  The following criteria have been applied in the design of the representation presented here:

• Fully standardized technologies are used wherever possible, in preference to Working Drafts.
• Where use is made of a Working Draft, the intention is to track the changes to the Working Draft in this specification.
• Completeness is favored over conciseness (all aspects of CIM should be modeled).

This specification describes an efficient method for WBEM Clients to discover WBEM Servers and WBEM Server capabilities. The objectives of this specification are to:

• Provide a mechanism that allows WBEM Clients to discover WBEM Servers
• Use existing standards and protocols for rapid development and deployment
• Provide a mechanism that scales from small environments to enterprise environments
• Provide WBEM Clients sufficient information in the advertisement to determine the WBEM
• Servers to communicate with

Scope the level of advertisement to avoid security holes The Service Location Protocol provides a flexible and scalable framework for providing clients, represented by User Agents, with access to information about the existence, location, and configuration of services, represented by Service Agents. Traditionally, clients have had to know the name and access method of services. The SLP eliminates the need for a client to know the name and access point of services. With SLP the client supplies a request for the desired type of service. The client receives information regarding the requested services

The Akoma Ntoso standard distinguishes between concepts regarding the description and identification of legal documents, their content, and the context in which they areused.  Names are used to associate the document representations to concepts so that documents can be “read/understood” by a machine, thus allowing sophisticated services that are impossible to attain with documents containing only typographical information, such as documents created in word-processing applications.To make documents machine-readable, every part with a relevant meaning and role must have a “name” (or “tag”) that machines can read. The content is marked up as precisely as possible according to the legal analysis of the text. This requires precisely identifying the boundaries of the different text segments, providing an element name that best describes the text in each situation, and also providing a correct identifier to each labelled fragment.

The Akoma Ntoso standard defines a number of referenceable concepts that are used in many situations in the lifecycle of legal documents. The purpose of this section is to provide: a standard referencing mechanism to these concepts through the use of IRI references associated to classes and instances of an ad hoc ontology (the Akoma Notoso Naming Convention). The referencing mechanism is meant to be generic and evolving with the evolution of the underlying ontology; a set of requirements for other naming conventions to be usable within Akoma Ntoso XML resources in a proper way.

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.

The Darwin Information Typing Architecture (DITA) is an XML-based architecture for authoring, producing, anddelivering topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways.While DITA historically has been driven by the requirements of large-scale technical documentation authoring,management, and delivery, it is a standard that is applicable to any kind of publication or information that mightbe presented to readers, including interactive training and educational materials, standards, reports, businessdocuments, trade books, travel and nature guides, and more.DITA is designed for creating new document types and describing new information domains based on existingtypes and domains. The process for creating new types and domains is called specialization. Specializationenables the creation of specific, targeted XML grammars that can still use tools and design rules that weredeveloped for more general types and domains; this is similar to how classes in an object-oriented system caninherit the methods of ancestor classes.

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.

MQTTisa Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.

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 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).