Re: [ebxml-dev] re BPSS: how can I identifyDocumentEnvelopefromreceivedmessage

["Himagiri(Hima) Mukkamala" <himagiri@sybase.com>]

Nagahashi-san,

If you look around line 2008 Section 8.1.4 for documentation
of BusinessDocument element from BPSS 1.05 schema
which was just released for public review.
-------------------------------------------------
specificationLocation of type xsd:anyURI
                            Reference to an external source of the schema

specificationID of type xsd:anyURI

Reference to an external source of the schema
definition. This defines the absolute path
including the element id within the schema
definition that defines the type of this document.
Use either specificationLocation or
specificationID.
-------------------------------------------------------------------

I guess this has changed from earlier versions(1.01) bpss where
there used to be a specificationElement. Looks like the replacement
for that would be the specificationID which also identifies the
element within the schema definition. So if this attribute is present
then DocumentEnvelope referring to a BusinessDocument with
specificationID of "http://www.sybase.com/PO.xml#PurchaseOrder";
is identified when a message is received with a payload of
schema "PurchaseOrder".

Please send a comment against BPSS 1.05 regarding the
mismatch between the UML diagram and the schema with reference
to schemaElement attribute


Not sure what you mean by this from your earlier email
"""""If it points to message schema (I'm not sure because there is
specificationLocation attribute), I have to validate the received
message against all possible schemas to identify DocumentEnvelope. This
sounds like a costly implementation. It would be lightweight if I could
use some short identifier I can get without parsing the payload.""'"".
Can you explain this statement?

cheers
hima


nagahashi@fla.fujitsu.com wrote:

> Hima,
>
> Thank you for your reply!
>
> I did't know the specificationElement attribute of BusinessDocument ...
> Ah, It is in the class diagram on page 22! (I'm reading 1.04 draft - I
> understand it is wip) I couldn't find any description for
> specificationElement, even on page 59 (the specificationID attribute is
> missing in BusinessDocument class in the diagram, too). Coudld you tell
> me what should I specify in specificationElement?
>
> If it points to message schema (I'm not sure because there is
> specificationLocation attribute), I have to validate the received
> message against all possible schemas to identify DocumentEnvelope. This
> sounds like a costly implementation. It would be lightweight if I could
> use some short identifier I can get without parsing the payload.
>
> If it is an identifier, question remains: in which MSH information I can
> find the identifier?
>
> Sorry if I missed something in other related ebXML specs.
>
> Thanks
> Kenji Nagahashi
>
> > DocumentEnvelope references the BusinessDocument
> > which points to a specificationElement.
> >
> > Based on the specificationElement in the document received
> > over the messaging layer, this identifies the DocumentEnvelope
> > corresponding to isPositiveResponse=false
> >
> > You could use the conditionExpression in the BusinessDocument, if for
> e.g
> >  same Schema is used for different BusinessDocuments but
> > based on the conditionExpression, like presence or absence
> > of a specific Element, they derive different DocumentEnvelopes.
> >
> > -hima
> >
> > nagahashi@jp.fujitsu.com wrote:
> >
> > > Hi
> > >
> > > I have a (possibly silly) question about BPSS. Anybody has
> experienced
> > > this problem? Could anybody give me an answer to it?
> > > ----
> > > Please assume I'm developing ebXML gateway which is configurable
> with
> > > BPSS and do some business process management staff for me.
> > >
> > > BusinessTransaction/RespondingActivity can have more than one
> > > DocumentEnvelope. If the gateway receives a message for
> DocumentEnvelope
> > > with isPositiveResponse="false", the BusinessTransaction must fail.
> > > In order to determine completion state of a BusinessTransaction, the
> > > gateway must identify which DocumentEnvelope it received.
> > >
> > > Question is, which information from BPSS gives me a key to identify
> > > DocumentEnvelope? Transport (ebMS) can pass many information up to
> BP
> > > manager. Which of them are used to identify DocumentEnvelope and
> Where
> > > is it specified in the BPSS? This is so important that there should
> be
> > > some 'standard' way.
> > >
> > > I found that BusinessDocument has conditionExpression. BPSS spec
> says
> > > this conditionExpression "determines whether this is a valid
> business
> > > document for its envelope." Is this it?
> > >
> > > Thanks in advance
> > >
> > > Kenji Nagahashi
> > >
> > > ----------------------------------------------------------------
> > > The ebxml-dev list is sponsored by OASIS.
> > > To subscribe or unsubscribe from this elist use the subscription
> > > manager: <http://lists.ebxml.org/ob/adm.pl>
> >
> >
> > ----------------------------------------------------------------
> > The ebxml-dev list is sponsored by OASIS.
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.ebxml.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> The ebxml-dev list is sponsored by OASIS.
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.ebxml.org/ob/adm.pl>