{"issue":{"created_at":"2011-09-28T12:25:07Z","state":"closed","updated_at":"2011-11-29T05:08:26Z","comments":2,"user":{"gravatar_id":"d1eed9d5ddfc6253f0583d50af00b2d9","id":456407,"url":"https://api.github.com/users/lanthaler","avatar_url":"https://secure.gravatar.com/avatar/d1eed9d5ddfc6253f0583d50af00b2d9?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"lanthaler"},"body":"@type is used to set the type of the active subject.\r\n@datatype is used to specify the datatype for a literal.\r\n\r\nSince @datatype has always to be used with @literal in an object it is kind of redundant. E.g. consider the following:\r\n```\r\n...\r\n  { \"@literal\": \"4.8\", \"@datatype\": \"xsd:decimal\" }\r\n...\r\n```\r\n\r\nIt would be invalid to create something like\r\n```\r\n{ \"@literal\": \"Markus\", \"@type\": \"foaf:Person\" }\r\n```\r\n\r\nI understand that in a RDF world the distinction is necessary, but in JSON-LD we do not need to distinguish the two keywords as they can't be misinterpreted.\r\n\r\nSo I would like to propose to merge @datatype and @type to @type (ISSUE-31). I think this won't cause any problems in the already implemented algorithms and just require a change from @datatype to @type. The reason behind this is that both, @type and @datatype, specify the \"data type\" of a construct, the only difference is that the one addresses subjects while the other addresses objects.\r\nSince simplicity is one of the design goals of JSON-LD, the reduction of keywords is desirable.\r\n","assignee":null,"id":1763833,"number":31,"labels":[{"name":"spec-design","color":"e10c02","url":"https://api.github.com/repos/json-ld/json-ld.org/labels/spec-design"}],"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"title":"Merge @type and @datatype","closed_at":"2011-11-29T05:08:26Z","html_url":"https://github.com/json-ld/json-ld.org/issues/31","url":"https://api.github.com/repos/json-ld/json-ld.org/issues/31","milestone":null},"action":"closed"}