[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel-spec-edit] Re: Updated Committee Spec docs and RDDL
I have prepared a memo for discussion with Patrick Gannon and Jamie Clark about the note below: > we will declare them as generic URLs always point to the latest version of those documents, right? > [mpm] > > yes In my judgment as Chief Information Architect, I believe that action ("we will declare..." will violate the OASIS Naming Guidelines, and unfairly allow a request that has been explicitly denied to at least four other TC, on principled grounds. I am, of course, prepared to be over-ruled on this decision, but the matter has not been escalated to the proper level. More later. - Robin Cover > _____ > > From: Alex Yiu [mailto:alex.yiu@oracle.com] > Sent: Thursday, February 01, 2007 4:52 PM > To: Diane Jordan > Cc: mary.mcrae@oasis-open.org; jevdemon@microsoft.com; wsbpel-spec-edit@lists.oasis-open.org; Alex Yiu; Martin Chapman > Subject: Re: [wsbpel-spec-edit] Re: Updated Committee Spec docs and RDDL > > > > Hi Diane, > > Thanks for the email. > > Mary, other OASIS staff and others ... > > I would like to confirm that I understand how to deal with URLs: > > [1] > For the following URL: > http://docs.oasis-open.org/wsbpel/2.0/wsbpel-specification-draft.pdf > http://docs.oasis-open.org/wsbpel/2.0/process/abstract/ws-bpel_abstract_common_base.xsd > http://docs.oasis-open.org/wsbpel/2.0/process/executable/ws-bpel_executable.xsd > http://docs.oasis-open.org/wsbpel/2.0/plnktype/ws-bpel_plnktype.xsd > http://docs.oasis-open.org/wsbpel/2.0/serviceref/ws-bpel_serviceref.xsd > http://docs.oasis-open.org/wsbpel/2.0/varprop/ws-bpel_varprop.xsd > > we will declare them as generic URLs always point to the latest version of those documents, right? > [mpm] > > yes > > [2] > And, we will copy docs previously published in PR01 to the new location > http://docs.oasis-open.org/wsbpel/2.0/PR01/wsbpel-specification-draft.pdf > http://docs.oasis-open.org/wsbpel/2.0/PR01/process/abstract/ws-bpel_abstract_common_base.xsd > http://docs.oasis-open.org/wsbpel/2.0/PR01/process/executable/ws-bpel_executable.xsd > http://docs.oasis-open.org/wsbpel/2.0/PR01/plnktype/ws-bpel_plnktype.xsd > http://docs.oasis-open.org/wsbpel/2.0/PR01/serviceref/ws-bpel_serviceref.xsd > http://docs.oasis-open.org/wsbpel/2.0/PR01/varprop/ws-bpel_varprop.xsd > [mpm] > > yes > > [3] > I am wondering whether we do the same for PR02 by keep documents for the version of PR02 also at docs.oasis-open.org. > (e.g. " http://docs.oasis-open.org/wsbpel/2.0/PR02/...") > [mpm] > > not at this point; it would mean re-working all the files. PR02 only lives in Kavi. > > [4] > I also noticed in RDDL one of previous version URL are: > http://docs.oasis-open.org/wsbpel/2.0/PR01/process/abstract/ws-bpel_abstract_common_base.xsd > (Note: PR01) > Some are: > http://docs.oasis-open.org/wsbpel/2.0/CD01/process/executable/ws-bpel_executable.xsd > (Note: CD01) > [mpm] ' > > yes, you're right - they should say "PR01" rather than "CD01" > > > I am wondering: > [a] what CD01 stands for? Comittee Draft? > [b] should they be "PR02" instead, because our last published version are PR02 (public review 2) before our CS01 > (committee specification 1)? [I hope I got all the terms, right?] > > [mpm] > CD = committee draft (CDs are to be consecutively numbered) > PR02 was not published in Kavi due to the problems with file names, etc. > > > All in all, I guess it is a good idea for OASIS to come up with a clear formal guidline on how to publish documents at > docs.oasis-open.org in future for TC members to follow. > > > > Thanks! > > > > Regards, > Alex Yiu > > > > > Diane Jordan wrote: > > > Mary, Thanks very much. > > John and Alex, please review the rddl and let us know if you have any questions. > > Mary, > As usual, I have questions for you! > > * How do we populate the specification uri's on the first page for this version and current version? Do you do > that? eg: Specification URIs: > > This Version: > <http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.html> > http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.html > > <http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.doc> > http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.doc > > <http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.pdf> > http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.pdf > > * Again on the first page, I'm not sure why you chose the link you did for the previous verson - ie, the version > that went into the second public review that shows changes from the first public review: > > h <http://www.oasis-open.org/committees/download.php/21574/wsbpel-specification-public_review_draft_2_diff.doc> > ttp://www.oasis-open.org/committees/download.php/21574/wsbpel-specification-public_review_draft_2_diff.doc > > <http://www.oasis-open.org/committees/download.php/21575/wsbpel-specification_public_review_draft_2_diff.pdf> > http://www.oasis-open.org/committees/download.php/21575/wsbpel-specification_public_review_draft_2_diff.pdf > > The change marks might be confusing since they're not the changes versus "This Version" but as compared with an older > version. It seems like it would make sense to point to either the clean second public review version, or a copy of the > second public review versio with changes marked versus "This Version". The latter is available at: > <http://www.oasis-open.org/committees/download.php/22037/wsbpel-specification-draft%20candidate%20CD%20Jan%2025%2007%20d > iff%20wit%85.pdf> > http://www.oasis-open.org/committees/download.php/22037/wsbpel-specification-draft%20candidate%20CD%20Jan%2025%2007%20di > ff%20wit%85.pdfand > <http://www.oasis-open.org/committees/download.php/21993/wsbpel-specification-draft%20candidate%20CD%20Jan%2025%2007%20d > iff%20with%20public%20review%20%202.doc> > http://www.oasis-open.org/committees/download.php/21993/wsbpel-specification-draft%20candidate%20CD%20Jan%2025%2007%20di > ff%20with%20public%20review%20%202.doc > > * How do we figure out what needs to be put in the trademark field? I know we use the names of other > specifications done at OASIS. Should they be there. Howe about those approved by other org's or just published by > companies? I guess we'd go according to the references section to identify them - does that sound right? > > > Regards, Diane > IBM Emerging Internet Software Standards > drj@us.ibm.com > (919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709 > > > > > "Mary McRae" <mailto:mary.mcrae@oasis-open.org> <mary.mcrae@oasis-open.org> > Sent by: Mary McRae <mailto:marypmcrae@gmail.com> <marypmcrae@gmail.com> > > > 01/31/2007 02:03 PM > > > Please respond to > <mailto:mary.mcrae@oasis-open.org> <mary.mcrae@oasis-open.org> > > > > To > Diane Jordan/Raleigh/IBM@IBMUS, "'John Evdemon'" <mailto:John.Evdemon@microsoft.com> <John.Evdemon@microsoft.com> > > cc > <mailto:wsbpel@lists.oasis-open.org> <wsbpel@lists.oasis-open.org> > > Subject > Updated Committee Spec docs and RDDL > > > > > > > > > Hi everyone, > > In order to shortcut further delays, I've taken the liberty (with Diane's okay) to update the specification with the > latest cover page(s) metadata as well as update the RDDL file. There's one new bit of metadata that was recently > approved by the Board of Directors concerning trademarks. More information can be found here: > <http://www.oasis-open.org/who/trademark.php> http://www.oasis-open.org/who/trademark.php. Note that the last paragraph > in the status section contains a field for any additional terms that should be trademarked and will need to be updated. > > Regards, > > Mary > > --------------------------------------------------- > Mary P McRae > Manager of TC Administration, OASIS > email: <mailto:mary.mcrae@oasis-open.org> mary.mcrae@oasis-open.org > web: <http://www.oasis-open.org/> www.oasis-open.org > phone: 603.232.9090 > > OASIS Symposium: > "eBusiness and Open Standards: > Understanding the Facts, Fiction, and Future" > 15-18 April 2007 San Diego, CA USA > <http://www.oasis-open.org/events/symposium/> http://www.oasis-open.org/events/symposium/ > > > > > _____ > > > <http://www.oasis-open.org> http://www.oasis-open.org > <http://www.oasis-open.org> www.oasis-open.org <http://www.oasis-open.org/who/> About OASIS > <http://www.oasis-open.org/about/foundational_sponsors.php> OASIS Members <http://www.oasis-open.org/join/> Join > OASIS <http://www.oasis-open.org/news/> OASIS News <http://www.oasis-open.org/events/> OASIS Events > <http://www.oasis-open.org/members/> Members Only <http://xml.coverpages.org/> XML Cover Pages > <http://www.xml.org> XML.org > > Web Services Business Process Execution Language (WS-BPEL) > > > 31 January 2007 > > > Introduction > > > This document describes version 2.0 of the WS-BPEL <http://docs.oasis-open.org/wsbpel/2.0> namespace. It also contains > a directory of links to related resources using the Resource > <http://www.openhealth.org/RDDL/20040118/rddl-20040118.html> Directory Description Language (RDDL) 2.0. > > > Namespace URI Versioning Policy > > > It is the intent of the OASIS WS-BPEL Technical Committee that the WS-BPEL v2.0 namespace URI will not change > arbitrarily with each subsequent revision of the corresponding WSDL or XML Schema documents but rather change only when > a subsequent revision, published in conjunction with a Committee Specification, results in non-backwardly compatible > changes from a previously published Committee Specification. > > Under this policy, the following are examples of backwards compatible changes that would not result in assignment of a > new namespace URI: > > * addition of new global element, attribute, complexType and simpleType definitions > > * addition of new operations within a WSDL portType or binding (along with the corresponding schema, message and > part definitions) > > * addition of new elements or attributes in locations covered by a previously specified wildcard > > * modifications to the pattern facet of a type definition for which the value-space of the previous definition > remains valid or for which the value-space of the preponderance of instance would remain valid > > * modifications to the cardinality of elements for which the value-space of possible instance documents conformant > to the previous revision of the schema would still be valid with regards to the revised cardinality rule > > > Related Resources for WS-BPEL v2.0 > > > Normative Reference: > > > WS-BPEL <http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.pdf> v2.0 > > > Title: > > OASIS Web Services Business Process Execution Language (WSBPEL) v2.0 > > Product: > > wsbpel > > Date: > > 31 January 2007 > > ProductVersion: > > 2.0 > > ArtifactType: > > specification > > Stage: > > Committee Specification > > Revision: > > 01 > > This version: > > > http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.pdf > > Previous version: > > > http://www.oasis-open.org/committees/download.php/21575/wsbpel-specification_public_review_draft_2_diff.pdf > <http://www.oasis-open.org/committees/download.php/21575/wsbpel-specification_public_review_draft_2_diff.pdf> > > Language: > > en-us > > Editors: > > > > > * Alexandre Alves, BEA > > * Assaf Arkin, Intalio > > * Sid Askary, Nuperus > > * Ben Bloch, Systinet > > * Francisco Curbera, IBM > > * Mark Ford, Active Endpoints, Inc. > > * Yaron Goland, BEA > > * Alejandro Guízar, JBoss, Inc. > > * Neelakantan Kartha, Sterling Commerce > > * Canyang Kevin Liu, SAP > > * Rania Khalaf, IBM > > * Dieter König, IBM > > * Mike Marin, FileNet > > * Vinkesh Mehta, Deloitte > > * Satish Thatte, Microsoft > > * Danny van der Rijn, TIBCO Software > > * Prasad Yendluri, webMethods > > * Alex Yiu, Oracle > > Additional Formats: > > > > > * XHTML <http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.html> > > * Microsoft <http://docs.oasis-open.org/wsbpel/2.0/CS01/wsbpel-v2.0-CS01.doc> Word 97-2003 > > Comments list: > > Submit comments <http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=wsbpel> > > Archive: > > Comments archive <http://lists.oasis-open.org/archives/wsbpel-comment/> > > > XML Schemas for WS-BPEL v2.0: > > > ws-bpel_abstract_common_base.xsd > <http://docs.oasis-open.org/wsbpel/2.0/CS01/process/abstract/ws-bpel_abstract_common_base.xsd> > > > Title: > > Schema for OASIS Business Process Execution Language (WS-BPEL) 2.0 - Abstract BPEL Common Base > > Product: > > wsbpel > > Date: > > 31 January 2007 > > ProductVersion: > > 2.0 > > ArtifactType: > > schema > > Stage: > > Committee Specification > > Revision: > > 01 > > This version: > > http://docs.oasis-open.org/wsbpel/2.0/CS01/process/abstract/ws-bpel_abstract_common_base.xsd > > Previous version: > > http://docs.oasis-open.org/wsbpel/2.0/PR01/process/abstract/ws-bpel_abstract_common_base.xsd > > Editors: > > > > > * Alexandre Alves, BEA > > * Assaf Arkin, Intalio > > * Sid Askary, Nuperus > > * Ben Bloch, Systinet > > * Francisco Curbera, IBM > > * Mark Ford, Active Endpoints, Inc. > > * Yaron Goland, BEA > > * Alejandro Guízar, JBoss, Inc. > > * Neelakantan Kartha, Sterling Commerce > > * Canyang Kevin Liu, SAP > > * Rania Khalaf, IBM > > * Dieter König, IBM > > * Mike Marin, FileNet > > * Vinkesh Mehta, Deloitte > > * Satish Thatte, Microsoft > > * Danny van der Rijn, TIBCO Software > > * Prasad Yendluri, webMethods > > * Alex Yiu, Oracle > > Comments list: > > Submit comments <http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=wsbpel> > > Archive: > > Comments Archive <http://lists.oasis-open.org/archives/wsbpel-comment/> > > > ws-bpel_executable.xsd <http://docs.oasis-open.org/wsbpel/2.0/CS01/process/executable/ws-bpel_executable.xsd> > > > Title: > > Schema for OASIS Business Process Execution Language (WS-BPEL) 2.0 - Schema for Executable Processes > > Product: > > wsbpel > > Date: > > 31 January 2007 > > ProductVersion: > > 2.0 > > ArtifactType: > > schema > > Stage: > > Committee Specification > > Revision: > > 01 > > This version: > > http://docs.oasis-open.org/wsbpel/2.0/CS01/process/executable/ws-bpel_executable.xsd > > Previous version: > > http://docs.oasis-open.org/wsbpel/2.0/CD01/process/executable/ws-bpel_executable.xsd > > Editors: > > > > > * Alexandre Alves, BEA > > * Assaf Arkin, Intalio > > * Sid Askary, Nuperus > > * Ben Bloch, Systinet > > * Francisco Curbera, IBM > > * Mark Ford, Active Endpoints, Inc. > > * Yaron Goland, BEA > > * Alejandro Guízar, JBoss, Inc. > > * Neelakantan Kartha, Sterling Commerce > > * Canyang Kevin Liu, SAP > > * Rania Khalaf, IBM > > * Dieter König, IBM > > * Mike Marin, FileNet > > * Vinkesh Mehta, Deloitte > > * Satish Thatte, Microsoft > > * Danny van der Rijn, TIBCO Software > > * Prasad Yendluri, webMethods > > * Alex Yiu, Oracle > > Comments list: > > Submit comments <http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=wsbpel> > > Archive: > > Comments Archive <http://lists.oasis-open.org/archives/wsbpel-comment/> > > > ws-bpel_plnktype.xsd <http://docs.oasis-open.org/wsbpel/2.0/CS01/plnktype/ws-bpel_plnktype.xsd> > > > Title: > > Schema for OASIS Business Process Execution Language (WS-BPEL) 2.0 - Schema for Partner Link Type > > Product: > > wsbpel > > Date: > > 31 January 2007 > > ProductVersion: > > 2.0 > > ArtifactType: > > schema > > Stage: > > Committee Specification > > Revision: > > 01 > > This version: > > http://docs.oasis-open.org/wsbpel/2.0/CS01/plnktype/ws-bpel_plnktype.xsd > > Previous version: > > http://docs.oasis-open.org/wsbpel/2.0/CD01/plnktype/ws-bpel_plnktype.xsd > > Editors: > > > > > * Alexandre Alves, BEA > > * Assaf Arkin, Intalio > > * Sid Askary, Nuperus > > * Ben Bloch, Systinet > > * Francisco Curbera, IBM > > * Mark Ford, Active Endpoints, Inc. > > * Yaron Goland, BEA > > * Alejandro Guízar, JBoss, Inc. > > * Neelakantan Kartha, Sterling Commerce > > * Canyang Kevin Liu, SAP > > * Rania Khalaf, IBM > > * Dieter König, IBM > > * Mike Marin, FileNet > > * Vinkesh Mehta, Deloitte > > * Satish Thatte, Microsoft > > * Danny van der Rijn, TIBCO Software > > * Prasad Yendluri, webMethods > > * Alex Yiu, Oracle > > Comments list: > > Submit comments <http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=wsbpel> > > Archive: > > Comments Archive <http://lists.oasis-open.org/archives/wsbpel-comment/> > > > ws-bpel_serviceref.xsd <http://docs.oasis-open.org/wsbpel/2.0/CS01/serviceref/ws-bpel_serviceref.xsd> > > > Title: > > Schema for OASIS Business Process Execution Language (WS-BPEL) 2.0 - Schema for Service Reference > > Product: > > wsbpel > > Date: > > 31 January 2007 > > ProductVersion: > > 2.0 > > ArtifactType: > > schema > > Stage: > > Committee Specification > > Revision: > > 01 > > This version: > > http://docs.oasis-open.org/wsbpel/2.0/CS01/serviceref/ws-bpel_serviceref.xsd > > Previous version: > > http://docs.oasis-open.org/wsbpel/2.0/CD01/serviceref/ws-bpel_serviceref.xsd > > Editors: > > > > > * Alexandre Alves, BEA > > * Assaf Arkin, Intalio > > * Sid Askary, Nuperus > > * Ben Bloch, Systinet > > * Francisco Curbera, IBM > > * Mark Ford, Active Endpoints, Inc. > > * Yaron Goland, BEA > > * Alejandro Guízar, JBoss, Inc. > > * Neelakantan Kartha, Sterling Commerce > > * Canyang Kevin Liu, SAP > > * Rania Khalaf, IBM > > * Dieter König, IBM > > * Mike Marin, FileNet > > * Vinkesh Mehta, Deloitte > > * Satish Thatte, Microsoft > > * Danny van der Rijn, TIBCO Software > > * Prasad Yendluri, webMethods > > * Alex Yiu, Oracle > > Comments list: > > Submit comments <http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=wsbpel> > > Archive: > > Comments Archive <http://lists.oasis-open.org/archives/wsbpel-comment/> > > > ws-bpel_varprop.xsd <http://docs.oasis-open.org/wsbpel/2.0/CS01/varprop/ws-bpel_varprop.xsd> > > > Title: > > Schema for OASIS Business Process Execution Language (WS-BPEL) 2.0 - Schema for Variable Properties > > Product: > > wsbpel > > Date: > > 31 January 2007 > > ProductVersion: > > 2.0 > > ArtifactType: > > schema > > Stage: > > Committee Specification > > Revision: > > 01 > > This version: > > http://docs.oasis-open.org/wsbpel/2.0/CS01/varprop/ws-bpel_varprop.xsd > > Previous version: > > http://docs.oasis-open.org/wsbpel/2.0/CD01/varprop/ws-bpel_varprop.xsd > > Editors: > > > > > * Alexandre Alves, BEA > > * Assaf Arkin, Intalio > > * Sid Askary, Nuperus > > * Ben Bloch, Systinet > > * Francisco Curbera, IBM > > * Mark Ford, Active Endpoints, Inc. > > * Yaron Goland, BEA > > * Alejandro Guízar, JBoss, Inc. > > * Neelakantan Kartha, Sterling Commerce > > * Canyang Kevin Liu, SAP > > * Rania Khalaf, IBM > > * Dieter König, IBM > > * Mike Marin, FileNet > > * Vinkesh Mehta, Deloitte > > * Satish Thatte, Microsoft > > * Danny van der Rijn, TIBCO Software > > * Prasad Yendluri, webMethods > > * Alex Yiu, Oracle > > Comments list: > > Submit comments <http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=wsbpel> > > Archive: > > Comments Archive <http://lists.oasis-open.org/archives/wsbpel-comment/> > > > Related Namespaces > > > * Abstract Process for WS-BPEL v2.0 namespace: http://docs.oasis-open.org/wsbpel/2.0/process/abstract > > * Executable Process for WS-BPEL v2.0 namespace: http://docs.oasis-open.org/wsbpel/2.0/process/executable > > * Partner Link Type for WS-BPEL v2.0 namespace: http://docs.oasis-open.org/wsbpel/2.0/plnktype > > * Service Reference for WS-BPEL v2.0 namespace: http://docs.oasis-open.org/wsbpel/2.0/serviceref > > * Variable Properties for WS-BPEL v2.0 namespace: http://docs.oasis-open.org/wsbpel/2.0/varprop = > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]