OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tag message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Groups - TestAssertionsModel-csd03-diffs (testassertionsmodel-1.0-cd-03-diffs.odt) uploaded


Preparing for standard submission - Several editorial fixes from previous
csd and cs01:
- from comment list: use of ISO keywords in Intro section and other
non-normative sections.
- from comment list: missing link in ISO ref.
- from comment list: added cross-refs in conformance Clause.
- from comment list: give a name to the different types of implementations
/artifacts that must conform. in conformance Clause.
- several (minor) formatting nits, line breaks missing, or that should be
removed. Extra-spaces, bold words with non-bold 1st letter, etc.
- unwarranted focus on conformance profile in 2.1 (instead, equally refer
to module/profile/level as defined in [VAR] ref)
- Some incorrect definitions (see in section 3.2, language attribute of
the target, also unwarranted mention of Conformance profile again, in 3.2
Prerequisite  probably forgot to remove this sentence.)
- Some lack of precision on cardinalities (see 2.1, also in 3.2 ref from
testAssertion to Normative Statement(s)
- Wrong cardinalities for name attr of 3.2 tag definition, and in 3.2
variable.
- lack of definition of what a property TA is (3.2. Reserved tag names
) and inappropriate style you can generate for a standard. Also
inaccurate def of VersionDrop.
- In 4.1 Shared, undefined acronym (TA).
- Conformance section: need to define subsections titled Conformance
Clause to stick to most recent updates on the OASIS TC process. Also do
not define these as conformance profiles (closer to conformance modules,
according to [VAR]).  Also, inappropriate acronyms (TA) used for Test
Assertion in such a high level section.


 -- Mr Jacques Durand

The document named TestAssertionsModel-csd03-diffs
(testassertionsmodel-1.0-cd-03-diffs.odt) has been submitted by Mr Jacques
Durand to the OASIS Test Assertions Guidelines (TAG) TC document
repository.

Document Description:
Several editorial fixes from previous csd and cs01:
- from comment list: use of ISO keywords in Intro section and other
non-normative sections.
- from comment list: missing link in ISO ref.
- from comment list: added cross-refs in conformance Clause.
- from comment list: give a name to the different types of implementations
/artifacts that must conform. in conformance Clause.
- several (minor) formatting nits, line breaks missing, or that should be
removed. Extra-spaces, bold words with non-bold 1st letter, etc.
- unwarranted focus on conformance profile in 2.1 (instead, equally refer
to module/profile/level as defined in [VAR] ref)
- Some incorrect definitions (see in section 3.2, language attribute of
the target, also unwarranted mention of Conformance profile again, in 3.2
Prerequisite  probably forgot to remove this sentence.)
- Some lack of precision on cardinalities (see 2.1, also in 3.2 ref from
testAssertion to Normative Statement(s)
- Wrong cardinalities for name attr of 3.2 tag definition, and in 3.2
variable.
- lack of definition of what a property TA is (3.2. Reserved tag names
) and inappropriate style you can generate for a standard. Also
inaccurate def of VersionDrop.
- In 4.1 Shared, undefined acronym (TA).
- Conformance section: need to define subsections titled Conformance
Clause to stick to most recent updates on the OASIS TC process. Also do
not define these as conformance profiles (closer to conformance modules,
according to [VAR]).  Also, inappropriate acronyms (TA) used for Test
Assertion in such a high level section.


View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=41239

Download Document:  
http://www.oasis-open.org/committees/download.php/41239/testassertionsmodel-1.0-cd-03-diffs.odt


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]