Re: [dxwg] Profile negotiation [RPFN]

Hm, maybe this is where we are thinking differently: I’m thinking of profile-based negotiation as selecting a version of a dataset based on the profile it is designed to support. Here you mention selecting only the metadata that comes with the dataset. Suppose we have two profiles that use two different controlled value lists for the same variable. In my view, selecting profile 1 means that I will get different data than profile 2. The metadata will be different, too, but the fact that the actual values returned differ seems important.
-Annette

> On Jun 11, 2018, at 3:28 PM, Nicholas Car via GitHub <sysbot+gh@w3.org> wrote:
> 
> For the main example in [Use Case 239](https://github.com/w3c/dxwg/issues/239), I referred to the *views* or profiles of the metadata for a physical sample, AU239 (coincidental numbering). That sample has different metadata for different audiences (legacy XML format, current SOSA RDF etc.) but we certainly want the same URI for the sample. Currently we're using query string args to separate out the profiles but would like to support HTTP profile negotiation for smarter machine clients.
> 
> We have to use the same URI for the sample as one of the reasons we have URIs for samples at all is to de-duplicate references to the same sample and to do that we need to know that it's really the same thing which, although possible with multiple URIs, is much easier with a single one.
> 
> We're trying to say "metadata for sample AU239 is at URI <http://pid.geoscience.gov.au/sample/AU239> regardless of the form of metadata you want".
> 
> -- 
> GitHub Notification of comment by nicholascar
> Please view or discuss this issue at https://github.com/w3c/dxwg/issues/74#issuecomment-396407236 using your GitHub account
>

Received on Monday, 11 June 2018 22:59:35 UTC