Room information was updated by: Stefan
Registration of attendance from now on open at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39124 as usual. Please register yourself. Thanks
Stefan: Voting Members: 1 of 13 (7%) (used for quorum calculation)
anonymous morphed into Matt Borges (SAP)
Stefan: I was on the voice line and could here Ralf talk to me, but he seems to not have been able to hear me. Do I have to enter the Connect session again? And advice very apreciated
Room Information:
Registration of attendance from now on open at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39124 as usual. Please register yourself. Thanks
Stefan: Voting Members: 5 of 13 (38%) (used for quorum calculation)
Stefan: Voting Members: 7 of 13 (53%) (used for quorum calculation)
Stefan: We are quorate.
Stefan: Registered attendance unchanged (7 of 13)
Stefan: Voting Members: 9 of 13 (69%) (used for quorum calculation)
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]
a.Minutes from November 05, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56868/odata-meeting-112_on-20151105-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.JSON Format for CSDL [8:20am PT]
a.Document Walk-through
i.https://www.oasis-open.org/committees/download.php/56882/odata-json-csdl-v4.0-wd01-2015-11-09.docx
Ralf Handl (SAP): Representation of keys: shorter form
"keys":[
"ID",
"ID2",
{"aliasName":"complex/Path"}
],
Ralf Handl (SAP): Plain string for unaliased key properties, object for aliased key property
Ralf Handl (SAP): Shorter syntax for dynamic expressions, e.g.
"@Org.OData.Measures.V1.ISOCurrency":{
"@odata.path":"Currency"
}
"@odata.if":[
{
"@odata.path":"IsFemale"
},
"Female",
"Male"
]
"@odata.apply":{
"function":"odata.concat",
"parameterValues":[
"Products(",
{
"@odata.path":"ID"
},
")"
]
}
Mike Pizzo1: I move we close ODATA--875 as applied.
Mark Biamonte (Progress): I second
Ralf Handl (SAP): ODATA-875 is closed as applied
Ralf Handl (SAP): 6.V4.0 ERRATA03 [8:50am PT]
a.Issues for V4.0_ERRATA03 in New or Open state
Ralf Handl (SAP): i.OData CSDL
1.ODATA-825 AnnotationPath and Path _expression_: traversal of multiple collection-valued scalar or navigation properties
Ralf Handl (SAP): ODATA-825 is OPEN
Mike Pizzo1: I move we resolve ODATA-825 as proposed.
Matt Borges (SAP): i second
Ralf Handl (SAP): ODATA-825 is resolved as proposed
Ralf Handl (SAP): 2.ODATA-865 14.2.1 Attribute Target: complete list of externally targetable CSDL elements
Ralf Handl (SAP): ODATA-865 is OPEN
Mark Biamonte (Progress): I move we resolve ODATA-865 as proposed
Mike Pizzo1: I second
Ralf Handl (SAP): ODATA-865 is resolved as proposed
Ralf Handl (SAP): 3.ODATA-878 Example 84: EntityContainer is a Singleton, not an EntitySet
Ralf Handl (SAP): ODATA-878 is OPEN
Gerald Krause (SAP): I second
Matt Borges (SAP): I move we resolve ODATA-878 as proposed.
Gerald Krause (SAP): I second.
Ralf Handl (SAP): ODATA-878 is resolved as proposed
Ralf Handl (SAP): 4.ODATA-880 14.5.10: edm:Null can have edm:Annotation child elements
Ralf Handl (SAP): ODATA-880 is OPEN
Ralf Handl (SAP): 14.5.10 _expression_ edm:Null
The edm:Null _expression_ returns an untyped null value. The null _expression_ MUST NOT contain any other elements or expressions.
The null _expression_ MUST be written with element notation.
Example 65:
<Annotation Term="org.example.display.DisplayName">
<Null/>
</Annotation>
Mike Pizzo1: alternate wording: "The only allowed child element of the null _expression_ is an edm:AnnotationType element.".
Mike Pizzo1: I move we resolve ODATA-880 by replacing the current sentence prohibiting child elements of the null _expression_ with the following text: "The only allowed child element of the null _expression_ is an edm:Annotation element."
Mark Biamonte (Progress): I second
Ralf Handl (SAP): ODATA-880 is resolved as proposed
Ralf Handl (SAP): ii.OData JSON Format
1.ODATA-656 Requesting clarity on payload ordering constraints for clients
Ralf Handl (SAP): ODATA-656 is OPEN
Mike Pizzo1: proposal: Clarify in Section 4.4 Payload Ordering Constraints that services may use the odata.streaming=true format parameter to specify that the contents of the payload supplied by the client follow the ordering constraints. In the absence of such a type parameter the service must assume that the properties of json objects are unordered.
Mike Pizzo1: amended: Clarify in Section 4.4 Payload Ordering Constraints that clients may use the odata.streaming=true format parameter to specify that the contents of the payload supplied by the client follow the ordering constraints. In the absence of such a type parameter the service must assume that the properties of json objects are unordered.
Mark Biamonte (Progress): I move we resolve ODATA-656 as ammended
Matt Borges (SAP): I second
Ralf Handl (SAP): ODATA-656 is resolved as proposed
Ralf Handl (SAP): 7.V4.01 [9:20am PT]
Ralf Handl (SAP): a.Issues for V4.01_WD01 in New or Open state
i.Adoption Blocker
Ralf Handl (SAP): 1.ODATA-881 Add support for Edm.Untyped
Ralf Handl (SAP): ODATA-881 is OPEN
Ralf Handl (SAP): 8.Next meeting [9:50am PT]
a.Thursday November 19, 2015 during 8-10am PT?
Ralf Handl (SAP): Agreed.
Ralf Handl (SAP): No meeting on November 26
Ralf Handl (SAP): The meeting is adjourned
From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf
Sent: Dienstag, 10. November 2015 11:14
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-11-12
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday November 12, 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=39124
2.
Approve agenda [8:05am PT]
3.
Approve minutes from previous meeting(s) [8:10am PT]
a.
Minutes from November 05, 2015 TC meeting:
https://www.oasis-open.org/committees/download.php/56868/odata-meeting-112_on-20151105-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.
JSON Format for CSDL [8:20am PT]
a.
Document Walk-through
i. https://www.oasis-open.org/committees/download.php/56882/odata-json-csdl-v4.0-wd01-2015-11-09.docx
b.
Issues
for JSON Format for CSDL in Applied state
i. ODATA-875
Use of $ref for referencing elements in a JSON Schema
6.
V4.0 ERRATA03 [8:50am PT]
a.
Issues
for V4.0_ERRATA03 in New or Open state
i. OData CSDL
1.
ODATA-825 AnnotationPath
and Path _expression_: traversal of multiple collection-valued scalar or navigation properties
2.
ODATA-865 14.2.1 Attribute
Target: complete list of externally targetable CSDL elements
3.
ODATA-878 Example 84:
EntityContainer is a Singleton, not an EntitySet
4.
ODATA-880 14.5.10: edm:Null
can have edm:Annotation child elements
ii. OData JSON Format
1.
ODATA-656 Requesting clarity
on payload ordering constraints for clients
iii. OData Protocol
1.
ODATA-830 Header OData-EntityId:
when required
2.
ODATA-837 Example 28:
replace $deltaToken with a valid custom query option
3.
ODATA-869 Explicitly state
the location of the Content-ID header in a change set
4.
ODATA-870 Round-off description
for creating related entities when creating an entity
5.
ODATA-882 Mismatch between
11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References
iv. OData URL Conventions
1.
ODATA-784 Need to specify
the behaviour of arithmetic operators on Decimal type
2.
ODATA-785 Numeric promotion
(on overflow) across "number type families" is undesirable.
7.
V4.01 [9:20am PT]
a.
Issues
for V4.01_WD01 in New or Open state
i. 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
ii. 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
iii. 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
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
6.
ODATA-820 Allow indexing
into collections
v. 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
8.
Next meeting [9:50am PT]
a.
Thursday November 19, 2015 during 8-10am PT?
9.
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