State consequences of using IRIs that are not URLs

Using an IRI that is not a URL as an entity-id requires to have in addition an edit link or read link. Even if the edit link is the standard encoded version of the IRI, they are treated as different and need to be represented separately in JSON The client must be prepared to accept any IRI but that services must use URIs in 4.0 since we have no lossless representation of an IRI in the entity-id header.

Core: https://www.oasis-open.org/committees/document.php?document_id=49675&wg_abbrev=odata JSON: https://www.oasis-open.org/committees/document.php?document_id=49674&wg_abbrev=odata Atom: https://www.oasis-open.org/committees/document.php?document_id=49673&wg_abbrev=odata Accepted: https://www.oasis-open.org/committees/download.php/49679/odata-meeting-43_on-20130624-minutes.html#odata-459