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

 


Help: OASIS Mailing Lists Help | MarkMail Help

bt-spec message

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


Subject: Re: [bt-spec] Possible xml for btp node state


Peter, I didn't get to the teleconference so this doesn't seem to have a
context (no pun intended). Can you place it please?

Mark.

----- Original Message -----
From: "Peter Furniss" <peter.furniss@choreology.com>
To: "BT - spec" <bt-spec@lists.oasis-open.org>
Sent: Wednesday, April 03, 2002 7:31 PM
Subject: [bt-spec] Possible xml for btp node state


> Below is the draft of xml to be the serialisation of a btp node, that I
> mentioned on the conference call just now. This should not be taken, at
this
> stage, to be anything other than a Choreology suggestion. Tony did the
first
> version, but the mistakes in this version are mine :-)
>
> If included in the document, it will need a bit more introduction. It
would
> go near the other xml. Tony has started on a schema for this.
>
> -------
>
>
> Taking the general case of a Sub-composer or Sub-coordinator that was able
> to recover from an active state, an informal XML representation of the
> information that would need to be persisted by a BTP actor is given below.
> This information, combined with the relevant application information, is
the
> state information that would allow the transfer of the BTP actor in its
role
> to another system. States are represented by the state identification from
> the state tables. Note there is one "information-as-inferior" (absent if
> this is the Composer or Coordinator) and a separate
>  "information-as-superior" for each relationship to another Inferior.
>
> It is assumed for this XML that the Identifier and BTP addresses used by
> this node are the same in its roles as Superior and Inferior  - these are
> the values in the "own-information" element.. This is not generally
required
> by the BTP protocol messages.
>
>
> <btpst:node-information>
>
>
>
<btpst:role>composer|coordinator|sub-composer|sub-coordinator|participant</b
> tpst:role>
>
>   <btpst:own-information>
>     <btpst:own-identifier>...URI...</btpst:own-identifier>
>     <btpst:own-address> +
>       <btp:binding-name>...carrier binding URI...</btp:binding-name>
>       <btp:binding-address>...carrier specific
> address...</btp:binding-address>
>       <btp:additional-information>...optional additional addressing
> information...</btp:additional-information> ?
>     </btpst:own-address>
>   </btpst:own-information>
>
>   <btpst:information-as-inferior> ?
>     <btpst:state>... statename from inferior state table ...</btpst:state>
>     <btpst:superiors-identifier>...URI...</btpst:superiors-identifier>
>     <btpst:superiors-address> +
>       <btp:binding-name>...carrier binding URI...</btp:binding-name>
>       <btp:binding-address>...carrier specific
> address...</btp:binding-address>
>       <btp:additional-information>...optional additional addressing
> information...</btp:additional-information> ?
>     </btpst:superiors-address>
>
>     <btp:qualifiers> ...qualifiers...  </btp:qualifiers> ?
>   </btpst:information -as-inferior>
>
>   <btpst:information-as-superior> +
>     <btpst:state>... statename from superior state table ...</btpst:state>
>     <btpst: inferiors-identifier>...URI...</btpst:inferiors-identifier>
>     <btpst: inferiors-address> +
>       <btp:binding-name>...carrier binding URI...</btp:binding-name>
>       <btp:binding-address>...carrier specific
> address...</btp:binding-address>
>       <btp:additional-information>...optional additional addressing
> information...</btp:additional-information> ?
>     </btpst:inferiors-address>
>
>     <btp:qualifiers> ...qualifiers... </btp:qualifiers> ?
>   </btpst:information -as-superior>
>
>  <btpst:other-information> optional additional information -
implementation
> dependent.  may be structured.
>  </btpst:other-information> ?
>
> </btpst:node-information>
>
>
>
> Peter
>
> ------------------------------------------
> Peter Furniss
> Chief Scientist, Choreology Ltd
> web: http://www.choreology.com
> email:  peter.furniss@choreology.com
> phone:  +44 20 7670 1679
> direct: +44 20 7670 1783
> mobile: +44 7951 536168
> 13 Austin Friars, London EC2N 2JX
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>



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


Powered by eList eXpress LLC