{"action":"created","issue":{"url":"https://api.github.com/repos/json-schema-org/json-schema-spec/issues/48","repository_url":"https://api.github.com/repos/json-schema-org/json-schema-spec","labels_url":"https://api.github.com/repos/json-schema-org/json-schema-spec/issues/48/labels{/name}","comments_url":"https://api.github.com/repos/json-schema-org/json-schema-spec/issues/48/comments","events_url":"https://api.github.com/repos/json-schema-org/json-schema-spec/issues/48/events","html_url":"https://github.com/json-schema-org/json-schema-spec/issues/48","id":177156442,"number":48,"title":"Does anyone actually use JSON Hyper-schema","user":{"login":"awwright","id":437517,"avatar_url":"https://avatars.githubusercontent.com/u/437517?v=3","gravatar_id":"","url":"https://api.github.com/users/awwright","html_url":"https://github.com/awwright","followers_url":"https://api.github.com/users/awwright/followers","following_url":"https://api.github.com/users/awwright/following{/other_user}","gists_url":"https://api.github.com/users/awwright/gists{/gist_id}","starred_url":"https://api.github.com/users/awwright/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/awwright/subscriptions","organizations_url":"https://api.github.com/users/awwright/orgs","repos_url":"https://api.github.com/users/awwright/repos","events_url":"https://api.github.com/users/awwright/events{/privacy}","received_events_url":"https://api.github.com/users/awwright/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/json-schema-org/json-schema-spec/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/json-schema-org/json-schema-spec/milestones/1","html_url":"https://github.com/json-schema-org/json-schema-spec/milestones/draft-5","labels_url":"https://api.github.com/repos/json-schema-org/json-schema-spec/milestones/1/labels","id":1225155,"number":1,"title":"draft-5","description":"","creator":{"login":"awwright","id":437517,"avatar_url":"https://avatars.githubusercontent.com/u/437517?v=3","gravatar_id":"","url":"https://api.github.com/users/awwright","html_url":"https://github.com/awwright","followers_url":"https://api.github.com/users/awwright/followers","following_url":"https://api.github.com/users/awwright/following{/other_user}","gists_url":"https://api.github.com/users/awwright/gists{/gist_id}","starred_url":"https://api.github.com/users/awwright/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/awwright/subscriptions","organizations_url":"https://api.github.com/users/awwright/orgs","repos_url":"https://api.github.com/users/awwright/repos","events_url":"https://api.github.com/users/awwright/events{/privacy}","received_events_url":"https://api.github.com/users/awwright/received_events","type":"User","site_admin":false},"open_issues":3,"closed_issues":9,"state":"open","created_at":"2015-07-25T07:48:09Z","updated_at":"2016-10-08T09:45:00Z","due_on":"2016-10-12T00:00:00Z","closed_at":null},"comments":52,"created_at":"2016-09-15T11:52:55Z","updated_at":"2016-10-11T01:22:11Z","closed_at":null,"body":"There's a lot of broken features defined in JSON Hyper-Schema, I want to ask implementors how much I can be allowed to \"break\" (i.e. make compliant with normative references).\r\n\r\nMostly things like quirks about how it defines URI templates, uses \"rel\", and uses \"method\".\r\n\r\nAnyone?"},"comment":{"url":"https://api.github.com/repos/json-schema-org/json-schema-spec/issues/comments/252787201","html_url":"https://github.com/json-schema-org/json-schema-spec/issues/48#issuecomment-252787201","issue_url":"https://api.github.com/repos/json-schema-org/json-schema-spec/issues/48","id":252787201,"user":{"login":"awwright","id":437517,"avatar_url":"https://avatars.githubusercontent.com/u/437517?v=3","gravatar_id":"","url":"https://api.github.com/users/awwright","html_url":"https://github.com/awwright","followers_url":"https://api.github.com/users/awwright/followers","following_url":"https://api.github.com/users/awwright/following{/other_user}","gists_url":"https://api.github.com/users/awwright/gists{/gist_id}","starred_url":"https://api.github.com/users/awwright/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/awwright/subscriptions","organizations_url":"https://api.github.com/users/awwright/orgs","repos_url":"https://api.github.com/users/awwright/repos","events_url":"https://api.github.com/users/awwright/events{/privacy}","received_events_url":"https://api.github.com/users/awwright/received_events","type":"User","site_admin":false},"created_at":"2016-10-11T01:22:11Z","updated_at":"2016-10-11T01:22:11Z","body":"@handrews For any problems you can identify with JSON Hyper-schema, I would strongly encourage you to file an issue describing the problem. Discussion here is fine too, but all the questions and responses I'm posing here are aimed at answering the question I opened this issue specifically to ask.\r\n\r\nI'm afraid the definitions used so far are more complex than they need to be, let me put forward these definitions:\r\n\r\n* A _resource_ is anything that can uniquely be identified by a URI (so, pretty much anything). It can be anything from a JSON document, to a record in a database, to an employee, to a point in time. I think for JSON Schema, the HTTP definition is suitable <https://tools.ietf.org/html/rfc7231#section-2>, and some additional discussion is available from Wikipedia: <https://en.wikipedia.org/wiki/Web_resource>. Resources can be identified by any number of URIs.\r\n\r\n* An _information resource_ (IR) is any string of octets described by a media type. A png image and a JSON document would be information resources. Depending on the context, IRs might even be of indefinite length (for example, a live video stream).\r\n\r\n* A _document_ is another name for an IR. I additionally make the distinction that a document has a meaning given by its media type, and has a known length.\r\n\r\n* A _non-information resource_ (NIR) is any resource that's not an IR. For example, a blog post record in a relational database, or a company. Sometimes also known as an _abstract resource_.\r\n\r\n* HTTP also calls an information resource a _representation_, and allows for the possibility that a URI can identify both an NIR and IR at the same URI: I see an \"author\" link relation (pointing to the author of the post), and when I dereference it, the server returns back an IR that has the same URI (e.g. a webpage _about_ the author of the post). For most people on the Web, this isn't problematic. For the other 20% of us, there's a long-standing problem called httpRange-14. The definition of \"resource\" has changed slightly as we've had to iron out problems, but when REST says \"Manipulating resources through representations\", today we take this to mean that we can edit a JSON representation of a blog post, and the HTML representation will change too; or that I can use PUT to change the physical flipped state of a light switch.\r\n\r\n* Older versions of HTTP also used the term _variant_, which I still use from time to time when discussing Content-Type negotiation and the Content-Location header. I don't anticipate this coming up in JSON Schema, though.\r\n\r\n* I've refined the definition of \"instance\" and \"schema\" in the current HEAD: In the context of a specific validation or annotation operation, an _instance_ is a JSON document interpreted according to the JSON Schema data model against a _schema_.\r\n\r\n* A _collection_ is a closed listing of _member_ resources.\r\n\r\n* A _class_ or _type_ is an open set of _instance_ resources. A JSON Schema is a particular kind of class.\r\n\r\n* A _profile_ is a particular kind of class that tells us how to interpret a document.\r\n"}}
{"actor":{"display_login":"awwright"}}