Re: [tag] RE: more detailed mark-up items

[Stephen Green <stephen.green@documentengineeringservices.com>]

That sounds a bit crazy though - is it really sensible to have a set of
TAs sharing predicates, prerequisites, etc each with a different
Prescription Level. Sounds a bit complex. Maybe we want to limit what
can be shared and its logic, otherwise the complexity might obscure
and undermine the usefulness of such sharing.

2009/3/3 Stephen Green <stephen.green@documentengineeringservices.com>:
> For the question of Shared TA Parts and whether the TA Parts should
> be multiple occurance: One reason to make it multiple occurance (with
> additive logic) is that each occurance of the TA Parts could have its own
> Prescription Level (which does not apply to the other TA Parts).
>
> Note: I think the structure used for the TA Parts should *not* be a reuse
> of the TA because the TA Id, I think, should not be included in TA Parts
> but it should be included in the TA.
>
> - Steve
>
> 2009/3/2 Durand, Jacques R. <JDurand@us.fujitsu.com>:
>> =========== current mark-up material:
>>
>> Schema and sample:
>>
>> http://www.oasis-open.org/apps/org/workgroup/tag/document.php?document_id=31406
>>
>> Current class diagram for our Test Assertions markup
>>
>> http://lists.oasis-open.org/archives/tag/200812/jpg00001.jpg
>>
>> =========== More detailed mark-up agenda:
>>
>>
>> 1. Restating the context of use of the mark-up:
>>
>> - embedding TAs inside a document & embedding TA sets, vs. a specific TA
>> "doc"
>> - kind of processing we expect on the mark-up? (overall objective)
>>
>> 2. Technical review:
>>
>> - The semantics of "multiples": how far should we go in specifying the
>> semantics of:
>> o multiple TestAssertionParts elements in a TA set header.
>> o multiple Predicate elements
>> o multiple prerequisite elements
>> o multiple Target elts.
>>
>> - Best Practices vs schema-supported:
>> o individual TA referencing a TA group: define the way "tags" are used for
>> this?
>> o prescription level: for "Property TAs": property used as a prefix? (should
>> we set it as @attribute?)
>> - Details:
>> o tag: Name = attribute?
>> o handling of extensibility (anyAttribute, xsdAny...) what is the best
>> approach?
>> o normative sources: case of "derived source": original source material vs.
>> derived source that the TA will actually address?
>> o in case of several targets, (should we provide means to identify a "main"
>> target?)
>>
>
>
>
> --
> Stephen D. Green
>
> Document Engineering Services Ltd
>
>
>
> http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice
>



-- 
Stephen D. Green

Document Engineering Services Ltd



http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice