W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > July 2019

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

From: Stephen Richard via GitHub <sysbot+gh@w3.org>
Date: Tue, 02 Jul 2019 20:30:50 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-507833126-1562099448-sysbot+gh@w3.org>
I don't see the value of calling something a profile if it doesn't constrain, extend, or annotate some other specifications-- in which case it would just be another specification as noted by @agreiner  in the [e-mail thread](https://lists.w3.org/Archives/Public/public-dxwg-wg/2019Jul/0057.html).

@tombaker 's definitions could reduce  to 

> data specification
     A specification, with human- and/or
    machine-processable representations, that defines
    the content and structure of data used in a given
    context

> data profile 
    A data specification that  constrains, extends, or
    annotates other data specifications.
    
With the understanding that a specification must be identifiable (named) to be useful.  The name/identifier for either a data specification or data profile could be used for profile negotiation, or as the value for a 'dcat:conformsTo' property on a dcat:Resource or dcat:Distribution.

Annotate is interpreted to mean provide additional guidance or recommendations on usage to improve interoperability

-- 
GitHub Notification of comment by smrgeoinfo
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/963#issuecomment-507833126 using your GitHub account
Received on Tuesday, 2 July 2019 20:30:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 October 2019 00:15:54 UTC