AS1 ties to EDI (was RE: AS2 XML requirements)

[Dave Roberts <dave.roberts@xxxxxxxxxxxxxxxxxx>]

On Thu, 23 Nov 2000, Dick Brooks wrote:

> However, there is no definitive text describing how non-rfc1767 types are
> supported in AS1. The AS1 specification is tightly intertwined with
> references to RFC 1767 and all examples are based on RFC 1767 payloads.

Right.

Terry, is it possible to change the text within the Security
Considerations paragraph and the Introduction?  I don't know if that's ok
at this late stage.  Changing most of the EDI references to "EC or EDI"
should set the tone for the remainder of the document.

> it to up to the individual AS1 vendors to decide how non-RFC1767 payloads
> are supported in their products and this opens the door to interoperability
> issues.

I see your point.  There is no clear guidance on what MIME type is to be
used for non-EDI data.  Whilst some may use the IANA MIME type, others may
not.

> AS2 contains definitive text describing support for ANY MIME media type. I
> believe the AS1 authors should consider adding language similar to what is
> contained in AS2.

Right, so an EDI payload uses the MIME types laid down in RFC 1767.
Non-EDI payloads should use the MIME types as laid down by the IANA.

Perhaps also a statement on the MIME types that MUST be supported (i.e. 
those specified by RFC1767), and a statement that any other MIME type is
up to the vendor to handle.  Or would that be too liberal?

- Dave.

--
Dave Roberts                     Servicing the Online Organisation
Principal Technical Consultant   http://www.saaconsultants.com/
SAA Consultants Ltd              Tel: +44 1752 606000 
Plymouth, UK.                    Fax: +44 1752 606838