[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [odata] Agenda for OData TC meeting on 2015-10-29 - chat transcript
anonymous morphed into Matt Borges (SAP) Ralf Handl (SAP): Please note: screen sharing and phone conference via https://sap.emea.pgiconnect.com/OData-TC/ Ralf Handl (SAP): Voting Members: 7 of 13 (53%) (used for quorum calculation) Ralf Handl (SAP): Achieved quorum:yes Ralf Handl (SAP): 2.Approve agenda [8:05am PT] Ralf Handl (SAP): Mike: add ODATA-877 and ODATA-876 to Agenda, both regard Change Tracking / Delta Ralf Handl (SAP): Mike: Proposal ready for V4.01 Simplified Syntax issue group, agenda item 8.a.x, move this up Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10am PT] Ralf Handl (SAP): a.Minutes from October 22, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56756/odata-meeting-110_on-20151022-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] Ralf Handl (SAP): a.Action items due i.Propose factoring of CSDL documents (Mike Pizzo)
Ralf Handl (SAP): Mike showed an approach where we have three documents: one for JSON, one for XML, and one for the shared parts. The format-specific documents link in sections of the shared part to have all necessary content for the format. Ralf Handl (SAP): Seems to work with change-tracking as well as HTML export Ralf Handl (SAP): Mike to check with Chet Ensign of TC Administration whether we can use this approach Ralf Handl (SAP): 5.JSON Format for CSDL [8:20am PT] Ralf Handl (SAP): a.Issues for JSON Format for CSDL in New or Open state i.ODATA-875 Use of $ref for referencing elements in a JSON Schema
ii.ODATA-872 Consider defining structure of bound actions/functions
iii.ODATA-863 ODATA-618 / Represent Terms similar to Types
Ralf Handl (SAP): ODATA-875: Use of $ref for referencing elements in a JSON Schema Ralf Handl (SAP): ODATA-875 is OPEN Ralf Handl (SAP): "ODataDemo.Supplier": { "type": "object",
"keys": [
{
"name": "ID"
}
],
"properties": {
"ID": {
"type": "string"
},
"Name": {
"type": [
"string",
"null"
]
},
"Address": {
"$ref": "#/definitions/ODataDemo.Address"
},
"Concurrency": {
"type": "integer",
"format": "int32"
},
"Products": {
"type": "array",
"items": {
"$ref": "#/definitions/ODataDemo.Product"
},
"relationship": {
"partner": "Supplier"
}
}
}
},
Ralf Handl (SAP): Mike: explore ways to make sure that /definitions/ schemas only use $ref to reference structured types and forbid inline definition of structured types Ralf Handl (SAP): "schemas": { "Org.OData.Core.V1": {
"$ref": "https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.json#/schemas/Org.OData.Core.V1"
},
"Core": {
"$ref": "https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.json#/schemas/Org.OData.Core.V1"
},
"Org.OData.Measures.V1": {
"$ref": "https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Measures.V1.json#/schemas/Org.OData.Measures.V1"
},
"UoM": {
"$ref": "https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Measures.V1.json#/schemas/Org.OData.Measures.V1"
},
Ralf Handl (SAP): "entitySets": { "Products": {
"entityType": {
"$ref": "#/definitions/ODataDemo.Product"
},
"navigationPropertyBindings": {
"Category": {
"target": "Categories"
}
}
},
Ralf Handl (SAP): "entitySets": { "Products": {
"entityType": "ODataDemo.Product",
"navigationPropertyBindings": {
"Category": {
"target": "Categories"
}
}
},
Ralf Handl (SAP): "singletons": { "Contoso": {
"type": {
"$ref": "#/definitions/ODataDemo.Supplier"
},
"navigationPropertyBindings": {
"Products": {
"target": "Products"
}
}
}
},
"functionImports": {
"ProductsByRating": {
"entitySet": "Products",
"function": {
"$ref": "#/schemas/ODataDemo/functions/ProductsByRating"
}
}
}
Ralf Handl (SAP): "ODataDemo": { "functions": {
"ProductsByRating": {
"parameters": [
{
"name": "Rating",
"type": [
"integer",
"null"
],
"format": "int32"
}
],
"returnType": {
"type": "array",
"items": {
"$ref": "#/definitions/ODataDemo.Product"
}
}
}
},
Ralf Handl (SAP): Mike: we should consistently refer to named types via $ref Mike Pizzo: One option: 1) Always use $ref to reference a named type (complex, entity, typedef, enum) 2) We use odata paths to represent entity sets and singletons
3) For functions and actions, use $ref
Mike Pizzo: (we could go either way on 3), we just need to pick one...) Mike Pizzo: I move to resolve ODATA-875 as proposed. Mark Biamonte (Progress): I second Ralf Handl (SAP): ODATA-875 is resolved as proposed Ralf Handl (SAP): ii.ODATA-872 Consider defining structure of bound actions/functions Ralf Handl (SAP): Services that want to explicitly advertise actions or function can do this via "properties": {
...,
"#My.SpecificFunction":{
"$ref":"http://docs.oasis-open.org/odata/odata-json-csdl/v4.0/edm.json#/definitions/odata.actionFunctionAdvertisement"
}
}
or more generic via a patternProperty for pattern "^#".
Ralf Handl (SAP): Mike: also have definition that defines this patternProperty use and can be included using anyOf Ralf Handl (SAP): annotatableStructuredType Ralf Handl (SAP): bindableStructuredType Mike Pizzo: Proposal: Mike Pizzo: 1) Define the structure of a function or action 2) Define an bindableStructuredType that includes property patterns for:functions/actions (that uses the structure above)
3) Define an annotatableStructuredType that includes property patterns for annotations
Ralf Handl (SAP): 1) Define the structure of a function or action advertisement Mike Pizzo: updated: 1) Define the structure of a function or action advertisement 2) Define an bindableStructuredType that includes property patterns for:functions/actions (that uses the structure above)
3) Define an annotatableStructuredType that includes property patterns for annotations
Mike Pizzo: I move we resolve ODATA-872 as proposed Mark Biamonte (Progress): I second Ralf Handl (SAP): ODATA-872 is resolved as proposed Ralf Handl (SAP): 6.Next Face-to-Face Meeting [9:00am PT] a.When?
b.Where/hosted by whom?
Ralf Handl (SAP): a. When: first week of February 2016, 01-05 Ralf Handl (SAP): All: check til next meeting whether this works, alternatives, and possible locations Ralf Handl (SAP): Topics: finish CSD01 for JSON CSDL Ralf Handl (SAP): Get agreement on scope and shape of V4.01, prepare draft documents Ralf Handl (SAP): 7.V4.0 ERRATA03 [9:20am PT] Ralf Handl (SAP): ODATA-877 Must delta responses continue to track "orphaned" entities? Ralf Handl (SAP): Mike: we already specify that entities no longer matching the filter of the initial request fall out Ralf Handl (SAP): What about entities that were only expanded into the result and would now no longer be expanded Ralf Handl (SAP): The tricky bit is whether tombstones have to be sent if an expanded entity becomes disconnected Ralf Handl (SAP): Matt: would be nice for the client to get a tombstone to clean up the local store, but might be hard for the server to figure out when to do that Ralf Handl (SAP): Mike: two books by the same author: one book drops out - author stays, second book drops out - author also drops out Ralf Handl (SAP): ODATA-877 is OPEN Ralf Handl (SAP): Mike to prepare proposal Ralf Handl (SAP): ODATA-876 Allow services to return contained entities inline for delta responses Ralf Handl (SAP): Mike: please take a look at ODATA-876 and get some direction Ralf Handl (SAP): ODATA-876 is OPEN Ralf Handl (SAP): 9.Next meeting [9:50am PT] a.Thursday November 05, 2015 during 8-10am
Ralf Handl (SAP): 9.Next meeting [9:50am PT] a.Thursday November 05, 2015 during 8-10am
Ralf Handl (SAP): 10.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 Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday October 29, 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=39122
2.
Approve agenda [8:05am PT]
3.
Approve minutes from previous meeting(s) [8:10am PT]
a.
Minutes from October 22, 2015 TC meeting:
https://www.oasis-open.org/committees/download.php/56756/odata-meeting-110_on-20151022-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. Propose
factoring of CSDL documents (Mike Pizzo)
5.
JSON Format for CSDL [8:20am PT]
a.
Issues
for JSON Format for CSDL in New or Open state
i. ODATA-875
Use of $ref for referencing elements in a JSON Schema
ii. ODATA-872
Consider defining structure of bound actions/functions
iii. ODATA-863
ODATA-618 / Represent Terms similar to Types
b.
Review documents
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
c.
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
6.
Next Face-to-Face Meeting [9:00am PT]
a.
When?
b.
Where/hosted by whom?
7.
V4.0 ERRATA03 [9:20am 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
ii. OData JSON Format
1.
ODATA-656 Requesting clarity
on payload ordering constraints for clients
2.
ODATA-828 Update I-JSON
reference
iii. OData Protocol
1.
ODATA-800 Media streams
section does not reference the AtomPub spec
2.
ODATA-830 Header OData-EntityId:
when required
3.
ODATA-837 Example 28:
replace $deltaToken with a valid custom query option
4.
ODATA-869
Explicitly state the location of the Content-ID header in a change set
5.
ODATA-870
Round-off description for creating related entities when creating an entity
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.
8.
V4.01 [9:40am PT]
a.
Issues
for V4.01_WD01 in New or Open state
i. Annotations
1.
ODATA-516 Add super type Edm.AnyPath
for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath
2.
ODATA-735 Enhance the CSDL for instance
annotations
3.
ODATA-786 Extend definition of edm:Path
_expression_
4.
ODATA-811 Define propagation and (partial)
overriding of annotations
5.
ODATA-631 Allow expressing that a
term can be applied any collection and is not restricted to entity sets
ii. Batch
1.
ODATA-480 $batch: remove restriction
"within the same change set " for Content-ID referencing
2.
ODATA-541 Allow the If-Match header
to reference the ETag that resulted from an earlier operation in a batch request
iii. Complex Types
1.
ODATA-560 Allow arbitrary properties
in referential constraints
2.
ODATA-572 Clarify that eq, ne can
be used with complex type
3.
ODATA-617 Allow eq/ne comparison of
instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props
iv. Decimal
1.
ODATA-557 Allow exponential notation
for Edm.Decimal
2.
ODATA-747 Allow IEEE 754 constants
[-]INF and NaN also for Edm.Decimal
v. Enum Types
1.
ODATA-494 Define inheritance for enumeration
types
2.
ODATA-849 Add possibility for enumeration
types to "extend" another enumeration type
vi. Interfaces
1.
ODATA-619 Attach action and function
signatures to terms, i.e. make a term definition an interface definition
2.
ODATA-696 Support "interfaces" for
casting entities to multiple different types
vii. 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
viii. 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
ix. 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
x. 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
xi. OData CSDL
1.
ODATA-674 Specify navigation property
binding combined with containment
2.
ODATA-618 Allow using term names in
positions that allow type names
3.
ODATA-743 Restructure/rename documents
CSDL, JSON Format, and JSON Format for CSDL
4.
ODATA-798 Semantic Key or Alternate
Key for entity types
5.
ODATA-817 Add client-side function
odata.matchesRegularExpression
xii. OData JSON Format
1.
ODATA-656 Requesting clarity on payload
ordering constraints for clients
2.
ODATA-838 Allow inclusion of "untyped
JSON" into JSON requests and responses
3.
ODATA-859 Define term, semantics for
inserting error information into a (mostly) successful response
xiii. OData Protocol
1.
ODATA-824 Header Content-Transfer-Encoding
not used in HTTP
2.
ODATA-846 Add version 4.01
xiv. OData URL Conventions
1.
ODATA-850 Improve document structure
for functions used in common expressions
xv. Vocabularies
1.
ODATA-571 Add annotation for properties that are
(not) part of the default selection if no $select is specified
2.
ODATA-760 Add to depth restrictions to Capabilities
Vocabulary
3.
ODATA-816 Add Capability term for filter _expression_
restrictions
9.
Next meeting [9:50am PT]
a.
Thursday November 05, 2015 during 8-10am PT?
10.
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
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]