Public Review for #XMILE Version 1.0 Errata 01 – ends March 9th

The OASIS XML Interchange Language (XMILE) for System Dynamics TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

XML Interchange Language for System Dynamics (XMILE) Version 1.0 Errata 01
Committee Specification Draft 01 / Public Review Draft 01
08 January 2016

and

XML Interchange Language for System Dynamics (XMILE) Version 1.0 Plus Errata 01
OASIS Standard Incorporating Public Review Draft 01 of Errata 01
08 January 2016

Specification Overview:

This Errata corrects a typographical error for the “report_interval” attribute in xmile.xsd schema. The content of the OASIS Standard itself is unchanged.

Public Review Period:

The public review starts 25 February 2016 at 00:00 UTC and ends 09 March 2016 at 11:59 UTC.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs:
The prose specification document and related files are available here:

– XML Interchange Language for System Dynamics (XMILE) Version 1.0 Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/xmile-v1.0-errata01-csprd01.doc

HTML:
http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/xmile-v1.0-errata01-csprd01.html

PDF:
http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/xmile-v1.0-errata01-csprd01.pdf

– XML Interchange Language for System Dynamics (XMILE) Version 1.0 Plus Errata 01
OASIS Standard Incorporating Public Review Draft 01 of Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/xmile-v1.0-errata01-csprd01-complete.doc

HTML:
http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/xmile-v1.0-errata01-csprd01-complete.html

PDF:
http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/xmile-v1.0-errata01-csprd01-complete.pdf

XML schema:
http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/schemas/

Examples:
http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/examples/

ZIP distribution files (complete):

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/xmile/xmile/v1.0/errata01/csprd01/xmile-v1.0-errata01-csprd01.zip

Additional information about this specification and the XMILE TC may be found on the TC’s public home page located at:

http://www.oasis-open.org/committees/xmile/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=xmile

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/xmile-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of ‘XML Interchange Language for System Dynamics (XMILE) Version 1.0 Errata 01’, we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

========== Additional references:

[1] OASIS XML Interchange Language (XMILE) for System Dynamics TC
http://www.oasis-open.org/committees/xmile/

[2] http://www.oasis-open.org/policies-guidelines/ipr

[3] https://www.oasis-open.org/committees/xmile/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

Public Reviews for #KMIP Specification V1.3 and Usage Guide v1.3 – ends March 18th

The OASIS Key Management Interoperability Protocol (KMIP) TC [1] members have recently approved a Committee Specification Draft (CSD) and a Committee Note Draft (CND) and submitted both for 30-day public reviews:

Key Management Interoperability Protocol Specification Version 1.3
Committee Specification Draft 01 / Public Review Draft 01
03 December 2015

and

Key Management Interoperability Protocol Usage Guide Version 1.3
Committee Note Draft 01 / Public Review Draft 01
03 December 2015

Overview:

The Key Management Interoperability Protocol (KMIP) is a single, comprehensive protocol for communication between clients that request any of a wide range of encryption keys and servers that store and manage those keys. By replacing redundant, incompatible key management protocols, KMIP provides better data security while at the same time reducing expenditures on multiple products.

KMIP v1.3 enhances the KMIP v1.2 standard by:
– defining new functionality in the protocol to improve interoperability;
– defining additional Test Cases for verifying and validating the new functionality;
– providing additional information in the KMIP Usage Guide to assist in effective implementation of KMIP in key management clients and servers; and
– defining new profiles for establishing KMIP-compliant implementations.

The KMIP Specification v1.3 is intended for developers and architects who wish to design systems and applications that interoperate using the Key Management Interoperability Protocol Specification.

The KMIP Usage Guide is intended to complement the Key Management Interoperability Protocol Specification by providing guidance on how to implement KMIP most effectively to ensure interoperability and to address key management usage scenarios.

Public Review Period:

The public reviews start 17 February 2016 at 00:00 UTC and ends 18 March 2016 at 23:59 UTC.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs:

The prose specification document and related files are available here:

– Key Management Interoperability Protocol Specification Version 1.3

Editable source (Authoritative):
http://docs.oasis-open.org/kmip/spec/v1.3/csprd01/kmip-spec-v1.3-csprd01.docx

HTML:
http://docs.oasis-open.org/kmip/spec/v1.3/csprd01/kmip-spec-v1.3-csprd01.html

PDF:
http://docs.oasis-open.org/kmip/spec/v1.3/csprd01/kmip-spec-v1.3-csprd01.pdf

– Key Management Interoperability Protocol Usage Guide Version 1.3

Editable source (Authoritative):
http://docs.oasis-open.org/kmip/ug/v1.3/cnprd01/kmip-ug-v1.3-cnprd01.docx

HTML:
http://docs.oasis-open.org/kmip/ug/v1.3/cnprd01/kmip-ug-v1.3-cnprd01.html

PDF:
http://docs.oasis-open.org/kmip/ug/v1.3/cnprd01/kmip-ug-v1.3-cnprd01.pdf

ZIP distribution file (complete):

For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:

– Key Management Interoperability Protocol Specification Version 1.3:
http://docs.oasis-open.org/kmip/spec/v1.3/csprd01/kmip-spec-v1.3-csprd01.zip

– Key Management Interoperability Protocol Usage Guide Version 1.3:
http://docs.oasis-open.org/kmip/ug/v1.3/cnprd01/kmip-ug-v1.3-cnprd01.zip

Additional information about these documents and the Key Management Interoperability Protocol (KMIP) TC may be found at the TC’s public home page:

https://www.oasis-open.org/committees/kmip/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility as explained in the instructions located via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/kmip-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of ‘Key Management Interoperability Protocol Specification Version 1.3’ and ‘Key Management Interoperability Protocol Usage Guide Version 1.3,’ we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

========== Additional references:

[1] OASIS Key Management Interoperability Protocol (KMIP) TC
https://www.oasis-open.org/committees/kmip/

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/odata/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Mode

15-day Public Review for #PKCS #11 Errata – ends February 17th

The OASIS PKCS 11 TC [1] members have recently approved three PKCS Errata Committee Specification Drafts and submitted them for a 15-day public review:

PKCS #11 Cryptographic Token Interface Base Specification Version 2.40 Errata 01
Committee Specification Draft 01 / Public Review Draft 01
09 December 2015

PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 2.40 Errata 01
Committee Specification Draft 01 / Public Review Draft 01
09 December 2015

PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 2.40 Errata 01
Committee Specification Draft 01 / Public Review Draft 01
09 December 2015

Overview:

These documents contain corrections to errors and omissions in the PKCS #11 Cryptographic Token Interface Base Specification, Current Mechanisms and Historical Mechanisms OASIS Standards respectively.

In addition, copies of the OASIS Standards with draft errata applied are provided as well.

TC Description:

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, development of conformance profiles, and providing reference implementations.

Public Review Period:

The public reviews start 03 February 2016 at 00:00 UTC and end 17 February 2016 at 23:59 UTC.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs:

The prose specification documents and related files are available here:

– Base Specification Version 2.40 Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/csprd01/pkcs11-base-v2.40-errata01-csprd01.doc

HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/csprd01/pkcs11-base-v2.40-errata01-csprd01.html

PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/csprd01/pkcs11-base-v2.40-errata01-csprd01.pdf

– Base Specification OASIS Standard Incorporating Public Review Draft 01 of Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/csprd01/pkcs11-base-v2.40-errata01-csprd01-complete.doc

HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/csprd01/pkcs11-base-v2.40-errata01-csprd01-complete.html

PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/csprd01/pkcs11-base-v2.40-errata01-csprd01-complete.pdf

Definition files:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/csprd01/include/pkcs11-v2.40/

– Current Mechanisms Specification Version 2.40 Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/errata01/csprd01/pkcs11-curr-v2.40-errata01-csprd01.doc

HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/errata01/csprd01/pkcs11-curr-v2.40-errata01-csprd01.html

PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/errata01/csprd01/pkcs11-curr-v2.40-errata01-csprd01.pdf

– Current Mechanisms OASIS Standard Incorporating Public Review Draft 01 of Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/errata01/csprd01/pkcs11-curr-v2.40-errata01-csprd01-complete.doc

HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/errata01/csprd01/pkcs11-curr-v2.40-errata01-csprd01-complete.html

PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/errata01/csprd01/pkcs11-curr-v2.40-errata01-csprd01-complete.pdf

– Historical Mechanisms Specification Version 2.40 Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/errata01/csprd01/pkcs11-hist-v2.40-errata01-csprd01.doc

HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/errata01/csprd01/pkcs11-hist-v2.40-errata01-csprd01.html

PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/errata01/csprd01/pkcs11-hist-v2.40-errata01-csprd01.pdf

– Historical Mechanisms OASIS Standard Incorporating Public Review Draft 01 of Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/errata01/csprd01/pkcs11-hist-v2.40-errata01-csprd01-complete.doc

HTML:
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/errata01/csprd01/pkcs11-hist-v2.40-errata01-csprd01-complete.html

PDF:
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/errata01/csprd01/pkcs11-hist-v2.40-errata01-csprd01-complete.pdf

ZIP distribution files (complete):

For your convenience, OASIS provides a complete package of each prose document and related files in ZIP distribution files. You can download the ZIP files here:

– PKCS #11 Cryptographic Token Interface Base Specification Version 2.40 Errata 01:
http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/csprd01/pkcs11-base-v2.40-errata01-csprd01.zip

– PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 2.40 Errata 01:
http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/errata01/csprd01/pkcs11-curr-v2.40-errata01-csprd01.zip

– PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 2.40 Errata 01
http://docs.oasis-open.org/pkcs11/pkcs11-hist/v2.40/errata01/csprd01/pkcs11-hist-v2.40-errata01-csprd01.zip

Additional information about the specification and the OASIS PKCS 11 TC may be found at the TC’s public home page:

https://www.oasis-open.org/committees/pkcs11/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility as explained in the instructions located via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=pkcs11

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/pkcs11-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with the public reviews of these OASIS Standard Errata, we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

========== Additional references:

[1] OASIS PKCS 11 TC
https://www.oasis-open.org/committees/pkcs11/

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/policies-guidelines/ipr

[4] http://www.oasis-open.org/committees/pkcs11/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.2
RF on RAND

Members Approve DITA 1.3 as OASIS Standard for Authoring and Publishing

1 February 2016 – The OASIS open standards consortium today announced that its members have approved the Darwin Information Typing Architecture (DITA) version 1.3 as an OASIS Standard, a status that signifies the highest level of ratification. DITA defines an XML architecture for designing, writing, and publishing information in numerous formats, including print, Web-based, mobile, and electronic publications. DITA is widely used for professionally-published books and magazines, technical documentation, online help, training and course development, marketing materials, and medical information because of its modular, topic-based approach and its ability to support content reuse.

This release of DITA comes in three parts, optimized for different audiences:

  • Base Edition is designed for application developers and users who need only the most fundamental pieces of the DITA framework.
  • Technical Content Edition includes specializations usually used by technical communicators.
  • All Inclusive Edition is designed for implementers who want all OASIS-approved specializations, as well as users who develop learning and training materials.

“The unique feature of the DITA standard is specialization,” said Kristen James Eberlein, chair of the OASIS DITA Technical Committee. “DITA enables practitioners to create new elements from existing ones in order to increase semantic precision. For example, a section element can be specialized to represent more specific types of sections such as ‘Introduction’, ‘Main point’, and ‘Conclusion’; this enables more precise semantic searching and better guidance for authors.”

“Done correctly,” Eberlein continued, “output processors will always understand the specialization hierarchy–a section is always a section, after all–and be able to apply general processing transformations. Together the re-use and interoperation possibilities of DITA allow great cost sharing and cost reductions.”

DITA 1.3 is ready for implementation. Prior to its approval, 14 Statements of Use for DITA 1.3 were provided by Comtech Services, IXIASOFT, PTC, and 11 other organizations and open source initiatives, including the DITA Open Toolkit.

Participation in the OASIS DITA Technical Committee and the DITA Adoption Committee is open to all companies, non-profit groups, governments, academic institutions, and individuals. As with all OASIS projects, archives of the Committees’ work are accessible to both members and non-members, and OASIS hosts an open mailing list for public comment.

Support for DITA 1.3

Adobe
“Adobe is delighted to provide continued support to the DITA standard which has leveraged the power of single-sourcing, content reuse and specialization over the years. Adobe also welcomes the new features, introduced in DITA 1.3, such as troubleshooting topic type, keyscopes, branch filtering, MathML domain, XML mention domain and many other valuable additions. Adobe has successfully used the DITA 1.3 Candidate OASIS Standard 01 Part 3 (All Inclusive Edition) and its authoring and publishing software, Adobe FrameMaker (2015 release), is a fully-aware DITA processor which interoperates with multiple independent implementations.”
— Pawan Goyal, Sr. Director and General Manager (Print, Scan, TechComm Business) Adobe

Cisco
“Cisco congratulates the DITA TC on another successful release of the DITA standard. Cisco uses DITA for its technical documentation because it enables content reuse, standardization, and output flexibility. We are eagerly awaiting the 1.3 release, especially the new troubleshooting template. This template allows us to create topics that contain both reference information and task steps in a single, unified chunk. It will greatly improve our ability to present troubleshooting information in a customer-friendly format.”
— Jen Allen, Information Architect and Jane Credland, Project Manager, Cisco Systems

Comtech
“Comtech Services, Inc. is very pleased by the strong support of the OASIS community for the DITA 1.3 specification. We believe that DITA 1.3 moves the capability of the DITA standard ahead significantly in support of the international information-development community. We have witnessed an ever-increasing group of industries and technologies adopting the DITA standard.”
–JoAnn T. Hackos, PhD, President, Comtech

IBM
“DITA continues to be a key part of IBM’s sourcing strategy for post-sales technical content. IBM is already using one new DITA 1.3 feature, branch filtering, to manage multiple publishing targets in complex reuse scenarios. The DITA 1.3 specification document itself represents a significant improvement over the 1.2 version. Hundreds of pages have been overhauled to reduce redundancy and clutter, with examples added to greatly improve clarity for adopters.”
–Eileen Jones, Director, Enterprise Content & eSupport Services, and IBM Client Content Quality Executive

ISIS Papyrus
“As an OASIS Sponsor, ISIS Papyrus appreciates the DITA standard to ensure an XML archi-tecture for designing, writing, managing, and publishing information. DITA is a step forward for better interoperability when publishing information in print and on the Web. Following the DITA data model helps to generate popular output formats (HTML, PDF, Java and HTML Help, etc.) from vendor and software version-independent content.”
–Max J. Pucher, co-founder/CTO, ISIS Papyrus Software

IXIASOFT
“As active members of OASIS, we are excited to play a part in the evolving DITA standard. Talking to our customers we know that there are many features of DITA 1.3 they are interested in and we are already in the process of adapting our product, the IXIASOFT DITA CMS, to ensure that our users can benefit from the new DITA standard as soon as possible.”
— Eric Bergeron, CEO, IXIASOFT

PTC
“PTC has actively supported and endorsed the DITA standard since its first release. We have seen a large number of customers embrace and realize the value of the DITA standard through content reuse and flexibility. PTC is excited to continue promoting DITA 1.3 for cus-tomers utilizing our Service and Parts Information Solution.”
–Pushpinder Toor, Director, SLM Solution Management, PTC

Oracle
“Oracle welcomes the continued development of the DITA specification. As an early adopter, Oracle invested heavily in DITA with both specialized and non-specialized markup. Now pervasive throughout Oracle, DITA is truly an evolving information development ecosystem. A perfect fit for Oracle’s ever-growing needs, DITA 1.3 promises enhanced accessibility, plus welcome improvements for large, interrelated publications with DITA features like scoped keys and cross–deliverable linking.”
–Jennifer Briscoe, VP, Product Development, Oracle

SDL
“SDL, a leader in global content management and language software and services, is pleased to see that DITA 1.3 is about to be approved as a standard. SDL has always pioneered the use of DITA in its structured content management solution, SDL Knowledge Center, to store, organize and manage all modular content in any language. The use of DITA allows our customers to easily reuse, share, filter and deliver content to all appropriate channels.”
–Dennis van der Veeke, CTO, SDL

About OASIS:

OASIS (Organization for the Advancement of Structured Information Standards) drives the development, convergence, and adoption of open standards for the global information society. A nonprofit consortium, OASIS advances standards for content technologies, IoT, security, cloud computing, emergency management, e-commerce, e-government, and other areas. OASIS open standards offer the potential to lower cost, stimulate innovation, grow global markets, and protect the right of free choice of technology. The consortium has more than 5,000 participants representing over 600 organizations and individual members in 100 countries.

Press contact: Carol Geyer, OASIS Senior Director, carol.geyer@oasis-open.org

ISO and IEC Approve OASIS UBL Universal Business Language Standard

Geneva, Switzerland and Boston, MA, USA; 28 January 2016-– The Universal Business Language (UBL), developed by the OASIS open standards consortium, has now been approved for release as an ISO and IEC International Standard. Version 2.1 of UBL was balloted through the Joint Technical Committee on Information Technology (JTC1) of the International Standards Organization (ISO) and the International Electrotechnical Commission (IEC) and given the designation ‘ISO/IEC 19845:2015’.

UBL is widely used around the world for procurement (e.g. ordering and electronic invoicing), sourcing (e.g. tendering and catalogues), replenishment (e.g. managed inventory) and transportation and logistics (e.g. waybills, forwarding instructions, and intermodal freight management).

“Allowing audiences to speak the same language and promoting a standardized exchange of data in electronic documents is of crucial importance for businesses and organizations. It helps optimize cost and avoids data lock-in. The IEC is happy to note that the Universal Business Language (UBL) Standard, developed by the OASIS open standards consortium, is now adopted as an International Standard, through the ISO IEC Joint Technical Committee on Information Technology (JTC1),” said Frans Vreeswijk, IEC General Secretary and CEO.

UBL provides the standards for the PEPPOL (Pan European eProcurement Online) platform and public procurement initiatives in Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Netherlands, Norway, Spain, Sweden, and UK (NHS). The European Commission chose UBL as one of the first consortium standards officially eligible for referencing in tenders from public administrations. UBL is now used routinely by government agencies for electronic invoicing across Europe as well as in Turkey, Peru, Colombia, and Panama.

“One of ways the software industry can assist in trade facilitation is to standardize on the formats of the data being exchanged in electronic documents. But until recently, the use of differing or proprietary formats has effectively created barriers to trade. This milestone marks the point at which the industry can stop debating what standards they should use for trade documents and start delivering the benefits to trade that such an opportunity offers,” said Tim McGrath, co-chair (Business Analysis) of the OASIS UBL Technical Committee.

“The publication of a comprehensive, royalty-free, international XML standard for electronic commerce ensures that businesses will not be locked into proprietary formats as they move into the digital age,” said Jon Bosak, who organized the OASIS UBL Technical Committee in 2001 and led the effort through the completion of UBL 2.1 in 2013. “Adoption of UBL will foster the growth of an entire standards-based ecosystem, leading to the creation of inexpensive, off-the-shelf solutions and lowering the cost of entry for enterprises of every size.”

“In UBL, developers find a complete library of XML schemas for a suite of structured data objects for common business documents. Being able to pick up and use peer-approved, structured document validation artifacts (for example, an electronic invoice), precludes having to create one’s own colloquial schemas for such XML documents. To meet custom sector-specific requirements, communities can tailor additional data objects to augment the standardized structures,” added G. Ken Holman, co-chair (XML technology) of the OASIS UBL Technical Committee.

“ISO/IEC approval of UBL as an International Standard is a logical milestone for a standard that is broadly used in public procurement and trading communities around the world,” noted Laurent Liscia, CEO of OASIS. “We appreciate the support this action shows for the OASIS open standards process, and we join ISO and IEC in recognizing the value and long-term viability of UBL.”

UBL 1.0 was published in 2004. In 2013, UBL 2.1 was ratified as an OASIS Standard and subsequently submitted by OASIS to the ISO/IEC JTC 1 Information Technology body. As ISO/IEC 19845, the standard will continue to be maintained and advanced by the OASIS UBL Technical Committee, which includes representatives of Boeing, Danish Ministry of Finance, NEC, Swedish Association of Local Authorities, US Department of Defense, Tradeshift and others. New members are welcome.

Additional Information:

ISO/IEC 19845:2015

OASIS UBL Technical Committee

About ISO/IEC JTC 1
JTC 1 is the standards development environment where experts come together to develop worldwide Information and Communication Technology (ICT) standards for business and consumer applications. Since 1987, ISO/IEC JTC 1 has brought about a number of very successful and relevant information and communication technologies (ICT) standards in many fields: IC cards (smart cards), automatic identification and data capture (AIDC) technologies, information security, biometrics, cloud computing, multimedia (MPEG), database query and programming languages as well as character sets, to name just a few. http://jtc1info.org/

About OASIS
OASIS is a non-profit, international consortium that drives the development, convergence and adoption of open standards for the global information society. OASIS promotes industry consensus and produces worldwide standards for business transactions, cloud computing, content technologies, security, privacy, M2M, IoT, energy, and other areas. OASIS open standards offer the potential to lower cost, stimulate innovation, grow global markets, and protect the right of free choice of technology. OASIS members broadly represent the marketplace of public and private sector technology leaders, users, and influencers. The consortium has more than 5,000 participants representing over 600 organizations and individual members in 65+ countries. http://www.oasis-open.org

OASIS press contact: Carol Geyer, OASIS Senior Director of Communications, carol.geyer@oasis-open.org +1.941.284.0403

30-day Public Review for #OData JSON Format for Common Schema Definition Language (CSDL) V4.0 – ends February 26th

The OASIS Open Data Protocol (OData) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted it for 30-day public review:

OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0
Committee Specification Draft 01 / Public Review Draft 01
03 December 2015

Overview:

The Open Data Protocol (OData) for representing and interacting with structured content is comprised of a set of specifications. This document extends the specification OData Version 4.0 Part 3: Conceptual Schema Definition Language (CSDL) by defining a JSON format for representing OData CSDL documents.

This JSON format for CSDL is based on JSON Schema.

Public Review Period:

The public review starts 28 January 2016 at 00:00 UTC and ends 26 February 2016 at 23:59 UTC.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs:

The prose specification document and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/odata/odata-json-csdl/v4.0/csprd01/odata-json-csdl-v4.0-csprd01.docx

HTML:
http://docs.oasis-open.org/odata/odata-json-csdl/v4.0/csprd01/odata-json-csdl-v4.0-csprd01.html

PDF:
http://docs.oasis-open.org/odata/odata-json-csdl/v4.0/csprd01/odata-json-csdl-v4.0-csprd01.pdf

JSON schema:
http://docs.oasis-open.org/odata/odata-json-csdl/v4.0/csprd01/schema/edm.json

ZIP distribution file (complete):

For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/odata/odata-json-csdl/v4.0/csprd01/odata-json-csdl-v4.0-csprd01.zip

Additional information about the specification and the OASIS Open Data Protocol (OData) TC can be found at the TC’s public home page:

https://www.oasis-open.org/committees/odata/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odata

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

https://lists.oasis-open.org/archives/odata-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of “OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0”, we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

========== Additional references:

[1] OASIS Open Data Protocol (OData) TC
https://www.oasis-open.org/committees/odata/

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/odata/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.2
RF on RAND Mode

15-day Public Review for #UBL Naming and Design Rules Version 3.0 – ends February 10th

The OASIS Universal Business Language (UBL) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

UBL Naming and Design Rules Version 3.0
Committee Specification Draft 02
16 December 2015

Specification Overview:

This specification prescribes a set of naming and design rules used to create XML document model validation artefacts (W3C Schema XSD files and OASIS Context/value association files) associated with abstract information bundles formally described using the Core Component Technical Specification 2.01 [CCTS].

** Also, please note this specific request from the TC **

Proposals are being considered to retitle this work product. Candidate new titles will be welcome as part of the public review. Two of the candidates being considered are:

– “Core Component Technical Specification 2.01 XML Naming and Design Rules Version 1.0”, and

– “ebXML Business Document Naming and Design Rules Version 1.0”.

Changing the title is not expected to change the body of the document in any way.

Reviewers with an opinion regarding these or other proposed title changes are invited to include comment about this in their response.

Public Review Period:

The public review starts 27 January 2016 at 00:00 UTC and ends 10 February 2016 at 11:59 UTC. The specification was previously submitted for public review [2].

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs:
The prose specification document and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/ubl/UBL-NDR/v3.0/csprd02/UBL-NDR-v3.0-csprd02.xml

HTML:
http://docs.oasis-open.org/ubl/UBL-NDR/v3.0/csprd02/UBL-NDR-v3.0-csprd02.html

PDF:
http://docs.oasis-open.org/ubl/UBL-NDR/v3.0/csprd02/UBL-NDR-v3.0-csprd02.pdf

ZIP distribution files (complete):

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/ubl/UBL-NDR/v3.0/csprd02/UBL-NDR-v3.0-csprd02.zip

Additional information about this specification and the OASIS Universal Business Language (UBL) TC may be found on the TC’s public home page located at:

http://www.oasis-open.org/committees/ubl/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=ubl

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/ubl-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of ‘UBL Naming and Design Rules Version 3.0 ‘, we call your attention to the OASIS IPR Policy [3] applicable especially [4] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

========== Additional references:

[1] OASIS Universal Business Language (UBL) TC
http://www.oasis-open.org/committees/ubl/

[2] Previous public reviews:

30-day public review, 17 March 2015:
https://lists.oasis-open.org/archives/members/201503/msg00002.html
– Comment resolution log:
http://docs.oasis-open.org/ubl/UBL-NDR/v3.0/csprd01/UBL-NDR-v3.0-csprd01-comment-resolution-log.txt

[3] http://www.oasis-open.org/policies-guidelines/ipr

[4] http://www.oasis-open.org/committees/ubl/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Terms Mode

XML Interchange Language for System Dynamics (#XMILE) V1.0 OASIS Standard published

OASIS is pleased to announce the publication of its newest OASIS Standard, approved by the members on 14 December 2015:

XML Interchange Language for System Dynamics (XMILE) Version 1.0
OASIS Standard
14 December 2015

What is XMILE?

XMILE enables System Dynamics modelers to share models and tools across platforms. Before XMILE, System Dynamics models were stored only in proprietary formats and it was impossible to share or build off of others work unless you used the same tool – and that tool also supported the features you needed.

XMILE enables the sharing of models and archiving of important models, the re-use of common components, the development of add-on tools that support the modeling process, and the integration with Big Data.

If you would like to learn more about system dynamics and XMILE, watch this webinar presented by members of the Technical Committee in November 2015.

https://youtu.be/4gntgKn-ST4

URIs:

The prose specifications and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/xmile/xmile/v1.0/os/xmile-v1.0-os.doc

HTML:
http://docs.oasis-open.org/xmile/xmile/v1.0/os/xmile-v1.0-os.html

PDF:
http://docs.oasis-open.org/xmile/xmile/v1.0/os/xmile-v1.0-os.pdf

Distribution ZIP files

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/xmile/xmile/v1.0/os/xmile-v1.0-os.zip

Our congratulations to the members of the OASIS XML Interchange Language (XMILE) for System Dynamics TC on achieving this milestone.

Public review for #WS-Calendar Minimal PIM-Conformant Schema V1.0 – ends February 18th

The OASIS Web Services Calendar (WS-Calendar) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted it for 30-day public review:

WS-Calendar Minimal PIM-Conformant Schema Version 1.0
Committee Specification Draft 01 / Public Review Draft 01
18 December 2015

Overview:

The WS-Calendar MIN is a WS-Calendar conformant schema optimized for use in machine-to-machine (M2M) schedule negotiations.

iCalendar (RFC5545) and its peer specification XCAL (also in WS-Calendar 1.0) is a well-known and long used means to convey schedule-related information. iCalendar makes extensive use of extension and recursion. The WS-Calendar Platform Independent Model (PIM) constrains iCalendar and defines a simpler information model which shares iCalendar semantics and can be used to create as the common basis for any number of Platform Specific Models (PSMs).

Because an information model is abstract, it can apply to many transmission and serialization schemas. The PIM itself does not include a transmission and serialization schema. Through transitive conformance such PSMs themselves conform to WS-Calendar. The Minimal PIM-Conformant (MIN) schema defines an XML Schema that conforms just with the PIM. MIN can be used by itself or as a seed-schema for other specifications.

Public Review Period:

The public review starts 20 January 2016 at 00:00 UTC and ends 18 February 2016 at 23:59 UTC.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

Reviewers may provide comments directly from the comment-tag version of document. The file

ws-calendar-min-v1.0-csprd01-COMMENT-TAGS.html

contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to ws-calendar-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send.

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ws-calendar.

URIs:

The prose specification document and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd01/ws-calendar-min-v1.0-csprd01.pdf

HTML:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd01/ws-calendar-min-v1.0-csprd01.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd01/ws-calendar-min-v1.0-csprd01-COMMENT-TAGS.html

Editable source:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd01/ws-calendar-min-v1.0-csprd01.docx

ZIP distribution file (complete):

For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd01/ws-calendar-min-v1.0-csprd01.zip

Additional information about the specification and the OASIS Web Services Calendar (WS-Calendar) TC can be found at the TC’s public home page:

https://www.oasis-open.org/committees/ws-calendar/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ws-calendar

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

https://lists.oasis-open.org/archives/ws-calendar-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of “WS-Calendar Minimal PIM-Conformant Schema Version 1.0”, we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

========== Additional references:

[1] OASIS Web Services Calendar (WS-Calendar) TC
https://www.oasis-open.org/committees/ws-calendar/

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/ws-calendar/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

30-day Public Review for #STIX Version 1.2.1 and #TAXII Version 1.1.1 – ends February 17th

The OASIS Cyber Threat Intelligence (CTI) TC [1] members have recently approved two Committee Specification Drafts (CSDs) and submitted them for 30-day public review:

STIX[TM] Version 1.2.1
Committee Specification Draft 01 / Public Review Draft 01
06 November 2015

and

TAXII[TM] Version 1.1.1
Committee Specification Draft 01 / Public Review Draft 01
06 November 2015

Special Notice:
In these Public Review Drafts, certain notations have been included in square brackets (e.g., “[TM]”) that have been proposed by the Technical Committee, but are still under management review, and may or may not appear in the finalized specification, pending approval by the OASIS Board of Directors.

Contents
——–
1. Overview
2. Public Review Period
3. Specification URIs
3.a – STIX Version 1.2.1
3.b – TAXII Version 1.1.1
3.c – ZIP distribution files
4. How to submit comments
5. Additional references

1. Overview

The Structured Threat Information Expression (STIX) is a collaborative, community-driven effort to define and develop a framework for expressing cyber threat information to enable cyber threat information sharing and cyber threat analysis. The STIX framework comprises a collection of extensible component specifications along with an overarching core specification and supporting specifications. STIX Version 1.2.1 provides an overview of those specifications and defines how they are used within the broader STIX framework.

The Trusted Automated eXchange of Indicator Information (TAXII) defines a set of services and message exchanges that, when implemented, enable sharing of actionable cyber threat information across organization and product/service boundaries. TAXII Version 1.1.1 defines concepts, protocols and messages to exchange cyber threat information for the detection, prevention, and mitigation of cyber threats. TAXII is not an information sharing initiative or application and does not attempt to define trust agreements, governance, or non-technical aspects of cyber threat information sharing. Instead, TAXII empowers organizations to achieve improved situational awareness about emerging threats, and enables organizations to easily share the information they choose with the partners they choose.

2. Public Review Period

The public review starts 19 January 2016 at 00:00 UTC and ends 17 February 2016 at 23:59 UTC.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

Reviewers may provide comments directly from the comment-tag versions of the documents. Files with

…-COMMENT-TAGS.html

in their filename contain the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to cti-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send. (Note however that some links such as the table of contents do not work in these files.)

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=cti.

3. Specification URIs

The prose specification document and related files are available here:

3.a – STIX Version 1.2.1
Committee Specification Draft 01 / Public Review Draft 01
06 November 2015

– STIX Version 1.2.1. Part 1: Overview

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part1-overview/stix-v1.2.1-csprd01-part1-overview.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part1-overview/stix-v1.2.1-csprd01-part1-overview.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part1-overview/stix-v1.2.1-csprd01-part1-overview-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part1-overview/stix-v1.2.1-csprd01-part1-overview.pdf

– STIX Version 1.2.1. Part 2: Common

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part2-common/stix-v1.2.1-csprd01-part2-common.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part2-common/stix-v1.2.1-csprd01-part2-common.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part2-common/stix-v1.2.1-csprd01-part2-common-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part2-common/stix-v1.2.1-csprd01-part2-common.pdf

– STIX Version 1.2.1. Part 3: Core

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part3-core/stix-v1.2.1-csprd01-part3-core.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part3-core/stix-v1.2.1-csprd01-part3-core.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part3-core/stix-v1.2.1-csprd01-part3-core-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part3-core/stix-v1.2.1-csprd01-part3-core.pdf

– STIX Version 1.2.1. Part 4: Indicator

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part4-indicator/stix-v1.2.1-csprd01-part4-indicator.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part4-indicator/stix-v1.2.1-csprd01-part4-indicator.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part4-indicator/stix-v1.2.1-csprd01-part4-indicator-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part4-indicator/stix-v1.2.1-csprd01-part4-indicator.pdf

– STIX Version 1.2.1. Part 5: TTP

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part5-ttp/stix-v1.2.1-csprd01-part5-ttp.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part5-ttp/stix-v1.2.1-csprd01-part5-ttp.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part5-ttp/stix-v1.2.1-csprd01-part5-ttp-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part5-ttp/stix-v1.2.1-csprd01-part5-ttp.pdf

– STIX Version 1.2.1. Part 6: Incident

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part6-incident/stix-v1.2.1-csprd01-part6-incident.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part6-incident/stix-v1.2.1-csprd01-part6-incident.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part6-incident/stix-v1.2.1-csprd01-part6-incident-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part6-incident/stix-v1.2.1-csprd01-part6-incident.pdf

– STIX Version 1.2.1. Part 7: Threat Actor

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part7-threat-actor/stix-v1.2.1-csprd01-part7-threat-actor.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part7-threat-actor/stix-v1.2.1-csprd01-part7-threat-actor.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part7-threat-actor/stix-v1.2.1-csprd01-part7-threat-actor-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part7-threat-actor/stix-v1.2.1-csprd01-part7-threat-actor.pdf

– STIX Version 1.2.1. Part 8: Campaign

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part8-campaign/stix-v1.2.1-csprd01-part8-campaign.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part8-campaign/stix-v1.2.1-csprd01-part8-campaign.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part8-campaign/stix-v1.2.1-csprd01-part8-campaign-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part8-campaign/stix-v1.2.1-csprd01-part8-campaign.pdf

– STIX Version 1.2.1. Part 9: Course of Action

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part9-coa/stix-v1.2.1-csprd01-part9-coa.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part9-coa/stix-v1.2.1-csprd01-part9-coa.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part9-coa/stix-v1.2.1-csprd01-part9-coa-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part9-coa/stix-v1.2.1-csprd01-part9-coa.pdf

– STIX Version 1.2.1. Part 10: Exploit Target

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part10-exploit-target/stix-v1.2.1-csprd01-part10-exploit-target.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part10-exploit-target/stix-v1.2.1-csprd01-part10-exploit-target.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part10-exploit-target/stix-v1.2.1-csprd01-part10-exploit-target-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part10-exploit-target/stix-v1.2.1-csprd01-part10-exploit-target.pdf

– STIX Version 1.2.1. Part 11: Report

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part11-report/stix-v1.2.1-csprd01-part11-report.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part11-report/stix-v1.2.1-csprd01-part11-report.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part11-report/stix-v1.2.1-csprd01-part11-report-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part11-report/stix-v1.2.1-csprd01-part11-report.pdf

– STIX Version 1.2.1. Part 12: Default Extensions

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part12-extensions/stix-v1.2.1-csprd01-part12-extensions.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part12-extensions/stix-v1.2.1-csprd01-part12-extensions.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part12-extensions/stix-v1.2.1-csprd01-part12-extensions-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part12-extensions/stix-v1.2.1-csprd01-part12-extensions.pdf

– STIX Version 1.2.1. Part 13: Data Marking

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part13-data-marking/stix-v1.2.1-csprd01-part13-data-marking.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part13-data-marking/stix-v1.2.1-csprd01-part13-data-marking.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part13-data-marking/stix-v1.2.1-csprd01-part13-data-marking-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part13-data-marking/stix-v1.2.1-csprd01-part13-data-marking.pdf

– STIX Version 1.2.1. Part 14: Vocabularies

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part14-vocabularies/stix-v1.2.1-csprd01-part14-vocabularies.doc

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part14-vocabularies/stix-v1.2.1-csprd01-part14-vocabularies.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part14-vocabularies/stix-v1.2.1-csprd01-part14-vocabularies-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part14-vocabularies/stix-v1.2.1-csprd01-part14-vocabularies.pdf

– STIX Version 1.2.1. Part 15: UML Model

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part15-uml-model/stix-v1.2.1-csprd01-part15-uml-model.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part15-uml-model/stix-v1.2.1-csprd01-part15-uml-model.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part15-uml-model/stix-v1.2.1-csprd01-part15-uml-model-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part15-uml-model/stix-v1.2.1-csprd01-part15-uml-model.pdf

– STIX UML Model:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/uml-model/

3.b – TAXII Version 1.1.1
Committee Specification Draft 01 / Public Review Draft 01
06 November 2015

– TAXII Version 1.1.1. Part 1: Overview

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part1-overview/taxii-v1.1.1-csprd01-part1-overview.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part1-overview/taxii-v1.1.1-csprd01-part1-overview.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part1-overview/taxii-v1.1.1-csprd01-part1-overview-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part1-overview/taxii-v1.1.1-csprd01-part1-overview.pdf

– TAXII Version 1.1.1. Part 2: Services

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part2-services/taxii-v1.1.1-csprd01-part2-services.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part2-services/taxii-v1.1.1-csprd01-part2-services.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part2-services/taxii-v1.1.1-csprd01-part2-services-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part2-services/taxii-v1.1.1-csprd01-part2-services.pdf

– TAXII Version 1.1.1. Part 3: HTTP Protocol Binding

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part3-http/taxii-v1.1.1-csprd01-part3-http.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part3-http/taxii-v1.1.1-csprd01-part3-http.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part3-http/taxii-v1.1.1-csprd01-part3-http-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part3-http/taxii-v1.1.1-csprd01-part3-http.pdf

– TAXII Version 1.1.1. Part 4: XML Message Binding

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part4-xml/taxii-v1.1.1-csprd01-part4-xml.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part4-xml/taxii-v1.1.1-csprd01-part4-xml.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part4-xml/taxii-v1.1.1-csprd01-part4-xml-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part4-xml/taxii-v1.1.1-csprd01-part4-xml.pdf

– TAXII Version 1.1.1. Part 5: Default Query

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part5-query/taxii-v1.1.1-csprd01-part5-query.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part5-query/taxii-v1.1.1-csprd01-part5-query.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part5-query/taxii-v1.1.1-csprd01-part5-query-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part5-query/taxii-v1.1.1-csprd01-part5-query.pdf

– XML schemas:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/schemas/TAXII-DefaultQuery-Schema.xsd

http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/schemas/TAXII-XMLMessageBinding-Schema.xsd

3.c – ZIP distribution files (complete):

For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:

– STIX Version 1.2.1:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/stix-v1.2.1-csprd01.zip

– TAXII Version 1.1.1:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/taxii-v1.1.1-csprd01.zip

Additional information about the specification and the OASIS Cyber Threat Intelligence (CTI) TC can be found at the TC’s public home page:

https://www.oasis-open.org/committees/cti/

4. How to submit comments

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=cti

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

https://lists.oasis-open.org/archives/cti-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of “STIX Version 1.2.1” and “TAXII Version 1.1.1,” we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

5. Additional references

[1] OASIS Cyber Threat Intelligence (CTI) TC
https://www.oasis-open.org/committees/cti/

TC Charter
https://www.oasis-open.org/committees/cti/charter.php

TC IPR page and disclosures
https://www.oasis-open.org/committees/cti/ipr.php

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/cti/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

30-day Public Review for #STIX Version 1.2.1 and #TAXII Version 1.1.1 – ends February 17th

The OASIS Cyber Threat Intelligence (CTI) TC [1] members have recently approved two Committee Specification Drafts (CSDs) and submitted them for 30-day public review:

STIX[TM] Version 1.2.1
Committee Specification Draft 01 / Public Review Draft 01
06 November 2015

and

TAXII[TM] Version 1.1.1
Committee Specification Draft 01 / Public Review Draft 01
06 November 2015

Special Notice:
In these Public Review Drafts, certain notations have been included in square brackets (e.g., “[TM]”) that have been proposed by the Technical Committee, but are still under management review, and may or may not appear in the finalized specification, pending approval by the OASIS Board of Directors.

Contents
——–
1. Overview
2. Public Review Period
3. Specification URIs
3.a – STIX Version 1.2.1
3.b – TAXII Version 1.1.1
3.c – ZIP distribution files
4. How to submit comments
5. Additional references

1. Overview

The Structured Threat Information Expression (STIX) is a collaborative, community-driven effort to define and develop a framework for expressing cyber threat information to enable cyber threat information sharing and cyber threat analysis. The STIX framework comprises a collection of extensible component specifications along with an overarching core specification and supporting specifications. STIX Version 1.2.1 provides an overview of those specifications and defines how they are used within the broader STIX framework.

The Trusted Automated eXchange of Indicator Information (TAXII) defines a set of services and message exchanges that, when implemented, enable sharing of actionable cyber threat information across organization and product/service boundaries. TAXII Version 1.1.1 defines concepts, protocols and messages to exchange cyber threat information for the detection, prevention, and mitigation of cyber threats. TAXII is not an information sharing initiative or application and does not attempt to define trust agreements, governance, or non-technical aspects of cyber threat information sharing. Instead, TAXII empowers organizations to achieve improved situational awareness about emerging threats, and enables organizations to easily share the information they choose with the partners they choose.

2. Public Review Period

The public review starts 19 January 2016 at 00:00 UTC and ends 17 February 2016 at 23:59 UTC.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

Reviewers may provide comments directly from the comment-tag versions of the documents. Files with

…-COMMENT-TAGS.html

in their filename contain the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to cti-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send. (Note however that some links such as the table of contents do not work in these files.)

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=cti.

3. Specification URIs

The prose specification document and related files are available here:

3.a – STIX Version 1.2.1
Committee Specification Draft 01 / Public Review Draft 01
06 November 2015

– STIX Version 1.2.1. Part 1: Overview

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part1-overview/stix-v1.2.1-csprd01-part1-overview.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part1-overview/stix-v1.2.1-csprd01-part1-overview.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part1-overview/stix-v1.2.1-csprd01-part1-overview-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part1-overview/stix-v1.2.1-csprd01-part1-overview.pdf

– STIX Version 1.2.1. Part 2: Common

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part2-common/stix-v1.2.1-csprd01-part2-common.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part2-common/stix-v1.2.1-csprd01-part2-common.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part2-common/stix-v1.2.1-csprd01-part2-common-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part2-common/stix-v1.2.1-csprd01-part2-common.pdf

– STIX Version 1.2.1. Part 3: Core

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part3-core/stix-v1.2.1-csprd01-part3-core.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part3-core/stix-v1.2.1-csprd01-part3-core.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part3-core/stix-v1.2.1-csprd01-part3-core-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part3-core/stix-v1.2.1-csprd01-part3-core.pdf

– STIX Version 1.2.1. Part 4: Indicator

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part4-indicator/stix-v1.2.1-csprd01-part4-indicator.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part4-indicator/stix-v1.2.1-csprd01-part4-indicator.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part4-indicator/stix-v1.2.1-csprd01-part4-indicator-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part4-indicator/stix-v1.2.1-csprd01-part4-indicator.pdf

– STIX Version 1.2.1. Part 5: TTP

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part5-ttp/stix-v1.2.1-csprd01-part5-ttp.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part5-ttp/stix-v1.2.1-csprd01-part5-ttp.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part5-ttp/stix-v1.2.1-csprd01-part5-ttp-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part5-ttp/stix-v1.2.1-csprd01-part5-ttp.pdf

– STIX Version 1.2.1. Part 6: Incident

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part6-incident/stix-v1.2.1-csprd01-part6-incident.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part6-incident/stix-v1.2.1-csprd01-part6-incident.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part6-incident/stix-v1.2.1-csprd01-part6-incident-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part6-incident/stix-v1.2.1-csprd01-part6-incident.pdf

– STIX Version 1.2.1. Part 7: Threat Actor

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part7-threat-actor/stix-v1.2.1-csprd01-part7-threat-actor.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part7-threat-actor/stix-v1.2.1-csprd01-part7-threat-actor.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part7-threat-actor/stix-v1.2.1-csprd01-part7-threat-actor-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part7-threat-actor/stix-v1.2.1-csprd01-part7-threat-actor.pdf

– STIX Version 1.2.1. Part 8: Campaign

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part8-campaign/stix-v1.2.1-csprd01-part8-campaign.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part8-campaign/stix-v1.2.1-csprd01-part8-campaign.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part8-campaign/stix-v1.2.1-csprd01-part8-campaign-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part8-campaign/stix-v1.2.1-csprd01-part8-campaign.pdf

– STIX Version 1.2.1. Part 9: Course of Action

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part9-coa/stix-v1.2.1-csprd01-part9-coa.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part9-coa/stix-v1.2.1-csprd01-part9-coa.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part9-coa/stix-v1.2.1-csprd01-part9-coa-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part9-coa/stix-v1.2.1-csprd01-part9-coa.pdf

– STIX Version 1.2.1. Part 10: Exploit Target

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part10-exploit-target/stix-v1.2.1-csprd01-part10-exploit-target.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part10-exploit-target/stix-v1.2.1-csprd01-part10-exploit-target.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part10-exploit-target/stix-v1.2.1-csprd01-part10-exploit-target-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part10-exploit-target/stix-v1.2.1-csprd01-part10-exploit-target.pdf

– STIX Version 1.2.1. Part 11: Report

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part11-report/stix-v1.2.1-csprd01-part11-report.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part11-report/stix-v1.2.1-csprd01-part11-report.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part11-report/stix-v1.2.1-csprd01-part11-report-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part11-report/stix-v1.2.1-csprd01-part11-report.pdf

– STIX Version 1.2.1. Part 12: Default Extensions

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part12-extensions/stix-v1.2.1-csprd01-part12-extensions.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part12-extensions/stix-v1.2.1-csprd01-part12-extensions.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part12-extensions/stix-v1.2.1-csprd01-part12-extensions-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part12-extensions/stix-v1.2.1-csprd01-part12-extensions.pdf

– STIX Version 1.2.1. Part 13: Data Marking

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part13-data-marking/stix-v1.2.1-csprd01-part13-data-marking.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part13-data-marking/stix-v1.2.1-csprd01-part13-data-marking.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part13-data-marking/stix-v1.2.1-csprd01-part13-data-marking-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part13-data-marking/stix-v1.2.1-csprd01-part13-data-marking.pdf

– STIX Version 1.2.1. Part 14: Vocabularies

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part14-vocabularies/stix-v1.2.1-csprd01-part14-vocabularies.doc

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part14-vocabularies/stix-v1.2.1-csprd01-part14-vocabularies.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part14-vocabularies/stix-v1.2.1-csprd01-part14-vocabularies-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part14-vocabularies/stix-v1.2.1-csprd01-part14-vocabularies.pdf

– STIX Version 1.2.1. Part 15: UML Model

Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part15-uml-model/stix-v1.2.1-csprd01-part15-uml-model.docx

HTML:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part15-uml-model/stix-v1.2.1-csprd01-part15-uml-model.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part15-uml-model/stix-v1.2.1-csprd01-part15-uml-model-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/part15-uml-model/stix-v1.2.1-csprd01-part15-uml-model.pdf

– STIX UML Model:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/uml-model/

3.b – TAXII Version 1.1.1
Committee Specification Draft 01 / Public Review Draft 01
06 November 2015

– TAXII Version 1.1.1. Part 1: Overview

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part1-overview/taxii-v1.1.1-csprd01-part1-overview.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part1-overview/taxii-v1.1.1-csprd01-part1-overview.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part1-overview/taxii-v1.1.1-csprd01-part1-overview-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part1-overview/taxii-v1.1.1-csprd01-part1-overview.pdf

– TAXII Version 1.1.1. Part 2: Services

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part2-services/taxii-v1.1.1-csprd01-part2-services.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part2-services/taxii-v1.1.1-csprd01-part2-services.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part2-services/taxii-v1.1.1-csprd01-part2-services-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part2-services/taxii-v1.1.1-csprd01-part2-services.pdf

– TAXII Version 1.1.1. Part 3: HTTP Protocol Binding

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part3-http/taxii-v1.1.1-csprd01-part3-http.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part3-http/taxii-v1.1.1-csprd01-part3-http.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part3-http/taxii-v1.1.1-csprd01-part3-http-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part3-http/taxii-v1.1.1-csprd01-part3-http.pdf

– TAXII Version 1.1.1. Part 4: XML Message Binding

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part4-xml/taxii-v1.1.1-csprd01-part4-xml.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part4-xml/taxii-v1.1.1-csprd01-part4-xml.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part4-xml/taxii-v1.1.1-csprd01-part4-xml-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part4-xml/taxii-v1.1.1-csprd01-part4-xml.pdf

– TAXII Version 1.1.1. Part 5: Default Query

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part5-query/taxii-v1.1.1-csprd01-part5-query.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part5-query/taxii-v1.1.1-csprd01-part5-query.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part5-query/taxii-v1.1.1-csprd01-part5-query-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/part5-query/taxii-v1.1.1-csprd01-part5-query.pdf

– XML schemas:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/schemas/TAXII-DefaultQuery-Schema.xsd

http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/schemas/TAXII-XMLMessageBinding-Schema.xsd

3.c – ZIP distribution files (complete):

For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:

– STIX Version 1.2.1:
http://docs.oasis-open.org/cti/stix/v1.2.1/csprd01/stix-v1.2.1-csprd01.zip

– TAXII Version 1.1.1:
http://docs.oasis-open.org/cti/taxii/v1.1.1/csprd01/taxii-v1.1.1-csprd01.zip

Additional information about the specification and the OASIS Cyber Threat Intelligence (CTI) TC can be found at the TC’s public home page:

https://www.oasis-open.org/committees/cti/

4. How to submit comments

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=cti

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

https://lists.oasis-open.org/archives/cti-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of “STIX Version 1.2.1” and “TAXII Version 1.1.1,” we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

5. Additional references

[1] OASIS Cyber Threat Intelligence (CTI) TC
https://www.oasis-open.org/committees/cti/

TC Charter
https://www.oasis-open.org/committees/cti/charter.php

TC IPR page and disclosures
https://www.oasis-open.org/committees/cti/ipr.php

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/cti/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

XLIFF OMOS Briefing: Developing a Serialization-Independent Object Model for XLIFF 2, 21 Jan / 17:00 CET

Join the GALA localization industry briefing on the new OASIS initiative to advance standards-based payload and metadata interoperability.

No results with the selected filters