- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Sun, 13 Jan 2019 14:21:24 +0000
- To: public-dxwg-wg@w3.org
I like very much your proposal @kcoyle . Indeed it's hard and the progress looks minor, but I believe this word- and concept-smithing is precious. I would suggest to adapt your suggestion to an even more "requirement-focused" approach (as @jpullmann suggested earlier) by having a should/must for the first part of the requirement too. And keep classes and properties as example, in order to make the thing easier to relate to existing approaches "Profiles must be made up sets of elements, such as classes and properties, that define instance data or metadata. Profiles must have an unique identifier or name." I'm opting for "must" over "should" because I think this reflects the original requirement. I.e. for the corresponding use case I guess that a profile that doesn't bring a set of elements and that doesn't have a name is useless. The WG may argue about this later on, as you suggest, but I believe this is a fair re-writing of the requirement. We could add a note about it, calling for feedback. But at least we would have solved a first round of discussion about this requirement :-) -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/dxwg/issues/275#issuecomment-453833824 using your GitHub account
Received on Sunday, 13 January 2019 14:21:26 UTC