- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Jul 2019 23:29:05 +0000
- To: public-dxwg-wg@w3.org
I think I can live with this - (its two definitions - but it has proven necessary to state that there is a special case of specification that relates to "data used in a given context" - this seems to match OK with "certain documents" in the IETF version - and propose a useful clarification. The only problem is that it may still be too hard to see how the (undefined) term "usage" resolves the ambiguity between re-use and profiling - you need to go through to the end of the data specification definition to the "data in a given context" and successfully infer that therefore a profile must also be constraining the same "given context". IMHO it would be useful to state this up front so the definition implications are clear, and vocab re-use is not swept up in a too broad definition of profiles. I therefor suggest something along the lines of A data specification that constrains, extends, combines, or provides guidance or explanation about the usage other data specifications whereby the "given context" or the profile remains compliant with these "base" specifications. without this explicit clause it will be too hard for the definitions to be interpreted as a whole, and the ambiguity of the word "usage" is too great - would i be using something if I made a statement like? :myClass owl:disjointWith you:yourClass (yes - i'd be using it to clarify semantics of the thing i was defining - but i'm not profiling it in any sense) (it would be easier if we had a definition equivalent to "conformanceClass" that we could make simple statements about, but I dont beleive we have identified an acceptable term for this "given context" -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/963#issuecomment-510689913 using your GitHub account
Received on Thursday, 11 July 2019 23:29:06 UTC