[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Locations for storing ebXML Messaging Service related schemas
Cool! Thanks Jeffrey. Chris Jeffrey Lomas wrote: > > Arvola, > I've set up the directory: > http://www.oasis-open.org/committees/ebxml-msg/schema/ > > Feel free to contact if ever you have need. > > Regards, > Jeffrey Lomas > Manager-Technology Services > OASIS > > Arvola Chan wrote: > > > Hi Jeffrey: > > > > Following Chris' recommendations, I like to request the attachments in this > > message be placed under: > > > > - > > http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-00.xs > > d > > > > - http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd > > > > - http://www.oasis-open.org/committees/ebxml-msg/schema/xlink.xsd > > > > - http://www.oasis-open.org/committees/ebxml-msg/schema/xml_lang.xsd > > > > - > > http://www.oasis-open.org/committees/ebxml-msg/schema/xmldsig-core-schema.xs > > d > > > > Colleen: > > > > The expectation is that when we finally publish the 1.1 version of the ebMS > > spec, the message header schema will be published as > > > > http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-1_1.xsd > > > > and the references from the spec body will have to be updated accordingly. > > > > In the mean time, the draft spec has to be updated to refer to > > > > http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-00.xs > > d > > > > as both the target namespace (see section 8.2.4) and the schema location (in > > the examples perhaps). > > > > Thanks, > > -Arvola > > > > -----Original Message----- > > From: christopher ferris <chris.ferris@Sun.COM> > > To: Dale Moberg <dmoberg@cyclonecommerce.com> > > Cc: Christopher Ferris <chris.ferris@east.sun.com>; Farrukh Najmi > > <najmi@east.sun.com>; Jeffrey Lomas <jeff.lomas@oasis-open.org>; Arvola Chan > > <arvola@tibco.com>; Karl Best <karl.best@oasis-open.org>; ian.c.jones@bt.com > > <ian.c.jones@bt.com> > > Date: Thursday, September 27, 2001 8:05 AM > > Subject: Re: Locations for storing ebXML Messaging Service related schemas > > > > >All, > > > > > >I just peeked at what the Security Services were doing. > > >They've chosen to use a namespace name that maps to > > >a sub-directory under their TC's URL which doubles > > >as the schemaLocation. > > > > > >They've also been using a versioning-scheme in the > > >name (appending a number representing the iteration > > >of the schema document). > > > > > >e.g. > > > > > >http://oasis-open.org/committees/security/docs/draft-sstc-schema-protocol-1 > > 6.xsd > > > > > >It isn't clear if their intent is to end up with something like: > > > > > >http://oasis-open.org/committees/security/docs/sstc-schema-protocol-1_0.xsd > > > > > >when all is said and done or if they plan something else. > > > > > >Time was when I was very much against use of a namespace for versioning, > > >which is why I wanted to have the version attribute for much the > > >same reason that XSLT has one). That said, I still am much in favor of > > preserving > > >the version attribute, as it is much simpler to get at than parsing > > >some namespace string or requiring that some mapping between namespace > > >name and version be performed. > > > > > >However, I think that I have come to learn that using a different > > >namespace name for iterations of a schema can be very important to > > >ensuring that you know what you're dealing with. > > > > > >What I'm thinking is that the version attribute should be populated > > >with the version (1.0, 1.1, 2.0, etc.) while we use a different > > "versioning" > > >scheme for the namespace name as it evolves during the developmental stages > > >such as the Security Services TC is doing. > > > > > >I think that using a sub-directory of the ebxml-msg and ebxml-cppa TC > > >team's respective URLs is as good a scheme as any for our respective > > >namespaces. > > > > > >e.g. > > > > > > http://oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-NN.xsd > > > http://oasis-open.org/committees/ebxml-cppa/schema/draft-cppa-NN.xsd > > > > > >I like the use of the 'draft' prefix as it makes it quite clear that it > > >is a draft, and not (yet) the real thing. The naming convention that the > > SSTC > > >used follows the IETF I-D format scheme, which IMO is as good as any > > >other. > > > > > >The W3C uses dates in the namespace names, which reflect when a schema was > > >published. I'm not enamored of this scheme at all, but basically, it > > accomplishes > > >a similar aim to what would be achieved using the scheme above similar to > > >that used by the Security Services TC. > > > > > >As to best practices, it seems that because the way that many of the > > >extant parsers work, to resolve the XSD document when parsing, that > > >the schemaLocation and namespace name should be the same value. > > > > > >I think that it is important that we publish the schema document at the > > namespace > > >name URI just so that we don't run into problems when the schemaLocation > > >attribute is accidentally (or intentionally) omitted. > > > > > >I also think that use of a 'docs' sub-directory for our respective draft > > specs and > > >supporting documentation is also a good idea. We should probably approach > > >the reg-rep team with this as well. I've copied Farrukh to see if he knows > > >of what plans the regrep team might have in this regard. > > > > > >Cheers, > > > > > >Chris > > > > > > > > >Dale Moberg wrote: > > >> > > >> Arvola and Ian, > > >> > > >> We should probably discuss best > > >> current practices for the > > >> namespace URI identifier > > >> to be used in Messaging and CPPA > > >> schemas, and also the values > > >> to be used for the location > > >> attribute to indicate where > > >> the schema can be retrieved. > > >> > > >> Chris F. > > >> Can you advise us on what > > >> your take is on tnose practices? > > >> > > >> Thanks > > >> Dale > > >> > > >> -----Original Message----- > > >> From: Jeffrey Lomas [mailto:jeff.lomas@oasis-open.org] > > >> Sent: Thursday, September 27, 2001 7:18 AM > > >> To: Arvola Chan > > >> Cc: Dale Moberg; Karl F. Best; ian.c.jones@bt.com > > >> Subject: Re: Locations for storing ebXML Messaging Service related > > >> schemas > > >> > > >> Arvola, > > >> You can make subdirectories within your Technical Committees directory > > >> by using > > >> the 'mkdir' command from within an ftp session. While OASIS has > > >> provided a > > >> template for page content, it is left to the discretion of the Technical > > >> Committee to organize their content in a way that makes sense to them > > >> beyond > > >> that which is presented on the Technical Committee home page. If there > > >> are > > >> specific actions which you would like my help on, let me know. I am > > >> always > > >> happy to help. > > >> > > >> Regards, > > >> Jeffrey Lomas > > >> Manager-Technology Services > > >> OASIS > > >> PO BOX 455 > > >> Billerica, MA 01821 > > >> 978.667.5115 x 205 > > >> > > >> Arvola Chan wrote: > > >> > > >> > Dale: > > >> > > > >> > You are right. I am requesting for two fixed directories (one for the > > >> MSG TC > > >> > and the other for the CPP/A TC) for placement of schemas (XSD files) > > >> and > > >> > sample instances. These can perhaps be under > > >> > > > >> > http://www.oasis-open.org/committees/ebxml-msg/ > > >> > > > >> > and > > >> > > > >> > http://www.oasis-open.org/committees/ebxml-cppa/ > > >> > > > >> > Thanks, > > >> > -Arvola > > >> > > > >> > -----Original Message----- > > >> > From: Dale Moberg <dmoberg@cyclonecommerce.com> > > >> > To: Karl F. Best <karl.best@oasis-open.org>; Arvola Chan > > >> <arvola@tibco.com> > > >> > Cc: jeff <jeff.lomas@oasis-open.org>; ian.c.jones@bt.com > > >> > <ian.c.jones@bt.com> > > >> > Date: Tuesday, September 25, 2001 10:28 AM > > >> > Subject: RE: Locations for storing ebXML Messaging Service related > > >> schemas > > >> > > > >> > Arvola is our designate example and schema keeper! > > >> > We should have a URL that can always serve > > >> > as our location value for the schemas, right > > >> > Arvola? So these postings should be something > > >> > like a repository for the schemas. > > >> > > > >> > Dale Moberg > > >> > > > >> > -----Original Message----- > > >> > From: Karl F. Best [mailto:karl.best@oasis-open.org] > > >> > Sent: Tuesday, September 25, 2001 8:47 AM > > >> > To: Arvola Chan > > >> > Cc: Karl; jeff; Dale Moberg; ian.c.jones@bt.com > > >> > Subject: RE: Locations for storing ebXML Messaging Service related > > >> > schemas > > >> > > > >> > Arvola: > > >> > > > >> > We won't post any new technical work to the ebxml.org web site, as the > > >> > work of that phase of the project is complete. New work will be posted > > >> > instead to the web pages of the OASIS ebXML TCs. The pages for the > > >> > Messaging TC and the CPPA TC are both maintained by the OASIS > > >> webmaster, > > >> > so any documents you would like to have posted to these web pages > > >> should > > >> > be submitted to webmaster@oasis-open.org. > > >> > > > >> > Also, to ensure that only authorized people are submitting content for > > >> > the web pages I should have the permission of the TC chairs. Ian, > > >> Dale: > > >> > does Arvola have permission to submit items to be posted to your TC > > >> web > > >> > pages? > > >> > > > >> > Arvola: when you submit documents please specify where they should be > > >> > placed. If there are just a couple of documents they could be listed > > >> > under the Documents section of each TC's web page, but if there's > > >> quite > > >> > a few docs then we should link to a separate page that lists them all. > > >> > > > >> > </karl> > > >> > ================================================================= > > >> > Karl F. Best > > >> > OASIS - Director, Technical Operations > > >> > 978.667.5115 x206 > > >> > karl.best@oasis-open.org http://www.oasis-open.org > > >> > > > >> > -----Original Message----- > > >> > From: Arvola Chan [mailto:arvola@tibco.com] > > >> > Sent: Tuesday, September 25, 2001 11:35 AM > > >> > To: Karl F. Best > > >> > Cc: ebxml-msg@lists.oasis-open.org; ebxml-cppa@lists.oasis-open.org > > >> > Subject: Locations for storing ebXML Messaging Service related schemas > > >> > > > >> > Hi Karl: > > >> > > > >> > I am on the ebxml-msg and ebxml-cppa TC's and have volunteered to > > >> bring > > >> > the schemas used by these specifications up to date to conform with > > >> the > > >> > W3C recommended version of XML Schema. During yesterday's MSG > > >> conference > > >> > call, it was recommended that I get in touch with you to obtain > > >> > assistance for getting the updated schemas posted. > > >> > > > >> > In the past, these schemas have been placed under > > >> > http://www.ebxml.org/project_teams/transport > > >> > amd http://www.ebxml.org/project_teams/trade_partner. Can you please > > >> > help allocate similar locations for the schemas to go with the 1.1 > > >> > version of the MSG and CPP/A specifications? > > >> > > > >> > Please let me know how I can submit the updated schemas. I need to > > >> know > > >> > the allocated storage locations ahead of time in order to set up the > > >> > cross-referencing within the XSD's properly. > > >> > > > >> > Thanks, > > >> > -Arvola Chan > > >> > TIBCO Software > > > > ------------------------------------------------------------------------ > > Name: draft-msg-header-00.xsd > > draft-msg-header-00.xsd Type: BizTalk Schema (text/xml) > > Encoding: quoted-printable > > > > Name: envelope.xsd > > envelope.xsd Type: BizTalk Schema (text/xml) > > Encoding: quoted-printable > > > > Name: xlink.xsd > > xlink.xsd Type: BizTalk Schema (text/xml) > > Encoding: quoted-printable > > > > Name: xml_lang.xsd > > xml_lang.xsd Type: BizTalk Schema (text/xml) > > Encoding: base64 > > > > Name: xmldsig-core-schema.xsd > > xmldsig-core-schema.xsd Type: BizTalk Schema (text/xml) > > Encoding: base64
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC