1472   Schema does not validate existence of DA/BDA type

Created: 20 Jan 2016

Status: In Force (green)

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

Links:

Page: 96

Clause: 9.5.1

Paragraph:

Category: Issue for edition 2 of this part

Issue

Schema does not verify that the "type" referenced in a DA or BDA element actually exists. This limits the value of validating a SCL file against the schema.

The XSD schema language does not permit this type of validation unless SCL is restricted to ensure "id" attributes of DAType and EnumType are unique. However SCL has never clearly declared this restriction although text in 9.5.1 states "All types are uniquely identified by their type id"

Proposal

1. Allow schema to enforce text in 9.5.1 "... uniquely identified ..."
2. Modify DataTypeTemplates.XSD to perform the check for DA@type and BDA@type against DAType@id and EnumType@id
3. Add to DataTypeTemplates.XSD verification that id attributes are unique

See attachment for Ed2 schema

Discussion Created Status
19 May 16 In Force (green)
[According to WG10 decision taken in Cathedral City]
Proposal accepted:
- Add identity constraint in SCL to verify that the DA/BDA type refers to an EnumType or DAType. Nonetheless tools still need to check that the referred to type is of the right “kind”.
- Add identity constraint in SCL to verify that no two DataTypeTemplates have a same id. Impact: at import time, SCT shall rename conflicting DTTs. (Not an issue for ICTs.)

Applicable for Amd 2.1. 		25 Feb 16 Ballot Period

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1