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

How to handle company specific extensions #40

Closed
Sander3003 opened this issue Jul 19, 2021 · 1 comment
Closed

How to handle company specific extensions #40

Sander3003 opened this issue Jul 19, 2021 · 1 comment

Comments

@Sander3003
Copy link
Member

Companies need some way to add their own specific extions to the SCL files.

Questions:
Where to store the XSD extensions?
How to validate the XSD extsions?
How to use them?

@dlabordus
Copy link

I think the most important part for now is the validator and there is a separate issue for that there (com-pas/compas-scl-validator#116).

No need to have it in the JAXB2 Converter for now. And that's maybe also possible if a custom config is used and a JAR file is added for the Company Specific generated classes, but that probably also means some kind of custom component build by the company itself.

So close it for now.

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