Re: [dxwg] Revisiting the definition of "profile" (#963)

RE: Constraints

@aisaac when you say:

>my problem is really that my extensions are constraints on the data.
I think we're talking about "constraints/restriction over an existing specification" (your sense) and "constraints over data, independently on whether they are derived from an existing specification

I suspect that we are tripping over the fact that we are sometimes talking about different things:

1) the profile in relation to an existing specification, where the profile can constrain or expand prior vocabularies
2) the profile in relation to the data it defines, where it the profile defines/constrains the data

So we should talk about these two separately in the definition. First, what the profile is in relation to other specifications, and then its role in defining/constraining the data for a use or application. If we make that clear then I think we may have solved the confusion we have about "constrain" - that a profile's purpose is the constrain some data, but it does so by being based on prior specifications and may limit or expand on those.



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

Received on Tuesday, 2 July 2019 17:48:00 UTC