Re: Very Rough Draft of Header Specification

[Christopher Ferris <chris.ferris@east.sun.com>]

David,

I agree that use of RFC 2119 would help tighten up the requirements
specification
language and we should probably adopt them for our use.

Would this also be something which should be submitted to the Requirements
WG for consideration?

Cheers,

Chris

David Burdett wrote:

> <snip/>

>
> 2. They have some good ideas, for example on the use of MUST, SHOULD, MUST
> NOT, etc - they really help to tighten up a specification
>
> Does this make sense?
>
> David
>
> -----Original Message-----
> From: Rik Drummond [mailto:drummond@onramp.net]
> Sent: Wednesday, March 15, 2000 8:35 AM
> To: David Burdett; ebXML Transport (E-mail)
> Subject: RE: Very Rough Draft of Header Specification
>
> David you have been busy!!!
>
> The requirements teams specifies that their document format is the one
> everyone should use. Do we want to support that? Is this that format? any
> issues?  best regards, rik
>
> -----Original Message-----
> From: owner-ebxml-transport@lists.oasis-open.org
> [mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of David
> Burdett
> Sent: Tuesday, March 14, 2000 8:45 PM
> To: ebXML Transport (E-mail)
> Subject: Very Rough Draft of Header Specification
>
> Folks
>
> I attach a very rough draft of the Header Specification. The roughest area
> is probably the Data Dictionary as I know there are inconsistencies in this
> section when compared with the Header Structures section - the latter is the
> more accurate and over rules what is currently in the Data Dictionary - it's
> just that I've run out of time and thought it better to get this to
> everyone a day earlier so that you can read it.
>
> The way the spec was developed was:
> 1. Identify the data requirements from our requirements documet
> 2. Do a quick review of the header classification work that John I did, to
> see if there were any gaps.
>
> What we absolutely must do (but haven't yet) is to do a rigorous comparison
> of this spec with other specs (BizTalk, AS1, AS2 etc) to make sure that we
> can map between them. This should then give a migration path from these
> standards to the approach we are developing.
>
> John Ibbotson is also planning to do a sample DTD so that we can see how
> this all fits together
>
> David
> PS If anyone wants a PDF version please let me know.
>  <<ebXML Message Header Specification v0-10.doc>>
>
> Advanced Technology, CommerceOne
> 4400 Rosewood Drive 3rd Fl, Bldg 4, Pleasanton, CA 94588, USA
> Tel: +1 (925) 520 4422 or +1 (650) 623 2888;
> mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com