[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-248) Define required/optional format(s) for OData
[ http://tools.oasis-open.org/issues/browse/ODATA-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Drees updated ODATA-248:
-------------------------------
Resolution: Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-248
> Define required/optional format(s) for OData
> --------------------------------------------
>
> Key: ODATA-248
> URL: http://tools.oasis-open.org/issues/browse/ODATA-248
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Task
> Components: OData Protocol
> Affects Versions: V4.0_WD01
> Environment: [Applied]
> Reporter: Michael Pizzo
> Assignee: Michael Pizzo
> Fix For: V4.0_WD01
>
>
> We need to define what format(s), if any, are required for a service to be OData "Conformant", and which are optional.
> For example, we could say that JSON is required, and ATOM is optional, meaning a service that supported only ATOM would not be conformant. This would help clients but might prevent some services from being compliant. Also, if we added another format (say, RDF), it would prevent a service from implementing just RDF and claiming conformance.
> We could, fore example, say that a service SHOULD support JSON for maximum interoperability, but not make it required. Or perhaps we can define levels of conformance.
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]