Re: [tag-comment] Document model constraints for a set of tag assertions

[Stephen Green <stephengreenubl@gmail.com>]

Thanks Ken,

[Note: I thought it best to respond immediately to your comment to
save you having to wait for advice on finding examples of marked up
test assertions. This is not, however, an official TC disposition though
it does reflect the ongoing, minuted discussions of the TC.]

We are likely to introduce a markup language for our test assertions,
following the TAG TC test assertion model, and we have a wiki page:

http://wiki.oasis-open.org/tag/TestAssertionMarkupLanguage

There we will maintain links to the latest drafts. Currently we have
there draft version 0.3 of this "Test Assertion Markup Language" and
there is an example there which is an instance similar to the example
in the public review draft of the Test Assertions Guidelines document.
[These documents are also found in the Documents area of the TAG TC
offical site
http://www.oasis-open.org/committees/documents.php?wg_abbrev=tag ]

It seems likely from ongoing TC discussions that we will combine the
markup with the content of the Test Assertions Guidelines document
to form what seems likely to be a normative committee specification
of the "Test Assertion Markup Language". So if you are looking for
something normative like this it will probably be found in the next
public review. [This is subject to official TC disposition.]

Best regards

Steve
---
Stephen D Green

Editor / Secretary TAG TC




2009/8/19 G. Ken Holman <gkholman@cranesoftwrights.com>:
> Hi folks!
>
> I'm looking for a formalized set of document constraints on an instance of
> tag assertions.  Does one exist?  I'm looking at
> http://wiki.oasis-open.org/tag/FrontPage under "Anatomy of a Test Assertion"
> and "Test Assertion Markup Language" where would have expected to find it.
>
> It would help me see the overall structure of an instance and give me clues
> on what to look up.
>
> It could be in RELAX-NG Compact Syntax ISO/IEC 19757-2Amd1 for legibility or
> I suppose any other document model constraint language that your committee
> might choose to use.
>
> Thank you for any guidance you may provide in this regard.
>
> . . . . . . . . . . . . . Ken
>
> --
> Interested in these classes?  http://www.CraneSoftwrights.com/o/i/
> Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
> Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
> Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
> Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
> G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
> Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/o/bc
> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
>
>
> --
> This publicly archived list offers a means to provide input to the
> OASIS Test Assertions Guidelines (TAG) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: tag-comment-subscribe@lists.oasis-open.org
> Unsubscribe: tag-comment-unsubscribe@lists.oasis-open.org
> List help: tag-comment-help@lists.oasis-open.org
> List archive: http://lists.oasis-open.org/archives/tag-comment/
> Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tag
> Join OASIS: http://www.oasis-open.org/join/
>
>