{"action":"created","issue":{"url":"https://api.github.com/repos/alps-io/spec/issues/67","labels_url":"https://api.github.com/repos/alps-io/spec/issues/67/labels{/name}","comments_url":"https://api.github.com/repos/alps-io/spec/issues/67/comments","events_url":"https://api.github.com/repos/alps-io/spec/issues/67/events","html_url":"https://github.com/alps-io/spec/issues/67","id":59735286,"number":67,"title":"clean up text on id & name, IANA, etc.","user":{"login":"mamund","id":38344,"avatar_url":"https://avatars.githubusercontent.com/u/38344?v=3","gravatar_id":"","url":"https://api.github.com/users/mamund","html_url":"https://github.com/mamund","followers_url":"https://api.github.com/users/mamund/followers","following_url":"https://api.github.com/users/mamund/following{/other_user}","gists_url":"https://api.github.com/users/mamund/gists{/gist_id}","starred_url":"https://api.github.com/users/mamund/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mamund/subscriptions","organizations_url":"https://api.github.com/users/mamund/orgs","repos_url":"https://api.github.com/users/mamund/repos","events_url":"https://api.github.com/users/mamund/events{/privacy}","received_events_url":"https://api.github.com/users/mamund/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/alps-io/spec/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-04T01:13:58Z","updated_at":"2015-03-04T01:36:24Z","closed_at":null,"body":"2.2.7.3. Link Relation Values and 'id' or 'name'\r\n\r\nI see a problem here.  It's all very well to say \"If the resulting link relation type is the same as a registered relation type, the descriptor MUST not change the meaning of the IANA relation type.\".\r\n\r\nBut an implementer cannot know what new relation types will be implemented in future.  An application that is conformant at the time of implementation may be rendered non-conformant by subsequent IANA registrations.  I think this is not consistent with progressing the notion of \"software engineering on the scale of decades\" which I'm guessing is a motivation for this work.\r\n\r\nOne possible approach might be to require any non-registered value to be a URI or URI reference, and introduce a distinguishable prefix for local ids.  (e.g. use fragment syntax such as '#idvalue' or a common URN prefix such as 'urn:ietf:alps:id:idvalue'.  I'm not suggesting these as specific solutions as I don't yet understand enough of the scope of what you're proposing, just as examples of alternative approaches to contemplate.)\r\n\r\n/via Graham Klyne"},"comment":{"url":"https://api.github.com/repos/alps-io/spec/issues/comments/77080647","html_url":"https://github.com/alps-io/spec/issues/67#issuecomment-77080647","issue_url":"https://api.github.com/repos/alps-io/spec/issues/67","id":77080647,"user":{"login":"mamund","id":38344,"avatar_url":"https://avatars.githubusercontent.com/u/38344?v=3","gravatar_id":"","url":"https://api.github.com/users/mamund","html_url":"https://github.com/mamund","followers_url":"https://api.github.com/users/mamund/followers","following_url":"https://api.github.com/users/mamund/following{/other_user}","gists_url":"https://api.github.com/users/mamund/gists{/gist_id}","starred_url":"https://api.github.com/users/mamund/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mamund/subscriptions","organizations_url":"https://api.github.com/users/mamund/orgs","repos_url":"https://api.github.com/users/mamund/repos","events_url":"https://api.github.com/users/mamund/events{/privacy}","received_events_url":"https://api.github.com/users/mamund/received_events","type":"User","site_admin":false},"created_at":"2015-03-04T01:36:24Z","updated_at":"2015-03-04T01:36:24Z","body":"i want to make sure authors don't attempt to *redefine* the intent/meaning of existing rel values. and i'd like to do that w/ a minimum of hassle ;)\r\n\r\nthere are a couple things to consider: \r\n - reg'd *where* (IANA, microformats, RDF ontology, etc.)\r\n - reg'd *when* (Graham's point, i think) maybe when i created the profile this was not a reg'd word, but two years later is now *is* What is to be done?\r\n\r\nyes, i'd like to make sure we don't create a HAL vortex ;) and i still want to come up w/ a clean solution. \r\n\r\nsadly, _namespaces_ come to mind ;<  RFC5988-style URIs solve that problem, right?\r\n\r\n\r\n"}}