ref, complexType in element-tag, documentation in non-leaf-tags - No #8 #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey, sry for the delay.
well actually I would like to send you an example, but I dont find a email. Thats why I post an example here and would like to ask you, to edit/remove the post (if possible), so the example isnt available all the time ^^. Or let me know, when you have copied the files for testing.
Thats a part of a complex xsd-file, that was created with the profession tool "Visual Paradigm". I just mention this point to point out, that the schema has to be valid.
In these two files you see, which transformations I have to do atm, to get a useable json-schema-file as output with all specified fields. (and there is an instance (complexType) encapsulated in an element-tag)
Thanks for an answer!