- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Sep 2019 00:57:27 +0000
- To: public-dxwg-wg@w3.org
rob-metalinkage has just created a new issue for https://github.com/w3c/dxwg: == Provide a safe home for definition of "data profile" == Profiles include "functional" profiles, such as examples for OGC services (a prime motivating use case for design and implementation of profiles) - and the Conneg document needed to distinguish between profiles of the specfication itself and the data profiles that are being negotiated. Proposal: Add a subclass of Profile called DataProfile which carries the "data profile" definition agreed and does not restrict the usefulness of the general model. Pros: 1. makes it clear that profiles _may_ be data profiles 2. makes it clear that other types of profiles may exist 3. makes it possible to distinguish that a particular profile is specifically about requirements for data content rather than functional behaviours. Cons: 1. (now redundant ) not originally modelled because "data profile" wasnt originally an identifiable thing with an agreed definition 2. begs the question whether other sub-types should be modelled 3. redundant if systems declare what the profile is about in other ways Those "cons" I think can now be dismissed - we dont have time or motivations to agree definitions for other sub-types and absence doesnt impact utility of what is modelled, and we dont have canonical ways to describe the scope of a dct:Standard available, so this subClass has semantic value. Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1072 using your GitHub account
Received on Friday, 13 September 2019 00:57:28 UTC