XACML v3.0 Related and Nested Entities Profile v1.0 approved as a Committee Specification

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the eXtensible Access Control Markup Language (XACML) TC [1]:

XACML v3.0 Related and Nested Entities Profile Version 1.0
Committee Specification 02
16 February 2021

Overview:

It is not unusual for access control policy to be dependent on attributes that are not naturally properties of the access subject or resource, but rather are properties of entities that are related to the access subject or resource. This profile defines the means to reference such attributes from within XACML policies for processing by a policy decision point.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Editable source (Authoritative):
https://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs02/xacml-3.0-related-entities-v1.0-cs02.docx
HTML:
https://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs02/xacml-3.0-related-entities-v1.0-cs02.html
PDF:
https://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs02/xacml-3.0-related-entities-v1.0-cs02.pdf
XML schemas:
https://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs02/schemas/

Distribution ZIP file

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:

https://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs02/xacml-3.0-related-entities-v1.0-cs02.zip

Members of the eXtensible Access Control Markup Language (XACML) TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references

[1] eXtensible Access Control Markup Language (XACML) TC
https://www.oasis-open.org/committees/xacml/

[2] Details of public reviews:
– https://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/csd02/xacml-3.0-related-entities-v1.0-csd02-public-review-metadata.html

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3567

Universal Business Language v2.3 from the UBL TC approved as a Committee Specification

OASIS is pleased to announce that Universal Business Language Version 2.3 from the OASIS Universal Business Language TC [1] has been approved as an OASIS Committee Specification.

UBL is the leading interchange format for business documents. It is designed to operate within a standard business framework such as ISO/IEC 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to businesses of all sizes. The European Commission has declared UBL officially eligible for referencing in tenders from public administrations, and in 2015 UBL was approved as ISO/IEC 19845:2015.

Specifically, UBL provides:

  • A suite of structured business objects and their associated semantics expressed as reusable data components and common business documents.
  • A library of schemas for reusable data components such as Address, Item, and Payment, the common data elements of everyday business documents.
  • A set of schemas for common business documents such as Order, Despatch Advice, and Invoice that are constructed from the UBL library components and can be used in generic procurement and transportation contexts.

UBL v2.3 is a minor revision to v2.2 that preserves backwards compatibility with previous v2.# versions. It adds new document types, bringing the total number of UBL business documents to 91.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Universal Business Language Version 2.3
Committee Specification 01
19 January 2021

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/UBL-2.3.xml

HTML:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/UBL-2.3.html

PDF:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/UBL-2.3.pdf

Code lists for constraint validation:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/cl/

Context/value Association files for constraint validation:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/cva/

Document models of information bundles:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/mod/

Default validation test environment:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/val/

XML examples:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/xml/

Annotated XSD schemas:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/xsd/

Runtime XSD schemas:
https://docs.oasis-open.org/ubl/cs01-UBL-2.3/xsdrt/

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 at:

https://docs.oasis-open.org/ubl/cs01-UBL-2.3/UBL-2.3.zip

Members of the UBL TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references:

[1] OASIS Universal Business Language TC
https://www.oasis-open.org/committees/ubl

[2] History of publication, including public reviews:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/UBL-2.3-csd04-public-review-metadata.html

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3552

STIX Version 2.1 from CTI TC approved as a Committee Specification

OASIS is pleased to announce that STIX Version 2.1 from the OASIS Cyber Threat Intelligence (CTI) TC [1] has been approved as an OASIS Committee Specification.

Structured Threat Information Expression (STIX™) is a language and serialization format used to exchange cyber threat intelligence. STIX enables organizations and tools to share threat intelligence with one another in a way that improves many different capabilities, such as collaborative threat analysis, automated threat exchange, automated detection and response, and more.

STIX v2.1 adds new objects and concepts and incorporates improvements based on experience implementing Version 2.0. The objects and features added for inclusion represent an iterative approach to fulfilling basic consumer and producer requirements for CTI sharing. Objects and properties not included in this version of STIX, but deemed necessary by the community, will be included in future releases.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

STIX Version 2.1
Committee Specification 02
25 January 2021

Editable source (Authoritative):
https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02.docx
HTML:
https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02.html
PDF:
https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02.pdf

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

https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02.zip

Members of the CTI TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

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

[2] Public reviews:
This Committee Specification contains changes made since its last public review. The changes made are documented in https://docs.oasis-open.org/cti/stix/v2.1/csd05/stix-v2.1-csd05-comment-resolution-log.xlsx. A change-marked PDF document is available at https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02-DIFF.pdf.
Information on earlier public reviews is available at https://docs.oasis-open.org/cti/stix/v2.1/csd05/stix-v2.1-csd05-public-review-metadata.html.

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3556

CACAO Security Playbooks v1.0 approved as a Committee Specification

OASIS is pleased to announce that CACAO Security Playbooks Version 1.0 from the OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Security TC [1] has been approved as an OASIS Committee Specification.

To defend against threat actors and their tactics, techniques, and procedures, organizations need to identify, create, document, and test detection, investigation, prevention, mitigation, and remediation steps. These steps, when grouped together, form a cyber security playbook that can be used to protect organizational systems, networks, data, and users.

This specification defines the schema and taxonomy for cybersecurity playbooks and how cybersecurity playbooks can be created, documented, and shared in a structured and standardized way across organizational boundaries and technological solutions.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

CACAO Security Playbooks Version 1.0
Committee Specification 01
12 January 2021

Editable source (Authoritative):
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs01/security-playbooks-v1.0-cs01.docx
HTML:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs01/security-playbooks-v1.0-cs01.html
PDF:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs01/security-playbooks-v1.0-cs01.pdf

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

https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs01/security-playbooks-v1.0-cs01.zip

Members of the CACAO TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references:
[1] OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Security TC
https://www.oasis-open.org/committees/cacao/

[2] Public review metadata document:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/csd02/security-playbooks-v1.0-csd02-public-review-metadata.html
– Comment resolution log:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/csd02/security-playbooks-v1.0-csd02-comment-resolution-log.txt

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3551

Invitation to comment on STIX v2.1

We are pleased to announce that STIX Version 2.1 Committee Specification Draft 05 from the OASIS Cyber Threat Intelligence (CTI) TC [1] is now available for public review and comment.

Structured Threat Information Expression (STIX) is a language and serialization format used to exchange cyber threat intelligence. STIX enables organizations and tools to share threat intelligence with one another in a way that improves many different capabilities, such as collaborative threat analysis, automated threat exchange, automated detection and response, and more.

STIX v2.1 adds new objects and concepts and incorporates improvements based on experience implementing Version 2.0. The objects and features added for inclusion represent an iterative approach to fulfilling basic consumer and producer requirements for CTI sharing. Objects and properties not included in this version of STIX, but deemed necessary by the community, will be included in future releases.

The documents and related files are available here:

STIX Version 2.1
Committee Specification Draft 05
18 December 2020

Editable source (Authoritative):
https://docs.oasis-open.org/cti/stix/v2.1/csd05/stix-v2.1-csd05.docx

HTML:
https://docs.oasis-open.org/cti/stix/v2.1/csd05/stix-v2.1-csd05.html

PDF:
https://docs.oasis-open.org/cti/stix/v2.1/csd05/stix-v2.1-csd05.pdf

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 at:
https://docs.oasis-open.org/cti/stix/v2.1/csd05/stix-v2.1-csd05.zip

How to Provide Feedback

OASIS and the CTI TC value your feedback. We solicit 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.

This public review starts 23 December 2020 at 00:00 UTC and ends 06 January 2021 at 11:59 UTC.

This specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous reviews. Changes are highlighted in a red-lined DIFF file included in the package [3].

Comments on the work may be submitted to the TC by following the instructions located at:
https://www.oasis-open.org/committees/comments/form.php?wg_abbrev=cti

Feedback submitted by TC non-members for this work and for other work of this TC is 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 the public review of these works, we call your attention to the OASIS IPR Policy [4] applicable especially [5] 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 information about this specification and the CTI TC may be found on the TC’s public home page [1].

Additional information related to this public review can be found in the public review metadata document [2].

Additional references:

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

[2] Public review metadata document, including timeline of previous public reviews:
– https://docs.oasis-open.org/cti/stix/v2.1/csd05/stix-v2.1-csd05-public-review-metadata.html

[3] Red-lined version:
https://docs.oasis-open.org/cti/stix/v2.1/csd05/stix-v2.1-csd05-DIFF.pdf

[4] https://www.oasis-open.org/policies-guidelines/ipr

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

Exchange Header Envelope (XHE) v1.0 from BDXR TC approved as a Committee Specification

OASIS is pleased to announce that Exchange Header Envelope (XHE) Version 1.0 from the OASIS Business Document Exchange (BDXR) TC [1] has been approved as an OASIS Committee Specification.

The Exchange Header Envelope (XHE) has been developed jointly by UN/CEFACT and OASIS as the successor to the UN/CEFACT Standard Business Document Header (SBDH) version 1.3 and the OASIS Business Document Envelope (BDE) Version 1.1.

XHE defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion. This vocabulary is modeled using the UN/CEFACT Core Component Technical Specification Version 2.01.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Exchange Header Envelope (XHE) Version 1.0
Committee Specification 03
13 December 2020

Editable source (Authoritative):
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs03/xhe-v1.0-cs03.xml
HTML:
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs03/xhe-v1.0-cs03-oasis.html
PDF:
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs03/xhe-v1.0-cs03-oasis.pdf
XML schemas and documentation:
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs03/xsd/
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs03/xsdrt/
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs03/mod/

Distribution ZIP file
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:
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs03/xhe-v1.0-cs03.zi

Members of the BDXR TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references:

[1] OASIS Business Document Exchange (BDXR) TC
https://www.oasis-open.org/committees/bdxr/

[2] Public review timeline:
Details of the three public reviews are listed in:
https://docs.oasis-open.org/bdxr/xhe/v1.0/csd03/xhe-v1.0-csd03-public-review-metadata.html
Comment resolution log for most recent public review:
https://docs.oasis-open.org/bdxr/xhe/v1.0/csd03/xhe-v1.0-csd03-comment-resolution-log.xlsx

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3544

Invitation to comment on Universal Business Language v2.3 from the UBL TC

We are pleased to announce that Universal Business Language Version 2.3 from the UBL TC [1] is now available for public review and comment. This is the fourth public review for Universal Business Language v2.3.

UBL is the leading interchange format for business documents. It is designed to operate within a standard business framework such as ISO/IEC 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to businesses of all sizes. The European Commission has declared UBL officially eligible for referencing in tenders from public administrations, and in 2015 UBL was approved as ISO/IEC 19845:2015.

Specifically, UBL provides:

  • A suite of structured business objects and their associated semantics expressed as reusable data components and common business documents.
  • A library of schemas for reusable data components such as Address, Item, and Payment, the common data elements of everyday business documents.
  • A set of schemas for common business documents such as Order, Despatch Advice, and Invoice that are constructed from the UBL library components and can be used in generic procurement and transportation contexts.

UBL v2.3 is a minor revision to v2.2 that preserves backwards compatibility with previous v2.# versions. It adds new document types, bringing the total number of UBL business documents to 91.

The specification documents and related files are available here:

Universal Business Language Version 2.3
Committee Specification Draft 04
25 November 2020

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/UBL-2.3.xml
HTML:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/UBL-2.3.html
PDF:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/UBL-2.3.pdf
Code lists for constraint validation:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/cl/
Context/value Association files for constraint validation:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/cva/
Document models of information bundles:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/mod/
Default validation test environment:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/val/
XML examples:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/xml/
Annotated XSD schemas:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/xsd/
Runtime XSD schemas:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/xsdrt/

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 at:

https://docs.oasis-open.org/ubl/csd04-UBL-2.3/UBL-2.3.zip

How to Provide Feedback

OASIS and the UBL TC value your feedback. We solicit 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.

This public review starts 15 December 2020 at 00:00 UTC and ends 29 December 2020 at 11:59 UTC.

This specification was previously submitted for public review [2]. This 15-day review may be limited in scope to changes made from the previous review. Changes are described in the previous comment resolution log [2] and highlighted in a red-lined file included in the package [3].

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 (https://www.oasis-open.org/committees/comments/index.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:
https://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 the public review of this work, we call your attention to the OASIS IPR Policy [4] applicable especially [5] 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 information about this specification and the UBL TC may be found on the TC’s public home page [1].

Additional references:

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

[2] Previous public reviews and comment resolution logs:
– Please see the “Timeline Summary” in the public review metadata document at:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/UBL-2.3-csd04-public-review-metadata.html

[3] Red-lined version:
https://docs.oasis-open.org/ubl/csd04-UBL-2.3/csd04-UBL-2.3-DIFF.pdf

[4] https://www.oasis-open.org/policies-guidelines/ipr

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

Open Document Format for Office Applications (OpenDocument) v1.3 from the OpenDocument TC approved as a Committee Specification

OASIS is pleased to announce that Open Document Format for Office Applications (OpenDocument) v1.3 from the OpenDocument TC [1] has been approved as an OASIS Committee Specification.

The OpenDocument Format is an open XML-based document file format for office applications, to be used for documents containing text, spreadsheets, charts, and graphical elements. OpenDocument Format v1.3 is an update to the international standard Version 1.2, which was approved by the International Organization for Standardization (ISO) as ISO/IEC 26300 (2015). OpenDocument Format v1.3 includes improvements for document security, clarifies underspecifications and makes other timely improvements.

The OpenDocument Format specifies the characteristics of an open XML-based application-independent and platform-independent digital document file format, as well as the characteristics of software applications which read, write and process such documents. It is applicable to document authoring, editing, viewing, exchange and archiving, including text documents, spreadsheets, presentation graphics, drawings, charts and similar documents commonly used by personal productivity software applications.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Open Document Format for Office Applications (OpenDocument) Version 1.3
Committee Specification 02
30 October 2020

Part 1: Introduction
Editable source (Authoritative):
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part1-introduction/OpenDocument-v1.3-cs02-part1-introduction.odt
HTML:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part1-introduction/OpenDocument-v1.3-cs02-part1-introduction.html
PDF:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part1-introduction/OpenDocument-v1.3-cs02-part1-introduction.pdf

Part 2: Packages
Editable source (Authoritative):
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part2-packages/OpenDocument-v1.3-cs02-part2-packages.odt
HTML:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part2-packages/OpenDocument-v1.3-cs02-part2-packages.html
PDF:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part2-packages/OpenDocument-v1.3-cs02-part2-packages.pdf

Part 3: OpenDocument Schema
Editable source (Authoritative):
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.odt
HTML:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.html
PDF:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.pdf

Part 4: Recalculated Formula (OpenFormula) Format
Editable source (Authoritative):
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part4-formula/OpenDocument-v1.3-cs02-part4-formula.odt
HTML:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part4-formula/OpenDocument-v1.3-cs02-part4-formula.html
PDF:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part4-formula/OpenDocument-v1.3-cs02-part4-formula.pdf

XML/RNG schemas and OWL ontologies:
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/schemas/

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 at:

https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/OpenDocument-v1.3-cs02.zip

Members of the OpenDocument TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references:

[1] OASIS Open Document Format for Office Applications (OpenDocument) TC
https://www.oasis-open.org/committees/office/

[2] Previous public reviews:

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3529

No results with the selected filters