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

Blog Post: XML Mapping - Question 8: Validation #105

Open
PwC-Arthur opened this issue Apr 17, 2024 · 0 comments
Open

Blog Post: XML Mapping - Question 8: Validation #105

PwC-Arthur opened this issue Apr 17, 2024 · 0 comments
Labels
Blog-XMLMapping A label to specifically discuss the Style Guide blog article on XML and mapping.

Comments

@PwC-Arthur
Copy link

In the context of the webinar on the review of the Core Vocabularies and the Style Guide blog post on XML Schema the following question was raised:

  • Currently SEMIC does not provide an XML schema validation service for the Core Vocabularies such as it is done for ITB CPSV-AP and DCAT-AP SCHACL validators. Is this type of service needed? [Link to slides] [Link to Blog post]

The feedback below was provided during the webinar:

  • As there are many existing XML Schema validators the need for a specialised instance is not necessary. That is, if the provided XSDs work with existing validators.
  • XSD validation and Schematron are support by the ITB.
  • In the case of Finland an XSD is generated, but no validation service is available. Their users heavily rely on API serialisations and are less interested in XML.

The community members are encouraged to use this issue as a platform to provide additional feedback on this question.

@PwC-Arthur PwC-Arthur added the Blog-XMLMapping A label to specifically discuss the Style Guide blog article on XML and mapping. label Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blog-XMLMapping A label to specifically discuss the Style Guide blog article on XML and mapping.
Projects
None yet
Development

No branches or pull requests

1 participant