Room information was updated by: Stefan
Please register yourselves at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39123
Room information was updated by: Stefan
Please register yourselves at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39123
Dial-in information: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/latest
Online chat room(here): http://webconf.soaphub.org/conf/room/odatatc
Screen sharing: https://sap.emea.pgiconnect.com/OData-TC/
Stefan: Voting Members: 1 of 13 (7%) (used for quorum calculation)
anonymous morphed into Matt Borges (SAP)
Stefan: Voting Members: 4 of 13 (30%) (used for quorum calculation)
Room Information:
Please register yourselves at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39123
Dial-in information: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/latest
Online chat room(here): http://webconf.soaphub.org/conf/room/odatatc
Screen sharing: https://sap.emea.pgiconnect.com/OData-TC/
Ralf Handl (SAP): https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39123
Ralf Handl (SAP): Voting Members: 7 of 13 (53%) (used for quorum calculation)
Ralf Handl (SAP): Achieved quorum: yes
Mark Biamonte (Progress): I need to step out for a couple minutes be right back
Stefan: Voting Members: 9 of 13 (69%) (used for quorum calculation)
Mark Biamonte (Progress): I am back
Mark Biamonte (Progress): I am back
Mark Biamonte (Progress): I am back
Ralf Handl (SAP): 6.Next Face-to-Face Meeting [8:20am PT]
Ralf Handl (SAP): 2.Approve agenda [8:05am PT]
Ralf Handl (SAP): Agenda is approved
Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10am PT]
Ralf Handl (SAP): a.Minutes from Occtober 29, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56814/odata-meeting-111_on-20151029-minutes.html
Ralf Handl (SAP): Minutes are approved
Ralf Handl (SAP): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
a.Action items due
i.None
Ralf Handl (SAP): 5.Extension for Data Aggregation [8:15am PT]
a.Result of electronic ballot https://www.oasis-open.org/apps/org/workgroup/odata/ballot.php?id=2877
Ralf Handl (SAP): Vote passed with 100% Yes - Thanks!
Ralf Handl (SAP): 6.Next Face-to-Face Meeting [8:20am PT]
a.When: First week February 2016, 01-05 does this work?
b.Where: please propose locations
c.What:
i.Finish CSD01 for JSON CSDL
ii.Get agreement on scope and shape of V4.01
iii.Prepare respective draft documents
Ralf Handl (SAP): Possible time slots
Ralf Handl (SAP): Week February 29 - March
Ralf Handl (SAP): Week February 29 - March 04
Ralf Handl (SAP): Location: Zrich
Stefan: Stefan would be in favour for Zurich also ...
Ralf Handl (SAP): I like Zurich
Mike Pizzo: That works for me.
Ralf Handl (SAP): No objections
Mark Biamonte (Progress): If I can lobby my company to come this week and location would work for me.
Ralf Handl (SAP): Action Item for Hubert: check if IBM can host the F2F in Zurich, Vulkanstraße
Ralf Handl (SAP): Due date November 19
Ralf Handl (SAP): 7.JSON Format for CSDL [8:40am PT]
a.Walk through current document revision
i.Specification document: https://www.oasis-open.org/committees/download.php/56763/odata-json-csdl-v4.0-wd01-2015-10-23.docx
ii.EDM JSON Schema: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edm.json
Ralf Handl (SAP): b.Issues for JSON Format for CSDL in Applied state
i.ODATA-841 Representation of Precision and Scale
ii.ODATA-855 Should we define patterns for some of the primitive types
iii.ODATA-856 Add annotations for Min/Max/Pattern
iv.ODATA-858 Define meaning of MaxLength for String, Binary, and Stream
v.ODATA-864 Translate @Core.Description annotations into JSON Schema description keywords
Stefan: Stefan will have to drop out of screen sharing but hopefully the voice line remains ...
Ramesh Reddy(Redhat): Another call, need to drop off, thanks
Ralf Handl (SAP): Mike to open a ticket on whether to always use arrays for action/function overloads
Ralf Handl (SAP): Hubert: always use an array, no special case for 1-element arrays
Ralf Handl (SAP): Mark and Ralf second
Ralf Handl (SAP): Ralf to open an issue to pull out entityContainer, actions, functions, and terms to top-level keywords
Ralf Handl (SAP): Resume walk-through in next meeting, we stopped just before 4.2.5 Annotations
Ralf Handl (SAP): b.Issues for JSON Format for CSDL in Applied state
i.ODATA-841 Representation of Precision and Scale
ii.ODATA-855 Should we define patterns for some of the primitive types
iii.ODATA-856 Add annotations for Min/Max/Pattern
iv.ODATA-858 Define meaning of MaxLength for String, Binary, and Stream
v.ODATA-864 Translate @Core.Description annotations into JSON Schema description keywords
Hubert Heijkers: I move to resolve ODATA-841, ODATA-855, ODATA-858 and ODATA-864 as applied.
Ted Jones (Red Hat): I second
Mark Biamonte (Progress): I second
Ralf Handl (SAP): Motion passes
Ralf Handl (SAP): Ralf to check whether the document still contains plain untranslated @Core.Description
Ralf Handl (SAP): 8.V4.0 ERRATA03 [9:10am PT]
a.Issues for V4.0_ERRATA03 in New or Open state
i.OData JSON Format
1.ODATA-828 Update I-JSON reference
Mike Pizzo: Revised Wording:The DateTimeOffset and TimeOfDay data types as defined in [OData-ABNF] allow for the seconds component to be omitted. For compatibility with [I-JSON], OData clients and servers SHOULD include the seconds component.
Mike Pizzo: I move we resolve ODATA-828 according to this revised proposal.
Hubert Heijkers: I second
Ralf Handl (SAP): ODATA-828 is resolved with the amended proposal
Ralf Handl (SAP): ii.OData Protocol
1.ODATA-877 Must delta responses continue to track "orphaned" entities?
Mike Pizzo: Proposed wording for ODATA-877:
Mike Pizzo: If a previously tracked related entity is orphaned because all paths to the entity as specified in the defining query have been broken (i.e., due to relationship changes and/or changes or deletions to parent entities) then the service MUST return the appropriate notifications for the client to determine that the entity has been orphaned (i.e., the changed relationships and removed parent entities) but the client should not assume that it will receive additional notifications for such an orphaned entity.
Hubert Heijkers: I move to resolve ODATA-877 as proposed.
Matt Borges (SAP): I second
Ralf Handl (SAP): ODATA-877 is resolved as proposed
Ralf Handl (SAP): 9.V4.01 [9:30am PT]
a.Issues for V4.01_WD01 in New or Open state
i.Enum Types
1.Proposal by Ken Baclawski: https://www.oasis-open.org/committees/download.php/56805/DerivationForEnumerations_KenBaclawski.html
2.ODATA-494 Define inheritance for enumeration types
3.ODATA-849 Add possibility for enumeration types to "extend" another enumeration type
Ralf Handl (SAP): <EnumType Name="ExtendedShippingMethod" Widens="ShippingMethod">
<Member Name="Economy"/>
</EnumType>
Ted Jones (Red Hat): I will be at TechEd next week
Ralf Handl (SAP): 10.Next meeting [9:50am PT]
a.Thursday November 12, 2015 during 8-10am PT
Ralf Handl (SAP): 11.AOB and wrap up [9:55am PT]
Ralf Handl (SAP): Meeting is adjourned!
From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf
Sent: Donnerstag, 5. November 2015 09:13
To: odata@lists.oasis-open.org
Subject: RE: [odata] Agenda for OData TC meeting on 2015-11-05
Added 9.1.ii Adoption Blocker:
1.
ODATA-881 Add support for Edm.Untyped
2.
ODATA-876 Allow services to return contained entities
inline for delta responses
3.
ODATA-814 Don't need TargetId in a deleted link
for a to 0..1 relationship
4.
ODATA-613 Allow POST to entity sets using the
delta-response format
From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf
Sent: Montag, 2. November 2015 13:47
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-11-05
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday November 05, 2015 during 8-10am PDT (17:00-19:00 CEST).
For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.
Thanks.
[1]
Agenda
1.
Roll call [8:00am PT]
a.
Self-registration link:
https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39123
2.
Approve agenda [8:05am PT]
3.
Approve minutes from previous meeting(s) [8:10am PT]
a.
Minutes from Occtober 29, 2015 TC meeting:
https://www.oasis-open.org/committees/download.php/56814/odata-meeting-111_on-20151029-minutes.html
4.
Review action items [Action item list:
https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
a.
Action items due
i. None
5.
Extension for Data Aggregation [8:15am PT]
a.
Result of electronic ballot
https://www.oasis-open.org/apps/org/workgroup/odata/ballot.php?id=2877
6.
Next Face-to-Face Meeting [8:20am PT]
a.
When: First week February 2016, 01-05 – does this work?
b.
Where: please propose locations
c.
What:
i. Finish CSD01 for JSON CSDL
ii. Get agreement on scope and shape of V4.01
iii. Prepare respective draft documents
7.
JSON Format for CSDL [8:40am PT]
a.
Walk through current document revision
i. Specification document:
https://www.oasis-open.org/committees/download.php/56763/odata-json-csdl-v4.0-wd01-2015-10-23.docx
ii. EDM JSON Schema:
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edm.json
b.
Issues
for JSON Format for CSDL in Applied state
i. ODATA-841
Representation of Precision and Scale
ii. ODATA-855
Should we define patterns for some of the primitive types
iii. ODATA-856
Add annotations for Min/Max/Pattern
iv. ODATA-858
Define meaning of MaxLength for String, Binary, and Stream
v. ODATA-864
Translate @Core.Description annotations into JSON Schema description keywords
c.
Issues
for JSON Format for CSDL in New or Open state
i. ODATA-863
ODATA-618 Represent Terms similar to Types
8.
V4.0 ERRATA03 [9:10am PT]
a.
Issues
for V4.0_ERRATA03 in New or Open state
i. OData JSON Format
1.
ODATA-828 Update I-JSON
reference
ii. OData Protocol
1.
ODATA-877 Must delta responses
continue to track "orphaned" entities?
2.
ODATA-837 Example 28:
replace $deltaToken with a valid custom query option
9.
V4.01 [9:30am PT]
a.
Issues
for V4.01_WD01 in New or Open state
i. Enum Types
1.
Proposal by Ken Baclawski:
https://www.oasis-open.org/committees/download.php/56805/DerivationForEnumerations_KenBaclawski.html
2.
ODATA-494 Define inheritance
for enumeration types
3.
ODATA-849 Add possibility
for enumeration types to "extend" another enumeration type
ii. Adoption Blocker
1.
ODATA-881 Add support for Edm.Untyped
2.
ODATA-876 Allow services to return
contained entities inline for delta responses
3.
ODATA-814 Don't need TargetId in a
deleted link for a to 0..1 relationship
4.
ODATA-613 Allow POST to entity sets
using the delta-response format
iii. Simplified Syntax
1.
ODATA-664 Consider supporting
parameterless function imports with no parens
2.
ODATA-812 Allow omitting
namespaces for unambiguous functions/actions
3.
ODATA-763 Allowing implicit
aliasing of parameters (public comment c201412e00001)
4.
ODATA-799 Define Key-As-Segment
URL convention for resource paths
5.
ODATA-834 Make type prefix
optional for enumeration literals in URLs
iv. Set Operations
1.
ODATA-666 Define Deep
Update and Deep Upsert operations
2.
ODATA-836 Allow applying
actions to a filtered collection of entities
3.
ODATA-613 Allow POST to
entity sets using the delta-response format
4.
ODATA-615 Allow PATCH
and DELETE with $filter on collections to modify or delete all (and only) the matching entities
5.
ODATA-616 Allow POST to
collections of complex and primitive types, and DELETE with $filter
v. New Query Capabilities
1.
ODATA-482 Allow inlining
stream properties and media resources
2.
ODATA-614 Allow $expand,
$select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape
3.
ODATA-827 introduce $compute
query option
4.
ODATA-556 Add "in" operator
as syntactic sugar for a chain of "or" expressions
5.
ODATA-820 Allow indexing
into collections
vi. Simplified Payload
1.
ODATA-561 odata.type shouldn't
require "#" for primitive types
2.
ODATA-630 Consider making
odata the default namespace for annotations
3.
ODATA-813 Allow no metadata
for non-OData clients
4.
ODATA-814 Don't need TargetId
in a deleted link for a to 0..1 relationship
5.
ODATA-818 Omit properties
whose value is null or the $metadata-defined default value
6.
ODATA-809 Define non-message
format for final response of async request
10.
Next meeting [9:50am PT]
a.
Thursday November 12, 2015 during 8-10am PT?
11.
AOB and wrap up [9:55am PT]
[2]
References
·
Conference call details:
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm
·
Chat room:
http://webconf.soaphub.org/conf/room/odatatc
[3]
Timeline
·
https://www.oasis-open.org/committees/document.php?document_id=56024&wg_abbrev=odata