Re: [dxwg] Axiomitise transitivity of dct:conformsTo through isProfileOf relationships (#844)

We've been around the block on this one more than once. (#507, #660) The problem here is what "conforms to" and "profile of" mean. What happens when I have one profile with A, B, and C properties, and profile of that profile that has properties A, B, C, D, E? This is the case with the DCAT-AP variations that I have seen. Doesn't conformance depend on what the profile creators says is conformance? A validation schema that is coded for the former profile would not validate the latter if the profile is seen as "closed" (does not allow unlisted properties). What if one profile says A is required and another says A is optional? Does that mean that they can't say that one is a profile of the other? 

Unfortunately, we need to resolve the questions brought up here and in the other issues. I don't see anything "axiomatic" yet in how these two properties are defined.

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

Received on Monday, 9 September 2019 04:17:28 UTC