Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Rule 4-15 Clarifying text #22

Open
cchipman6 opened this issue Mar 26, 2020 · 0 comments
Open

Add Rule 4-15 Clarifying text #22

cchipman6 opened this issue Mar 26, 2020 · 0 comments
Assignees
Labels

Comments

@cchipman6
Copy link

The following comment was received during the review of the NIEM-based Code List Specification being developed for the NATO Core Data Framework (NCDF):

Specifically for Example D-5 for the complex binding, I wonder whether the elementName attribute should be e.g. “nc:VehicleMakeAbstract”, as that is an element of the nv:VehicleType used for the Vehicle element. And it is the substitution group used for the extension element “ext:VehicleMakeCode”. Looking at Rule 4-15, current wording is not clear whether the value of elementName needs to be an element that is in a substitution group, of is the element that is the base of a substitution group. I recommend clearer rewording.

Proposed solution: Rule 4-15 states that the bound element is the first element in the substitution group named by elementName. Each element is in its own substitution group.
Add text after rule 4-15 clarifying that each element is in its own substitution group, and that elementName may indicate a concrete element or a different element within the substitution group of the named element.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants