1647   SDO@count definition inconsistent

Created: 04 Feb 2019

Status: Discussion (red)

Part: Part 6 (2009-12; Edition 2)

Links: #1648 DA@count definition needs restriction

Page: 123

Clause: 9.5.3

Paragraph: Table 46

Category: Issue for edition 2 of this part

Issue

Table 46 defines SDO@count to be an integer but the schema defines as integer or any-string-starting-with-lower-case-letter (tSDOCount).
1. schema and table text are not aligned
2. if string is desired then only "maxPts" should be allowed because that is the only reasonable symbolic reference

Note that the type for DA@count (tDACount) differs from tSDOCount but these should also be aligned

Proposal

1. Restrict tSDOCount to xs:integer or the literal string "maxPts"
2. Change text in Table 46 row "count" to align with the intent of Table 49 (DA element) row count "Optional. Shall state the number of array elements or reference the attribute stating this number in case that this attribute is an array. A referenced attribute named maxPts shall exist in the same type definition. The default value 0 states that the attribute is no array"

Discussion Created Status
I agree with the proposal to change the text in part 6 that usage of numeric value in count attribute is kept only for backward compatibility 07 Feb 19 Discussion (red)
maxPts is not the only attribute used to indicate the maximum number of elements into an array (VMH is using numHar).

Proposal is to change the text in part 6 (SDO and DA) to indicate that usage of numeric value in count attribute is kept only for backward compatibility
06 Feb 19 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 21.10.16.1