W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > June 2018

Re: [dxwg] Profile negotiation [RPFN]

From: Ruben Verborgh via GitHub <sysbot+gh@w3.org>
Date: Fri, 01 Jun 2018 21:47:20 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-394017998-1527889639-sysbot+gh@w3.org>
> I understand that the motivation for profile negotiation is that some users want to be able to use the same URL for versions of a dataset that conform to different profiles.

No, the motivation is to have the same resource available in different profiles.
And resources on the Web happen to be identified by URLs.

Note that each representation still _can_ have its own URL. We will just provide the mechanism to get from resource to representation.

> Can anyone explain why some users want that?

- to get from a resource to its representations
- to see what other representations a resource has

> It does work to model the versions as representations of a resource, but it would also work to model them as separate resources (as in Ruben's suggestion above).

Both models are the exact same, really.

To understand this, it's important to see that the "representation" concept is a relative notion. E.g., in the sentence "A is a representation of B", B the resource that A  is the representation of. However, A is a resource in its own right.

An example to clarify:

- http://example.org/weather/amsterdam/2018-06-01 is the weather report for Amsterdam for 1 June
- http://example.org/weather/amsterdam/2018-06-01.html is the weather report for Amsterdam for 1 June in HTML

The latter is a representation of the former. Both are resources (regardless of whether the latter has its own URL or not).

-- 
GitHub Notification of comment by RubenVerborgh
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/74#issuecomment-394017998 using your GitHub account
Received on Friday, 1 June 2018 21:47:23 UTC

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