Re: [ebxml-dev] ebXML MS v1.0 schema

[Dave Welsh <dave@collaborativedomain.com>]

Well Neil,
I think MS 1.0 specifications were carried over to the current OASIS TC,
link below. The new OASIS MS TC has worked on 2.0 for 10 months now.
You may want to directly seek their exact technical guidance, instead of on
this more public discussion list.

Best regards
-Dave


----- Original Message -----
From: Belford Neil <Neil.Belford@vencorp.vic.gov.au>
To: 'Dave Welsh' <dave@collaborativedomain.com>
Cc: Ebxml-Dev (E-mail) <ebxml-dev@lists.ebxml.org>
Sent: Thursday, April 11, 2002 10:19 PM
Subject: RE: [ebxml-dev] ebXML MS v1.0 schema


> Dave,
>
> Thanks for the consideration, however the v2.x of the messageHeader specs
> are of no use to the 25 or so actual implementations of toolkits on the
v1.0
> spec; or for B2B communities trying to use those tools to build real
> systems. All of these groups are making their own ad-hoc decisions on what
> the schema should actually be. This situation is a DISASTER.
>
> I am aware how open standards are developed - the problem here is that the
> people who are actually doing the work - and getting paid for it - are
> completely letting down those paying the bills. The worst part is that I
> suspect the people you refer to - who are footing the bill - don't know
that
> the real deliverables are not there.
>
>
> regards
> Neil Belford
> B2B Architect
> FRC Project, VENCorp
>
>
> -----Original Message-----
> From: Dave Welsh [mailto:dave@collaborativedomain.com]
> Sent: Friday, April 12, 2002 11:30 AM
> To: Belford Neil
> Cc: Ebxml-Dev (E-mail)
> Subject: Re: [ebxml-dev] ebXML MS v1.0 schema
>
>
> Neil,
> Have you looked at
> https://www.oasis-open.org/committees/ebxml-msg/#documents for the latest
> (version 2.0 I think) of the ebXML messaging specs ?
>
> Thanks
> -Dave
> ps. ebXML are "open standards" developed with the kind / free contribution
> from companies, industry associations and government institutions from
> around the world. Thanks and all the best.
>
> ----- Original Message -----
> From: Belford Neil <Neil.Belford@vencorp.vic.gov.au>
> To: Ebxml-Dev (E-mail) <ebxml-dev@lists.ebxml.org>
> Sent: Thursday, April 11, 2002 5:36 PM
> Subject: [ebxml-dev] ebXML MS v1.0 schema
>
>
> > It is a disgrace and a total abdication of responsibility that those
> > provided with the resources to develop and maintain ebXML have left the
> ebMS
> > 1.0 'messageHeader.xsd' schema hanging. I hope you guys who are getting
> paid
> > to do this work are enjoying your sinecure while you swan around to
> > conferences.
> >
> > To facilitate Full Retail Contesability, the Gas Industry in the state
of
> > Victoria in Australia is deploying a B2B system based on ebXML MS 1.0.
The
> > payload is an (local industry standard) aseXML document.
> >
> > We have a reference 'messageHeader.xsd' that is derived from the flawed
> one
> > published in the ebXML MS v1.0 spec, which I will gladly furnish, caveat
> > emptor, to anybody who wants it.
> >
> > However we feel this is a ridiculous state of affairs. Will someone,
> perhaps
> > a tool vendor, or some other organisation who understands the problem
> please
> > hang out a reference schema somewhere on the web that we can all use.
> >
> > Also can we all please bring some pressure to bear on the people
providing
> > the funding to ebXML.org to ensure they know that the people charged
with
> > the responsibility of conveying the technical information are not
> fulfilling
> > their duties.
> >
> >
> >
> > Neil Belford
> > B2B Architect
> > FRC Project, VENCorp
> >
> >
> >
> > ******************************************************************
> > This e-mail is confidential and for the sole use of the intended
> > recipient(s).  If you are not the intended recipient, you are not
> > authorised to disclose, use, distribute or in any other way make
> > use of the information contained in it, and such activities are
> > prohibited.  If you have received this e-mail in error, please
> > notify the sender by reply e-mail, delete the document and destroy
> > all copies of the original message.
> > ******************************************************************
> >
>