xml-dev - Using processing instructions as transaction semantics

["Barney, Chris" <Chris.Barney@pegsinc.com>]

Here is a question.

What does the group think of using processing instructions as transaction
semantics vs. using elements

The intent is to send some XML off for processing, and get back some result.
We're looking at two ways of specifying what action is to be done to
what data.

Example 1:

<?OP1 function=perform-some-operation ?>
<Customer operation="OP1">
	<Name>Fred C. Flinstone</Name>
	<Address>1234 Bedrock Ave.</Address>
</Customer>
	
	or

Example 2:

<PerformSomeOperation>
<Customer >
	<Name>Fred C. Flinstone</Name>
	<Address>1234 Bedrock Ave.</Address>
</Customer>
</PerfromSomeOperation>


Does either approach have noticeable advantages/disadvantages?
Can anyone here speak from experience with using PIs (either in
a similar circumstance, or at all)?


Thank you,

Chris




***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************