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

Why can't I add Complex Types to my Subset #25

Open
CB2 opened this issue Jun 30, 2017 · 3 comments
Open

Why can't I add Complex Types to my Subset #25

CB2 opened this issue Jun 30, 2017 · 3 comments

Comments

@CB2
Copy link
Member

CB2 commented Jun 30, 2017

Question/Feedback received via NIEM.gov/contact-us:

I'm trying out Movement for JSON. I want to select both IdentificationEffectiveDate (nc:DateType) and IdentificationExpirationDate (nc:DateType). I can expand each of them and select Date. I don't understand what I do to get the EffectiveDate and ExpirationDate. Can this be done in Movement? How?

@CB2
Copy link
Member Author

CB2 commented Jun 30, 2017

Good Question! Movement adopted some business rules based on user feedback--a high level overview can be found in the "Build your exchange" section our Movement Overview page.

Currently, users are not allowed to select NIEM complex types, such as IdentificationEffectiveDate and IdentificationExpirationDate. The complex types cater to the structure and relationship of the NIEM model instead of the validation aspects needed from a schema. We were hoping that by allowing the user to only select NIEM simple types--in this case, any of the synonym terms found under DateRepresentation--it would create a more approachable environment for the user and focus on the intended JSON Schema solution.

You can easily find DateRepresentation in any of the IdentificationEffectiveDate and IdentificationExpirationDate details page. Here you can select any of the simple type synonym terms to validate your JSON data.

That said, we are still in the beta stage of the tool because we want broad user feedback on how things should be. We had to start somewhere, which is the lightweight use case. Please let us now if the current version of Movement does not accomplish what you were expecting from the tool and we will take into account for future iterations. For transparency, you can easily track the status of backlog items once our developers and tool contributors start addressing them.

@CB2
Copy link
Member Author

CB2 commented Jun 30, 2017

Question/Feedback received via NIEM.gov/contact-us:

I understand the desire to only handle simple types in JSON. However NIEM uses complex types for many simple elements. E.g. all date elements use the DateRepresentation to support different flavors of dates. The problem is Momentum only provides a selection for the representation, and wont offer the element to be selected. So in my example I can only select one element called Date when I really need multiple elements for different data, e.g. IdentificationEffectiveDate and IdentificationExpirationDate.

My thought is Momentum needs to allow the selection of a field like IdentificationExpirationDate and to allow the user to select its representation. Then output a schema containing IdentificationExpirationDate with the selected representation.

Mark

@CB2
Copy link
Member Author

CB2 commented Jun 30, 2017

This is exactly the feedback we need. So, thank you!

Over the summer months we hope to collect input from the community to feed further refinements of the tool. Ideally, we'll have you and others who share the same idea to help us craft the functionality requirements so we can hand it off to the development team or hold a hackathon to get it built. For example, I'm not sure IdentificationExpirationDate should have an 'add to subset' button, but there is value in setting the right business rules so that it is automatically included in the schema output.

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

No branches or pull requests

1 participant