How would an upgrade from verbose JSON to JSON light affect someone who only looks at the data, and not the metadata? -

Can someone explain me plainly in English? What is the main difference with some bullet points between JSON and JSON Lite Is WCF Data Services Different? I got a document called "Jason Light on a Non" by Microsoft, but this page is 23 pages long! I do not care about metadata; I care about data only, I know that the JSON light "d" leaves the cover and something else? Are data types (dates, bullion, etc.) sent in the same format?

EDIT: I know that Microsoft is now just calling "JSON" JSON Lite, and JSON Verbose is outdated, excluded standard. I am calling the new standard "JSON light" for clarity.

"I only care about metadata data"

In fact there is a large tagline for a completely JSON light :)

The main principle of JSON light is that when a client needs some metadata in the unnecessary metadata payload (for example , The URL should be used to edit the unit), then the client will be able to access the general Audita URI It can generate that URI on the wire.

A customer can control how much metadata should the server have in the payload by requesting one of three levels of metadata:

• For those customers, "Application / Jason; Odata = Fullmetadata "which is required to use metadata and not
• " Application / Jason; odata = nometadata "
• " application / json; odata = minimalmetadata " Use metadata but computing yourself
• In any case

  If you are writing a client who does not really care about any metadata (where the edit link, entity type, type of property in the metadata, Stream information, navigation properties, etc.), you can request "Application / Jason; Odata = Notatata" and you will get back a bag of properties.

  Even if you do not care about metadata, there are very few differences between JSN Verbose and JSN Lite. I strongly recommend to rely on a library for this if you are in a language where one is available (for example, WCF Data Services Client in .NET and Datja or Jaiver in Javascript). Here's a list of some differences from my head:

  • In Odeta V2, title-based format (e.g., "last update": "\" / date (1240718400000) \ / "), but v3 JSON only supports ISO 8601 (e.g., " 1992-01-01T00: 00: 00 ")
  • There is now no "d" cover on the result payload.
  • Instead of a "result" cover for the archive results, now there is a "value" wrapper
  • Instead of "__count" For inline count, JSON light uses "odata.count"

    As an example, look at the differences in the payload produced by this query:

    http://services.odata.org/v3/OData/OData.svc/Products?tdinlinecount= Allpages & amp; $ top = 2 & amp; $ format = application / json + odata = verbose

    this vs:

    http://services.odata.org/v3/OData/OData. Svc / products? $ Inlinecount = allpages & amp; $ top = 2 & amp; $ format = application / json + odata = nometadata