[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-assembly] ISSUE 254: Names of channels should allow "/",should be declared as URIs....
On 2/1/2011 6:11 AM, Peter Niblett wrote: > Eric > > In path oriented addressing schemes (like files in a hierarchical file > systems), the last (leaf) part of the path is often the name of the > object itself, while the rest of the path describes the context in which > it is situated (and also disambiguates multiple objects that have the > same name). So, a bit like Martin says, I am wondering what you are > asking for is actually a way to define some kind of formal relationship > between channels, and that it would be better to tackle that question, > rather than allow a syntax which could allow some people to inter a > relationship by convention. > > Also we say that you can reference a channel binding by taking the URI > of the channel and appending /bindingname. So if you allow global > channels to have / in their channel names, then you could have a channel > called //A with a binding called B and also a channel called //A/B - > both of which would have the same URI. I thought we got rid of this, now that we have restricted channels to a single binding. -Anish -- > > Regards > > Peter Niblett > IBM Senior Technical Staff Member > Member of the IBM Academy of Technology > +44 1962 815055 > +44 7825 657662 (mobile) > > > > > From: Martin Chapman <MARTIN.CHAPMAN@ORACLE.COM> > To: OASIS SCA Assembly <sca-assembly@lists.oasis-open.org> > Date: 01/02/2011 13:48 > Subject: [sca-assembly] ISSUE 254: Names of channels should allow "/", > should be declared as URIs.... > ------------------------------------------------------------------------ > > > > The only concern I have about this issue/proposal is that its seems to > imply that there is a relationship between global channels that is > somehow understood by the SCA Runtime. As currently defined there are no > architectural relationships between global channels, which is why I > think we originally settled on a NCname. Changing this to a URI might > allow a user to imply some relationship between global channels, but an > SCA Runtime will not be aware of such relationships. > > Martin. > > *From:* Mike Edwards [mailto:mike_edwards@uk.ibm.com] * > Sent:* 31 January 2011 22:50* > To:* OASIS SCA Assembly* > Subject:* Re: [sca-assembly] NEW ISSUE: (1.2) Names of channels should > allow "/", should be declared as URIs.... > > > Logged as _http://www.osoa.org/jira/browse/ASSEMBLY-! 254_ > <http://www.osoa.org/jira/browse/ASSEMBLY-254> > > Yours, Mike > > ------------------------------------------------------------------------ > Dr Mike Edwards Mail Point 146, Hursley Park > STSM Winchester, Hants SO21 2JN > SCA & Services Standards United Kingdom > Co-Chair OASIS SCA Assembly TC > IBM Software Group > Phone: +44-1962 818014 > Mobile: +44-7802-467431 (274097) > e-mail: mike_edwards@uk.ibm.com > > > > > From: Eric Johnson <eric@tibco.com> > To: OASIS SCA Assembly <sca-assembly@lists.oasis-open.org> > Date: 31/01/2011 18:24 > Subject: [sca-assembly] NEW ISSUE: (1.2) Names of channels should allow > "/", should be declared as URIs.... > > > > ------------------------------------------------------------------------ > > > > > Title: Names of channels should allow "/" character, and should be > declared as URIs.... > > Target: Assembly 1.2 WD 03 > > Description: > > As declared in section 5.7, the name of a channel is defined as an > NCName. However, NCNames do not allow for "/". > > All references to channels use the type "xs:anyURI", but ironically, we > don't allow for "/" in the names of channels. Further, there's > potentially a discrepancy between a URI and NCNames. To be consistent, > we should use xs:anyURI for both the definition & the references. > > While this capability may not add much for private/local channels, for > the purposes! of global domain channels, this facilitates a natural > hierarchy of global domain channels following the well-accepted practice > of using "/" to indicate hierarchy. > > Proposal: > > Change the type of the "@name" attribute on channel to be of type > xs:anyURI. Note the caveat that this must conform to the "path-rootless" > production from part 3.3 of RFC 3986. In other words, it cannot start > with a scheme, nor a "/". > > -Eric. > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to 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/ > > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to 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/ > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]