OASIS Open

OSLC PROMCODE V1.0 has been presented to the membership by the OASIS OSLC PROMCODE) TC [1] as a candidate for OASIS Standard. Do you consent or object to its approval as an OASIS Standard?

Managing software delivery can be highly challenging due to the diversity of the development processes, methods, tools and platforms used by different organizations participating in a project. Manual work done in order to exchange proprietary management data is inefficient, error-prone and inflexible. OSLC PROMCODE Version 1.0 is designed to address the need for systematic sharing of project management information within and between organizations.

Note that Committee Specification 03 was produced to correct non-material changes discovered during the 60-day public review. This was done in accordance with the procedures outlined in section 2.8.2 of the TC Process (https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#OSpublicRev). The list of changes can be seen in https://lists.oasis-open.org/archives/oslc-promcode/202202/msg00002.html and in the red-lined copies at https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab-DIFF.pdf, https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-spec-DIFF.pdf, and https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes-DIFF.pdf.

The TC received 3 Statements of Use from IBM, Fujitsu, and NEC [2].

This is a call to the Organizational Members of OASIS to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however your consent is assumed unless you register an objection [3]. To register an objection, you must:

1. Indicate your objection on this ballot, and

2. Provide a reason for your objection and/or a proposed remedy to the TC.

You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC's mailing list [3]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent.

URIs:

The prose specification document and related files are available here:

Part 1: Specification

HTML
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-spec.html

PDF
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-spec.pdf

Part 2: Vocabulary

HTML
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab.html

PDF
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab.pdf

Part 3: Constraints

HTML
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes.html

PDF
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes.pdf

Vocabulary terms
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab.ttl

Constraints
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes.ttl

--- Additional information ---

[1] OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TC
https://www.oasis-open.org/committees/oslc-promcode/

[2] Statements of use

- IBM:
https://lists.oasis-open.org/archives/oslc-promcode-comment/202111/msg00004.html

- Fujitsu:
https://lists.oasis-open.org/archives/oslc-promcode-comment/202111/msg00003.html

- NEC:
https://lists.oasis-open.org/archives/oslc-promcode-comment/202111/msg00001.html

[3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

OSLC PROMCODE TC comment mailing list: oslc-promcode-comment@lists.oasis-open.org (You must be subscribed to send to this list. To subscribe, see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=oslc-promcode.)

TC main mailing list: oslc-promcode@lists.oasis-open.org