[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (TAG-9) Tag-Comment: Why TAMLPredicate not Formal?
[ http://tools.oasis-open.org/issues/browse/TAG-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Hamilton updated TAG-9:
------------------------------
Resolution:
[updated 2010-12-06]
1. There was no intention to introduce a machine-executable formalism for Test Assertion predicates. It was intended that there be no difference between the TA model and the TA markup in this respect. The TA Markup Language is for carrying the test assertion in an XML markup structure, but not to require any formalization nor require machine interpretation. In particular, satisfaction of the predicate may require human action and inspection, so the statement of the predicate will often be intended as a human-readable prescription, even if it appeals to a mechanized or programmed verification procedure.
However, the optional lg attribute (for "language") on the taml:predicate element is provided for the identification of special formalisms, thereby providing for machine-interpretable predicate notations when that is desired.
2. Dennis Hamilton will respond to the commenter and convey our thanks for the question and our response.
was:
1. There was no intention to introduce a machine-executable formalism for Test Assertion predicates. It was intended that there be no difference between the TA model and the TA markup in this respect. The TA Markup Language is for carrying the test assertion in an XML markup structure, but not to require any formalization nor require machine interpretation. In particular, satisfaction of the predicate may require human action and inspection, so the statement of the predicate will often be intended as a human-readable prescription, even if it appeals to a mechanized or programmed verification procedure.
2. Dennis Hamilton will respond to the commenter and convey our thanks for the question and our response.
> Tag-Comment: Why TAML Predicate not Formal?
> -------------------------------------------
>
> Key: TAG-9
> URL: http://tools.oasis-open.org/issues/browse/TAG-9
> Project: OASIS Test Assertions Guidelines (TAG) TC
> Issue Type: Improvement
> Components: TA markup doc CD 02
> Reporter: Dennis Hamilton
> Assignee: Dennis Hamilton
>
> This TAG-Comment is from "Bahareh Heravi" <Bahareh.Heravi@brunel.ac.uk> on 2010-05-11:
> <http://lists.oasis-open.org/archives/tag-comment/201005/msg00002.html>.
> The question is why is not a formal notation for predicates introduced in TAML To wit,
> """
> As far as I understand Test Assertions are meant to kind of formalise Normative Statements in the specifications which is superb.
> I couldn't find a description for Test Assertion Mark-up Language in its spec but I reckon it provides a XML representation of the Test Assertions. However, I don't quite get the point of a machine readable representation when the predicates are not formal.
> """
> The concern is that the predicate is not machine-interpretable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]