[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [uddi-spec] RE: [wsrp-pfb] UDDI tech note draft-08
Re: useType John: You're absolutely correct wrt the use of the wsdlDeployment tModel - it isn't strictly compatible with its intended use. The WSDL Address tModel [1] is probably what we want here but then the TN needs to add a tModelInstanceInfo reference to this tModel; we should discuss this off-line. Richard: for the moment, it's probably best for you to hold off adding a footnote wrt to the useType attribute's use in v3. I sense that we'll come to agreement on the use of "other". Re: entityKeyValues John: you are correct that a legacy v2 registry will not implement the tModel behaviour; however a v3 registry supporting v2 clients would. That said as long as the tModel is available in a v2 registry then a consistent mapping to v2 and v3 will be in place that can be enforced by a v3 registry (supporting v2 and v3 clients) if and when one is ever used. In order for this TN to be implemented, it will need to ensure that the registry (either v2 or v3) holds a base set of tModel it leverages; I suggest that the TN leverage the entityKeyValues tModel (thus add it to its base set) to ensure at leastnv3 nodes supporting v2/v3 clients will be in a position to enforce the type of reference made. Re: predetermined v2 keys John, thanks for brining up this point. I think that where the WSPR TC is heading is just that: the necessity for bootstrapping. If this isn't clear, then we should walk them through the implications (which you've addressed largely). Otherwise, in the case of a v3 node, the necessity for requiring a bootstrap is significantly diminished (if required at all - I'd have to think about that some more). [1] http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v 200-20031104.htm#_Toc58391188 Luc Clément Systinet -----Original Message----- From: John Colgrave [mailto:colgrave@hursley.ibm.com] Sent: Friday, July 09, 2004 05:32 To: 'Richard Jacob'; 'Luc Clement' Cc: uddi-spec@lists.oasis-open.org; wsrp-pfb@lists.oasis-open.org Subject: RE: [uddi-spec] RE: [wsrp-pfb] UDDI tech note draft-08 As the WSDL in UDDI V2.0 TN says, the use of the V3 wsdlDeployment feature is not compatible with the WSDL/UDDI TN, and therefore it is not compatible with the mapping in the WSRP document as that uses at least part of the UDDI/WSDL TN mapping. The V3 keys shown for the canonical tModels are not valid UDDI V3 keys. They need to begin with "uddi:". I think it unlikely that a "legacy V2" registry will implement support for the "Entity Key Values" category system so I think it is reasonable that you only use that in a registry that supports V3. This is separate to the issue of predetermined V2 keys. On the issue of predetermined V2 keys, I am assuming that you will publish the canonical tModels you define using the process defined by the UDDI TC and this will ensure that the tModels are published to the UDDI Business Registry with the correct V3 and V2 keys. I think the assumption is that UDDI registry products will provide support for tModels that are approved by the UDDI TC, including their predetermined key, even if they do not have a general capability for introducing content with predetermined keys. There will inevitably be a delay however so if a registry is used that does not have such a general capability then applications will have to go through a bootstrapping procedure to query the various tModels to discover the keys to use in the particular registry they are targeting. John Colgrave IBM > -----Original Message----- > From: Richard Jacob [mailto:richard.jacob@de.ibm.com] > Sent: 09 July 2004 12:53 > To: Luc Clement > Cc: uddi-spec@lists.oasis-open.org; wsrp-pfb@lists.oasis-open.org > Subject: [uddi-spec] RE: [wsrp-pfb] UDDI tech note draft-08 > > > > > > Luc, > > thanks for your valueable input. > I've added your suggestion to our next revision (draft-08). > Our TC is definitly interested in a UDDI TC review and we appreciate > the UDDI TC's comments. > We are going to start our first TC review in a few days. > I will post an additional message to your list asking for comments and > providing the links once we're set and ready for review. > > Following some preliminary questions regarding your input: > How does the usage of the useType attribute relate to the WSDL in UDDI > V2.0 technical note, Appendix A. > We had the note concerning V3 wsdlDeployment usage in a previous > version but haven't been sure about the compatibility to the tech note. > > Could the use of the entityKeyValues tModel affect private UDDI > registry usage, given the fact that "legacy" V2 registry may not > provide this tModel? > > Or to be more general: how do you deal with "legacy" registries where > tModels with the predefined keys can not be injected, i.e. the > registry would assign new keys. > I'm asking because this might become also an interoperability issue > with our tech note and I'm wondering if we need to add some guidance > to our tech note. > How do you deal with it? > > 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:richard.jacob@de.ibm.com > > > > "Luc Clement" > <luc.clement@syst > inet.com> To > Richard Jacob/Germany/IBM@IBMDE, > 07/08/2004 07:46 <wsrp-pfb@lists.oasis-open.org> > PM cc > <uddi-spec@lists.oasis-open.org> > Subject > RE: [wsrp-pfb] UDDI tech note > draft-08 > > > > > > > > > > > Richard, > > I commend your TC for such a nice job of mapping WSRP onto UDDI. I'd > like to offer some brief comments on the TN (albeit these are based on > draft 7 as I haven't had a chance to review draft 8 yet). > > A. useType attribute on accessPoint. > > > I like the fact that the TN isolates itself from v2 and v3 version > issues but would like to propose that you note the following wrt the > use of "useType" in the context of UDDI v3. The TC anticipated the use > of a WSDL as an access point and thus provided support for it in UDDI > v3 (which by the way maps to "other" in v2 as you've chosen). Section > 3.5.2.1 accessPoint of the v3 spec [1] describes the following useType: > "wsdlDeployment: designates that the accessPoint points to a remotely > hosted WSDL document that already contains the necessary binding > information, including the actual service endpoint." > > I think it would be worth mentioning this as a footnote in the TN > > B. Categorization of the > urn:oasis:names:tc:wsrp:wspr_producer_service_reference tModel > > > I recommend that his tModel be categorized with the > uddi-org:entityKeyValues category system to enforce the reference to a > businessService. For more information on this tModel - please see > Section > 11.1.9 UDDI “Entity Key Values” Category System of the v3 spec [1]. > > > I think that careful review of version 8 and future drafts may uncover > additional small issues and to this end, I recommend that the UDDI > Spec TC review this TN though we may want to do so once you get closer > to completing your work. I've copied the UDDI Spec TC as a heads up. > > > [1] http://uddi.org/pubs/uddi_v3.htm > > Regards, > > Luc Clément > Secretary, OASIS UDDI Spec TC > Systinet Corporation > Tel: +1.617.395.6798 > > -----Original Message----- > From: Richard Jacob [mailto:richard.jacob@de.ibm.com] > Sent: Thursday, July 08, 2004 08:04 > To: wsrp-pfb@lists.oasis-open.org > Subject: [wsrp-pfb] UDDI tech note draft-08 > > > > > > Hi all, > > I just post these to the list for now for a final SC review. > As discussed please review the TN and let me know of intended changes. > I espacially added the appendix A-E, added clarification on Portlet > publishing (tModelKey redundancy in case of UDDI V3, Producer service > reference) and revised the suggested editorial changes. > Would be great if you could finish your review by end of monday (no > matter what timezone :-) ). > After that we can enter TC review. > > (See attached file: wsrp-pfb-uddi-tn-draft-08.doc)(See attached file: > wsrp-pfb-uddi-tn-draft-08.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:richard.jacob@de.ibm.com [attachment > "wsrp-pfb-uddi-tn-draft-08.doc" deleted by Richard Jacob/Germany/IBM]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]