Standards Watch

  • Home
  • Standards Watch

Click on the interactive map below or utilise the filtering interface on the side to browse the items that are currently in our Standards Watch*.

IT_general it_security software networking cloud computing other iot big data ai cybersecurity data tecnologies iso iec 27005 5g communications iso iec etsi osi it terminal application information computer grafics information coding office machine interface interconnection equipment languages used in it microprocessor system data storage services

The Standards Watch of StandICT.eu monitors the status of ICT standards at international level, starting from the five priority areas of the Digital Single Market: 5G communications,cloud computing,cybersecurity,data technology, and IoT – Internet of Things.

In particular, special attention is given to the rapidly evolving ICT topics of: Artificial Intelligence, Big Data, IoT. Gradually, the Standards Watch will be expanded to other ICT domains and topics, with the aim of better identifying gaps, needs & opportunities and consequently stimulating European Experts to pursue the openings granted by the StandICT.eu initiative.

The primary focus of the I/O Traces, Tools, and Analysis (IOTTA) TWG is to create a worldwide repository for storage-related I/O trace collection and analysis tools, application workloads, I/O traces, and best practices around such topics. That repository is located at http://iotta.snia.org

Working group
Submit a comment here

The Cloud Storage TWG acts as the primary technical entity for the SNIA to identify, develop, and coordinate systems standards for Cloud Storage. This group aims to produce a comprehensive set of specifications and drives consistency of interface standards and messages across the various Cloud Storage related efforts.

Working group
Submit a comment here

The OASIS PKCS 11 Technical Committee develops enhancements to improve the PKCS #11 standard for ease of use in code libraries, open source applications, wrappers, and enterprise/COTS products: implementation guidelines, usage tutorials, test scenarios and test suites, interoperability testing, coordination of functional testing, devel

Working group
Submit a comment here

The OpenDocument Format (ODF) is an open XML-based document file format for office applications to be used for documents containing text, spreadsheets, charts, and graphical elements. The file format makes transformations to other formats simple by leveraging and reusing existing standards wherever possible.

Working group
Submit a comment here

The OASIS OData TC works to simplify the querying and sharing of data across disparate applications and multiple stakeholders for re-use in the enterprise, Cloud, and mobile devices. A REST-based protocol, OData builds on HTTP and JSON using URIs to address and access data feed resources.

Working group
Submit a comment here

CoRE provides a framework for resource-oriented applications intended to run on constrained IP networks. Such networks have limited packet sizes, may exhibit a high degree of packet loss, and may have a substantial number of devices that may be powered off at any point in time but periodically "wake up" for brief periods of time.

Working group
Submit a comment here

The OpenC2 TC was chartered to draft documents, specifications, lexicons or other artifacts to fulfill the needs of cyber security command and control in a standardized manner. The Technical Committee will leverage pre-existing standards to the greatest extent practical, identifying gaps pertaining to the command and control of technologies that provide or support cyber defenses.

Working group
Submit a comment here

Concise Binary Object Representation (CBOR, RFC 7049) extends the JavaScript Object Notation (JSON, RFC 8259) data interchange format to include binary data and an extensibility model, using a binary representation format that is easy to parse correctly. It has been picked up by a number of IETF efforts (e.g., CORE, ANIMA GRASP) as a message format.

Working group
Submit a comment here

Interception techniques need to become more effective and fail-safe as endpoints become inherently more secure. The IETF Captive Portal Interaction (CAPPORT) Working Group will define secure mechanisms and protocols to:

Working group
Submit a comment here

The OASIS Litigant Portal (LP) Technical Committee is chartered to produce specifications for data interoperation between Litigant Portal Modules. The technical specifications are collectively referred to as the Litigant Portal Exchange (LPX) Specifications. Portal modules are designed to provide assististance to self-represented litigants.

Working group
Submit a comment here

The OASIS Electronic Court Filing TC will develop specifications for the use of XML to create legal documents and to transmit legal documents from an attorney, party or self-represented litigant to a court, from a court to an attorney, party or self-represented litigant or to another court, and from an attorney or other user to another attorney or other user of legal documents.
 

Working group
Submit a comment here

Pages