OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: Agenda for OData TC meeting on 2019-03-07 - chat transcript


[17:00] Room information was updated by: Ralf Handl (SAP)
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 07, 2019 during 8-10 am PST (17:00-19:00 CET). 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:00 am PT]
a.Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=47976 
 
2.Approve agenda [8:05 am PT]
 
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from February 28, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64790/Minutes%20of%202019-02-28%20Meeting%20%23249.docx  
 
4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2019-03-28
b.In progress
i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26
 
5.Issues [8:20 am PT]
a.APPLIED
i. ODATA-1282 How to set the mediaReadLink and mediaEditLink of a stream property
1.https://github.com/oasis-tcs/odata-vocabularies/pull/37/files 
2.Only merge pull request, keep Jira issue in APPLIED state until document walk-through
ii.ODATA-1273 Define mapping of permission scopes to resources
1.https://github.com/oasis-tcs/odata-vocabularies/pull/35/files 
 
b.V4.01: NEW or OPEN
i.ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand
ii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
iii.ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)
iv.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL
v.ODATA-1286 What is the meaning of year 0, and negative years
 
vi.ODATA-1064 Add ability to annotate collections to return only count and NextLink
vii.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
 
c.Data Aggregation: NEW or OPEN
i.ODATA-1218 Transformations for recursive hierarchy processing
ii.ODATA-945 Correct examples 53 and 54
 
d.Vocabularies: NEW or OPEN with concrete proposal
i.ODATA-1287 Annotate a property as "late updatable"
ii.ODATA-1285 ODATA-1099 / Add ReadableByKey to ReadRestrictions
1.https://github.com/oasis-tcs/odata-vocabularies/pull/41/files 
iii.ODATA-1264 CRUDQ descriptions on entity sets
1.https://github.com/oasis-tcs/odata-vocabularies/pull/40/files 
 
e.Vocabularies: NEW or OPEN that need more discussion
i.ODATA-1275 Describing and querying "JSON properties"
ii.ODATA-1214 Annotate constructor actions
iii.ODATA-1140 ODATA-884 / Add details to HttpResponse
iv.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"
v.ODATA-1060 Improve specification of element response requirements
vi.ODATA-884 Allow describing possible responses to requests for a particular resource (public comment c201510e00019)
 
6.Next meetings [9:50 am PT]
a.Thursday March 14, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
b.Thursday March 21, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
c.Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
d.Thursday April 04, 2019 during 8-10 am PDT (17:00-17:00 CET)
 
7.AOB and wrap up [9:55 am PT]
 
[2] References
Chat room: https://soaphub.org/conf/room/odatatc 
Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098 
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm 
 
[3] Timeline
https://www.oasis-open.org/committees/download.php/64563/TC%20Timeline%202019-01-23.docx
[17:00] anonymous morphed into Ted Jones (Red Hat)

 

[17:01] Ralf Handl (SAP): Voting Members: 5 of 9 (55%) (used for quorum calculation)

 

[17:02] anonymous2 morphed into Mike Pizzo (Microsoft)

 

[17:02] Ralf Handl (SAP): Achieved quorum: yes

 

[17:03] anonymous morphed into Mark Biamonte (Progress)

 

[17:03] Ralf Handl (SAP): Voting Members: 6 of 9 (66%) (used for quorum calculation)
[17:03] Ralf Handl (SAP): 2.Approve agenda [8:05 am PT]
[17:04] Ralf Handl (SAP): New issue: https://issues.oasis-open.org/browse/ODATA-1288 - Precisely specify the format of the Error Response
[17:05] Ralf Handl (SAP): New issue: https://issues.oasis-open.org/browse/ODATA-1289 - Capabilities: use Edm.Boolean instead of Core.Tag as a type for properties
[17:06] Ralf Handl (SAP): Agenda approved with these changes
[17:06] Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from February 28, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64790/Minutes%20of%202019-02-28%20Meeting%20%23249.docx
[17:07] Ralf Handl (SAP): Mike: look great
[17:07] Ralf Handl (SAP): Minutes are approved
[17:08] Ralf Handl (SAP): Ted will keep minutes next meeting
[17:08] Ralf Handl (SAP): Thanks!
[17:08] Ralf Handl (SAP): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2019-03-28
b.In progress
i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26
[17:08] Ralf Handl (SAP): No news

 

[17:09] anonymous morphed into Ramesh Reddy(RedHat)

 

[17:09] Ralf Handl (SAP): 5.Issues [8:20 am PT]
[17:09] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-1289 - Capabilities: use Edm.Boolean instead of Core.Tag as a type for properties

 

[17:12] Mike Pizzo (Microsoft): SelectSupportType:
Property
Type
Description
Supported
Boolean
Supports $select
Expandable
Boolean
$expand within $select is supported
Filterable
Boolean
$filter within $select is supported
Searchable
Boolean
$search within $select is supported
TopSupported
Tag
$top within $select is supported
SkipSupported
Tag
$skip within $select is supported
ComputeSupported
Tag
$compute within $select is supported
Countable
Boolean
$count within $select is supported
Sortable
Boolean
$orderby within $select is supported
[17:12] Mike Pizzo (Microsoft): <ComplexType Name="SelectSupportType">
 
        <Property Name="Supported" Type="Edm.Boolean" Nullable="false" DefaultValue="true">
 
          <Annotation Term="Core.Description" String="Supports $select" />
 
        </Property>
 
        <Property Name="Expandable" Type="Edm.Boolean" Nullable="false" DefaultValue="false">
 
          <Annotation Term="Core.Description" String="$expand within $select is supported" />
 
        </Property>
 
        <Property Name="Filterable" Type="Edm.Boolean" Nullable="false" DefaultValue="false">
 
          <Annotation Term="Core.Description" String="$filter within $select is supported" />
 
        </Property>
 
        <Property Name="Searchable" Type="Edm.Boolean" Nullable="false" DefaultValue="false">
 
          <Annotation Term="Core.Description" String="$search within $select is supported" />
 
        </Property>
 
        <Property Name="TopSupported" Type="Core.Tag" Nullable="false" DefaultValue="false">
 
          <Annotation Term="Core.Description" String="$top within $select is supported" />
 
        </Property>
 
        <Property Name="SkipSupported" Type="Core.Tag" Nullable="false" DefaultValue="false">
 
          <Annotation Term="Core.Description" String="$skip within $select is supported" />
 
        </Property>
 
        <Property Name="ComputeSupported" Type="Core.Tag" Nullable="false" DefaultValue="false">
 
          <Annotation Term="Core.Description" String="$compute within $select is supported" />
 
        </Property>
 
        <Property Name="Countable" Type="Edm.Boolean" Nullable="false" DefaultValue="false">
 
          <Annotation Term="Core.Description" String="$count within $select is supported" />
 
        </Property>
 
        <Property Name="Sortable" Type="Edm.Boolean" Nullable="false" DefaultValue="false">
 
          <Annotation Term="Core.Description" String="$orderby within $select is supported" />
 
        </Property>
 
      </ComplexType>

 

[17:13] Ralf Handl (SAP): Inconsistency: some Boolean, some Tag
[17:14] Ralf Handl (SAP): Tag was designed as a type for a tagging term with default value "true"
[17:14] Ralf Handl (SAP): Here used for properties with default value "false"

 

[17:14] Mike Pizzo (Microsoft): Should only use Core.Tag for Boolean terms, not properties

 

[17:15] Ralf Handl (SAP): ODATA-1289 is OPEN
[17:16] Ralf Handl (SAP): Proposal: See summary: only use Core.Tag for tagging terms with default value "true"

 

[17:17] Mike Pizzo (Microsoft): Slightly amended: 
See summary: only use Core.Tag for tagging terms with default value "true":
Replace existing use of Core.Tag in properties (i.e., in SelectSupportType) with Edm.Boolean.
[17:18] Mike Pizzo (Microsoft): I move to resolve ODATA-1289 as proposed

 

[17:18] George Ericson (Dell): Second

 

[17:18] Ralf Handl (SAP): ODATA-1289 is RESOLVED with the above proposal
[17:18] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-1288 - Precisely specify the format of the Error Response
[17:19] Ralf Handl (SAP): Change paragraphs 3 to 5 in chapter 21 Error Response:
 
The value for the code name/value pair is a language-independent string. Its value is a service-defined error code. This code serves as a sub-status for the HTTP error code specified in the response.
 
The value for the message name/value pair MUST beis a string containing a human-readable, language-dependent representation of the error. The Content-Language header MUST contain the language code from [[RFC5646]|#rfc5646] corresponding to the language in which the value for message is written.
 
The value for the target name/value pair is a string containing the target of the particular error (for example, the name of the property in error).
 
Neither code nor message nor target can have the value null.

 

[17:20] George Ericson (Dell): Change specification text to say that value is a string or an indication of null.

 

[17:25] anonymous morphed into Saurabh Madan

 

[17:26] Ralf Handl (SAP): We need to specify the format-independent minimal content of an error response body in Protocol
[17:26] Ralf Handl (SAP): code: non-empty string, not null
[17:27] Ralf Handl (SAP): code: not language-dependent
[17:27] Ralf Handl (SAP): message: language-dependent, non-empty, not null, human-readable
[17:28] Ralf Handl (SAP): target: string, can be null, can be omitted, can be empty
[17:31] Ralf Handl (SAP): details: collection of structured instances with code, message, target, same rules as above
[17:32] Ralf Handl (SAP): innererror: optional, structured instance, anything goes
[17:34] Ralf Handl (SAP): Make comment about security concerns "global" to error response, not only specific to innererror
[17:35] Ralf Handl (SAP): ODATA-1288 is OPEN

 

[17:37] Mike Pizzo (Microsoft): I move we resolve ODATA-1288 with the revised proposal.

 

[17:37] George Ericson (Dell): Second

 

[17:38] Ralf Handl (SAP): ODATA-1288 is RESOLVED with the revised proposal
[17:38] Ralf Handl (SAP): a.APPLIED
i. ODATA-1282 How to set the mediaReadLink and mediaEditLink of a stream property
1.https://github.com/oasis-tcs/odata-vocabularies/pull/37/files 
2.Only merge pull request, keep Jira issue in APPLIED state until document walk-through

 

[17:41] Mike Pizzo (Microsoft): I move we approve the application of ODATA-1282 as applied and merge https://github.com/oasis-tcs/odata-vocabularies/pull/37/files.

 

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

 

[17:41] George Ericson (Dell): second

 

[17:42] Ralf Handl (SAP): No objection, motion passes
[17:45] Ralf Handl (SAP): b.V4.01: NEW or OPEN
i.ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand
[17:47] Ralf Handl (SAP): Mike: concerns about referencing outside instead of passing in an alias
[17:47] Ralf Handl (SAP): Skip for today
[17:47] Ralf Handl (SAP): ii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
[17:48] Ralf Handl (SAP): 5.2.3ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
[12:26] Ralf Handl (SAP): Current text in JSON Format
An entity reference (see [OData-Protocol]) MAY take the place of an entity in a JSON payload, based on the client request. It is serialized as a JSON object that MUST contain the id of the referenced entity and MAY contain the type control information and instance annotations, but no additional properties.
[12:54] Ralf Handl (SAP): Mike: semantics described in the issue is correct
[12:55] Ralf Handl (SAP): Question: in JSON Format: if we have an object with @id and @etag: is this a reference or is this a very rudimentary object?

 

[17:49] Mike Pizzo (Microsoft): Proposed updated Proposal:
Make clear that EntityCollection/$ref and SingleEntity/$ref are intentionally allowed to return an ETag.
EntityCollection/$ref (where EntityCollection is an entity set or collection-valued navigation path) may have an (own) ETag returned in the ETag header which changes if the list of references changes, i.e. a reference is added or removed.
SingleNavigation/$ref (where SingleNavigation is a single-valued navigation path) may have an ETag which represents the identity of the related entity. If the relationship is changed to point to a different OData entity, the ETag MUST change.
Note: the ETag for an entity reference (i.e. EntitySet(key)/$ref) can never change.
In JSON, if an object contains an etag then it is a (possibly minimal) representation of the object, not an entity reference. 
so:
{"@id":"people(1)"} 
is an entity reference to the resource in the people entity set with the key value 1, where:
{"@id":"people(1)","@etag":"xyz123"} 
is a minimal representation of the resource (not the reference), just as
{"@id":"people(1)","name":"maggie"}
is a minimal representation of the resource.
So, if 
{"@id":"people(1)","@etag":"xyz123"} 
is returned, the etag refers to the person (and not the reference) and changes if any properties of the person changes.
[17:54] Mike Pizzo (Microsoft): updated proposal:
 
Make clear that EntityCollection/$ref and SingleEntity/$ref are intentionally allowed to return an ETag.
EntityCollection/$ref (where EntityCollection is an entity set or collection-valued navigation path) may have an (own) ETag returned in the ETag header which changes if the list of references changes, i.e. a reference is added or removed.
SingleNavigation/$ref (where SingleNavigation is a single-valued navigation path) may have an ETag which represents the identity of the related entity. If the relationship is changed to point to a different OData entity, the ETag MUST change.
Note: the ETag for an entity reference (i.e. EntitySet(key)/$ref) can never change.
In JSON, if an object contains an etag (or other control information other than type) then it is a representation of the object, not an entity reference. 
so:
{"@id":"people(1)"} 
is an entity reference to the resource in the people entity set with the key value 1, where:
{"@id":"people(1)","@etag":"xyz123"} 
is a minimal representation of the resource (not the reference), just as
{"@id":"people(1)","name":"maggie"} 
is a minimal representation of the resource.
So, if 
{"@id":"people(1)","@etag":"xyz123"} 
is returned, the etag refers to the person (and not the reference) and changes if any properties of the person changes.
[17:55] Mike Pizzo (Microsoft): I move to resolve ODATA-1168 as proposed.

 

[18:04] Ralf Handl (SAP): Example 29: collection of entity references
 
{
 
  "@context": "http://host/service/$metadata#Collection($ref)",
 
  "value": [
 
    { "@id": "Orders(10643)" },
 
    { "@id": "Orders(10759)" }
 
  ]
 
}

 

[18:05] George Ericson (Dell): second

 

[18:05] Ralf Handl (SAP): ODATA-1168 is RESOLVED as proposed
[18:06] Ralf Handl (SAP): iii.ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)
[18:08] Ralf Handl (SAP): If present, the request MUST only be processed if the specified ETag value matches the current ETag value of the target resource. Services sending ETag headers with weak ETags that only depend on the representation-independent entity state MUST use the weak comparison function because it is sufficient to prevent accidental overwrites. This is a deviation from [RFC7232].
[18:11] Ralf Handl (SAP): 8.2.4 Header If-Match
As defined in [RFC7232], a client MAY include an If-Match header in a request to GET, PUT, PATCH or DELETE. The value of the If-Match request header MUST be an ETag value previously retrieved for the resource, or * to match any value.
 
If an operation on an existing resource requires an ETag, (see Core.OptimisticConcurrency in [OData-VocCore]) and the client does not specify an If-Match request header in a Data Modification Request or in an Action Request bound to the resource, the service responds with a 428 Precondition Required and MUST ensure that no observable change occurs as a result of the request.
 
If present, the request MUST only be processed if the specified ETag value matches the current ETag value of the target resource. Services sending ETag headers with weak ETags that only depend on the representation-independent entity state MUST use the weak comparison function because it is sufficient to prevent accidental overwrites. This is a deviation from [RFC7232].
 
If the value does not match the current ETag value of the resource for a Data Modification Request or Action Request, the service MUST respond with 412 Precondition Failed and MUST ensure that no observable change occurs as a result of the request. In the case of an upsert, if the addressed entity does not exist the provided ETag value is considered not to match.
 
An If-Match header with a value of * in a PUT or PATCH request results in an upsert request being processed as an update and not an insert.
 
The If-Match header MUST NOT be specified on a batch request, but MAY be specified on individual requests within the batch.

 

[18:14] Mike Pizzo (Microsoft): I move to close ODATA-1198 with no action.

 

[18:14] George Ericson (Dell): second

 

[18:14] Mark Biamonte (Progress): I second

 

[18:15] Ralf Handl (SAP): No objections, ODATA-1198 is CLOSED without action

 

[18:16] Mike Pizzo (Microsoft): Sorry; we missed an issue raised by Evan in ODATA-1168.  I created ODATA-1290 to track that issue.

 

[18:17] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-1290
[18:17] Ralf Handl (SAP): ODATA-1290 is OPEN

 

[18:17] Mike Pizzo (Microsoft): I move we resolve ODATA-1290 as proposed

 

[18:17] Ted Jones (Red Hat): I second

 

[18:17] George Ericson (Dell): Second

 

[18:18] Ralf Handl (SAP): ODATA-1290 is RESOLVED as proposed
[18:18] Ralf Handl (SAP): iv.ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL
[18:23] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-1260
[18:24] Ralf Handl (SAP): Mike: in case edit and read URL differ, PATCH/PUT to the read URL will likely fail
[18:30] Ralf Handl (SAP): To update an individual entity, the client makes a PATCH or PUT request to a URL that identifies the entity. Services MAY restrict updates to requests to the edit URL of the entity.
[18:33] Ralf Handl (SAP): ODATA-1260 is OPEN

 

[18:37] Mark Biamonte (Progress): I move to Resolve OData-1260 as proposed

 

[18:37] Mike Pizzo (Microsoft): I second

 

[18:38] Ralf Handl (SAP): ODATA-1260 is RESOLVED with the amended proposal
[18:38] Ralf Handl (SAP): v.ODATA-1286 What is the meaning of year 0, and negative years
[18:38] Ralf Handl (SAP): https://issues.oasis-open.org/browse/ODATA-1286
[18:42] Ralf Handl (SAP): ODATA-1286 is OPEN
[18:47] Ralf Handl (SAP): http://dotat.at/tmp/ISO_8601-201x-1-DIS.pdf
[18:48] Ralf Handl (SAP): year = positiveYear | negativeYear | "0000" ;
[18:49] Ralf Handl (SAP): NOTE In the proleptic Gregorian calendar, the calendar year [0000] is a leap year

 

[18:49] George Ericson (Dell)1: http://dotat.at/tmp/ISO_8601-201x-1-DIS.pdf

 

[18:56] Ralf Handl (SAP): https://en.wikipedia.org/wiki/ISO_8601
[18:56] Ralf Handl (SAP): To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation but only by prior agreement between the sender and the receiver.[19] An expanded year representation [YYYYY] must have an agreed-upon number of extra year digits beyond the four-digit minimum, and it must be prefixed with a + or  sign[20] instead of the more common AD/BC (or CE/BCE) notation; by convention 1 BC is labelled +0000, 2 BC is labeled 0001, and so on.[21]
[18:58] Ralf Handl (SAP): Skip for today and try to find a normative reference
[18:58] Ralf Handl (SAP): 6.Next meetings [9:50 am PT]
a.Thursday March 14, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
b.Thursday March 21, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
c.Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET)  Europe still on winter time
d.Thursday April 04, 2019 during 8-10 am PDT (17:00-17:00 CET)
[19:00] Ralf Handl (SAP): 7.AOB and wrap up [9:55 am PT]
[19:01] Ralf Handl (SAP): Meeting is adjourned

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 6. März 2019 11:33
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-03-07

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday March 07, 2019 during 8-10 am PST (17:00-19:00 CET). 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:00 am PT]

    1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=47976

 

2.        Approve agenda [8:05 am PT]

 

3.        Approve minutes from previous meeting(s) [8:10 am PT]

    1. Minutes from February 28, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/64790/Minutes%20of%202019-02-28%20Meeting%20%23249.docx  

 

4.        Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]

    1. Upcoming

                                  i.    #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-03-28

    1. In progress

                                  i.    #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

 

5.        Issues [8:20 am PT]

    1. APPLIED

                                  i.     ODATA-1282 How to set the mediaReadLink and mediaEditLink of a stream property

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/37/files
        2. Only merge pull request, keep Jira issue in APPLIED state until document walk-through

                                 ii.    ODATA-1273 Define mapping of permission scopes to resources

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/35/files

 

    1. V4.01: NEW or OPEN

                                  i.    ODATA-1284 Allow referencing properties of "outer" entity in expressions nested within $expand

                                 ii.    ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

                                iii.    ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)

                                iv.    ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL

                                 v.    ODATA-1286 What is the meaning of year 0, and negative years

 

                                vi.    ODATA-1064 Add ability to annotate collections to return only count and NextLink

                               vii.    ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

 

    1. Data Aggregation: NEW or OPEN

                                  i.    ODATA-1218 Transformations for recursive hierarchy processing

                                 ii.    ODATA-945 Correct examples 53 and 54

 

    1. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1287 Annotate a property as "late updatable"

                                 ii.    ODATA-1285 ODATA-1099 / Add ReadableByKey to ReadRestrictions

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/41/files

                                iii.    ODATA-1264 CRUDQ descriptions on entity sets

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/40/files

 

    1. Vocabularies: NEW or OPEN that need more discussion

                                  i.    ODATA-1275 Describing and querying "JSON properties"

                                 ii.    ODATA-1214 Annotate constructor actions

                                iii.    ODATA-1140 ODATA-884 / Add details to HttpResponse

                                iv.    ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

                                 v.    ODATA-1060 Improve specification of element response requirements

                                vi.    ODATA-884 Allow describing possible responses to requests for a particular resource (public comment c201510e00019)

 

6.        Next meetings [9:50 am PT]

    1. Thursday March 14, 2019 during 8-10 am PDT (16:00-18:00 CET) – Europe still on winter time
    2. Thursday March 21, 2019 during 8-10 am PDT (16:00-18:00 CET) – Europe still on winter time
    3. Thursday March 28, 2019 during 8-10 am PDT (16:00-18:00 CET) – Europe still on winter time
    4. Thursday April 04, 2019 during 8-10 am PDT (17:00-17:00 CET)

 

7.        AOB and wrap up [9:55 am PT]

 

[2] References

 

[3] Timeline

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]