[OASIS Issue Tracker] Updated: (ODATA-337) Review results for OData JSON Format Version 4.0

[ http://tools.oasis-open.org/issues/browse/ODATA-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Zurmuehl updated ODATA-337:
----------------------------------

    Description: 
In our review today we came up with the following points and resolution proposals (copied from the chat): 

Review document can be found at https://www.oasis-open.org/committees/download.php/48589/odata-json-format-v4.0-wd01-2013-03-19.doc
SDx, HHx and so on are references to comments in this document 

JSON 1 introduction
HH2: accepted
SD3: accepted - rephrase sentence
SD4: accepted
 3 Requesting the JSON Format
Hubert: open ticket to make json constant case-insensitive
Ralf: sync with Protocol spec and clearly state that mime types are allowed in $format
SD6: no action
SD7: no action
SD8: state that odata.metadata=minimal MAY be explicitly requested
SD11: accepted - make clear that structure is similar, not necessarily the content
HH13: Ralf to check with Mike whether last bullet point on navigation properties is necessary
HH14: accepted
SD15: accepted
SD16: accepted
SD18: no action
HH19: state use cases here
HH21: correct example URLs and remove $links
HH21: Hubert will open a ticket regarding the template
SD20: correct here, no action
SD22: no action

  was:
In our review today we came up with the following points and resolution proposals (copied from the chat): 

Review document can be found at https://www.oasis-open.org/committees/download.php/48589/odata-json-format-v4.0-wd01-2013-03-19.doc
SDx, HHx and so on are references to comments in this document 

JSON 1 introduction
HH2: accepted
SD3: accepted - rephrase sentence
SD4: accepted
 3 Requesting the JSON Format
Hubert: open ticket to make json constant case-insensitive
Ralf: sync with Protocol spec and clearly state that mime types are allowed in $format
SD6: no action
SD7: no action
SD8: state that odata.metadata=minimal MAY be explicitly requested
SD11: accepted - make clear that structure is similar, not necessarily the content



> Review results for OData JSON Format Version 4.0
> ------------------------------------------------
>
>                 Key: ODATA-337
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-337
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Extension for JSON Data 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Martin Zurmuehl
>
> In our review today we came up with the following points and resolution proposals (copied from the chat): 
> Review document can be found at https://www.oasis-open.org/committees/download.php/48589/odata-json-format-v4.0-wd01-2013-03-19.doc
> SDx, HHx and so on are references to comments in this document 
> JSON 1 introduction
> HH2: accepted
> SD3: accepted - rephrase sentence
> SD4: accepted
>  3 Requesting the JSON Format
> Hubert: open ticket to make json constant case-insensitive
> Ralf: sync with Protocol spec and clearly state that mime types are allowed in $format
> SD6: no action
> SD7: no action
> SD8: state that odata.metadata=minimal MAY be explicitly requested
> SD11: accepted - make clear that structure is similar, not necessarily the content
> HH13: Ralf to check with Mike whether last bullet point on navigation properties is necessary
> HH14: accepted
> SD15: accepted
> SD16: accepted
> SD18: no action
> HH19: state use cases here
> HH21: correct example URLs and remove $links
> HH21: Hubert will open a ticket regarding the template
> SD20: correct here, no action
> SD22: no action

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