Re: [dxwg] Requirement: Profiles may be written in or may link to a document or schema in a validation language (ShEx, SHACL, XMLschema). [ID41] (5.41)

I think the idea was that the validation rules, in a validation language like shacl or shex or xsd, could be a separate file, but that the profile would provide a URL or (if in RDF) a property with the identifier of the validation file as its value. If the profile is itself expressed as some form of code (k/v pairs, xml, rdf, etc.) then my preference would be that there be an explicit metadata element for the validation document, not just something like "dct:related". You'd want to be able to know precisely if the profile has an actionable validation file somewhere.

Where I see a hitch is that there are validation descriptions, like xsd, shacl, and shex, which are files that define validation but need software to run them, and then there are actual validation programs that someone may provide. In my community there are a lot of home-grown validation programs for metadata. I don't know if people are sharing those, but they are of a different nature from the validation files that are input to to a program like schematron or topbraid.

-- 
GitHub Notification of comment by kcoyle
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/279#issuecomment-417056655 using your GitHub account

Received on Wednesday, 29 August 2018 18:27:07 UTC