Mix of concerns in Requirment 2.1.3 (sic) : assumptions around files.. #12
Description
"Requirment 2.1.3 Each vocabulary MUST be presented in a single file which does not contain information other than that which is directly part of the vocabulary and the file is considered the point-of-truth"
The profile might (but perhaps should not) make a statement about a GRAPH - but it really should not constrain or know anything about FILES...
Is there really a separate constraint here - or should normal RDF mechanics and container or memberships properties be relied on to do the job they are designed to do..? I would end up needing to postprocess any validation outputs to remove any such spurious assumptions (or may inject some disabling flag into the rule?)