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

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.0_WD01
    • Affects Version/s: V4.0_WD01
    • Component/s: JSON Format
    • None
    • Environment:

      [Proposed]

      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" }

      ]
      }

            Assignee:
            handl
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: