[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-896) Reconsider guidance on odata.count position
[ https://issues.oasis-open.org/browse/ODATA-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61446#comment-61446 ] Ralf Handl commented on ODATA-896: ---------------------------------- I think this is a left-over from before collecting all payload ordering constraints in section 4.4 and requiring them only for odata.streaming=true. Question is: would "streaming" recipients benefit from knowing the number up-front, knowing that it is may get outdated while receiving the streamed data? > Reconsider guidance on odata.count position > ------------------------------------------- > > Key: ODATA-896 > URL: https://issues.oasis-open.org/browse/ODATA-896 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Reporter: Mark Stafford > Priority: Minor > > In the JSON format, we say in section 12: "The odata.count name/value pair represents the number of entities in the collection. If present, it MUST come before the value name/value pair. " > Per public feedback, we should consider softening this statement to SHOULD, and perhaps clarify which page(s) it should appear on. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]