[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
The specification change request and errata process is intended to = address defects found in a specification. It may NOT be used to add new functionality or substantively change existing functionality except as minimally required to effect a fix.=20 When an error is discovered in one of the UDDI specifications or related documents, the person discovering it should post to the uddi-spec = mailing list if he/she is a UDDI Spec TC member or to the public = uddi-spec-comment mailing list if they are not. In the latter case, debate on the uddi-spec-comment mailing list shall be sufficient to determine that the problem is valid and requires attention by the TC. The TC shall = consider the issue, debate it, and reach agreement that it justifies a change to = the specification. Such debate should occur on the uddi-spec mailing list.. When a consensus appears to be reached, the TC Chairs will inform the = person having made the discovery to prepare a Specification Change Request (CR) = and submit it, or in the case where the individual is not a member of the = TC, the TC Chairs will delegate this responsibility to a TC member; IPR = rules should be reiterated at that time by the TC Chairs. Luc Cl=E9ment Microsoft Co-chair, OASIS UDDI Spec TC=20 -----Original Message----- From: Daniel Feygin [ <mailto:feygin@unitspace.com> mailto:feygin@unitspace.com] Sent: Wednesday, October 08, 2003 08:44 To: 'UDDI Spec TC' Subject: RE: [uddi-spec] Restructuring the UDDI Schemas and WSDL Why wait till V4 to do this? If it's just clean-up then we can slip = this into 3.0.1 (or 3.1?). Daniel > -----Original Message----- > From: John Colgrave [ <mailto:colgrave@hursley.ibm.com> mailto:colgrave@hursley.ibm.com] > Sent: Wednesday, October 08, 2003 7:30 PM > To: 'UDDI Spec TC' > Subject: [uddi-spec] Restructuring the UDDI Schemas and WSDL > > > This is not related to the code-generation issue. > > I have been looking at restructuring the UDDI schemas and WSDL to make > it clearer what is the core registry content and what is related to > one or more APIs. > > I have started to put together an initial "V4" description of UDDI > which is based on the V3 description but with an OASIS-style namespace > and restructured to factor out elements into the appropriate place. > > I have a four-tier structure at the moment. > > The foundation is uddi_v4_im.xsd (the "im" stands for "information > model") which is basically tModel, businessEntity and everything that > those elements reference. > I have adopted a style of using local anonymous types wherever > possible and the combination of adopting this style and omitting those > elements and types that are only used in the definition of one or more > APIs results in a core schema that is around one third the size of > uddi_v3.xsd. > > The next layer up is uddi_v4_common.wsdl which contains some types > that are used in more than one API, and corresponding message > definitions. This file does a schema import of uddi_v4_im.xsd within > the types section. > > The next layer up is a set of portType WSDL files, I have only done > uddi_v4_publish_portType.wsdl. Each of these portType files has a > types section that defines types unique to that portType, a > corresponding set of message definitions for those types, and then a > single portType. Each file does a wsdl import of uddi_v4_common.wsdl > and a schema import of uddi_v4_im.xsd within the types section. > > The final layer is a set of binding WSDL files, I have only done > uddi_v4_publish_binding.wsdl. These are pretty much the same as the > V3 ones. Each binding WSDL file does a wsdl import of the > corresponding portType WSDL file and defines a single SOAP/HTTP > binding for that portType. > > I know it is difficult to visualize this without seeing it so if there > is sufficient interest I will put together a "4.0.1" > version of what I have done based on the final 3.0.1 schemas and make > that available. > > John Colgrave > 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> http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members /leave_workgroup.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_wor= kgr oup.php> http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_work= gro up.php. ------=_NextPart_000_03F5_01C3924D.5C2F59D0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <TITLE>Message</TITLE> <META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR></HEAD> <BODY> <DIV> <DIV><FONT face=3DTahoma size=3D2> <DIV> <DIV><SPAN class=3D240370408-14102003><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D479151408-14102003>Luc,</SPAN></FONT></SPAN></DIV> <DIV><FONT face=3DArial color=3D#0000ff></FONT> </DIV> <DIV><SPAN class=3D240370408-14102003><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D479151408-14102003>John's proposed schema restructuring does not = add new=20 functionality or alter existing behavior. If it also addresses a = defect,=20 then it appears to fully qualify for a CR. I'm not sure what = problems he=20 was trying to address with the restructuring - perhaps instrumentation=20 appeasement is one. I don't know if changing to OASIS-style = namespace is=20 required (or appropriate) for V3 - this could be another issue he was = trying to=20 address.</SPAN></FONT></SPAN></DIV> <DIV><FONT face=3DArial color=3D#0000ff></FONT> </DIV> <DIV><SPAN class=3D240370408-14102003><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D479151408-14102003>Daniel<BR></SPAN></FONT></SPAN></DIV> <DIV><SPAN class=3D240370408-14102003><SPAN=20 class=3D479151408-14102003></SPAN></SPAN> </DIV></DIV>-----Original = Message-----<BR><B>From:</B> Luc Clement = [mailto:lclement@windows.microsoft.com]=20 <BR><B>Sent:</B> Sunday, October 12, 2003 3:41 AM<BR><B>To:</B> Daniel = Feygin;=20 UDDI Spec TC<BR><B>Subject:</B> RE: [uddi-spec] Restructuring the UDDI = Schemas=20 and WSDL<BR><BR></FONT></DIV></DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px = solid; MARGIN-RIGHT: 0px"><!-- Converted from text/plain format --> <P><FONT size=3D2><FONT face=3D"Franklin Gothic Book">Please, let's = exercise=20 constraint. This type of change should not be considered lightly and = certainly=20 does not qualify for inclusion in 3.0.1. Daniel I'm sure that you = really=20 didn't mean to "slip" it in .... sounds like a slip of the=20 tougue.</FONT></FONT></P> <P><FONT size=3D2><FONT face=3D"Franklin Gothic Book">Let me remind = all of the=20 "Specification Change Request and Errata Process" we've adopted (<A=20 = href=3D"http://www.oasis-open.org/committees/uddi-spec/doc/process/uddi-s= pec-tc-process-20021212.htm#_Toc27444262">http://www.oasis-open.org/commi= ttees/uddi-spec/doc/process/uddi-spec-tc-process-20021212.htm#_Toc2744426= 2</A>):</FONT></FONT></P> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <P><FONT size=3D2><FONT face=3D"Franklin Gothic Book"=20 color=3D#000080><STRONG><EM>1.6 Specification Change Request and = Errata=20 Process</EM></STRONG></FONT></FONT></P> <P><FONT size=3D2><FONT face=3D"Franklin Gothic Book"><EM>From time = to time,=20 <U>errors, inconsistencies or ambiguities</U> will be discovered in = a UDDI=20 TC Specification or UDDI Standard based upon ongoing experience with = the=20 specification by those implementing it. Such feedback is essential = to=20 improving the quality of these documents. <BR><BR>The = specification=20 change request and errata process is intended to <U>address = defects</U>=20 found in a specification. <U>It may NOT be used to add new=20 functionality or substantively change existing functionality except = as=20 minimally required to effect a fix</U>. <BR><BR>When an error = is=20 discovered in one of the UDDI specifications or related documents, = the=20 person discovering it should post to the uddi-spec mailing list if = he/she is=20 a UDDI Spec TC member or to the public uddi-spec-comment mailing = list if=20 they are not. In the latter case, debate on the = uddi-spec-comment=20 mailing list shall be sufficient to determine that the problem is = valid and=20 requires attention by the TC. The TC shall consider the issue, = debate=20 it, and reach agreement that it justifies a change to the=20 specification. Such debate should occur on the uddi-spec = mailing=20 list..<BR><BR>When a consensus appears to be reached, the TC Chairs = will=20 inform the person having made the discovery to prepare a = Specification=20 Change Request (CR) and submit it, or in the case where the = individual is=20 not a member of the TC, the TC Chairs will delegate this = responsibility to a=20 TC member; IPR rules should be reiterated at that time by the TC=20 Chairs.</EM></FONT></FONT></P></BLOCKQUOTE> <P dir=3Dltr><FONT size=3D2><FONT face=3D"Franklin Gothic Book"><FONT=20 face=3D"Franklin Gothic Book" size=3D2>Luc = Cl=E9ment<BR>Microsoft<BR>Co-chair, OASIS=20 UDDI Spec TC </FONT></P> <P dir=3Dltr><FONT color=3D#0000ff></FONT><BR>-----Original = Message-----<BR>From:=20 Daniel Feygin [</FONT><A href=3D"mailto:feygin@unitspace.com"><FONT=20 face=3D"Franklin Gothic = Book">mailto:feygin@unitspace.com</FONT></A><FONT=20 face=3D"Franklin Gothic Book">]<BR>Sent: Wednesday, October 08, 2003=20 08:44<BR>To: 'UDDI Spec TC'<BR>Subject: RE: [uddi-spec] Restructuring = the UDDI=20 Schemas and WSDL<BR><BR>Why wait till V4 to do this? If it's = just=20 clean-up then we can slip this into 3.0.1 (or = 3.1?).<BR><BR>Daniel<BR><BR>>=20 -----Original Message-----<BR>> From: John Colgrave [</FONT><A=20 href=3D"mailto:colgrave@hursley.ibm.com"><FONT=20 face=3D"Franklin Gothic = Book">mailto:colgrave@hursley.ibm.com</FONT></A><FONT=20 face=3D"Franklin Gothic Book">]<BR>> Sent: Wednesday, October 08, = 2003 7:30=20 PM<BR>> To: 'UDDI Spec TC'<BR>> Subject: [uddi-spec] = Restructuring the=20 UDDI Schemas and WSDL<BR>><BR>><BR>> This is not related to = the=20 code-generation issue.<BR>><BR>> I have been looking at = restructuring=20 the UDDI schemas and WSDL to make<BR>> it clearer what is the core = registry=20 content and what is related to<BR>> one or more = APIs.<BR>><BR>> I=20 have started to put together an initial "V4" description of = UDDI<BR>> which=20 is based on the V3 description but with an OASIS-style = namespace<BR>> and=20 restructured to factor out elements into the appropriate=20 place.<BR>><BR>> I have a four-tier structure at the=20 moment.<BR>><BR>> The foundation is uddi_v4_im.xsd (the "im" = stands for=20 "information<BR>> model") which is basically tModel, businessEntity = and=20 everything that<BR>> those elements reference.<BR>> I have = adopted a=20 style of using local anonymous types wherever<BR>> possible and the = combination of adopting this style and omitting those<BR>> elements = and=20 types that are only used in the definition of one or more<BR>> APIs = results=20 in a core schema that is around one third the size of<BR>>=20 uddi_v3.xsd.<BR>><BR>> The next layer up is uddi_v4_common.wsdl = which=20 contains some types<BR>> that are used in more than one API, and=20 corresponding message<BR>> definitions. This file does a = schema=20 import of uddi_v4_im.xsd within<BR>> the types = section.<BR>><BR>> The=20 next layer up is a set of portType WSDL files, I have only = done<BR>>=20 uddi_v4_publish_portType.wsdl. Each of these portType files has=20 a<BR>> types section that defines types unique to that portType, = a<BR>>=20 corresponding set of message definitions for those types, and then = a<BR>>=20 single portType. Each file does a wsdl import of=20 uddi_v4_common.wsdl<BR>> and a schema import of uddi_v4_im.xsd = within the=20 types section.<BR>><BR>> The final layer is a set of binding = WSDL files,=20 I have only done<BR>> uddi_v4_publish_binding.wsdl. These are = pretty=20 much the same as the<BR>> V3 ones. Each binding WSDL file = does a wsdl=20 import of the<BR>> corresponding portType WSDL file and defines a = single=20 SOAP/HTTP<BR>> binding for that portType.<BR>><BR>> I know it = is=20 difficult to visualize this without seeing it so if there<BR>> is=20 sufficient interest I will put together a "4.0.1"<BR>> version of = what I=20 have done based on the final 3.0.1 schemas and make<BR>> that=20 available.<BR>><BR>> John Colgrave<BR>>=20 IBM<BR>><BR>><BR>><BR>><BR>> To unsubscribe from this = mailing=20 list (and be removed from the roster<BR>> of the OASIS TC), go = to<BR>>=20 </FONT><A=20 = href=3D"http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members"><= FONT=20 face=3D"Franklin Gothic = Book">http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members</FON= T></A><BR><FONT=20 face=3D"Franklin Gothic Book">/leave_workgroup.php.<BR><BR><BR><BR>To=20 unsubscribe from this mailing list (and be removed from the roster of = the=20 OASIS TC), go to </FONT><A=20 = href=3D"http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/le= ave_workgroup.php"><FONT=20 face=3D"Franklin Gothic = Book">http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leav= e_workgroup.php</FONT></A><FONT=20 face=3D"Franklin Gothic = Book">.<BR><BR><BR></P></BLOCKQUOTE></FONT></FONT></BODY></HTML> ------=_NextPart_000_03F5_01C3924D.5C2F59D0--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]