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 documentation (definitions) for data constraints (simple type facets). #12

Open
smrubin opened this issue Jun 21, 2017 · 1 comment

Comments

@smrubin
Copy link
Contributor

smrubin commented Jun 21, 2017

In the JSON schema generation, when a facet is included (e.g. enum), it is only bringing that data constraint's values.

For example, an enum might have the value: VA, NC, and SC. But it would be nice to include their definitions as well, which are Virginia, North Carolina, and South Carolina, respectively.

These definitions also exist for other facets besides enum, such as pattern, maxInclusive, minInclusive, etc.

@mark-aamva
Copy link

I think the documentation of code values is really needed. NIEM contains some quite cryptic code lists, e.g. ncic:VMOCodeSimpleType

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

No branches or pull requests

2 participants