[OASIS Issue Tracker] Created: (ODATA-249) "Kind" property should be optional for EntitySets in JSON Service Documents

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

"Kind" property should be optional for EntitySets in JSON Service Documents
---------------------------------------------------------------------------

                 Key: ODATA-249
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-249
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData JSON Format v1.0
    Affects Versions: WD01
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: WD01


In JSON, service documents are returned as an array containing objects that represent entitysets and named entities, as shown below. By far the most common of these is "EntitySet", which is consistent with legacy OData services. We should make the "kind" property optional for objects in the service document that represent entity sets.

{
  "odata.metadata": "http://host/service/$metadata";,
"value": [
    { 
      "name": "Orders",
      "kind": "EntitySet"
      "url": "Orders"
    },
    {
      "name": "OrderDetails",
      "kind": "EntitySet"
      "url": "OrderDetails"
    },
    {
      "name": "Contoso",
      "kind": "Entity"
      "url": "Contoso"
    }
  ]
}


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira