There are no changes to the published documents (Part 1: Specification, Part 2: Vocabulary, and Part 3: Constraints). Changes have been made only to the two machine-readable "turtle" files (promcode-vocab.ttl and promcode-shapes.ttl).

Status:

This document was last revised or approved by the OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TC on the above date. The level of approval is also listed above. Check the "Latest stage" location noted above for possible later revisions of this document. Any other numbered Versions and other technical work produced by the Technical Committee (TC) are listed at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=oslc-promcode#technical.

TC members should send comments on this document to the TC's email list. Others should send comments to the TC's public comment list, after subscribing to it by following the instructions at the "Send A Comment" button on the TC's web page at https://www.oasis-open.org/committees/oslc-promcode/.

This document is provided under the RF on Limited Terms Mode of the OASIS IPR Policy, the mode chosen when the Technical Committee was established. For information on whether any patents have been disclosed that may be essential to implementing this document, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the TC's web page (https://www.oasis-open.org/committees/oslc-promcode/ipr.php).

Note that any machine-readable content (Computer Language Definitions) declared Normative for this Work Product is provided in separate plain text files. In the event of a discrepancy between any such plain text file and display content in the Work Product's prose narrative document(s), the content in the separate plain text file prevails.

Citation format:

When referencing this document, the following citation format should be used:

[OSLC-PROMCODE-v1.0-Errata01]

OSLC PROMCODE Version 1.0 Errata 01. Edited by Mikio Aoyama, Yoshio Horiuchi, Tom Kamimura, Shinji Matsuoka, Shigeaki Matsumoto, Masaki Wakao, Kazuo Yabuta, and Hiroyuki Yoshida. 03 June 2022. OASIS Approved Errata. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/errata01/os/promcode-v1.0-errata01-os.html. Latest stage: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/errata01/promcode-v1.0-errata01.html.

Notices:

Distributed under the terms of the OASIS IPR Policy, [https://www.oasis-open.org/policies-guidelines/ipr/]. For complete copyright information please see the full Notices section in an Appendix below.

Table of Contents

1 Introduction. 4

1.1 Description of changes. 4

1.2 Scope of changes. 4

2 Conformance. 5

Appendix A. References. 6

A.1 Normative references. 6

A.2 Informative references. 6

Appendix B. Acknowledgments. 7

B.1 Special Thanks. 7

B.2 Participants. 7

Appendix C. Notices. 8

1 Introduction

This document lists the approved changes to the OASIS Standard OSLC PROMCODE Version 1.0 [OSLC-PROMCODE-v1.0-OS], a multi-part specification consisting of the following components:

· OSLC PROMCODE Version 1.0. Part 1: Specification.

· OSLC PROMCODE Version 1.0. Part 2: Vocabulary.

· OSLC PROMCODE Version 1.0. Part 3: Constraints.

· Machine-readable vocabulary terms: promcode-vocab.ttl.

· Machine-readable constraints: promcode-shapes.ttl.

1.1 Description of changes

After the PROMCODE specification was approved as OS, the members of the OSLC PROMCODE TC worked with OSLC Open Project team to include two machine-readable files (promcode-shapes.ttl and promcode-vocab.ttl) in their GitHub repository, as all such machine-readable files are made available from the OSLC Open Project. In doing so, we had to make a few editorial modifications to these files to meet the strict requirement of the OSLC Open Project.

Three kinds of modifications to the machine-readable files were needed:

1. Changes to the approved date, and the status of specification, from CS03 to OS.

2. Changes to some URLs to reference the specification documents in the official site of OASIS library.

3. Eliminating blank characters immediately before the end of string enclosed by “…”. Also, eliminating a new line character within a string enclosed in “…”. A tool to check the format, called Shape checker, produced a number of warnings without these modifications, and the OSLC Open Project required the warnings to be eliminated.

All the changes made are purely editorial and therefore non-material.

1.2 Scope of changes

The only approved changes are to the two machine-readable files, promcode-shapes.ttl and promcode-vocab.ttl.

The corrected machine-readable files are linked in the section "Additional artifacts" on the title page.

2 Conformance

1. The conformance requirements stated in the OASIS Standard OSLC PROMCODE Version 1.0 [OSLC-PROMCODE-v1.0-OS] are not changed in any way by the publication of this Errata document.

Appendix A. References

A.1 Normative references

The following documents are referenced in such a way that some or all of their content constitutes requirements of this document.

[OSLC-PROMCODE-v1.0-OS]

OSLC PROMCODE Version 1.0. Edited by Mikio Aoyama, Yoshio Horiuchi, Tom Kamimura, Shinji Matsuoka, Shigeaki Matsumoto, Masaki Wakao, Kazuo Yabuta, and Hiroyuki Yoshida. 11 March 2022. OASIS Standard. A multi-part specification consisting of the following components:

· OSLC PROMCODE Version 1.0. Part 1: Specification. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/os/promcode-spec.html.

· OSLC PROMCODE Version 1.0. Part 2: Vocabulary. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/os/promcode-vocab.html.

· OSLC PROMCODE Version 1.0. Part 3: Constraints. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/os/promcode-shapes.html.

· Machine-readable vocabulary terms: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/os/promcode-vocab.ttl.

· Machine-readable constraints: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/os/promcode-shapes.ttl.

A.2 Informative references

[PROMCODE13]

PROMCODE (PROject Management of COntracted Delivery), Interface Specification, Version 1. http://www.promcode.org/

Appendix B. Acknowledgments

B.1 Special Thanks

The PROMCODE TC would like to thank the members of the PROMCODE Consortium [PROMCODE13] for their work that became a precursor to the current work. The TC would also like to thank Prof. Mikio Aoyama of Nanzan University who served as the Chair of the TC from March of 2014 to May of 2021. His leadership, dedication and broad experience with project management played a major role in shaping the content of the specification. The TC would also like to thank Nanzan University for their support of the OASIS PROMCODE activity. Finally, thanks by the TC also go to Arthur Ryman and Kazuhiko Funakoshi who helped in creating technical content at an early stage of the project.

B.2 Participants

The following individuals were members of the OSLC PROMCODE Technical Committee during the creation of this document and their contributions are gratefully acknowledged:

Amsden, Mr. James - IBM

Horiuchi, Mr. Yoshio - IBM

Kamimura, Dr. Tom - Individual

Kobayashi, Mr. Shigenori - NEC Corporation

LaRochelle, Mr. Robert - IBM

Matsumoto, Mr. Shigeaki - NEC Corporation

Matsuoka, Mr. Shinji - Fujitsu Limited

Speicher, Steve - IBM

Wakao, Mr. Masaki - IBM

Watanabe, Mr. Takeshi - IBM

Yabuta, Mr. Kazuo - Individual

Yoshida, Dr. Hiroyuki - Individual

Appendix C. Notices

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website: [https://www.oasis-open.org/policies-guidelines/ipr/].

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS AND ITS MEMBERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THIS DOCUMENT OR ANY PART THEREOF.

As stated in the OASIS IPR Policy, the following three paragraphs in brackets apply to OASIS Standards Final Deliverable documents (Committee Specifications, OASIS Standards, or Approved Errata).

[OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Standards Final Deliverable, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this deliverable.]

[OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this OASIS Standards Final Deliverable by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this OASIS Standards Final Deliverable. OASIS may include such claims on its website, but disclaims any obligation to do so.]

[OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this OASIS Standards Final Deliverable or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Standards Final Deliverable, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.]

The name "OASIS" is a trademark of OASIS, the owner and developer of this document, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, documents, while reserving the right to enforce its marks against misleading uses. Please see https://www.oasis-open.org/policies-guidelines/trademark/ for above guidance.