The following comment was received during the review of the NIEM-based Code List Specification being developed for the NATO Core Data Framework (NCDF):
Example D-5 documents two methods of binding at schema-time a code list in the same example. This is a bit unclear at first, since from the example you can’t say whether both methods are needed in all cases, of whether they are indeed alternatives, as intended. I would suggest to split it in two examples.
Proposed solution: Split Schema examples into 2 separate appendices; one defining the complex code list binding, and the other defining 2 simple code list bindings. This will entail additional narrative to clarify that they describe different sets of constraints.
The following comment was received during the review of the NIEM-based Code List Specification being developed for the NATO Core Data Framework (NCDF):
Example D-5 documents two methods of binding at schema-time a code list in the same example. This is a bit unclear at first, since from the example you can’t say whether both methods are needed in all cases, of whether they are indeed alternatives, as intended. I would suggest to split it in two examples.
Proposed solution: Split Schema examples into 2 separate appendices; one defining the complex code list binding, and the other defining 2 simple code list bindings. This will entail additional narrative to clarify that they describe different sets of constraints.