{"action":"created","issue":{"url":"https://api.github.com/repos/csarven/ldn/issues/44","repository_url":"https://api.github.com/repos/csarven/ldn","labels_url":"https://api.github.com/repos/csarven/ldn/issues/44/labels{/name}","comments_url":"https://api.github.com/repos/csarven/ldn/issues/44/comments","events_url":"https://api.github.com/repos/csarven/ldn/issues/44/events","html_url":"https://github.com/csarven/ldn/issues/44","id":180107389,"number":44,"title":"Coment on HTML example in section 3.1 Discovery","user":{"login":"nfreire","id":5079915,"avatar_url":"https://avatars.githubusercontent.com/u/5079915?v=3","gravatar_id":"","url":"https://api.github.com/users/nfreire","html_url":"https://github.com/nfreire","followers_url":"https://api.github.com/users/nfreire/followers","following_url":"https://api.github.com/users/nfreire/following{/other_user}","gists_url":"https://api.github.com/users/nfreire/gists{/gist_id}","starred_url":"https://api.github.com/users/nfreire/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nfreire/subscriptions","organizations_url":"https://api.github.com/users/nfreire/orgs","repos_url":"https://api.github.com/users/nfreire/repos","events_url":"https://api.github.com/users/nfreire/events{/privacy}","received_events_url":"https://api.github.com/users/nfreire/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-29T17:05:28Z","updated_at":"2016-09-29T17:41:37Z","closed_at":null,"body":"Hi,\r\n\r\nIn the example for \"Discovering an Inbox with a GET request to retrieve HTML.\"\r\nCurrentlym this is used:\r\n\r\n```\r\n<a href=\"/inbox/\" rel=\"http://www.w3.org/ns/ldp#inbox\">My inbox</a>\r\n```\r\n                            \r\n\r\nI was expecting that in HTML, the discovery of the inbox would be done from the header of the html with a link element. Something like:\r\n```\r\n<html xmlns=\"http://www.w3.org/1999/xhtml\">\r\n  <head>\r\n    <title>A home-page</title>\r\n    <link href=\"/inbox/\" rel=\"http://www.w3.org/ns/ldp#inbox\" />\r\n  </head>\r\n  <body>...</body>\r\n</html>\r\n```\r\n\r\nAn element <a> would display the link for human users, which may happen to be desired in some cases, but I would not expect it to be frequent. "},"comment":{"url":"https://api.github.com/repos/csarven/ldn/issues/comments/250538605","html_url":"https://github.com/csarven/ldn/issues/44#issuecomment-250538605","issue_url":"https://api.github.com/repos/csarven/ldn/issues/44","id":250538605,"user":{"login":"csarven","id":429987,"avatar_url":"https://avatars.githubusercontent.com/u/429987?v=3","gravatar_id":"","url":"https://api.github.com/users/csarven","html_url":"https://github.com/csarven","followers_url":"https://api.github.com/users/csarven/followers","following_url":"https://api.github.com/users/csarven/following{/other_user}","gists_url":"https://api.github.com/users/csarven/gists{/gist_id}","starred_url":"https://api.github.com/users/csarven/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/csarven/subscriptions","organizations_url":"https://api.github.com/users/csarven/orgs","repos_url":"https://api.github.com/users/csarven/repos","events_url":"https://api.github.com/users/csarven/events{/privacy}","received_events_url":"https://api.github.com/users/csarven/received_events","type":"User","site_admin":false},"created_at":"2016-09-29T17:41:37Z","updated_at":"2016-09-29T17:41:37Z","body":"Given this discovery option:\r\n> make a GET request on the target URL and, for RDF sources [RDF 1.1], the Inbox is the object of the predicate http://www.w3.org/ns/ldp#inbox.\r\n\r\nIt can actually be anywhere in the case of HTML if it is parsed as RDFa, i.e., `<link href=\"/inbox/\" rel=\"http://www.w3.org/ns/ldp#inbox\" />` is just as possible [1]. An HTML+RDFa parser (hence the body being an \"RDF source\") permits alternative possibilities, including but not limited to for example ` property=\"http://www.w3.org/ns/ldp#inbox\" href=\"/inbox/\"` on any resource. An LDN discoverer can essentially treat text/html as HTML+RDFa. We treat it as RDFa so that any subject URI (especially including URIs with fragment identifiers in the document) can have their own inbox. On the other hand, if it is parsed only as HTML, the \"subject\" of the relation (for `@rel`) can only be the resolved URL. With RDFa, we cover both possibilities. So, in the case of `<link href=\"/inbox/\" rel=\"http://www.w3.org/ns/ldp#inbox\" />` will have its subject (the \"target\") as the resolved URL in both HTML and HTML+RDFa parsing.\r\n\r\nIf content negotiation is in place, the human-visible link to an inbox will essentially list hyperlinks to each notification.\r\n\r\nWe can update the example to also mention the `<link href=\"/inbox/\" rel=\"http://www.w3.org/ns/ldp#inbox\" />` possibility if that makes it more clear/necessary/desirable.\r\n\r\n[1] and so is something like `<img about=\"/inbox/\" src=\"http://example.org/foo.png\" rev=\"http://www.w3.org/ns/ldp#inbox\"/>` (an image's inbox)"}}
{"actor":{"display_login":"csarven"}}