RE: [ws-rx-editors] Anomalies in PDF spec formats

[Doug Davis <dug@us.ibm.com>]

Would just like to hear from Mary before
I make the edits - 'cause if edits outside of the title page and footer
causes us to redo the vote then we have a big decision ahead of us.
Although, I would find it very annoying/silly
if the oasis rules didn't allow for very obvious typos to be fixed - especially
when the doc is still "in house".

thanks
-Doug
______________________________________________________
STSM  |  Web Services Architect  |  IBM Software Group
(919) 254-6905  |  IBM T/L 444-6905  |  dug@us.ibm.com

Marc Goodner <mgoodner@microsoft.com>

03/06/2007 11:55 AM

To	Robin Cover <robin@oasis-open.org>, Doug Davis/Raleigh/IBM@IBMUS
cc	Mary McRae <mary.mcrae@oasis-open.org>, WS-RX Editors <ws-rx-editors@lists.oasis-open.org>
Subject	RE: [ws-rx-editors] Anomalies in PDF spec formats

Weird. In the initial conversion[1] those URLs were
fine.

I think fixing these is a straightforward editorial issue. It's hard to
argue that these are anything other than easy to interpret mistakes. Especially
as demonstrated above the URLs had been correct in earlier drafts and no
issues were introduced to change them.

1 http://www.oasis-open.org/archives/ws-rx-editors/200702/msg00160.html

-----Original Message-----
From: Robin Cover [mailto:robin@oasis-open.org]
Sent: Tuesday, March 06, 2007 8:36 AM
To: Doug Davis
Cc: Mary McRae; WS-RX Editors; Robin Cover
Subject: Re: [ws-rx-editors] Anomalies in PDF spec formats

On Tue, 6 Mar 2007, Doug Davis wrote:

> Robin,
> What's the rules for fixing these obvious typos for the CS (assuming
the
> CD passes the vote)?

 <unofficial>
Doug, I don't typically get into TC Process casuistry; I
know Mary McRae will be happy to answer questions about
allowable changes.

Of possible relevance (but without implying any official
ruling), I would note the assersions below which contain
the word change*.  3.4 is potentially relevant because the
draft submission combines approval of the CD as CS and
requests submission for consideration as OS. </>

========================================================================
2.18 Specification Quality
http://www.oasis-open.org/committees/process.php#2.18

   "Any change made to a specification requires a new version
or revision
    number, except for changes made to the title page and in
the running
    footer noting the approval status and date, which must be
made after
    the approval of the specification."

    ----------------------------------------------------------

3.4 Approval of an OASIS Standard
http://www.oasis-open.org/committees/process.php#3.4

"Simultaneously with the approval of a Committee Specification
or at a later date, and after three Statements of Use have
been presented to the TC, a TC may resolve by Special Majority
Vote to submit the Committee Specification to the Membership
of OASIS for consideration as an OASIS Standard. Upon
resolution of the TC to submit the specification, its Chair
shall submit the following items to the TC Administrator:

(a) Links to the approved Committee Specification in the
TC's document repository, and any appropriate supplemental
documentation for the specification, both of which must be
written using the OASIS templates. The specification may
not have been changed between its approval as a Committee
Specification and its submission to OASIS for consideration
as an OASIS Standard, except for the changes on the title
page and running footer noting the approval status and date."

==========================================================================

>
> The 2nd set of oddities you mentioned may have been done by Word -
Mary
> noticed some very odd things like this in a previous version as well.
 I
> think that during the conversion from OpenOffice to Word some of the
> href's/URLs went thru a randomizer :-)

Not sure... I checked at random the .doc and .html for WSMC, and
some of the (e.g.,) "/200/70/2/" cases are attested [in my local
software applications] in both.

-rcc

>
> thanks
> -Doug
> ______________________________________________________
> STSM  |  Web Services Architect  |  IBM Software
Group
> (919) 254-6905  |  IBM T/L 444-6905  |  dug@us.ibm.com
>
>
>
> Robin Cover <robin@oasis-open.org>
> 03/06/2007 10:35 AM
>
> To
> WS-RX Editors <ws-rx-editors@lists.oasis-open.org>
> cc
> Robin Cover <robin@oasis-open.org>, Mary McRae <mary.mcrae@oasis-open.org>
> Subject
> [ws-rx-editors] Anomalies in PDF spec formats
>
>
>
>
>
>
> Last last night, while writing some documentation for Staff
> (action URIs) I encountered a couple anomalies in the PDF versions
for
> WS-RX TC specs being balloted.  I didn't check the corresponding
> .doc or .html formats.
>
> --------------------------------------------------------------
> I. Location of normative WSDL for WSMC/WS-MC and WSRM
> --------------------------------------------------------------
>
> A. In the PDF for WSMC being balloted:
>
> http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/22738/wsmc-1.0-spec-cd-02.pdf:
>
>
> Appendix B. WSDL
> The normative WSDL 1.1 definition for WS-MakeConnection is located
> at:
> http://docs.oasis-open.org/ws-rx/wsmc/200702/wsdl/wsmc-1.0-wsdl-200702.wsdl
>
>
> B. In In the PDF for WSRM being balloted:
>
> http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/22736/wsrm-1.1-spec-cd-06.pdf
>
>
> Appendix B. WSDL
> The normative WSDL 1.1 definition for WS-ReliableMessaging is located
> at:
> http://docs.oasis-open.org/ws-rx/wsrm/200702/wsdl/wsrm-1.1-wsdl-200702.wsdl
>
>
>
> * I think these two '/200702/wsdl/' URIs were overlooked when the
> (current)
>   CD-level versions of the specs were installed; no idea why
>
> * The file "WS-RX_CS-01_DirStructured.zip" referenced here
>   http://lists.oasis-open.org/archives/ws-rx-editors/200703/msg00049.html
>
>   indicates that the two WSDLs should be stored directly in a
directory
>   /200702/, not in /200702/wsdl/
>
>     1584 02-22-07 13:39  6228161f
> ws-rx/wsmc/200702/wsmc-1.0-wsdl-200702.wsdl
>     2654 02-11-07 18:09  19456660
> ws-rx/wsrm/200702/wsrm-1.1-wsdl-200702.wsdl
>
> * If the TC's intent it to make the official/canonical locations to
be
>   /200702/ (according to the "WS-RX_CS-01_DirStructured.zip"
file), then
>   I think we can create a server level URI mapping to ensure
that
>   the resources are available at the URIs given in Appendix B,
yet
>   without creating a visible URI in the server index listing
at locations
>   /200702/wsdl/ (i.e., we can avoid creating the /wsdl/ directories
and
>   still honor the assertions about the location of the normative
WSDL 1.1
>   definitions being at the locations declared in Appendix B.
>
> * If the TC intends to make the WSDL URIs nominated in Appendix B
>   "normative" for the "normative definition",
then we can use some
>   other kind of URI aliasing (e.g.,) symlink to normalize the
>   data and make the content appear at both locations, visible
>   for both occurrences in the server's file index
>
> * In connection with the above, it's not clear to me whether you
>   intended to say "The normative WSDL 1.1 definition for
> WS-MakeConnection..."
>   when, as I understand the situation, the WSMC WSDL is actually
"1.0"
>   Or.... ??
>
> --------------------------------------------------------------
> II. Possible errors in action URIs, anonymous URI
> --------------------------------------------------------------
>
> **I'm not sure if what I see in my (older) version of Adobe Acrobat
> is a software display artifact or a real mistake -- visible in all
> later versions of Acrobart reader...
>
> In the PDF for WSMC being balloted
> http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/22738/wsmc-1.0-spec-cd-02.pdf:
>
>
> I see "200702" munged to read as "20070/2" and
"200/70/2" in several
> locations.
>
> 731-732
> <wsa:Action>http://docs.oasis-open.org/ws-rx/wsmc/200/70/2/MakeConnection</wsa:Action>
>
> 750-752
> <wsa:Action>http://docs.oasis-open-org/ws-rx/wsrm/200/70/2/CreateSequence</wsa:Action>
> <wsa:To>http://docs.oasis-open.org/ws-rx/wsrm/200/70/2/anonymous?id=550e8400-e29b-11d4-a716-446655440000</wsa:To>
>
> 777-778
> <wsa:Action>http://docs.oasis-open-org/ws-rx/wsrm/200/70/2/CreateSequenceResponse</wsa:Action>
>
> 797
> <wsa:Action>http://docs.oasis-open.org/ws-rx/wsmc/200/70/2/MakeConnection</wsa:Action>
>
> 815-816
> <wsa:To>http://docs.oasis-open.org/ws-rx/wsrm/200/70/2/anonymous?id=550e8400-e29b-11d4-a716-446655440000</wsa:To>
>
> 837-838
> <wsa:To>http://docs.oasis-open.org/ws-rx/wsrm/20070/2/anonymous?id=550e8400-e29b-11d4-a716-446655440000</wsa:To>
>
> -rcc
>
>
>
>