OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [sca-bindings] Bindings work products progression

A normative reference to latest can change underneath. One should never reference latest in normative sections.

The whole motivation for using DCRs is so you don't have to use latest.


On 4/18/13 7:24 AM, Martin Chapman wrote:
I disagree with using latest since it could change under the covers to
anything. A normative reference should always be to an exact version and
date .

*From:*Simon Holdsworth [mailto:simon_holdsworth@uk.ibm.com]
*Sent:* 18 April 2013 11:31
*To:* sca-bindings@lists.oasis-open.org
*Subject:* [sca-bindings] Bindings work products progression

Folks,  I've checked with TC admin and the following appears to me to be
the best way forward for the WS binding work products:

A) WS Binding Specification:

Move current CSPRD03 to Committee Specification, subject to four
designated cross-references:

1) Normative references for SCA-Assembly, SCA-Policy and SCA-JCAA
updated to use the "Latest" reference for each work product.
2) Non-normative reference to WS-Testcases to be updated to point to the
"Latest" reference for that work product.
Note: the "Related work" references to 1) and 2) already use the
"Latest" references.

Note from TC admin (Paul Knight):  "Yes, that's right, it can be handled
using the designated cross references (DCR) process.  We might also
suggest using the "Latest" references (instead of references to specific
CS publications), so they will not need to be updated as the various
specifications move to higher stages. This is preferable to constantly
using DCRs.
Note that OASIS does not have a prohibition against using variable
(Latest) references in Normative References. Some other standards
organizations or individual TCs may desire specific stage references.
OASIS does prohibit a DCR from introducing a change to a new numeric
Version (capital V) of a reference."

If there's an objection to using the "Latest" reference to the other SCA
specifications then we would need to coordinate this with the other TCs
so that we can have the update made to their CS versions.  Note that the
"Latest" reference is only "Latest 1.1", any version change beyond that
would require an update to the URLs anyway, so at this point I don't see
a need to refer to anything more specific.

One comment on the current CSPRD is that for some reason the internal
hyperlinks (e.g. [SCA-Assembly]) while hyperlinked in the PDF version
are not generated as links in the HTML version. I don't know if its
possible to have the HTML version re-generated from the PDF (and
checked!) as part of this process to fix the links.

Here's the TC admin suggested motion for the move to CS with designated
cross references (modified a bit by me):

[someone] moves that the TC approves the Chair requesting that TC
Administration hold a Special Majority Ballot to approve the SCA Web
Service Binding Specification Version 1.1 contained in
a Committee Specification, in addition the TC approves the Chair
requesting that TC Administration update the following Designated
Cross-References as defined by
https://www.oasis-open.org/policies-guidelines/tc-process#crossRefsduring publication
of the Committee Specification:

- Current reference to be updated:  line 31: [SCA-Assembly] OASIS
Committee Specification Draft 07, Service Component Architecture
Assembly Model Specification Version 1.1, January 2011

Expected approval status and date: Replace with Latest version link.

- Current reference to be updated:  line 35: [SCA-Policy] OASIS
Committee Draft 04, SCA Policy Framework Specification Version 1.1,
September 2010
Expected approval status and date: Replace with Latest version link.

- Current reference to be updated:  line 38: [SCA-JCAA] OASIS Committee
Specification Draft 05, Service Component Architecture SCA-J Common
Annotations and APIs Specification Version 1.1, November 2010
Expected approval status and date: Replace with Latest version link.

- Current reference to be updated: line 91: [WS-Testcases] OASIS
Committee Draft 01, "TestCases for the SCA Web Service Binding
Specification Version 1.1", July 2010,

Expected approval status and date: Replace with Latest version link.

The TC acknowledges that approval and publication of the specification
may be delayed by the Designated Cross-Reference Changes.

An alternative approach that was suggested was to create a new working
draft with the updated links it in, and then have that approved as CS
following the Non-Material Change process.

B) WS Binding Testcase document/test artefacts:

Approve a new CSD package with updated test artefacts, with one update
to the Testcases document to update the [SCA-WSBinding] Normative
reference to use the "Latest" reference for the specification.

A new PR for the updated CSD is not necessarily needed; if we did want
to move the testcases to CS we would either to agree that the changes
were Non-Material, or else proceed with a PR.

Note that this can be done independently of A) if we update the
testcases reference in the specification to use the "Latest" reference
as suggested.

Regards, Simon

Simon Holdsworth
STSM, WebSphere ESB Product Architect
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet - Simon_Holdsworth@uk.ibm.com <mailto:Simon_Holdsworth@uk.ibm.com>
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]