RE: [tag] added issue 031, with some proposals

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

Interesting idea, close to proposal #3 but more flexible in its use.
Agree that the focus should be more on the predicate.
I would assume that if the GP is reusing some "atomic" predicates
already used by other Tas, the GP would still be able to make use of
notation like: TA1.predicate AND TA2.predicate (which implicitly concern
respective targets from TA1 and TA2).

If I get that right:
- A "global predicate" may or may not be used in a TA. It is a notation
we offer for whatever use, within or beyond TA definition.
- It may be used in the pre-requisite part of a TA.
- it may also be used in lieu of the normal "predicate" part, in case we
want to use it in a higher-level TA for example to address requirements
for a complex property like "medium-size". 

Now I would keep it just a predicate notation, i.e. if we have a need
for a prescription level, etc, then that could be provided by the
regular TA structure once this predicate is referenced by such a TA?

Jacques

-----Original Message-----
From: stephen.green@systml.co.uk [mailto:stephen.green@systml.co.uk] 
Sent: Thursday, April 17, 2008 12:53 AM
To: tag@lists.oasis-open.org
Subject: Re: [tag] added issue 031, with some proposals

4th proposal added
--
Stephen D. Green

Partner
SystML, http://www.systml.co.uk
Tel: +44 (0) 117 9541606

http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice



Quoting "Durand, Jacques R." <JDurand@us.fujitsu.com>:

> see http://wiki.oasis-open.org/tag/DocIssues
>
> Issue 031: Property-defining Spec Requirements and related Test 
> Assertions
>




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