Re: [dxwg] A profile may be (partially) "implemented" by "schemas" (in OWL, SHACL, XML Schema...) that allow different levels of data validation [ID37] (5.37)

@smrgeoinfo your interpretations are interesting, but they don't apply here. The requirement here is more basic. "(partially)" was just added because we needed to accommodate cases where the "implementation" of a profile according to a schema language would fail to express all the validation rules, just because the schema language is not expressive enough. For example, XML Schema can't express everything that SHACL allows to express. And SHACL itself may fail to express what a profile wants to express. So the "partial" coverage would happen more by accident than by design. 

This said what you suggest is quite certainly a valid concerns. But it should be raised as a different requirement then, because our use case 37 does not support it.

@kcoyle @smrgeoinfo @nicholascar I like the idea of a 'center' but I'd advise to not spend time on it as it's a risky notion. Taking a basic, real-world counter-example that every profile has such 'center': in the Europeana Data Model, one could see the 'center' to be the human-readable spec. But when we embarked on creating an XML Schema for our model, we realized this schema would have to impose an order on the elements in the data, which we didn't want! So in some respects the XML Schema (in the line of my remark above) has failed to implement everything we wanted to implement. But on other respects it actually forced us to an implementation that has more than what an "ideal" implementation would have.

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

Received on Sunday, 18 November 2018 22:49:26 UTC