- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Nov 2018 16:14:56 +0000
- To: public-dxwg-wg@w3.org
Actually I would argue against 'comprise' in @jpullmann 's suggestion because it feels strange to say that profile comprises a collection with a name, while the original idea is that the name of the collection is the name of the profile itself. @kcoyle 's rewording fixes this, but then the name is gone! Then the fact that the elements of a profile are from published vocabularies is probably relevant but I would prefer to rely on other existing requirements to carry this instead of extending the scope of this one. E.g. we could piggyback on the one that says that profiles are based on existing specifications. Such a requirement is probably a better fit, as profiling a specification is probably nonsensical if that specification has not been published anywhere. And talking about @agreiner I guess she may argue about restricting the scope to 'metadata' - she has made a comment about this for the intro of the Profile guidance ;-) -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/dxwg/issues/275#issuecomment-440331236 using your GitHub account
Received on Tuesday, 20 November 2018 16:14:58 UTC