OASIS Open Projects
Open source projects now have path to international recognition in policy & procurement
60-day Public Review for Akoma Ntoso V1.0 COS01 – ends August 12th
Members of the OASIS LegalDocumentML(LegalDocML) TC [1] have recently approved a Special Majority Ballot [2] to advance Akoma Ntoso Version 1.0 as a Candidate OASIS Standard (COS). The COS now enters a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.
Akoma Ntoso means “linked hearts” in the Akan language of West Africa. For legal publishers and makers of legal information systems, Akoma Ntoso provides a framework for creating “machine readable” parliamentary, legislative and judiciary documents such as legislation, debate records, minutes, judgements, etc. In doing so, it helps build a strong foundation for “open access” to government information.
The specification is in two parts:
Part 1: XML Vocabulary presents the main motivations, design principles, and benefits of the Akoma Ntoso vocabulary and approach. The document is non-normative material that presents the main pillars of Akoma Ntoso to the stakeholders that need to take decisions about how to manage legal sources in a digital manner in a Semantic Web society.
Part 2: Specifications documents the Akoma Ntoso XSD and DTD standard, including the graphic representation using Oxygen library.
Akoma Ntoso received 8 Statements of Use from the Parliamentary Counsel Office of the Scottish Government, the Biblioteca del Congreso Nacional de Chile, Xcential Corporation, Aubay s.a., the ICT Conception and Development Unit of the Directorate General of Innovation and Technological Support of the European Parliament, Information Systems Development of the Italian Senate, The Meeting Programming and Documentation Service of the Food and Agriculture Organization of the United Nations (FAO), and CIRSFID, University of Bologna. [3].
The COS is available here:
Akoma Ntoso Version 1.0
Candidate OASIS Standard 01
08 May 2018
– Part 1: XML Vocabulary
HTML (Authoritative):
http://docs.oasis-open.org/legaldocml/akn-core/v1.0/cos01/part1-vocabulary/akn-core-v1.0-cos01-part1-vocabulary.html
Editable source:
http://docs.oasis-open.org/legaldocml/akn-core/v1.0/cos01/part1-vocabulary/akn-core-v1.0-cos01-part1-vocabulary.doc
– Part 2: Specifications
HTML (Authoritative):
http://docs.oasis-open.org/legaldocml/akn-core/v1.0/cos01/part2-specs/akn-core-v1.0-cos01-part2-specs.html
XML schemas:
http://docs.oasis-open.org/legaldocml/akn-core/v1.0/cos01/part2-specs/schemas/
XML examples:
http://docs.oasis-open.org/legaldocml/akn-core/v1.0/cos01/part2-specs/examples/
ZIP distribution file (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/legaldocml/akn-core/v1.0/cos01/akn-core-v1.0-cos01.zip
The 60-day public review starts 14 June 2018 at 00:00 UTC and ends 12 August 2018 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.
Additional information about the specification and the LegalDocML TC may be found at the TC’s public home page:
https://www.oasis-open.org/committees/legaldocml/
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=legaldocml
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/legaldocml-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 “Akoma Ntoso Version 1.0,” 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.
==============
[1] OASIS LegalDocumentML(LegalDocML) TC
https://www.oasis-open.org/committees/legaldocml/
[2] Special Majority Vote:
https://www.oasis-open.org/committees/ballot.php?id=3205
[3] Statements of Use:
Parliamentary Counsel Office of the Scottish Government: https://www.oasis-open.org/committees/download.php/63011/8.AKN%20letter.pdf
Biblioteca del Congreso Nacional de Chile: https://www.oasis-open.org/committees/download.php/63010
XCential Corporation: https://www.oasis-open.org/committees/download.php/62423/statementOfUse.zip
Aubay s.a.: https://www.oasis-open.org/committees/download.php/62423/statementOfUse.zip
The ICT Conception and Development Unit of the Directorate General of Innovation and Technological Support of the European Parliament: https://www.oasis-open.org/committees/download.php/62423/statementOfUse.zip
Information Systems Development of the Italian Senate:https://www.oasis-open.org/committees/download.php/62423/statementOfUse.zip
The Meeting Programming and Documentation Service of the Food and Agriculture Organization of the United Nations (FAO): https://www.oasis-open.org/committees/download.php/62423/statementOfUse.zip
CIRSFID, University of Bologna: https://www.oasis-open.org/committees/download.php/62423/statementOfUse.zip
[4] http://www.oasis-open.org/policies-guidelines/ipr
[5] http://www.oasis-open.org/committees/legaldocml/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode
Invitation to comment on #OSLC Core Version 3.0 from the OSLC Core TC – ends June 21st
We are pleased to announce that OSLC Core Version 3.0 from the OASIS OSLC Lifecycle Integration Core (OSLC Core) TC [1] is now available for public review and comment.
Information Technology enterprises are constantly looking for more efficient development processes. They want integration of their software or hardware development tools regardless of vendor but this level of integration is challenging to achieve. In order to enable integration between various tools, OSLC seeks to define a sufficient supporting architecture that is loosely coupled, minimal, and standardized. It is based on World Wide Web and Linked Data principles, and provides a cohesive set of specifications that can enable products, services, and other distributed network resources to interoperate successfully.
The documents and related files are available here:
OSLC Core Version 3.0
Committee Specification Draft 03 / Public Review Draft 03
31 May 2018
– Part 1: Overview
HTML (Authoritative):
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/part1-overview/oslc-core-v3.0-csprd03-part1-overview.html
– Part 2: Discovery
HTML (Authoritative):
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/part2-discovery/oslc-core-v3.0-csprd03-part2-discovery.html
– Part 3: Resource Preview
HTML (Authoritative):
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/part3-resource-preview/oslc-core-v3.0-csprd03-part3-resource-preview.html
– Part 4: Delegated Dialogs
HTML (Authoritative):
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/part4-delegated-dialogs/oslc-core-v3.0-csprd03-part4-delegated-dialogs.html
– Part 5: Attachments
HTML (Authoritative):
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/part5-attachments/oslc-core-v3.0-csprd03-part5-attachments.html
– Part 6: Resource Shape
HTML (Authoritative):
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/part6-resource-shape/oslc-core-v3.0-csprd03-part6-resource-shape.html
– Part 7: Vocabulary
HTML (Authoritative):
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/part7-core-vocabulary/oslc-core-v3.0-csprd03-part7-core-vocabulary.html
Additional components:
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/contexts/
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/schema/
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/shapes/
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/styles/
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/vocab/
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:
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd03/oslc-core-v3.0-csprd03.zip
How to Provide Feedback
OASIS and the OSLC Core 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 07 June 2018 at 00:00 UTC and ends 21 June 2018 at 11:59 UTC.
This specification was previously submitted for public review [2].
Comments on the work may be submitted to the TC by following the instructions located at:
http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=oslc-core
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/oslc-core-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 [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 information about this specification and the OSLC Core TC may be found on the TC’s public home page.
========== Additional references:
[1] OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
http://www.oasis-open.org/committees/oslc-core/
[2] Previous public reviews:
– 15-day public review, 17 February 2017:
https://lists.oasis-open.org/archives/members/201702/msg00006.html
– Comment resolution log:
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd02/oslc-core-v3.0-csprd02-comment-resolution-log.xls
– 30-day public review, 29 August 2016:
https://lists.oasis-open.org/archives/members/201608/msg00004.html
– Comment resolution log:
http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/csprd01/oslc-core-v3.0-csprd01-comment-resolution-log.xls
[3] http://www.oasis-open.org/policies-guidelines/ipr
[4] http://www.oasis-open.org/committees/oslc-core/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode
Cloud Application Management for Platforms V1.2 from the CAMP TC approved as a Committee Specification
OASIS is pleased to announce that Cloud Application Management for Platforms V1.2 from the OASIS Cloud Application Management for Platforms (CAMP) TC [1] has been approved as an OASIS Committee Specification.
For cloud application developers, Cloud Application Management for Platforms Version 1.2 defines the artifacts and APIs that need to be offered by a Platform as a Service (PaaS) cloud to manage building, running, administering, and monitoring applications in a cloud.
Its key purpose is to enable interoperability among self-service interfaces to PaaS clouds by defining artifacts and formats that can be used with any conforming cloud. This enables independent vendors to create tools and services that interact with any conforming cloud using the defined interfaces.
Cloud vendors can use these interfaces to develop new PaaS offerings that will interoperate with other, independently-developed tools and components.
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:
Cloud Application Management for Platforms Version 1.2
Committee Specification 01
15 May 2018
PDF (Authoritative):
http://docs.oasis-open.org/camp/camp-spec/v1.2/cs01/camp-spec-v1.2-cs01.pdf
HTML:
http://docs.oasis-open.org/camp/camp-spec/v1.2/cs01/camp-spec-v1.2-cs01.html
Editable source:
http://docs.oasis-open.org/camp/camp-spec/v1.2/cs01/camp-spec-v1.2-cs01.doc
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:
http://docs.oasis-open.org/camp/camp-spec/v1.2/cs01/camp-spec-v1.2-cs01.zip
Members of the CAMP 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 Cloud Application Management for Platforms (CAMP) TC
https://www.oasis-open.org/committees/camp/
[2] Public reviews:
* 30-day public review, 25 May 2017:
https://lists.oasis-open.org/archives/camp/201705/msg00011.html
– Comment resolution log:
TBD
* 15-day public review, 11 January 2018:
https://lists.oasis-open.org/archives/members/201801/msg00003.html
– Comment resolution log:
http://docs.oasis-open.org/camp/camp-spec/v1.2/csprd02/camp-spec-v1.2-csprd02-comment-resolution-log.txt
[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3209
Invitation to comment on #DITA V1.3 Errata 02 from the DITA TC – ends June 13th
We are pleased to announce that Darwin Information Typing Architecture (DITA) Version 1.3 Errata 02 from the OASIS Darwin Information Typing Architecture (DITA) TC [1] is now available for public review and comment.
The document contains the errata for Darwin Information Typing Architecture (DITA) Version 1.3. A version of the complete DITA v1.3 OASIS Standard with the draft errata applied is included in the package.
The documents and related files are available here:
Darwin Information Typing Architecture (DITA) Version 1.3 Errata 02
Committee Specification Draft 01 / Public Review Draft 01
23 January 2018
HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/dita-v1.3-errata02-csprd01.html
PDF:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/dita-v1.3-errata02-csprd01.pdf
Editorial Source:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/dita-v1.3-errata02-csprd01-dita.zip
– DITA v1.3. Part 0: Overview Plus Errata 02.
HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/complete/part0-overview/dita-v1.3-errata02-csprd01-part0-overview-complete.html.
Editorial Source:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/complete/part0-overview/dita-v1.3-errata02-csprd01-part0-overview-complete-dita.zip
– DITA v1.3. Part 1: Base Edition Plus Errata 02.
HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/complete/part1-base/dita-v1.3-errata02-csprd01-part1-base-complete.html
Editorial source:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/complete/part1-base/dita-v1.3-errata02-csprd01-part1-base-complete-dita.zip
– DITA v1.3. Part 2: Technical Content Edition Plus Errata 02.
HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/complete/part2-tech-content/dita-v1.3-errata02-csprd01-part2-tech-content-complete.html
Editorial Source:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/complete/part2-tech-content/dita-v1.3-errata02-csprd01-part2-tech-content-complete-dita.zip
– DITA v1.3. Part 3: All-Inclusive Edition Plus Errata 02.
HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/complete/part3-all-inclusive/dita-v1.3-errata02-csprd01-part3-all-inclusive-complete.html
Editorial source:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/complete/part3-all-inclusive/dita-v1.3-errata02-csprd01-part3-all-inclusive-complete-dita.zip
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:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/csprd01/dita-v1.3-errata02-csprd01.zip
How to Provide Feedback
OASIS and the DITA 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 30 May 2018 at 00:00 UTC and ends 13 June 2018 at 11:59 UTC.
Comments on the work may be submitted to the TC by following the instructions located at:
http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=dita
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/dita-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 [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 information about this specification and the DITA TC may be found on the TC’s public home page.
========== Additional references:
[1] OASIS Darwin Information Typing Architecture (DITA) TC
http://www.oasis-open.org/committees/dita/
[2] http://www.oasis-open.org/policies-guidelines/ipr
[3] http://www.oasis-open.org/committees/dita/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode
OASIS updates privacy & webcookie disclosures
Learn about what we do with your data, your rights & controls
#MQTT V5.0 Committee Specification 02 approved & published
OASIS is pleased to announce that Committee Specification 02 of MQTT Version 5.0 from the OASIS Message Queuing Telemetry Transport (MQTT) TC [1] has been approved as an OASIS Committee Specification.
MQTT is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections.
The changes from CS01 were non-material. A red-lined PDF highlighting the changes is also included in this package [2].
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:
MQTT Version 5.0
Committee Specification 02
15 May 2018
Editable source (Authoritative):
http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.docx
HTML:
http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.html
PDF:
http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.pdf
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:
http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.zip
Members of the MQTT TC approved this specification by Special Majority Vote [3].
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 Message Queuing Telemetry Transport (MQTT) TC
https://www.oasis-open.org/committees/mqtt/
[2] http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02-DIFF.pdf
[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3210
TrendMicro becomes newest OASIS Sponsor
Cybersecurity company to advance STIX & TAXII
#LegalRuleML Core Specification V1.0 from the OASIS LegalRuleML TC approved as a Committee Specification
OASIS is pleased to announce that LegalRuleML Core Specification Version 1.0 from the OASIS LegalRuleML TC [1] has been approved as an OASIS Committee Specification.
Legal texts, e.g. legislation, regulations, contracts, and case law, are the source of norms, guidelines, and rules. As text, it is difficult to exchange specific information content contained in the texts between parties, to search for and extract structured the content from the texts, or to automatically process it further. Legislators, legal practitioners, and business managers are, therefore, impeded from comparing, contrasting, integrating, and reusing the contents of the texts, since any such activities are manual. In the current web-enabled context, where innovative eGovernment and eCommerce applications are increasingly deployed, it has become essential to provide machine-readable forms (generally in XML) of the contents of the text.
The objective of the LegalRuleML Core Specification Version 1.0 is to define a standard (expressed with XML-schema and Relax NG and on the basis of Consumer RuleML 1.02) that is able to represent the particularities of the legal normative rules with a rich, articulated, and meaningful mark-up language.
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:
LegalRuleML Core Specification Version 1.0
Committee Specification 01
08 May 2018
HTML (Authoritative):
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/legalruleml-core-spec-v1.0-cs01.html
Editable source:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/legalruleml-core-spec-v1.0-cs01.docx
XSD schemas:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/xsd-schema/
RelaxNG schemas:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/relaxng/
XSLT transformations:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/xslt/
XSD-conversion drivers:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/generation/
RDFS metamodel:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/rdfs/
Metamodel diagrams:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/diagrams/
Examples:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/cs01/examples/
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:
Members of the LegalRuleML 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 LegalRuleML TC
https://www.oasis-open.org/committees/legalruleml/
[2] Public reviews:
* 30-day public review, 13 February 2017:
https://lists.oasis-open.org/archives/members/201702/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/legalruleml-core-spec-v1.0-csprd01-comment-resolution-log.xls
* 15-day public review, 15 September 2017:
https://lists.oasis-open.org/archives/members/201709/msg00008.html
– Comment resolution log:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/legalruleml-core-spec-v1.0-csprd02-comment-resolution-log.txt
[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3204
Invitation to comment on Classification of Everyday Living V1.0 from the #COEL TC – ends May 23rd
We are pleased to announce that Classification of Everyday Living Version 1.0 from the OASIS Classification of Everyday Living (COEL) TC [1] is now available for public review and comment. This is the third public review for COEL V1.0 and incorporates updates to Committee Specification 01.
The OASIS COEL specification provides a privacy-by-design framework for the collection and processing of behavioural data. It is uniquely suited to the transparent use of dynamic data for personalised digital services, IoT applications where devices are collecting information about identifiable individuals and the coding of behavioural data in identity solutions. The specification pseudonymises personal data at source and maintains a separation of different data types with clearly defined roles & responsibilities for all actors. All behavioural data are defined as event-based packets. Every packet is connected directly to an individual and can contain a summary of the consent they provided for the processing of the data. A combination of a taxonomy of all human behaviours and the event-based protocol provide a universal template for data portability. Simple interface specifications enforce the separation of roles and provide system-level interoperability.
The documents and related files are available here:
Classification of Everyday Living Version 1.0
Committee Specification Draft 04 / Public Review Draft 03
04 May 2018
Specification URIs
Editable source (Authoritative):
http://docs.oasis-open.org/coel/COEL/v1.0/csprd03/COEL-v1.0-csprd03.docx
HTML:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd03/COEL-v1.0-csprd03.html
PDF:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd03/COEL-v1.0-csprd03.pdf
COEL model v1.0:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd03/model/coel.json
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:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd03/COEL-v1.0-csprd03.zip
How to Provide Feedback
OASIS and the COEL 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 09 May 2018 at 00:00 UTC and ends 23 May 2018 at 11:59 UTC.
This 15-day review is limited in scope to changes made to Committee Specification 01. Changes are highlighted in red-lined file included in the package [3].
Comments on the work may be submitted to the TC by following the instructions located at:
http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=coel
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/coel-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 COEL TC may be found on the TC’s public home page.
========== Additional references:
[1] OASIS Classification of Everyday Living (COEL) TC
http://www.oasis-open.org/committees/coel/
[2] Previous public reviews:
– 30-day public review, 10 November 2016:
https://lists.oasis-open.org/archives/members/201611/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd01/COEL-v1.0-csprd01-comment-resolution-log.xlsx
– 15-day public review, 11 December 2017:
https://lists.oasis-open.org/archives/members/201712/msg00002.html
– Comment resolution log:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd02/COEL-v1.0-csprd02-comment-resolution-log.xlsx
[3] Red-lined version:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd03/COEL-v1.0-csprd03-DIFF.pdf
[4] http://www.oasis-open.org/policies-guidelines/ipr
[5] http://www.oasis-open.org/committees/coel/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Mode
Invitation to comment on Exchange Header Envelope (XHE) V1.0 – ends May 29th
OASIS members and other interested parties,
OASIS and the OASIS Business Document Exchange (BDXR) TC [1] are pleased to announce that Exchange Header Envelope (XHE) Version 1.0 is now available for public review and comment.
The Exchange Header Envelope (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.
XHE, a specification developed jointly by UN/CEFACT and OASIS, is the successor to the UN/CEFACT Standard Business Document Header (SBDH) version 1.3 [SBDH] and the OASIS Business Document Envelope (BDE) version 1.1 [BDE].
The documents and related files are available here:
Exchange Header Envelope (XHE) Version 1.0
Committee Specification Public Review Draft 01
23 April 2018
Editable source (Authoritative):
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xhe-v1.0-csprd01.xml
HTML:
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xhe-v1.0-csprd01-oasis.html
PDF:
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xhe-v1.0-csprd01-oasis.pdf
Document models of information bundles:
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/mod
Annotated XSD schemas:
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xsd
Runtime XSD schemas:
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xsdrt/XHE-1.0.xsd
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:
http://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xhe-v1.0-csprd01.zip
How to Provide Feedback
OASIS and the BDXR TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
The public review starts 30 April 2018 at 00:00 UTC and ends 29 May 2018 at 23:59 UTC.
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=bdxr).
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/bdxr-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, 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 information about the specification and the TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/bdxr/
========== Additional references:
[1] OASIS Business Document Exchange (BDXR) TC
https://www.oasis-open.org/committees/bdxr/
[2] http://www.oasis-open.org/who/intellectualproperty.php
[3] http://www.oasis-open.org/committees/bdxr/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode
60-day Public Review for Universal Business Language (#UBL) V2.2 COS01 – ends June 23rd
Members of the OASIS Universal Business Language TC [1] have recently approved a Special Majority Ballot [2] to advance Universal Business Language Version 2.2 as a Candidate OASIS Standard (COS). The COS now enters a 60-day public review period in preparation for the member call to consider its approval as an OASIS Standard.
The Universal Business Language (UBL) is an open library of standard electronic XML business documents for procurement and transportation such as purchase orders, invoices, transport logistics and waybills. 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.
Version 2.2 is completely backward-compatible with UBL 2.0. UBL is freely available to everyone without legal encumbrance or licensing fees.
The TC has received 3 Statements of Use from JAVEST, the eSENS eTendering pilot, and the Norwegian Agency for Public Management and eGovernment (Difi) [3].
The prose specifications and related files are available at:
Universal Business Language Version 2.2
Candidate OASIS Standard 01
22 April 2018
Editable source (Authoritative):
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.xml
HTML:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.html
PDF:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.pdf
Code lists for constraint validation:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/cl/
Context/value Association files for constraint validation:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/cva/
Document models of information bundles:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/mod/
Default validation test environment:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/val/
XML examples:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xml/
Annotated XSD schemas:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xsd/
Runtime XSD schemas:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xsdrt/
ZIP distribution file (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 at:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.zip
Public Review Period:
The 60-day public review begins 25 April 2018 at 00:00 UTC and ends 23 June 2018 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.
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=ubl
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/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 “Universal Business Language Version 2.2,” 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.
==============
[1] OASIS Universal Business Language TC
http://www.oasis-open.org/committees/ubl/
[2] https://www.oasis-open.org/committees/ballot.php?id=3200
[3] Statements of Use:
JAVEST: https://lists.oasis-open.org/archives/ubl/201803/msg00025.html
eSENS eTendering pilot: https://lists.oasis-open.org/archives/ubl-comment/201804/msg00000.html
Norwegian Agency for Public Management and eGovernment (Difi): https://lists.oasis-open.org/archives/ubl/201804/msg00003.html
[4] http://www.oasis-open.org/policies-guidelines/ipr
[5] http://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
No results with the selected filters