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

[dxwg] List profiles for dynamic resources (#785)

From: Kam Hay Fung via GitHub <sysbot+gh@w3.org>
Date: Mon, 04 Mar 2019 00:11:08 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-416584473-1551658267-sysbot+gh@w3.org>
kamhayfung has just created a new issue for https://github.com/w3c/dxwg:

== List profiles for dynamic resources ==
In 7.1 (https://www.w3.org/TR/dx-prof-conneg/#listprofilehttplink), an assumption is made that the resource URIs will bear static media and profile type information in a Link header, such as the "prof1" and "ttl" parts in http://example.org/a/resource.prof1.ttl

What if a server supplies content dynamically and does not wish to hard-code media type information in the URIs? In other words, would the following header also be a valid link to list the profiles for a resource?

```
Link: <http://example.org/a/resource>; rel="self"; type="text/turtle"; profile="urn:example:profile:1",
  <http://example.org/a/resource>; rel="alternate"; type="text/turtle"; profile="urn:example:profile:2",
  <http://example.org/a/resource>; rel="alternate"; type="application/xml"; profile="urn:example:profile:1",
  <http://example.org/a/resource>; rel="alternate"; type="application/xml"; profile="urn:example:profile:2",
  <http://example.org/a/resource>; rel="alternate"; type="text/html"
```

For comparison, this is the example Link in the draft specification:
```
Link: <http://example.org/a/resource.prof1.ttl>; rel="self"; type="text/turtle"; profile="urn:example:profile:1",
  <http://example.org/a/resource.prof2.ttl>; rel="alternate"; type="text/turtle"; profile="urn:example:profile:2",
  <http://example.org/a/resource.prof1.xml>; rel="alternate"; type="application/xml"; profile="urn:example:profile:1",
  <http://example.org/a/resource.prof2.xml>; rel="alternate"; type="application/xml"; profile="urn:example:profile:2",
  <http://example.org/a/resource.html>; rel="alternate"; type="text/html"
```


Please view or discuss this issue at https://github.com/w3c/dxwg/issues/785 using your GitHub account
Received on Monday, 4 March 2019 00:11:09 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 14 March 2019 16:33:09 UTC