toggle quoted messageShow quoted text
Very much appreciated, Chet! Have a nice weekend!
On Fri, Jun 28, 2019 at 8:03 PM +0200, "Chet Ensign"
Slowly but surely, I am getting oriented to where we are and catching up...
On Thu, Jun 27, 2019 at 5:48 PM Andrii Berezovskyi <andriib@...
I want to make sure I got this right, so let me make some comments and please correct me if I got this wrong in any way:
1) We are not submitting a spec for public review.
The OP rules do not require that so yes, that is fine.
Instead, OP maintainers are preparing to ask the PGB to approve a Project Specification
Draft 04 (we will skip PSDs 1 to 3 for Core to avoid any confusion with the CSPRDs 1 to 3 published by the Core TC, I don't know how many CSPRDs were published by the Domains TC for the QM spec). The only approval required for this is from PGB, with 14 days
Correct. And approving it as PSD04 is fine.
Right, no approval needed from us. By 'designated branch' we were trying to say, basically, you should approve a labeled branch that people can get back to later if they want to review the evolution of the TC work product.
2) We do not have to use OASIS infrastructure to publish a PSD or to produce PDFs.
We are planning to make a PR with the changes to the document revision, status and links and tag it on Github with a tag 'psd-04', for example.
3) I suggest to have all comments on the PSDs to be submitted as Github issues.
That is certainly a good way to do it process-wise. But personally, I wouldn't rule out that you might get good comments via the email list.
4) The specification will not be provided under the Apache 2.0 license. Apache license
is best suited for the source code. The text of the spec will be CC BY 4.0 licensed (Attribution 4.0 International). Vocabulary and OSLC Shape machine-readable documents will be provided under the Apache 2.0 license. Did I miss something?
That is fine - your call.
Also, we had some discussion in the OP call regarding the naming of the specs and publishing of the PDFs. Chet, we are still working it out but I would appreaciate if you follow/participate
Yes, I have been working my way through the discussions. I definitely have some questions to discuss with you there. Will get those thoughts together today.
Chet Ensign <chet.ensign@...>
Sent: 26 June 2019 23:51
To: Jim Amsden
Cc: Andrii Berezovskyi
Subject: Re: Submitting the Quality
Management Open Project Specification for public review
Jim, Andrew, I'm spending the afternoon catching up on all this. Apologies for falling behind...
On Mon, Jun 10, 2019 at 2:00 PM Jim Amsden <jamsden@...>
1. Make sure the
oslc-op@... mailing list is working so
that we can collaborate appropriately.
Yes and that's done.
2. Finalize the text for the Status section of the Open Project in ReSpec. I suggest the following
Yes, this section looks good.
This document was last revised or approved by the
OSLC Open Projecton the above date. The level of approval is also listed above. Check the “Latest version” location
noted above for possible later revisions of this document.
Comments on this specification can be sent to the OSLC Open Project’s
public comment list oslc-op@...,
after subscribing to it by following the instructions in “Contributing” at
That sounds right. I'll look at the text in CONTRIB now and may make
a suggestion via pull request.
This specification is being provided under the Apache 2.0 License and Attribution 4.0 International.
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.
does not describe the process for subscribing to the oslc-op mailing list - assuming that's what will be used for public review comments, and does not yet describe the feedback licensing terms. Is there a link we should include in the Status section that describes
the feedback process and licensing implications? Something similar to https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=oslc-corebut
for open projects?
Not yet. Let me sort that out.
4. The content of the Notices section needs to be finalized.
Here's what we currently have
Copyright © OASIS Open 201
All Rights Reserved.
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
be found at the OASIS website.
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 Open Project (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 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 Project Specification or OASIS Standard, to notify OASIS
Project (OP) Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the
IPR Mode licensing of
the OASIS Open Project that produced this specification.
OASIS invites any party to contact the OASIS
Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent
with the IPR Mode licensing of
the OASIS Open Project that produced this specification. 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 document 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 Open Project 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 Project Specification or OASIS Standard,
can be obtained from the OASIS
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
the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against
misleading uses. Please see https://www.oasis-open.org/policies-guidelines/trademark for
5. Determine a process for publishing open project specifications
- Determine the URL pattern for the published specifications
Yes. Still TBD.
- Publish rendered specifications to OASIS
I'm not sure what you mean by 'publish' here. Hand
them off to us to load and announce?
I'm not sure of the import of this either. Are the
resource shapes something different from the QM Spec?
Jim Amsden, Senior Technical Staff Member
ELM Quality Manager
Mobile: +1 201-341-1393
Mobile: +1 201-341-1393