re: Message from Internet (via MIME!)

[David RR Webber <Gnosis_@compuserve.com>]

Message text written by "Burdett, David"
> 
Folks

To get around the Service Interface definition problem. How about using the
term Service Type in the ebXML Message Header. Similarly we could have
Action Type instead of Action. I think that both these elements will
contain
"type" values and therefore perhaps more accurately represents what it is.

Thoughts?

David
<<<<<<<<<<<<<<<<<<<<<

Dave,

What's the context here?  Registry Services?  If so I'm beginning to
think we are mixing apples and oranges here and that perhaps
we should have two separate Service categories, or maybe
three or four categories.  Examples - TRP simple messaging, 
Registry services, Publish Subscribe services, Multi-hop services.

This certainly helps on the Conformance side.  If I build a simple
SMTP interface to do simple messaging, I don't expect people
to hit it up for multi-hop messaging, and so on.

It will also help us long term create a TRP model that is 
transport neutral, right now what we have is highly MIME 
specific.  If we move to a more generic XML se of methods and
structures,  we can do MIME, SOAP, et al into the future.

DW.