OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: [ebxml-dev] ebXML specifications interdendancies


Thanks, but I still don't think I have an answer.  I know perfectly well what "context"
is.  From your previous messages in this thread, I thought you were referring to the
"context message".  Specifically, about it I was asking:

1)  How do you expect the context message to be used?

2)  Why is the context message "depended on by several other systems in ebXML"?  (or at
least that's what I thought that you were asserting.  Forgive me if I misread you.)



A minor point below :

Duane Nickull wrote <snipped>:

> > 2)  Why is it "depended on by several other systems in ebXML"
> >>>>>>>>>>>>>>>
> Becuase it is a design time issue,  theoretically no one can advance to
> runtime until this issue is solved. (eg - with the context mechanism and
> fully automatic collaborations, which was in the ebXML requirement
> document)

I don't recall anything about fully automatic collaborations being in the ebXML
requirements document.  "automatic" does not appear in either the May 2000, or May 2001
versions, and "collaboration" only appears in the 2001 version when associated with the
CPA/CPP.  Can you point me to a reference?

Michael C. Rawlins, Rawlins EC Consulting

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC