Re: [sca-bindings] Re: [TC Admin] Request for web ballot for CS with designated cross references

[Eric Johnson <eric@tibco.com>]

I, for one, would prefer that we fix the document so that HTML ends up with the proper links.

Eric.

On 4/26/13 8:39 AM, Chet Ensign wrote:

Hi Simon, 

I confirm what Paul wrote. I try to keep TC Admin out of the content as much as possible lest we cause some problem with your content or create confusion about where some element of the content came from. 

If you all would like to fix those links as Paul has described so that they do work in the HTML, no problem at all. It will not require a new round of public review, just a reapproval with Non-Material Changes (see https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft-with-non-material-changes for an overview of how to do this). We will just hold the ticket open and wait for your updated working draft. 

Or we can proceed with the CSD as is. 

Please let me know how you'd like to proceed. I will wait to hear from you before starting the ballot. 

Best, 

/chet 

On Fri, Apr 26, 2013 at 10:12 AM, Paul Knight <paul.knight@oasis-open.org> wrote:

Hi Simon,  (copying Chet for confirmation of handling policy)

This took a bit of research and experimenting...

While we DO regenerate the files as we produce the Committee Specification, it turns out that the cross-reference links in your particular document will not be active links in the HTML version.  Apparently the way the cross-reference fields are defined in the document does not produce a hyperlink in the HTML version when it is generated by MS-Word.

I experimented a bit, and it turns out to be fairly straightforward to modify (actually replace) the links in the MS-Word document so that they will show up as HTML links, but it is a fix that must be applied to each instance separately. I'm pretty sure that Chet will not feel that this level of change is something that we (TC Administration) can do for the TC.

I have attached an example of the fix, in the DOC file and HTML output.

If you look at the third paragraph under Section 1 - Introduction, you will see three links to [WSDL11].

The first one is the one already in the document. The second and third ones are new ones which I added.  They are essentially the same, but I turned one into black text rather than default hyperlink color (usually blue), to demonstrate this option.  

You will see that all three links are functional in the MS-Word version, while the first [WSDL11] link does not function as a link in HTML, but the other two which I inserted function as expected.

The working links were created by selecting the text, then using right-click ---> hyperlink, then "Place in this Document", then selecting the proper referent (place), which was previously defined when the non-working links were established.  I believe this will also work for the yellow text items or any of the cross-references in the document.

The changes I'm describing will definitely fall into the category of "non-material changes", so it would be possible for the TC to generate a new Working Draft with these link corrections, and still approve it as a Committee Specification without another two-week Public Review, if desired.  The Designated Cross-References can also be included, as in your current ballot request.

So I see two options - accept the non-working links in HTML, or fix them by producing a new Working Draft with non-material changes to the links.  If you want to make the changes, I believe we can keep the ballot request [1] open while the new WD is prepared, and then structure the ballot so it will approve the new WD for publication as a Committee Specification.

I hope this is fairly clear...Chet may have other suggestions as well...

Best regards,

Paul

[1] https://tools.oasis-open.org/issues/browse/TCADMIN-1259

On Fri, Apr 26, 2013 at 6:48 AM, Simon Holdsworth <simon_holdsworth@uk.ibm.com> wrote:

Paul,

I have entered the request via the form.  

Please could you address my final question from the email:  the HTML version of the specification in question has some issues with hyperlinks, where the links work in the PDF version they don't in the HTML version.  Will the HTML version be re-generated as part of the DCR update, and if so, will there be an opportunity to check that these links do work in the CS version?

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



From:        Paul Knight <paul.knight@oasis-open.org>
To:        Simon Holdsworth/UK/IBM@IBMGB,
Cc:        "tc-admin@oasis-open.org" <tc-admin@oasis-open.org>, sca-bindings@lists.oasis-open.org
Date:        22/04/2013 15:19
Subject:        Re: [TC Admin] Request for web ballot for CS with designated cross references

---

Hi Simon,

Congratulations to you and the TC on your progress!

Please submit this request (and the other expected CS ballot requests as they are readied) into the TC Admin work tracking system by using the TC Admin Request Forms link, from the "Resources" tab on the main OASIS web site.

The request forms page is https://www.oasis-open.org/resources/tc-admin-requests.

The specific CS Ballot request form is: 
https://www.oasis-open.org/resources/tc-admin-requests/committee-specification-ballot-request.

Thanks and best regards,
Paul



On Mon, Apr 22, 2013 at 5:59 AM, Simon Holdsworth <simon_holdsworth@uk.ibm.com> wrote:
Hi,

The SCA Bindings TC recently resolved to request a web ballot for Committee Specification with Designated Cross Rerefences. Please see minutes [1].  The resolution was as follows:

>>>>>>>>>>>>>>
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 http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-spec-csprd03.html as 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#crossRefs during 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 http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-spec-csd07.pdf
Expected approval status and date: Committee Specification, May 2013

- Current reference to be updated:  line 35: [SCA-Policy] OASIS Committee Draft 04, SCA Policy Framework Specification Version 1.1, September 2010 http://docs.oasis-open.org/opencsa/sca-policy/sca-policy-1.1-spec-cd04.pdf
Expected approval status and date: Committee Specification, May 2013

- 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 http://docs.oasis-open.org/opencsa/sca-j/sca-javacaa-1.1-spec-csd05.pdf
Expected approval status and date: Committee Specification, May 2013

- 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, http://docs.oasis-open.org/opencsa/sca-bindings/sca-wsbinding-1.1-testcases-cd01.pdf
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.
The TC asserts that there is no material change to the specification from the last PR draft.
(m: Mike Edwards, s: David Booz, no objections)
<<<<<<<<<<<<

Note: The referenced SCA-Assembly, SCA-Policy and SCA-JCAA specifications are expected to follow suit and request CS ballots in the next few weeks.  The TC agreed that a specific version (CS) references was needed for these normative references.  They also agreed that a "latest" reference was appropriate for the non-normative WS-Testcases reference.

I'd appreciate it if you could start the web ballot, and coordinate the updates to the specification document with the other specifications as their ballots (hopefully) pass.

One final comment; the HTML version of the specification in question has some issues with hyperlinks, where the links work in the PDF version they don't in the HTML version.  Will the HTML version be re-generated as part of the DCR update, and if so, will there be an opportunity to check that these links do work in the CS version?

Thanks, Simon

Simon Holdsworth

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU



--
Paul Knight  - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

--
Paul Knight  - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst

--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open