To be consistent, I believe the "name"
element of the tModel should by a URN format and use - characters and the
tModelKey should be URI formatted with a domain part and it should use
. for name part seperators.
In order to avoid mistakes, it's probably
best to always list both.
Regards.
Andrew Hately
IBM Software Group, Emerging Technologies
email:
phone: (512) 838-2866
"Steve Capell"
<>
11/08/2004 09:37 PM
To
"'Luc Clement'"
<>, <>
cc
Subject
RE: [uddi-spec] FW: [wsrp-pfb]
PFB technical notes ready for public review
Just a little point...
We have had alot of little "issues" in deployment becuase of
inconsistency
about the use of "." vs "-" in the domain name part
of tModel keys. URN
convention says a domain name should be of the form "uddi-org"
whereas
typical URLs are of the form "uddi.org". I notice that
most canonical
tModels use the urn form "uddi-org:...". Now you are proposing
a key
generator of the form "oasis-open.org". Should it be "oasis-open-org"?
Inconsistency with regard to these little issues of colons vs slashes,
dots
vs dashes, etc wreak havoc when it comes to deployment... :)
Regards
Steve Capell
Red Wahoo Pty Ltd
+61 410 437854
-----Original Message-----
From: Luc Clement [mailto:]
Sent: Tuesday, 9 November 2004 12:47 PM
To:
Subject: [uddi-spec] FW: [wsrp-pfb] PFB technical notes ready for public
review
FYI,
A number of TCs are requiring the assignment of key spaces. Find below
a
thread of discussion whereby it has been discussed and resolve that the
following convention will be used "uddi:oasis-open.org:owner"
(where owner
is the TC name) for the assignment of key spaces for TCs.
There are a few details to work out - comments welcome.
Luc
Luc Cl幦ent
Co-Chair OASIS UDDI Spec TC
Systinet
Tel: +1.617.768.4268
www.systinet.com
-----Original Message-----
From: Richard Jacob [mailto:]
Sent: Wednesday, November 03, 2004 06:21
To: Luc Clement
Cc: ; 'Andrew Hately'; 'James Bryce Clark'; 'John
Colgrave'; ; 'Rich Thompson'; ;
;
Subject: RE: [wsrp-pfb] PFB technical notes ready for public review
Luc,
great that we agree here. Sounds like we have a convention for OASIS
partitions in UDDI.
This would also fit well with our tech note.
I also agree that we shouldn't stuck this only in our committees.
I suppose you need to drive this through the UDDI TC to get the final
approval for the convention?
I would suggest to add a paragraph about the convention into the OASIS
Artifact Naming Guidelines (in section 6).
Tim Moses and Bill Cox are the editors, so best thing would be to get in
touch with them (I copied Bill).
Could the UDDI TC propose a paragraph here?
Mit freundlichen Gruessen / best regards,
Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development WSRP Standardization
Technical Lead
Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888
Email: mailto:
"Luc Clement"
<Luc.Clement@syst
inet.com>
To
Richard
Jacob/Germany/IBM@IBMDE,
11/02/2004 10:07
"'Rich Thompson'"
PM
<>
cc
<>,
<>,
<>,
"'Andrew
Hately'"
<>, John
Colgrave/UK/IBM@IBMGB,
<>,
"'James
Bryce Clark'"
<>
Subject
RE: [wsrp-pfb]
PFB technical notes
ready for
public review
Richard/Rich:
I'm fine with the convention you propose. How do we get buy-in from the
TAB
and add this to the naming guidelines? What I don't want to happen is for
this to get "stuck in committee".
Luc
-----Original Message-----
From: Richard Jacob [mailto:]
Sent: Tuesday, November 02, 2004 09:40
To: Rich Thompson
Cc: Luc Clement; ; ;
; Andrew Hately; John Colgrave
Subject: RE: [wsrp-pfb] PFB technical notes ready for public review
Thanks Rich,
in this case I would stick to section 6.1.2 (URLs).
We can't use URN in the partititon names since this would contradict the
seperator used for partitions in UDDI.
Therefor I would choose the URL-like syntax:
"uddi:oasis-open.org:owner" where owner is the TC name. (section
7.3 of this
documents has some similar examples).
To overcome the limitation of having OASIS their own tModels we could have
a
"oasis" partition similar to the other TCs' partitions.
So I would propose to:
1. register uddi:oasis-open.org:keygenerator 2. register
uddi:oasis-open.org:oasis:keygenerator (if OASIS feels they need it at
that
time) 3. register uddi:oasis-open.org:uddi-spec:keygenerator
4. register uddi:oasis-open.org:wsrp:keygenerator
Btw. seems we lost some people on this thread, I'll add them to cc: again
Mit freundlichen Gruessen / best regards,
Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development WSRP Standardization
Technical Lead
Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888
Email: mailto:
Rich Thompson
<
m>
To
Richard
Jacob/Germany/IBM@IBMDE
11/02/2004 03:17
cc
PM
"Luc Clement"
<>
Subject
RE: [wsrp-pfb]
PFB technical notes
ready for
public review
Sure ... I have attached the proposed guidelines (draft of what the TAB
SC
is working on). As you noted, this is consistent with the urn format we
were
given for use in our wsdl and not completely consistent with the url format
used elsewhere.
Rich Thompson
OASIS WSRP TC Chair
IBM T.J. Watson Research Center / Yorktown Heights, NY
Phone: (914) 945-3225 / (203) 445-0384 email:
Richard Jacob
<>
To
11/02/2004 08:54 AM
Rich
Thompson/Watson/IBM@IBMUS
cc
"Luc Clement"
<>
Subject
RE: [wsrp-pfb] PFB technical
notes ready for public review
I must admin, I haven't found the conventions anywhere (perhaps because
of
my "lax" search mode).
Could you point me to such conventions?
I know that we use "urn:oasis:names:tc:wsrp" as the URN namespace
which was
approved by OASIS.
However the OASIS site used "www.oasis-open.org/committees/TCname"
for the
documents we stored to have constant URLs (for example our WSDLs).
Mit freundlichen Gruessen / best regards,
Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development WSRP Standardization
Technical Lead
Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888
Email: mailto:
Rich Thompson
<
m>
To
Richard Jacob/Germany/IBM@IBMDE
11/02/2004 02:30
cc
PM
"Luc Clement"
<>
Subject
RE: [wsrp-pfb]
PFB technical notes
ready for
public review
I would note that the proposed (& I think current) guidelines use "tc"
rather than "committees".
Rich Thompson
OASIS WSRP TC Chair
IBM T.J. Watson Research Center / Yorktown Heights, NY
Phone: (914) 945-3225 / (203) 445-0384 email:
Richard Jacob
<richard.jacob
@de.ibm.com>
To
"Luc Clement" <>,
11/02/2004
08:08 AM
cc
"'Von Riegen, Claus'"
<>, Andrew
Hately/Austin/IBM@IBMUS, "'John
Colgrave'"
<>, "'Rob
Kochman'"
<>, "'Rogers,
Tony'"
<>
Subject
RE: [wsrp-pfb] PFB technical notes ready
for public review
Luc,
thanks for working this out. I copied the wsrp-pfb SC on this.
I agree on this appoach, sounds good to me.
There is one thing to notice:
We talked about the oasis partition in the UBR a while ago with John and
Claus (afair) and by that time we came out with uddi:oasis-open.org:<tc
name> as the partititons.
We're now adding the "committees" subpartition.
In general I agree on following the oasis convention (this is used on the
OASIS-Site only, right?).
However, do we need the "committees" subpartition at all?
The only advantage I see it brings us is the fact that keys having the
same
name as a tc might be registered in the oasis-open.org partition.
I see that having the subcommittees partition is a little bit cleaner.
In our current UDDI TN we have chosen the first convention for our keys:
"uddi:oasis-open.org:wsrp".
If you intend to introduce the "committees" subpartition, please
let us now,
since we then need to change the V3 keys in our tech note (and thus
regenerate the derived V2 keys).
We intended to accept and finalize the tech note on our F2F next week.
The change, or at least the change request for this must be done prior
to
this.
To be clear: I (and hopefully speaking on behalf of our SC) am happy with
either convention, but it is important for us timing wise to know which
direction you intend to go as soon as possible.
On the timing: when do you think we will be ready to go and have the tModel
keys in place?
You can find all the keys we intend to register in our tech note:
http://www.oasis-open.org/apps/org/workgroup/wsrp/wsrp-pfb/download.php/9532
/wsrp-pfb-uddi-tn-1.0-draft-11.pdf
Mit freundlichen Gruessen / best regards,
Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development WSRP Standardization
Technical Lead
Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888
Email: mailto:
"Luc Clement"
<Luc.Clement@syst
inet.com>
To
Richard Jacob/Germany/IBM@IBMDE
10/30/2004 05:25
cc
PM
"'Rogers, Tony'"
<>,
John
Colgrave/UK/IBM@IBMGB,
"'Von
Riegen, Claus'"
<>,
"'Rob
Kochman'"
<>,
"'Andrew Hately'"
<>
Subject
RE: [wsrp-pfb]
PFB technical notes
ready for public
review
Richard,
See attached email. Sorry for the delay - I hope to solidify this plan
shortly. Once we agree on the plan (per attachement) you and I should
approach OASIS to get this "blessed". Are you ok with this approach?
Once this is one, we can ask the elected UBR operator to register the
specific set of keys you need. Could you please provide me with that list
of
keys?
Luc
Luc Cl幦ent
Co-Chair OASIS UDDI Spec TC
Systinet
Tel: +1.617.768.4268
www.systinet.com
----- Message from "Luc Clement" <>
on Sat, 30 Oct
2004 11:21:47 -0400 -----
To: "'John Colgrave'" <>, "'Andrew
Hately'"
<>, "'Von Riegen, Claus'"
<>, "'Rob Kochman'" <>
cc: "'Rogers, Tony'" <>
Sub RE: OASIS keyGenerator
jec
t:
John:
This is how I'd like to deal with this - basically, we follow your
suggestion:
1. we register a key generator for oasis-open.org; register
a key
generators for "committees"; and register key generators
for each TC
as they need it. To start with we would create keys for the
following
TC:
UDDI Spec TC
WSRP
I propose the following name/address
convention based on
current the current OASIS convention:
uddi:oasis-open.org:committees:<tc
identifier>
2. To start with, we would register:
1. uddi:oasis-open.org:keygenerator
(derived key:
uuid:966812b7-f798-3cd0-bc23-a946d36270d6)
2. uddi:oasis-open.org:committees:keygenerator
(derived key:
uuid:61c808e5-8159-348a-9ab1-b0df93de48d3)
3. uddi:oasis-open.org:committees:uddi-spec:keygenerator
(derived key: uuid:6852eca3-bcb2-3f32-b168-ca6c83d848c8)
4. uddi:oasis-open.org:committees:wsrp:keygenerator
(derived
key: uuid:c906ae88-26d0-33ec-9a41-861a4f35d108)
Based on this I've prepared the list
of keygenerator tModels
that we should register - see attached.
3. We get one of the operators to register the following
tModels - I
propose IBM but will let Claus/Andrew/Rob to figure out who
should
publish (and maintain the source file).
4. We post these keygenerators at http://uddi.org/tmodels.html
Once we
settle on this, we'll get approval from the TC and inform OASIS of the
plan.
Luc
From: John Colgrave [mailto:]
Sent: Tuesday, August 17, 2004 09:21
To:
Subject: OASIS keyGenerator
Luc,
There was an e-mail discussion about six months ago regarding registering
a
keyGenerator for OASIS, with a key of uddi:oasis-open.org:keyGenerator.
Has any progress been made with this? The WSRP folks are getting
close to
defining their keys and I imagine we will have to have this OASIS
keyGenerator tModel in place first.
Regards,
John
--------------------------------------------------
John Colgrave
Architect, IBM WebSphere UDDI Registry[attachment
"OASIS-keyGenerator-tModels.xml" deleted by Richard Jacob/Germany/IBM]
To unsubscribe from this mailing list (and be removed from the roster of
the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsrp-pfb/members/leave_workgrou
p.php
.
[attachment "tab-artifact_naming_guidelines-1.0-spec-wd-09-diff.doc"
deleted by Richard Jacob/Germany/IBM]
[attachment "tab-artifact_naming_guidelines-1.0-spec-wd-09-diff.doc"
deleted by Richard Jacob/Germany/IBM]
To unsubscribe from this mailing list (and be removed from the roster of
the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgro
up.php.
To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgroup.php.
