RE: [tamie] 2 Proposals for change of tamie etsm schema

["Jacques R. Durand" <JDurand@us.fujitsu.com>]

comment inline

-jacques

-----Original Message-----
From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On Behalf Of Stephen Green
Sent: Sunday, August 30, 2009 1:07 PM
To: tamie@lists.oasis-open.org
Subject: [tamie] 2 Proposals for change of tamie etsm schema

I note there is one change item to consider for the ETSM draft core schema which would impact on the translator -

to make attribute '//catch/match/@condition' into an element '//catch/match/condition' (to allow addition of further attributes to the 'condition' node)

<JD> I guess your point is that sometimes the condition expression is too complex or long to be conveniently held by a single attribute. In such case, we could instead add some named <variable> or <expression> child elements to <match>, that the <condition> can then refer to. The issue I see with several <condition> elements, is that the semantics of their combination is unclear. If you say it is an implicit AND, that would not help cases where complexity come from a large OR expression...

Another set of changes would not impact to translator -

to add items missing from the translator examples but present in the core set of eTSM features e.g. //decide/else-if

I'd propose these changes since the impact on the translator is minimal. This would result in a new draft, version 0.3 of the Core eTSM schema.

Best regards

Steve

---
Stephen D Green

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php