RE: [odata] Groups - Minutes of 2016-03-02 and 2016-03-03 Meeting#122 (F

[9:16] Ralf Handl (SAP): Dial-in information: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/latest

Online chat room: http://webconf.soaphub.org/conf/room/odatatc

Screen sharing: https://sap.emea.pgiconnect.com/OData-TC/

[9:16] Ralf Handl (SAP): Voting Members: 8 of 13 (61%) (used for quorum calculation)

[9:16] Ralf Handl (SAP): Achieved quorum: yes

[9:18] Ralf Handl (SAP): 2.Approve agenda

[9:22] anonymous morphed into Martin Zurmuehl SAP

[9:25] Ralf Handl (SAP): Agenda is approved

[9:26] Ralf Handl (SAP): Lunch break will be 12:00 to 13:00 CET

[9:26] Ralf Handl (SAP): 3.Approve minutes from previous meeting(s)

[9:26] Ralf Handl (SAP): https://www.oasis-open.org/apps/org/workgroup/odata/download.php/57641/odata-meeting-121_on-20160225-minutes.html

[9:29] Ralf Handl (SAP): Minutes are approved

[9:29] Ralf Handl (SAP): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [9:15am]

a.Action items due

i.None

[9:29] Ralf Handl (SAP): 5.Errata 3 Issues

[9:29] Ralf Handl (SAP): a.Review applications of Errata 3 issue resolutions (This is a carryover from previous meeting)

[9:30] Ralf Handl (SAP): We left in JSON Format, chapter 12

[9:36] Ralf Handl (SAP): Agreement to issue application

[9:48] Mark Biamonte (Progress): Review of JSON Format complete

[9:48] Mark Biamonte (Progress): Reviewing changes to CSDL Document

[9:56] Ralf Handl (SAP): Discussion on ODATA-803

[9:56] Mike Pizzo: I move we reopen Issue-803 to consider meaning of absence of nullable facet for collections.

[9:59] Mark Biamonte (Progress): I second

[10:00] Ralf Handl (SAP): No objections, issue is reopened

[10:01] Hubert Heijkers: I'd argue that Nullable being true for collection valued properties would be the exceptional case.

[10:02] Hubert Heijkers: As such this changes what clients might expect to be able to do, insert null values in these collections, whereas before they, presumable, would have not assumed to be able to do so in the absence of the Nullable facet

[10:05] Mike Pizzo1: Upon reviewing, while clients can't assume that absence means you can insert a null value, saying that absence means true implies that the client can insert null values. Then saying that they may not be able to insert null values even in this case makes the presence of nullable=true meaningless.

[10:06] Mike Pizzo1: in addition, this default is likely to be the wrong choice in most cases.

[10:08] Mike Pizzo: Proposal:

Absence of nullable facet on collection means it's unknown if you can insert nulls. You can try, but it may fail.

Nullable=true means that the collection *may* contain null values (although attempting to insert a null value may still fail for a variety of reasons)

Nullable=false means that the collection can not contain null values

[10:20] Mark Biamonte (Progress): I move that we accept the revised proposal for OData 803

[10:20] Ramesh Reddy(Redhat): I second

[10:20] Mike Pizzo: I second

[10:21] Ralf Handl (SAP): No objections, motion passes

[10:31] Ralf Handl (SAP): 13.1.2 Attribute Extends: make additional text a note because we don't want to introduce normative language in an erratum.

[10:45] Ralf Handl (SAP): Finished CSDL document

[10:46] Ralf Handl (SAP): Starting with Errata document for OData

[10:52] Ralf Handl (SAP): No comments

[10:53] Ralf Handl (SAP): Starting with Errata document for JSON Format

[10:56] Ralf Handl (SAP): No comments

[10:56] Ralf Handl (SAP): Finished with reviewing documents

[11:01] Ralf Handl (SAP): I move to close issues ODATA-656, ODATA-781, ODATA-819, ODATA-821, ODATA-822, ODATA-823, ODATA-825, ODATA-826, ODATA-828, ODATA-830, ODATA-831, ODATA-832, ODATA-835, ODATA-837, ODATA-840, ODATA-847, ODATA-850, ODATA-852, ODATA-853, ODATA-861, ODATA-865, ODATA-869, ODATA-870, ODATA-877, ODATA-878, ODATA-880, ODATA-885, ODATA-891, ODATA-892, ODATA-893, ODATA-896, ODATA-899, ODATA-903 as applied

[11:01] Mike Pizzo: I second

[11:01] Ralf Handl (SAP): No objections, motion passes

[11:04] Ralf Handl (SAP): b.Errata 3 Issues in New/Open State

i.Issues for V4.0_ERRATA03 in New or Open state

[11:22] Ralf Handl (SAP): ODATA-908 8.1.1 Header Content-Type: is only SHOULD in RFC7231

[11:22] Ralf Handl (SAP): Issue is now OPEN

[11:23] Mike Pizzo: Proposal is to change Content-type from MUST to SHOULD for media types only.

[11:23] Mark Biamonte (Progress): I move that we accept ODATA-908 as proposed

[11:25] Mike Pizzo: I second

[11:25] Ralf Handl (SAP): ODATA-908 is RESOLVED as proposed

[11:26] Ralf Handl (SAP): ODATA-916 Define what services (and clients?) do with unknown format parameters

[11:26] Ralf Handl (SAP): ODATA-916 is OPEN

[11:30] Mark Biamonte (Progress): I move that we accept ODATA-916 as proposed

[11:31] Ramesh Reddy(Redhat): I second

[11:31] Ralf Handl (SAP): ODATA-916 is RESOLVED as proposed

[11:34] Ralf Handl (SAP): ODATA-913 Should we specify a default response format if neither Accept header nor system query $format are specified

[11:34] Ralf Handl (SAP): ODATA-913 is OPEN

[11:37] Mark Biamonte (Progress): I move that we accept ODATA-913 as proposed

[11:37] Mike Pizzo: I second

[11:38] Ralf Handl (SAP): ODATA-913 is RESOLVED as proposed

[11:38] Ralf Handl (SAP): ODATA-912 Clarify what clients should do if they see an unknown/invalid _expression_ for a known annotation term.

[11:40] Ralf Handl (SAP): ODATA-913 is OPEN

[11:43] Mark Biamonte (Progress): I move that we accept ODATA-912 as proposed

[11:43] Ramesh Reddy(Redhat): I second

[11:44] Ralf Handl (SAP): ODATA-912 is RESOLVED as proposed

[11:46] Ralf Handl (SAP): ODATA-915 Be consistent in citing rules around namespace qualification

[11:47] Ralf Handl (SAP): ODATA-915 is OPEN

[11:48] Ralf Handl (SAP): I move to resolve ODATA-915 as proposed

[11:48] Ramesh Reddy(Redhat): I second

[11:48] Ralf Handl (SAP): ODATA-915 is RESOLVED as proposed

[11:48] Ralf Handl (SAP): ODATA-917 5.1.1.2.1 Addition and 5.1.1.2.2 Subtraction: Date add/sub Duration is DateTimeOffset - but in which time zone?

[12:00] Ralf Handl (SAP): ODATA-917 is OPEN

[12:11] Ralf Handl (SAP): Hi Stefan: we'll break for lunch. Please ping us here in the chat after 13:00 if you want to join the screen sharing session

[12:12] Stefan: Cool. Yes. I will upload the minutes to date soon (in the next minute ...)

[12:12] Ralf Handl (SAP): P42DT12H53M == 24.1253

[12:13] Ralf Handl (SAP): P42DT12H53M == 42.1253

[12:28] Mike Pizzo: I move we resolve ODATA-917 as proposed.

[12:28] Mark Biamonte (Progress): I second

[12:29] Ralf Handl (SAP): ODATA-917 is RESOLVED as proposed

[12:29] Ralf Handl (SAP): @Stefan: we will now break for lunch and be back 13:30

[13:43] Ralf Handl (SAP): @Stefan: we are back

[13:45] Ralf Handl (SAP): ODATA-882 Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References

[13:51] Stefan: @Ralf: Stefan is in the shared call =(

[13:52] Stefan: I can hear you but set myself on mute

[14:01] Mark Biamonte (Progress): I move that we accept ODATA-882 as proposed

[14:01] Ramesh Reddy(Redhat): I second

[14:01] Ralf Handl (SAP): ODATA-882 is resolved as proposed

[14:04] Ralf Handl (SAP): ODATA-785 Numeric promotion (on overflow) across "number type families" is undesirable.

[14:05] Ralf Handl (SAP): Issue is already OPEN

[15:48] Ramesh Reddy(Redhat): I move that we accept ODATA-785 as proposed

[15:48] Mike Pizzo: I second

[15:49] Ralf Handl (SAP): ODATA-785 is RESOLVED as proposed

[16:06] Mike Pizzo: I move we resolve ODATA-785 as proposed

[16:06] Mike Pizzo: I second

[16:06] Mark Biamonte (Progress): I second

[16:07] Mike Pizzo: scratch those from the record...

[16:07] Mike Pizzo: I move we resolve ODATA-784 as proposed

[16:07] Mark Biamonte (Progress): I second

[16:07] Ralf Handl (SAP): ODATA-784 is RESOLVED as proposed

[16:48] Ralf Handl (SAP): Demo of Swagger as carrier format for JSON CSDL

[16:48] Ralf Handl (SAP): Showing TripPin service in Swagger UI

[16:49] Ralf Handl (SAP): Interactively explore metadata and try out requests online

[16:49] Ralf Handl (SAP): ODATA-907 Consider Swagger for describing OData metadata in JSON format (public comment c201602e00000)

[16:49] Ralf Handl (SAP): ODATA-907 is OPEN

[16:54] Ralf Handl (SAP): I move to resolve ODATA-907 as proposed

[16:54] Stefan: second

[16:55] Stefan: Was this effective :-?

[16:56] Stefan: I repeat: I second

[16:57] Ralf Handl (SAP): ODATA-907 is RESOLVED as proposed

[16:57] Stefan: and minute

[16:58] Ralf Handl (SAP): ODATA-902 4.5.2: make "annotations" a hash-map with the target as key

[16:58] Ralf Handl (SAP): ODATA-902 is OPEN

[16:59] Ralf Handl (SAP): I move to resolve ODATA-902 as proposed

[16:59] Stefan: I second

[16:59] Mark Biamonte (Progress): I second

[17:00] Ralf Handl (SAP): ODATA-902 is RESOLVED as proposed

[17:03] Ralf Handl (SAP): ODATA-910 Consider format that is tailored for programmatic access (public comment c201602e00002)

[17:03] Ralf Handl (SAP): ODATA-910 is OPENB

[17:03] Ralf Handl (SAP): Consider this when reworking JSON CSDL to be based on Swagger / OpenAPI

[17:04] Ralf Handl (SAP): ODATA-914 Comments from OASIS Technical Advisory Board (TAB)

[17:04] Ralf Handl (SAP): ODATA-914 is OPEN

[17:09] Stefan: I move to apply the proposed changes.

[17:09] Mark Biamonte (Progress): I second

[17:09] Ralf Handl (SAP): ODATA-914 is RESOLVED as proposed

[17:09] Ralf Handl (SAP): ODATA-911 Miscellanous feedback (public comment c201602e00003)

[17:12] Ralf Handl (SAP): ODATA-911 is OPEN

[17:12] Ralf Handl (SAP): I move to resolve ODATA-911 as proposed

[17:12] Stefan: I second

[17:12] Ralf Handl (SAP): ODATA-911 is RESOLVED as proposed

[17:14] Ralf Handl (SAP): ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL

[17:16] Ralf Handl (SAP): ODATA-906 is OPEN

[17:17] Ralf Handl (SAP): Postpone until after next draft of JSON CSDL is available and we know how namespaces are reflected

[17:18] Ralf Handl (SAP): ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this message

[17:18] Ralf Handl (SAP): ODATA-890 is OPEN

[17:19] Ralf Handl (SAP): Propably covered by /paths section of a Swagger document, park until next revision of JSON CSDL is prepared

[17:19] Ralf Handl (SAP): ODATA-889 Make edm.json a stand-alone schema

[17:20] Ralf Handl (SAP): I move to close this without action as it is obsolete after the move to Swagger

[17:21] Mark Biamonte (Progress): I second

[17:21] Ralf Handl (SAP): ODATA-889 is CLOSED without action

[17:21] Ralf Handl (SAP): ODATA-863 Represent Terms similar to Types

[17:22] Ralf Handl (SAP): Postpone until next revision of JSON CSDL is prepared

[17:22] Ralf Handl (SAP): This finishes agenda item 6 b

[17:23] Ralf Handl (SAP): TC will break for today, reconvene tomorrow at 09:00 CET

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Stefan Hagen
Sent: Mittwoch, 2. März 2016 12:17
To: odata@lists.oasis-open.org
Subject: [odata] Groups - Minutes of 2016-03-02 and 2016-03-03 Meeting#122 (F2F Zurich, CH) uploaded

Submitter's message
Near Real Time Draft of Minutes with timestamp 20160302T110000Z - This draft will be overwritten with successive revisions as the face to face meeting is ongoing. Hint: Before lunch break on day one.
-- Mr. Stefan Hagen

Document Name: Minutes of 2016-03-02 and 2016-03-03 Meeting#122 (F2F Zurich, CH)

Description
As minuted by all participants during meeting into the chat and edited for
readability by Stefan Hagen after the meeting.
Download Latest Revision
Public Download Link

Submitter: Mr. Stefan Hagen
Group: OASIS Open Data Protocol (OData) TC
Folder: Meeting Notes
Date submitted: 2016-03-02 03:17:09

odata message