[OASIS Issue Tracker] Created: (ODATA-247) More clearly define extensibility of Formats

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

More clearly define extensibility of Formats
--------------------------------------------

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


The ATOM format already says, in section 15, that additional payload may be returned anywhere supported by Section 6 of [RFC4287], but that extensions must not be in the OData namespaces and should not be required to be understood by the client in order for the payload to be correctly interpreted.

In ATOM we should be clear that this means that the service may return additional children of the <feed> or <entry> elements, and that it is safe for the client to ignore anything (in any namespace, including the odata namespace) not defined in the version of the payload being returned. This allows for forward compatibility of incremental information without rev'ing the payload version.

In JSON we should be clear that clients should ignore annotations (in any namespace, including the odata namespace), as well as objects with an odata.kind, that are not defined in the version of the payload being returned.

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