Notes from Session B, and more

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

Notes from Session B, Wednesday 7th, 9pm-10pm:

 

Attendees: Youngkon L., Jacques D.

 

- YL: About Glossary: we need to keep it, it should define terms beyond what 2.1 describes (only TA parts), and still remind of each TA part but defer to 2.1 for their more complete definition. In other words, 2.1. should be where TA parts are fully defined, while just a place holder in section 4.

 

- Section 3.4 (by Kevin): YL agrees mostly with Jacques comments in email April 24, although TAs about "bindings" needs better explanation. The "conjured examples" from Kevin about referred specs (Widget, EmbeddedWidget, MobileWidget) are not convincing in the sense these targets are strongly related (subclass of each other), while referred specs are about different targets (e.g. HTTP envelope, SOAP envelope, even if these may contain each other).

 

- Section 3.5.1 (by Jacques): YL: another important relationship between target, besides subclass and component: "dependency" like between a WSDL definition and a on-wire SOAP message. The notion of "target class" is misleading, to reminiscent of object-oriented, and not introduced before (in Section 2 we talk of "target category"). Should be avoided.

 

-YL + JD: discussions in advanced feature section 3, e.g. 3.5.1, are a bit too technical for a basic TA guideline doc.

 

MAJOR SUGGESTION:

 

- consider we have enough material today in the Guideline for wrapping up the first deliverable. Any more detail on advanced features can be described in an annex (adjunct) document to the guideline, which would be about "complex TAs" or "advanced TAs" or the like.

- while keeping the same subsections in the basic Guideline doc, for section 3, only outline the issues and options for each 3.x subsection. No detailed treatment. This means reducing 3.5.1 to no more than half a page.

- for stable sections like 3.2 Prerequisite , consider shortening too.

 

 

---- a proposal that addresses issue 031 as well as some of above concerns:

 

See my proposed updates of section 3.2 "Test Assertions Prerequisites" in wiki: http://wiki.oasis-open.org/tag/TestAssertionGuidelines

- split former 3.2 into two subsections, as the first part is really about TAs related to "properties", not about prerequisites.

- when a TA and its prescription level (like in widget-TA3 and widget-TA4) are about a specific property like "medium-size", the NormativeSource part must indicate it clearly (see proposed added paragraph in new 3.3).

 

Jacques