[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [odata] Fwd: [odata-comment] Specification of $count for "Delta Responses"
I have acknowledged (https://lists.oasis-open.org/archives/odata-comment/201305/msg00001.html) the comment (on the odata-comment list) and indicated that this TC will process the comment and respond soon. Let's process this comment in this TC via a JIRA ticket with the tagging mechanism Stefan describes below. Once we have a proper resolution, we will circle back with the commenter. Yes, let's add this to the agenda for this week's TC meeting as suggested below. -----Original Message----- From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Stefan Drees Sent: Wednesday, May 8, 2013 9:33 AM To: odata@lists.oasis-open.org Subject: [odata] Fwd: [odata-comment] Specification of $count for "Delta Responses" We received the first public comment during CSD01 Public Review. The below comment archived at mailing list archive URL https://lists.oasis-open.org/archives/odata-comment/201305/msg00000.html has been registered as public comment with id c201305e00000 (procedure as described at eg. https://www.oasis-open.org/committees/download.php/48109/formal-aspects-meeting-minutes-v1.html#pcnotation). Please refer to it by citing it's mailing list archive URL or the id: c201305e00000 PS: I hereby suggest to add this to the agenda of tomorrow's call after the action item handling and before the usual processing of issues. What do you think? All the best, Stefan. -------- Original-Nachricht -------- Betreff: [odata-comment] Specification of $count for "Delta Responses" Datum: Wed, 8 May 2013 16:17:09 +0000 Von: Degenkolb, Marko <marko.degenkolb@sap.com> An: odata-comment@lists.oasis-open.org <odata-comment@lists.oasis-open.org> Reading the new specification of "Delta Responses" (http://docs.oasis-open.org/odata/odata-json-format/v4.0/csprd01/odata-json-format-v4.0-csprd01.zip => odata-json-format-v4.0-csprd01.pdf => chapter 14) I have two comments: 1) The way how the $count behavior is defined seems inconsistent with the behavior of $count on "normal" EntitySets. There, $count returns the number of instances in the specified EntitySet. That means, for example, that if $count returns 0 a GET without $count returns an empty feed. With the current specification - not counting added or deleted links - this coherence does not apply anymore. 2) The specification is not clear whether 'the returned count is the count of added, changed, or deleted entities' includes "expanded" entities or not. In the example you mention this would mean: does #4 count or not? In other words, would $count in this example return 2 or 3? Many thanks, Marko -- This publicly archived list offers a means to provide input to the OASIS Open Data Protocol (OData) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: odata-comment-subscribe@lists.oasis-open.org Unsubscribe: odata-comment-unsubscribe@lists.oasis-open.org List help: odata-comment-help@lists.oasis-open.org List archive: http://lists.oasis-open.org/archives/odata-comment/ Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: http://www.oasis-open.org/maillists/guidelines.php Committee: http://www.oasis-open.org/committees/odata Join OASIS: http://www.oasis-open.org/join/ --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]