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

 


Help: OASIS Mailing Lists Help | MarkMail Help

opencsa-liaison message

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


Subject: RE: [opencsa-liaison] Namespaces and Specification CDs....



I guess there is not much to discuss without Mary's input (on the
background and rationale for inserting the 'ns' token in the namespace
URI)!

> -----Original Message-----
> From: Jeff Mischkinsky [mailto:jeff.mischkinsky@oracle.com] 
> Sent: Friday, Mar 07, 2008 10:34 AM
> To: Martin Chapman
> Cc: mary.mcrae@oasis-open.org; ashok.malhotra@oracle.com; 
> opencsa-liaison@lists.oasis-open.org
> Subject: Re: [opencsa-liaison] Namespaces and Specification CDs....
> 
> hi,
>    Do we need a meeting to discuss this or can it be handled 
> via email?
>       cheers,
>      jeff
> On Mar 07, 2008, at 7:08 AM, Martin Chapman wrote:
> 
> > Replying only to the SCA Liaison SC.
> >
> > Mary has basically informed us that we should be using namespaces  
> > in OpenSCA with a prefix of:
> > http://docs.oasis-open.org/ns/opencsa/..., and  Mary has an action  
> > item from a Steering Committee meeting to write this up.
> > It is not clear to me why  the /ns/ is before opensca, as no other  
> > TCs use this approach, but such is life.
> > Thus I just wanted to make sure that all OpenSCA TCs are aware of  
> > this prefix.
> >
> > Cheers,
> >   Martin.
> >
> >
> >
> >> -----Original Message-----
> >> From: Mary McRae [mailto:marypmcrae@gmail.com] On Behalf Of Mary  
> >> McRae
> >> Sent: Tuesday, February 26, 2008 9:56 PM
> >> To: ashok.malhotra@oracle.com
> >> Cc: 'Mike Edwards'; 'OASIS Assembly';
> >> opencsa-liaison@lists.oasis-open.org
> >> Subject: [sca-assembly] RE: [opencsa-liaison] RE:
> >> [sca-assembly] Namespaces and Specification CDs....
> >>
> >>
> >> Thanks Ashok,
> >>
> >>  Here's a good example showing interrelationships:
> >>
> >> http://docs.oasis-open.org/ws-rx/wsrmp/200702
> >> http://docs.oasis-open.org/ws-rx/wsmc/200702
> >>
> >> Regards,
> >>
> >> Mary
> >>
> >>> -----Original Message-----
> >>> From: ashok malhotra [mailto:ashok.malhotra@oracle.com]
> >>> Sent: Tuesday, February 26, 2008 4:34 PM
> >>> To: mary.mcrae@oasis-open.org
> >>> Cc: 'Mike Edwards'; 'OASIS Assembly';
> >>> opencsa-liaison@lists.oasis-open.org
> >>> Subject: Re: [opencsa-liaison] RE: [sca-assembly] Namespaces and
> >>> Specification CDs....
> >>>
> >>>> And who will be providing the requisite namespace document?
> >>>
> >>> Mary, if you point me to one or more examples I will write the
> >>> namespace document.
> >>>
> >>> Ashok
> >>>
> >>> Mary McRae wrote:
> >>>
> >>>> Hi everyone,
> >>>>
> >>>>
> >>>>
> >>>>   One of the concerns expressed when the notion of a common
> >>>> namespace was initially brought up was the matter of control and
> >>>> approval. I believe that sca-policy was directed by the
> >> sca-assembly
> >>>> TC to use http://docs.oasis-open.org/ns/opencsa/sca/200712. While
> >>>> this document has not yet gone for Public Review, and no 
> namespace
> >>>> document was provided, I would like to ensure that this is all
> >>>> worked out before more documents get to the Committee
> >> Draft / Public
> >>>> Review stage. Sca-bpel is **also** using the 200712 
> namespace. Who
> >>>> will instruct the TCs that the namespace used in their
> >>>> specifications needs to be updated? Should all namespace
> >> requests be
> >>>> handled by the Open CSA Liaison subcommittee?
> >>>>
> >>>>
> >>>>
> >>>> And who will be providing the requisite namespace document?
> >>>>
> >>>>
> >>>>
> >>>> Mary
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> *From:* Mike Edwards [mailto:mike_edwards@uk.ibm.com]
> >>>> *Sent:* Tuesday, February 26, 2008 3:25 PM
> >>>> *To:* OASIS Assembly
> >>>> *Subject:* RE: [sca-assembly] Namespaces and 
> Specification CDs....
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Martin, Sanjay,
> >>>>
> >>>> Thanks for digging this out.  So, the formal proposal,
> >> which should
> >>>> be placed into the CD of the Assembly spec is:
> >>>>
> >>>> http://docs.oasis-open.org/ns/opencsa/sca/200803
> >>>>
> >>>> Now, this episode says also the following:
> >>>>
> >>>> a) we need to make clearer decisions as recorded in the meeting
> >>>> minutes - this is a case of something very confusing being
> >> recorded.
> >>>> Not blaming anyone but myself as chair for that, but it
> >> does need to
> >>>> change.
> >>>>
> >>>> b) we need to vote again on the format, since there is a change
> >>>> (forced by OASIS) from the format agreed by the TC
> >>>> - don't think that anyone will object, but I'd like to see
> >> a formal
> >>>> agreement to the actual format that we're going to use
> >>>>
> >>>>
> >>>> Yours,  Mike.
> >>>>
> >>>> Strategist - Emerging Technologies, SCA & SDO.
> >>>> Co Chair OASIS SCA Assembly TC.
> >>>> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN,
> >> Great Britain.
> >>>> Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431
> >>>> Email:  mike_edwards@uk.ibm.com
> >>>>
> >>>> *"Patil, Sanjay" <sanjay.patil@sap.com>*
> >>>>
> >>>> 26/02/2008 16:26
> >>>>
> >>>>
> >>>>
> >>>> To
> >>>>
> >>>>
> >>>>
> >>>> "Martin Chapman" <martin.chapman@oracle.com>, "OASIS Assembly"
> >>>> <sca-assembly@lists.oasis-open.org>
> >>>>
> >>>> cc
> >>>>
> >>>>
> >>>>
> >>>> Subject
> >>>>
> >>>>
> >>>>
> >>>> RE: [sca-assembly] Namespaces and Specification CDs....
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> If you follow the link in Martin's email below and open the
> >>>> attachment pointed at the bottom of that link, you will find the
> >>>> right proposal [1] for the namespace URI design.
> >>>>
> >>>> The additional change OASIS staff later required is - 
> insertion of
> >>>> the token 'ns' in the namespace URI.
> >>>>
> >>>> Assuming that the ballot for the first CD passes in Mar 
> 2008, then
> >>>> the namespace URI that would be compliant with the
> >> proposal we have
> >>>> adopted and that incorporates the change suggested by the OASIS
> >>>> staff would look as follows:
> >>>>
> >>>> http://docs.oasis-open.org/ns/opencsa/sca/200803
> >>>>
> >>>> -- Sanjay
> >>>>
> >>>> [1]
> >>>> http://www.oasis-open.org/apps/org/workgroup/sca-
> >>> assembly/email/archives/200710/bin00002.bin
> >>>>
> >>>>
> >>>>
> >> 
> --------------------------------------------------------------------
> >>>> ----
> >>>>
> >>>> *From:* Martin Chapman [mailto:martin.chapman@oracle.com] *
> >>>> Sent:* Tuesday, Feb 26, 2008 8:04 AM*
> >>>> To:* 'OASIS Assembly'*
> >>>> Subject:* RE: [sca-assembly] Namespaces and Specification CDs....
> >>>>
> >>>> Here's a link to the mail i thought we had agreed.
> >>>>
> >>>> http://www.oasis-open.org/apps/org/workgroup/sca-
> >>> assembly/email/archives/200710/msg00096.html
> >>>>
> >>>> -----Original Message-----*
> >>>> From:* Martin Chapman [mailto:martin.chapman@oracle.com] *
> >>>> Sent:* Tuesday, February 26, 2008 3:53 PM*
> >>>> To:* 'Mike Edwards'; 'OASIS Assembly'*
> >>>> Subject:* RE: [sca-assembly] Namespaces and Specification CDs....
> >>>>
> >>>> This is not what I thought we had agreed to do. We only
> >> need to rev
> >>>> the namespace when non-backwards compatible changes are
> >> made, not at
> >>>> each CD etc.
> >>>>
> >>>> Martin.
> >>>> -----Original Message-----*
> >>>> From:* Mike Edwards [mailto:mike_edwards@uk.ibm.com] *
> >>>> Sent:* Tuesday, February 26, 2008 10:02 AM*
> >>>> To:* OASIS Assembly*
> >>>> Subject:* [sca-assembly] Namespaces and Specification CDs....
> >>>>
> >>>>
> >>>> Folks,
> >>>>
> >>>> My view on the namespace is that we should aim to have 
> one and one
> >>>> only and not change it at all until the publication of 
> the "final"
> >>>> version of the specification.  Making changes for every
> >>>> CD makes no sense to me.  The CD's are drafts and have no
> >> "official"
> >>>> status.
> >>>>
> >>>> Folks who are trying to "follow" the XSDs etc during the spec
> >>>> development process will simply have to put up with the changes,
> >>>> with no assistance from dates in the NS's.  Only once there is
> >>>> something official available will there be a need to mark
> >> any future
> >>>> changes with a different NS.
> >>>>
> >>>> So, to cut to the chase how about the following as a 
> namespace for
> >>>> assembly:
> >>>>
> >>>>
> >>>> http://docs.oasis-open.org/OpenCSA/SCA-Common/200803
> >>>>
> >>>>
> >>>>
> >>>> ...we can vote to change to a later dated namespace once
> >> we get near
> >>>> final publication of OASIS SCA 1.0....
> >>>>
> >>>> Yours,  Mike.
> >>>>
> >>>> Strategist - Emerging Technologies, SCA & SDO.
> >>>> Co Chair OASIS SCA Assembly TC.
> >>>> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN,
> >> Great Britain.
> >>>> Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431
> >>>> Email:  mike_edwards@uk.ibm.com
> >>>>
> >>>> *Anish Karmarkar <Anish.Karmarkar@oracle.com>*
> >>>>
> >>>> 26/02/2008 02:00
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> To
> >>>>
> >>>>
> >>>>
> >>>> Bryan Aupperle <aupperle@us.ibm.com>
> >>>>
> >>>> cc
> >>>>
> >>>>
> >>>>
> >>>> sca-assembly@lists.oasis-open.org
> >>>>
> >>>> Subject
> >>>>
> >>>>
> >>>>
> >>>> Re: [sca-assembly] Groups -
> >> sca-assembly-1.1-spec-WD-03.doc uploaded
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> I agree.
> >>>> But before we do that we need to figure out a NS change
> >> policy: when
> >>>> would we change the namespace between two CDS? Would there be a
> >>>> change for every version, or would it change only when there is a
> >>>> backward incompatible change? Do we need to sync up the 
> NS between
> >>>> various TCs?
> >>>>
> >>>> Putting such a policy in place would be helpful for early
> >>>> adopters/implementers.
> >>>>
> >>>> -Anish
> >>>> --
> >>>>
> >>>> Bryan Aupperle wrote:
> >>>>>
> >>>>> I know this is a nit, but if we are going to consider WD 03 as a
> >>>>> potential CD, doesn't that mean that date for the
> >> namespace will be
> >>>>> set and therefore the declared namespace at the front of the
> >>>>> document should be filled in and not left as TBD?
> >>>>>
> >>>>> Bryan Aupperle, Ph.D.
> >>>>> STSM, WebSphere Enterprise Platform Software Solution Architect
> >>>>> Master Inventor
> >>>>>
> >>>>> Research Triangle Park,  NC
> >>>>> +1 919-254-7508 (T/L 444-7508)
> >>>>> Internet Address: aupperle@us.ibm.com
> >>>>>
> >>>>>
> >>>>> *Anish.Karmarkar@oracle.com*
> >>>>>
> >>>>> 02/19/2008 12:50 AM
> >>>>>
> >>>>>
> >>>>> To
> >>>>>                  sca-assembly@lists.oasis-open.org
> >>>>> cc
> >>>>>
> >>>>> Subject
> >>>>>                  [sca-assembly] Groups -
> >>>> sca-assembly-1.1-spec-WD-03.doc uploaded
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> The document revision named sca-assembly-1.1-spec-WD-03.doc has
> >>>>> been submitted by Dr. Anish Karmarkar to the OASIS Service
> >>>>> Component Architecture / Assembly (SCA-Assembly) TC document
> >>>>> repository.  This document is revision #2 of
> >>>>> sca-assembly-1.1-spec-WD-03.doc.
> >>>>>
> >>>>> Document Description:
> >>>>> WD-03 incorporates issues: 1A, 4, 9, 19, 21, 22
> >>>>> +
> >>>>> - in Implementation and ComponentType section added 
> attribute and
> >>>> element
> >>>>> description for service, reference, and   property
> >>>>> - removed comments that helped understand the initial
> >> restructuring
> >>>>> for WD02
> >>>>> - added changes for issue 43
> >>>>> - added changes for issue 45, except the changes for 
> policySet and
> >>>> requires
> >>>>> attribute on property elements
> >>>>>
> >>>>> View Document Details:
> >>>>> http://www.oasis-open.org/apps/org/workgroup/sca-
> >>> assembly/document.php?document_id=27238
> >>>>>
> >>>>> Download Document:
> >>>>> http://www.oasis-open.org/apps/org/workgroup/sca-
> >>> assembly/download.php/27238/sca-assembly-1.1-spec-WD-03.doc
> >>>>>
> >>>>> Revision:
> >>>>> This document is revision #2 of sca-assembly-1.1-spec-WD-03.doc.
> >>>>> The document details page referenced above will show 
> the complete
> >>>>> revision history.
> >>>>>
> >>>>>
> >>>>> PLEASE NOTE:  If the above links do not work for you, your email
> >>>> application
> >>>>> may be breaking the link into two pieces.  You may be 
> able to copy
> >>>> and paste
> >>>>> the entire link address into the address field of your
> >> web browser.
> >>>>>
> >>>>> -OASIS Open Administration
> >>>>>
> >>>>
> >>>>
> >> 
> --------------------------------------------------------------------
> >>>> -
> >>>> To unsubscribe from this mail list, you must leave the
> >> OASIS TC that
> >>>> generates this mail.  You may a link to this group and all
> >> your TCs in
> >>>> OASIS
> >>>> at:
> >>>>
> >> https://www.oasis-open.org/apps/org/workgroup/portal/ 
> >> my_workgroups.php
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >> 
> --------------------------------------------------------------------
> >>>> ----
> >>>>
> >>>>
> >>>>
> >>>> /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/
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >> 
> --------------------------------------------------------------------
> >>>> ----
> >>>>
> >>>>
> >>>>
> >>>> /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/
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> All the best, Ashok
> >>
> >>
> >> 
> ---------------------------------------------------------------------
> >> To unsubscribe from this mail list, you must leave the OASIS
> >> TC that generates this mail.  You may a link to this group and
> >> all your TCs in OASIS
> >> at:
> >> https://www.oasis-open.org/apps/org/workgroup/portal/ 
> >> my_workgroups.php
> >>
> >>
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  You may a link to this group and all 
> your TCs  
> > in OASIS
> > at:
> > 
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> >
> 
> --
> Jeff Mischkinsky			          		
> jeff.mischkinsky@oracle.com
> Director, Oracle Fusion Middleware and Web Services Standards	+1(650) 
> 506-1975
> Consulting Member Technical Staff           			
> 500 Oracle Parkway, M/ 
> S 4OP9
> Oracle							
> 	Redwood Shores, CA 94065
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all 
> your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php 
> 
> 


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