Re:
=========================================================================================
- latest URI is now: http://docs.oasis-open.org/ws-rx/wsrm/wsrm.pdf
Robin - is this an ok URI?
- Robin/Mary - is it ok that we have other sections (like 'conformance'
and 'namespace' in section 1 ?)
- reformatting the contributors section - each person got their own line
now - Robin/Mary - can we do multiple-columns
or does it have to be this way? Its a lot of space.
[...]
Mary/Robin - could I ask you guys to look over this doc to see if it
conforms to the new template? I tried to match
all of the sections and formatting styles as best I could.
=========================================================================================
Sorry for delay... I've had connectivity issues and other distractions.
On the first question:
"latest URI is now: http://docs.oasis-open.org/ws-rx/wsrm/wsrm.pdf OK?"
I think the intent in the Naming Guidelines is that a "Latest Version: " URI
set will have three formats (or possibly two, if the editable source is XHTML):
HTML, PDF, editable source. The examples could be clearer, since they
envision the minimal case in which HTML == editable source, so the two
"Latest Version: " formats are PDF and HTML. See:
http://docs.oasis-open.org/specGuidelines/namingGuidelines/metadata.html#specURIs
In the case of WSRM/WSRMP/WSMC, if the editable source is DOC, then the
"Latest Version: " URIs should be, I think:
http://docs.oasis-open.org/ws-rx/wsrm/wsrm.pdf
http://docs.oasis-open.org/ws-rx/wsrm/wsrm.html
http://docs.oasis-open.org/ws-rx/wsrm/wsrm.doc
Right, Mary?
Best wishes,
Robin
================================================================================
On Fri, 23 Feb 2007, Mary McRae wrote:
> Hi Doug,
>
> Looks good. Yes, it's okay to include namespace and conformance in section 1; note that with the upcoming changes to
> the TC Process there will be a new section created for conformance requirements but these docs will be through the cycle
> before those changes go into effect. Multiple columns for acknowledgements is fine.
>
> A couple of things:
>
> Latest Approved Version URI: This is intended to act in the same manner as "Latest Version URI" except that it would
> skip over any working drafts or revisions that had not yet been approved by the TC (i.e. CD 01 R 02 is unofficial until
> approved as CD 02)
>
> lines 56 and 62: add a trailing slash to URI
>
> All URIs should be created as Hyperlinks so that a reader can actually navigate to the location directly from the
> document. If you highlight the link itself, then go to "insert" -> Hyperlink it will bring up a dialog box. By default
> it should create a link to the same text that you highlighted. Just save and you now have a navigable link.
>
> Trademarks - according to the policy, all terms related to the specification and the TC are to be listed - this would
> include "WS-ReliableMessaging", wsrm, WS-RX, etc.
>
> That's everything that's jumping out at me.
>
> Regards,
>
> Mary
>
>
>
> _____
>
> From: Doug Davis [mailto:]
> Sent: Tuesday, February 20, 2007 7:44 PM
> To: Paul Fremantle
> Cc: ; ;
> Subject: Re: [ws-rx-editors] [Fwd: Re: Help please [about date-less/version-less spec URIs]]
>
>
>
> All,
> I've gone thru the RM spec and reformatted things per the latest template. In terms of edits to the doc, I tried to
> not do any textual changes with the exception of the following:
> - renamed it CD06 - should probably have been optimistic and called it CS :-)
> - latest URI is now: http://docs.oasis-open.org/ws-rx/wsrm/wsrm.pdf Robin - is this an ok URI?
> - moved the normative and non-normative sections to the top of the doc - per the template
> - Robin/Mary - is it ok that we have other sections (like 'conformance' and 'namespace' in section 1 ?)
> - reformatting the contributors section - each person got their own line now - Robin/Mary - can we do multiple-columns
> or does it have to be this way? Its a lot of space.
>
> The doc is here: http://www.oasis-open.org/apps/org/workgroup/ws-rx-editors/download.php/22537/wsrm-1.1-spec-cd-06.doc
>
> Mary/Robin - could I ask you guys to look over this doc to see if it conforms to the new template? I tried to match all
> of the sections and formatting styles as best I could.
>
> Editors - please give this doc a scan. Things to look for:
> - At times I had to manually re-add some text/URLs (like in the references sections) to get things to format correctly.
> - And watch for variables in the examplars (e.g. xs:string) not being in italics
> - paragraph numbering and bullets - tried to make sure we were consistent across the entire doc w.r.t. indenting etc...
> - missing hyper-links - examples and code snippets were removed on purpose, but others should probably be there.
> - check bookmarks - I had to redo them all by hand - for some reason they were all messed up after I moved the (non)
> normative sections
>
> Once people look this over and are ok with it, then I'll move on to RMP and MC.
>
> thanks
> -Doug
> ______________________________________________________
> STSM | Web Services Architect | IBM Software Group
> (919) 254-6905 | IBM T/L 444-6905 |
>
>
>
> Paul Fremantle <>
>
>
> 02/19/2007 10:51 AM
>
>
> To
> "" <>
>
> cc
>
> Subject
> [ws-rx-editors] [Fwd: Re: Help please [about date-less/version-less spec URIs]]
>
>
>
>
>
>
> FYI here is Robin's advice for our URIs.
>
> Paul
>
> -------- Original Message --------
> Subject: Re: Help please [about date-less/version-less spec URIs]
> Date: Mon, 19 Feb 2007 09:42:08 -0500 (EST)
> From: Robin Cover <>
> To: Paul Fremantle <>
> CC: Robin Cover <>
> References: <>
>
> Paul,
>
> Re:
>
> > I would have thought that we'd want a URL that was date-less as well as
> > version-less.
>
> I apologize for failing to respond to your request for advice
> in a timely manner. The request is quite reasonable, as
> seems to be proven by the successful W3C practice of publishing
> its recommendation-track specifications at URIs like:
>
> Latest version: http://www.w3.org/TR/xquery-semantics/
> Latest version: http://www.w3.org/TR/ws-addr-core
> Latest version: http://www.w3.org/TR/xkms2/
> Latest version: http://www.w3.org/TR/soap12-part0/
>
> Initially, when I saw the proposal for "Something like"
>
> > http://docs.oasis-open.org/ws-rx/wsrm
> > http://docs.oasis-open.org/ws-rx/wsrmp
> > http://docs.oasis-open.org/ws-rx/wsmc
>
> I was stumped, because we have a commitment to use the
> "directory URIs" [slash "/" and slashless ""] as identifiers
> for directory listings, as in this current example:
>
> http://docs.oasis-open.org/ws-rx/wsrm/
> http://docs.oasis-open.org/ws-rx/wsrm
>
> *That index listing is ugly now, but we have plans to make it
> more usable.
>
> The Naming Guidelines do require that specifications be
> assigned a "Latest Version:" URI, which is a URI alias pointing
> to the resource that is the current/latest at any point in
> time. See:
>
> "Specification URIs"
> http://docs.oasis-open.org/specGuidelines/namingGuidelines/metadata.html#specURIs
>
> The OASIS membership provided clear feedback (ASIS review) that we should
> impose no single format for the "Latest Version:" URI -- allowing the TCs
> to select something reasonable, suitable to their needs and sensibilities.
>
> Some of the examples provided for "Latest Version:" URI are
> dateless, as you can see in the section "Specification URIs" cited above:
>
> http://docs.oasis-open.org/exampleTC/fruitMarkup/v2/fruit2.html
>
> No examples are "version-less" though -- in part, because some reviewers
> asked that we NOT assume genetic continuity between [e.g.] DITA 1.0
> and DITA 3.0, such as might be implied by a generic/version-agnostic
> URI like this, which otherwise could serve as the
> latest/dateless/version-less
> URI for all 'DITA' specs.
>
> http://docs.oasis-open.org/dita/TR
>
> Their argument was that an entirely different group of people might
> work on "DITA 3.0" than worked on "DITA 1.0", the the DITA-3 people
> might not want to be forced to use a URI that implies "DITA 3.2" is
> the "latest" version of the DITA 1.0 product, in close continuity with
> it.
>
> We use the term "Version" in a fairly specific way in connection with
> identifying a specification version:
>
> http://docs.oasis-open.org/specGuidelines/namingGuidelines/metadata.html#version
>
> I *do* encourage you to bring up this issue with the WS-RX TC editors,
> however, since selection of a "Latest Version:" URI is needed for
> wsrm, wsrmp, and wsmc. In the WS-ReliableMessaging 1.1 spec here:
>
> http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cd-05.pdf
>
> the text says:
>
> Latest Version:
> http://docs.oasis-open.org/ws-rx/wsrm/200702
>
> and that's not what we have in mind; that's the NS URI.
>
> The spec title page has a dsignated place for the associated
> NS URI(s), e.g.,
>
> Declared XML Namespaces:
> http://docs.oasis-open.org/ws-rx/wsrm/200702
>
> I'll try to make myself available, if needed, to help
> think through (or review candidates for) possible
> Latest Version URIs suitable for the WS-RX TC's specs.
>
> Caveats:
>
> * The TAB and Board are considering options for a method of
> using the concept/term "normative" [or "official"]
> format (XHTML vs. PDF vs. EditableSource). The
> results might lead to a change in the Naming Guidelines
> so that there would be only one "Latest Version:" URI
> printed on a spec title page, not 2-3 URIs, as in:
>
> Latest Version:
>
> http://example.com/fishing/fishML.pdf
> http://example.com/fishing/fishML.doc
> http://example.com/fishing/fishML.html
>
> * The OASIS IT programming team is preparing a new
> URI aliasing tool (serving some of the functions
> of Apache mod_alias, mod_rewrite, etc.) to give
> us greater flexibility in handling the URI
> aliasing mechanisms [server-side URI rewrite
> in addition to client-side redirect], but it's
> not certain when that will be activated.
> ***Privately***: see a prototype here:
>
> http://docs3.oasis-open.org/ws-rx/
>
> Please don't publish that -- it might be buggy.
>
> Again, I sincerely apologize for not responding on time;
> please forgive me.
>
> Best wishes.
>
> Robin Cover
>
> -------------
>
> On Mon, 12 Feb 2007, Paul Fremantle wrote:
>
> > Robin
> >
> > Can you advise us on this one please?
> >
> > Paul
> >
> > -------- Original Message --------
> > Subject: RE: [ws-rx-editors] RE: CD5.3
> > Date: Mon, 12 Feb 2007 07:19:01 -0500
> > From: Doug Davis <>
> > To: Marc Goodner <>
> > CC: 'Mary McRae' <>,
> > <>, Paul Fremantle <>, 'Robin
> > Cover' <>,
> > <>
> >
> >
> >
> >
> > I would have thought that we'd want a URL that was date-less as well as
> > version-less. Something like:
> > http://docs.oasis-open.org/ws-rx/wsrm
> > http://docs.oasis-open.org/ws-rx/wsrmp
> > http://docs.oasis-open.org/ws-rx/wsmc
> >
> > That way even if we have a v.Next the URL would still not need to
> > change. Mary - is this possible?
> >
> > thanks
> > -Doug
> > ______________________________________________________
> > STSM | Web Services Architect | IBM Software Group
> > (919) 254-6905 | IBM T/L 444-6905 |
> >
> >
> > *Marc Goodner <>*
> >
> > 02/11/2007 10:40 PM
> >
> >
> > To
> > Paul Fremantle <>, ""
> > <>
> > cc
> > Doug Davis/Raleigh/IBM@IBMUS, "'Mary McRae'" <>,
> > ""
> > <>, "'Robin Cover'"
> > <>
> > Subject
> > RE: [ws-rx-editors] RE: CD5.3
> >
> >
> >
> >
> >
> >
> >
> >
> > My reading is that Dug has made all of the requested changes except one
> > we are still discussing. The open issue is what to use for the latest
> > link in the doc.
> >
> > My recommendation is to just use the current namespace. Mary has
> > suggested a permanent latest URI could be assigned for this use. I'm not
> > inherently opposed to that but I'd prefer some more discussion before
> > putting it into practice.
> >
> > -----Original Message-----
> > From: Paul Fremantle [mailto:]
> > Sent: Sunday, February 11, 2007 7:30 PM
> > To:
> > Cc: Marc Goodner; 'Doug Davis'; 'Mary McRae';
> > ; 'Robin Cover'
> > Subject: Re: [ws-rx-editors] RE: CD5.3
> >
> > I'd like to thank Marc, Doug and Mary for all your efforts this weekend.
> >
> > Can anyone give me a brief status update? I've seen a ton of useful
> > messages but I haven't quite figured out what is still needed before the PR.
> >
> > Thanks
> > Paul
> >
> > Mary McRae wrote:
> > > We can also invent another URI to be used - like
> > > docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm-v1.1.doc etc. - that way even
> > > if the date changes we're still talking about the latest version of the
> > > 1.1 spec ...
> > >
> > > m
> > >
> > >
> > ------------------------------------------------------------------------
> > > *From:* Marc Goodner [mailto:]
> > > *Sent:* Sunday, February 11, 2007 9:18 PM
> > > *To:* Doug Davis;
> > > *Cc:* 'Mary McRae';
> > > *Subject:* RE: [ws-rx-editors] RE: CD5.3
> > >
> > > So on 2, yeah we don't have anything like that. I think the best we
> > > can do is a link to the namespace as that could eventually contain
> > > the previous/latest links there. The only other immediate
> > > alternative I can think of would be the Public TC page.
> > >
> > >
> > >
> > > My vote for now would be to use the namespace. The reason is that if
> > > we progress with the same namespace from this PR, and I'm pretty
> > > hopeful we will, then the CS will be in that location with a link to
> > > the previous CD for the same namespace. That seems to best satisfy
> > > the intent.
> > >
> > >
> > >
> > > *From:* Doug Davis [mailto:]
> > > *Sent:* Sunday, February 11, 2007 5:38 PM
> > > *To:*
> > > *Cc:* 'Mary McRae'; Marc Goodner;
> > > *Subject:* RE: [ws-rx-editors] RE: CD5.3
> > >
> > >
> > >
> > >
> > > 1. I'll remove the [insert...] since, as Marc said, I don't think we
> > > have any.
> > > 2. The guideline says:
> > > A bookmarkable, version-agnostic, generic URI serving as a URI alias
> > > which is always associated with the latest/current specification
> > > instance, thus having a changing referent; it serves to identify and
> > > directly locate each successive published instance of a developing
> > > specification, through time [Label: Latest Version]
> > > Do we have a URL like that? As far as I know all of our URLs have
> > > dates in them. Can Oasis assign us a non-dated set of URLs?
> > > 3. Done - as much as I could anyway :-)
> > >
> > > Latest zip is here:
> > >
> > http://www.oasis-open.org/apps/org/workgroup/ws-rx-editors/download.php/22331/CD05.zip
> > >
> > > (you guys are probably sick of me sending huge zip files)
> > > Will replace the individual files in the CD5 folder once people 'ok'
> > > it but I think I still need those static URLs mentioned in #2.
> > >
> > > thanks
> > > -Doug
> > > ______________________________________________________
> > > STSM | Web Services Architect | IBM Software Group
> > > (919) 254-6905 | IBM T/L 444-6905 |
> > >
> > > *"Mary McRae" <>*
> > > Sent by: Mary McRae <>
> > >
> > > 02/11/2007 07:54 PM
> > >
> > > Please respond to
> > > <>
> > >
> > >
> > >
> > > To
> > >
> > >
> > >
> > > Doug Davis/Raleigh/IBM@IBMUS, "'Marc Goodner'"
> > <>
> > >
> > > cc
> > >
> > >
> > >
> > > "'Mary McRae'" <>,
> > > <>
> > >
> > > Subject
> > >
> > >
> > >
> > > RE: [ws-rx-editors] RE: CD5.3
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Before you do that ;-)
> > >
> > > 1. in all three spec files -- pay attention to the last para of the
> > > Notices section. It refers to OASIS' new Trademark policy. In the
> > > first line you'll see "[insert specific trademarked names,
> > > abbreviations, etc. here]" - any terms that the TC believes should
> > > be trademarked should be listed there and the boilerplate text
> > removed.
> > >
> > > 2. also, for "latest version" the intent is to use a URI that will
> > > always bring up the most recent copy of the spec (see samples in
> > > naming guidelines documents). Oops - just found another bad link on
> > > the templates page.
> > >
> > http://docs.oasis-open.org/templates/OASISSpecificationTemplateGuidelines.html
> > > section 3.4.3 or here:
> > >
> > http://docs.oasis-open.org/specGuidelines/namingGuidelines/metadata.html#specURIs
> > >
> > >
> > > 3. I apparently also messed up when I created the new templates for
> > > OO (and possibly Word). There were supposed to be two more
> > > categories on the cover page between Editors and Abstract:
> > > Related Work
> > > and
> > > Declared XML Namespaces
> > > (can be seen here:
> > >
> > http://docs.oasis-open.org/templates/OASISSpecificationTemplateV3.0.html)
> > >
> > >
> > > No penalties for not including #3, but bonus points awarded if you
> > > do ;-)
> > >
> > > I'm going to go watch the Grammys ... I think you guys have it under
> > > control and we'll be all set for announcement tomorrow.
> > >
> > > m
> > >
> > >
> > ------------------------------------------------------------------------
> > >
> > > *From:* Doug Davis [mailto:] *
> > > Sent:* Sunday, February 11, 2007 7:29 PM*
> > > To:* Marc Goodner*
> > > Cc:* Mary McRae; ;
> > > *
> > > Subject:* RE: [ws-rx-editors] RE: CD5.3
> > >
> > >
> > > Actually, I was hoping you might be able to generate new HTML by
> > > importing it into Word :-)
> > >
> > > thanks
> > > -Doug
> > > ______________________________________________________
> > > STSM | Web Services Architect | IBM Software Group
> > > (919) 254-6905 | IBM T/L 444-6905 |
> > >
> > > *Marc Goodner <>*
> > >
> > > 02/11/2007 07:22 PM
> > >
> > >
> > >
> > >
> > >
> > > To
> > >
> > >
> > >
> > > Doug Davis/Raleigh/IBM@IBMUS, ""
> > > <>
> > >
> > > cc
> > >
> > >
> > >
> > > Mary McRae <>,
> > > ""
> > > <>
> > >
> > > Subject
> > >
> > >
> > >
> > > RE: [ws-rx-editors] RE: CD5.3
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Thanks for the quick turnaround on the doc Dug. Mary, thanks a ton
> > > for staying engaged with us over the weekend.
> > >
> > > A quick scan and this looks good to me. It looks like the correct
> > > Notices now, but I defer to Mary on that.
> > >
> > > This one doesn't have the HTML in it. We're we just going to update
> > > the previous generated HTML by hand?
> > > *
> > > From:* Doug Davis [mailto:] *
> > > Sent:* Sunday, February 11, 2007 3:17 PM*
> > > To:* *
> > > Cc:* Mary McRae; *
> > > Subject:* RE: [ws-rx-editors] RE: CD5.3
> > >
> > >
> > > ***********************
> > > Warning: Your file, CD05.zip, contains more than 32 files after
> > > decompression and cannot be scanned.
> > > ***********************
> > >
> > >
> > >
> > > ok - let's give this one a try.
> > >
> > >
> > > thanks
> > > -Doug
> > > ______________________________________________________
> > > STSM | Web Services Architect | IBM Software Group
> > > (919) 254-6905 | IBM T/L 444-6905 |
> > >
> > > *"Mary McRae" <>*
> > > Sent by: Mary McRae <>
> > >
> > > 02/11/2007 06:05 PM
> > >
> > >
> > >
> > > Please respond to
> > > <>
> > >
> > >
> > >
> > >
> > >
> > > To
> > >
> > >
> > >
> > > Doug Davis/Raleigh/IBM@IBMUS
> > >
> > > cc
> > >
> > >
> > >
> > > <>
> > >
> > > Subject
> > >
> > >
> > >
> > > RE: [ws-rx-editors] RE: CD5.3
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Almost - new Copyright line says:
> > > Copyright (c) OASIS(r) 1993-2007. All Rights Reserved. OASIS
> > trademark,
> > > IPR and other policies apply.
> > >
> > > And then you'll need to make sure that it's the same in both the
> > > spec and the schema/wsdl themselves.
> > >
> > > m
> > >
> > >
> > >
> > >
> > ------------------------------------------------------------------------
> > >
> > >
> > > *
> > > From:* Doug Davis [mailto:] *
> > > Sent:* Sunday, February 11, 2007 5:03 PM*
> > > To:* *
> > > Cc:* *
> > > Subject:* [ws-rx-editors] RE: CD5.3*
> > > Importance:* High
> > >
> > >
> > > Mary,
> > > am I correct in assuming that if I replace:
> > > <!--> OASIS takes no position regarding the validity or scope
> > of any
> > > intellectual prop
> > > erty or other rights that might be claimed to pertain to the
> > > implementation or u
> > > se of the technology described in this document or the extent to
> > > which any licen
> > > se 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's
> > > procedures with respect to rights in OASIS specifications can be
> > > found at the OA
> > > SIS website. Copies of claims of rights made available for
> > > publication and any a
> > > ssurances 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
> > > implementors or users of this specification, can be obtained from
> > > the OASIS Exe
> > > cutive Director.
> > > OASIS invites any interested party to bring to its attention any
> > > copyrights, pat
> > > ents or patent applications, or other proprietary rights which may
> > > cover technol
> > > ogy that may be required to implement this specification. Please
> > > address the inf
> > > ormation to the OASIS Executive Director.
> > > Copyright (c) OASIS Open 2002-2007. All Rights Reserved.
> > > 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 implem
> > > entation 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 paragraph are included on all such copies and derivative works.
> > > However, th
> > > is document itself does not be modified in any way, such as by
> > > removing the copy
> > > right notice or references to OASIS, except as needed for the
> > > purpose of develop
> > > ing OASIS specifications, in which case the procedures for
> > > copyrights defined in
> > > the OASIS Intellectual Property Rights document must be followed, or
> > > as require
> > > d to translate it into languages other than English.
> > > The limited permissions granted above are perpetual and will not be
> > > revoked by O
> > > ASIS or its successors or assigns.
> > > This document and the information contained herein is provided on an
> > > "AS IS" bas
> > > is and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
> > > BUT NOT LIM
> > > ITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
> > > INFRINGE AN
> > > Y RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR
> > > A PARTICULA
> > > R PURPOSE.
> > > -->
> > >
> > > with just:
> > >
> > > <!-- Copyright (c) OASIS Open 2002-2007. All Rights Reserved. -->
> > >
> > > That'd we'd be ok?
> > >
> > > thanks
> > > -Doug
> > > ______________________________________________________
> > > STSM | Web Services Architect | IBM Software Group
> > > (919) 254-6905 | IBM T/L 444-6905 |
> > >
> > > *"Mary McRae" <>*
> > > Sent by: Mary McRae <>
> > >
> > > 02/11/2007 04:47 PM
> > >
> > >
> > >
> > > Please respond to
> > > <>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > To
> > >
> > >
> > >
> > > Doug Davis/Raleigh/IBM@IBMUS, <>
> > >
> > > cc
> > >
> > >
> > >
> > > Subject
> > >
> > >
> > >
> > > RE: CD5.3
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi Doug,
> > >
> > > I haven't unzipped yet, but the schema / wsdl *do* need the Notices
> > > section that's inserted as a comment at the beginning of the files
> > > changed from the legacy IPR policy language to the 4-15-2005 policy
> > > language ... I'm willing to go the extra mile to get this out by end
> > > of day Monday since you're working hard to get everything
> > accomplished.
> > >
> > > Mary
> > >
> > >
> > >
> > >
> > ------------------------------------------------------------------------
> > >
> > >
> > > *
> > > From:* Doug Davis [mailto:] *
> > > Sent:* Sunday, February 11, 2007 10:26 AM*
> > > To:* *
> > > Cc:* *
> > > Subject:* CD5.3*
> > > Importance:* High
> > >
> > > ***********************
> > > Warning: Your file, CD05.zip, contains more than 32 files after
> > > decompression and cannot be scanned.
> > > ***********************
> > >
> > >
> > >
> > >
> > >
> > > Editors:
> > > Here's CD5.3 with the changes Mary wanted. I did not update the
> > > schema/wsdl as that was just a suggestion and I wanted to keep the
> > > diffs as small as possible.
> > > Take a look and see if all looks well.
> > >
> > >
> > > thanks
> > > -Doug
> > > ______________________________________________________
> > > STSM | Web Services Architect | IBM Software Group
> > > (919) 254-6905 | IBM T/L 444-6905 |
> > >
> >
> > --
> > Paul Fremantle
> > VP/Technology and Partnerships, WSO2
> > OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> >
> > (646) 290 8050
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> >
> >
> > --
> > Paul Fremantle
> > VP/Technology and Partnerships, WSO2
> > OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> >
> > (646) 290 8050
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology and Partnerships, WSO2
> OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
>
> (646) 290 8050
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
>
>
>
>
