Validation of SHOULD NOT property

Hi All,

I would like to know what is the expected behaviour of the validator for a SHOULD NOT property. The options are either to not validate as the property is present or validate because it is permissible for the property to be present.

The specific example at hand is the void:sparqlEndpoint property on an RDF distribution level description. We have stated that this is a SHOULD NOT property since there is a requirement to maintain the SPARQL endpoint at the specified location with the specific distribution file. However the validator code does not permit the generation of warnings (although this would be a nice feature in the future). So currently we either have to accept a void:sparqlEndpoint statement on a distribution level description as valid or invalid.

With SHOULD properties we accept a description as valid if the statement is there in the correct form or not present.

With MUST NOT properties we do not accept a description which contains them.

This is captured in the GitHub issue tracker for the validator
https://github.com/AlasdairGray/HCLSValidator/issues/13

Thoughts please,

Alasdair

Alasdair J G Gray
Lecturer in Computer Science, Heriot-Watt University, UK.
Email: A.J.G.Gray@hw.ac.uk<mailto:A.J.G.Gray@hw.ac.uk>
Web: http://www.alasdairjggray.co.uk
ORCID: http://orcid.org/0000-0002-5711-4872
Telephone: +44 131 451 3429
Twitter: @gray_alasdair








----- 
We invite research leaders and ambitious early career researchers to 
join us in leading and driving research in key inter-disciplinary themes. 
Please see www.hw.ac.uk/researchleaders for further information and how
to apply.

Heriot-Watt University is a Scottish charity
registered under charity number SC000278.