Re: [tag] conf call 10/23 ?

[Kevin Looney <kevin.looney@oracle.com>]

Unfortunately, that doesn't work well for me (doctors appointment).

Wed/Thurs are available though.

Kevin



On 10/16/12 1:48 PM, Jacques Durand wrote:
> Kevin:
> Let us discuss this among other things on a next conf call.
> Would everyone be available Tuesday 10/23, 2pmPT?
> Agenda:
> - next steps for our specs (TAM, TAML)
> - update for Guidelines: editorial + content?
> Thanks,
> -jacques
>
>
> -----Original Message-----
> From: Kevin Looney [mailto:kevin.looney@oracle.com]
> Sent: Tuesday, October 16, 2012 1:45 PM
> To: Jacques Durand
> Cc: tag@lists.oasis-open.org
> Subject: A late editorial issue for the guideline
>
> Hi Jacques,
>
>        I was spreading news and references around here for the standard, and one of our Java Specification experts noticed something:
>
> It looks like we might have missed a reference in the glossary to 'Conformance Target' (which looks like it is defined in a different reference).  Probably the right thing to do is to add the definition to the glossary, and put the reference where it comes from on the glossary definition.
>
> Thanks,
> Kevin
> > > On a picky note, the "Normative Statement" entry in the Glossary
> > > refers to "conformance target" but there is no entry for that. There
> > > is merely an entry for "Test Assertion Target" which I don't think is
> > > quite the same thing. I imagine a 1:n relationship between
> > > conformance target and test assertion targets, akin to the 1:n
> > > relationship between normative statement and test assertions.
> > On 10/16/2012 12:00 PM, Kevin Looney wrote:
> > > Hmm - this sounds like an oversight.  I know we spent a lot of time
> > > hashing 'conformance target', and I if I recall correctly, that was a
> > > term that was coming from some other reference - but you are
> > > absolutely correct that there should be a closure in the terminology.
> > > I'll pass this back along to Jacques (spec lead).
> > It comes from the [CONFCLAUSE] reference,
> > http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html.
> > To be fair, "conformance target" doesn't appear in your document, but
> > 2.2 clearly tries to differentiate spec constructs from test
> > constructs, so it would be a good place to introduce conformance
> > targets as distinct from 3.1's test assertion targets.
> >
> > Alex
>
> On 10/16/12 11:42 AM, Jacques Durand wrote:
> > Chet:
> > It occurs to me that we did not define an acronym for this standard. "TAG" is more the TC name. Maybe "TAM" (Test Assertion Model) would do. Any thought from others?
> > -jacques
> >
> > -----Original Message-----
> > From: tag@lists.oasis-open.org [mailto:tag@lists.oasis-open.org] On Behalf Of Chet Ensign
> > Sent: Tuesday, October 16, 2012 7:02 AM
> > To: tag@lists.oasis-open.org
> > Cc: Carol Geyer
> > Subject: [tag] The ballot to approve Test Assertions Model v1.0 as an OASIS Standard has passed
> >
> > Members of the TAG TC,
> >
> > The ballot to approve Test Assertions Model v1.0 as an OASIS Standard has passed. You needed 48 affirmative votes to pass and you received 54. You can see the ballot results at
> > https://www.oasis-open.org/committees/ballot.php?id=2294 .
> >
> > I will now announce the results to the OASIS members and publish the finished OS. TCADMIN JIRA ticket
> > https://tools.oasis-open.org/issues/browse/TCADMIN-1086 has been entered to manage this work.
> >
> > Please let me know if you have any questions and congratulations on reaching this milestone.
> >
> > Best regards,
> >
> > /chet
> > ----------------
> > Chet Ensign
> > Director of Standards Development and TC Administration
> > OASIS: Advancing open standards for the information society http://www.oasis-open.org
> >
> > Primary: +1 973-996-2298
> > Mobile: +1 201-341-1393
> >
> > TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
> >
> > Follow OASIS on:
> > LinkedIn:    http://linkd.in/OASISopen
> > Twitter:        http://twitter.com/OASISopen
> > Facebook:  http://facebook.com/oasis.open
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tag-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: tag-help@lists.oasis-open.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tag-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: tag-help@lists.oasis-open.org


--
kevin.looney@oracle.com