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

Make json schemas from CII XSDs in https://unece.org/trade/uncefact/mainstandards #63

Open
nissimsan opened this issue Nov 1, 2021 · 2 comments

Comments

@nissimsan
Copy link
Contributor

Can we use our machinery to transform the schemas available https://unece.org/trade/uncefact/mainstandards into JSON schemas.

Preferably, but perhaps secondarily, including JSON-LD links to https://service.unece.org/trade/uncefact/vocabulary/uncefact/.

I know there are a lot of schemas, and perhaps this requires a ticket for each. So focusing this ticket on the Cross Industry Invoice schema: https://service.unece.org/trade/uncefact/publication/Supply%20Chain%20Management/CrossIndustrySCRDM/Invoice/Invoice%20CII/XSD/Schema.zip
Others can be added subsequently once the tooling is in place.

@AndreasPvd
Copy link

I like the idea very much to add standardised JSON schemas published by UN/CEFACT for the CrossIndustryDocuments.

As the project is still under progress and still has quite some open issues I would be cautious to use results of this project at this time in production environment. Especially in the conversion of some XML specific artefacts to JSON schema not all questions are solved yet. Using the vocab as a start would make things worse as there currently happens a lot of undocumented magic in creating the vocab.

Maybe it would be better to start a project on this short hand. Then it could be an official UN/CEFACT output. You would get my support in doing so. This would assure maintenance and an harmonised standard if the project includes the movement to the library maintenance team. Else it will only be a "one-shot" creating a new non-standard.

What do you think?

@nissimsan
Copy link
Contributor Author

Thanks @AndreasPvd,

The formalities you describe are absolutely needed in the long run. I do suggest we start from the technical side though and determine what output can be generated before standing up a project around it. There are surely many things we need to learn before understanding and sharing a mental model of what this suggestion.

Leading with example is not the same as a "one-shot". It's just a discussion of the order of things. :)

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

No branches or pull requests

2 participants