-
Notifications
You must be signed in to change notification settings - Fork 26
Closed
Description
Since LDP officially supports JSON-LD as a 'SHOULD', it feels like the WAC spec should too, right? But when trying to write unit test for ACL docs in JSON-LD format, I ran into this problem:
$ curl -H "Accept: application/ld+json" http://www.w3.org/ns/auth/acl
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>406 Not Acceptable</title>
</head><body>
<h1>Not Acceptable</h1>
<p>An appropriate representation of the requested resource /ns/auth/acl could not be found on this server.</p>
Available variants:
<ul>
<li><a href="acl.ttl">acl.ttl</a> , type text/turtle</li>
<li><a href="acl.rdf">acl.rdf</a> , type application/rdf+xml</li>
<li><a href="acl.n3">acl.n3</a> , type text/n3</li>
</ul>
</body></html>Should we ask the webmasters of w3.org to publish a JSON-LD representation of http://www.w3.org/ns/auth/acl?
akuckartz and leinue
Metadata
Metadata
Assignees
Labels
No labels