[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-15 - chat transcript
Room information was updated by: Stefan Pleas register your attendance at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39120 approx. 15 minutes before or during the meeting. Thanks
Stefan: Info=>Voting Members: 1 of 13 (7%) (used for quorum calculation) anonymous morphed into Matt Borges (SAP) Ralf Handl (SAP): Voting Members: 7 of 13 (53%) (used for quorum calculation) Ralf Handl (SAP): Achieved quorumyes Ralf Handl (SAP): 2.Approve agenda [8:05am PT] Ralf Handl (SAP): Agenda approved Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10am PT] a.Minutes from October 08, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56677/odata-meeting-108_on-20151008-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:20am PT] Ralf Handl (SAP): a.Issues for Data Aggregation in New or Open state i.ODATA-866 3.14 Transformation compute: add reference to numeric promotion rules
Ralf Handl (SAP): Explicitly refer to URL Conventions and add sentence: The type of the property is determined by the rules for evaluating $filter expressions and numeric promotion defined in [OData-URL].
Ralf Handl (SAP): ODATA-866 is OPEN Hubert Heijkers: I move to resolve ODATA-866 as proposed. Gerald Krause (SAP): I second. Ralf Handl (SAP): ODATA-866 is resolved as proposed Ralf Handl (SAP): b.Review documents i.Specification document: https://www.oasis-open.org/committees/download.php/56661/odata-data-aggregation-ext-v4.0-wd04-2015-10-09.docx
ii.Summary of changes; https://www.oasis-open.org/committees/download.php/56662/odata-data-aggregation%20CSD03%20Summary%20of%20Non-Material%20Changes.docx
iii.ABNF Changes: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-abnf.txt?op=diff&rev=729
iv.ABNF Testcases: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-testcases.xml?op=diff&rev=752
Ralf Handl (SAP): Fix version V4.0_CS02 Ralf Handl (SAP): Affects version: V4.0_CSD03 Ralf Handl (SAP): ODATA-871: Clarify that properties added with Compute MUST include the odata.type (if not described in $metadata) Ralf Handl (SAP): ODATA-871 is OPEN Ralf Handl (SAP): Proposal: Clarify that properties added with Compute or Aggregated MUST include the odata.type following rules defined for dynamic properties Hubert Heijkers: I move to resolve ODATA-871 as proposed. Mike Pizzo: I second Ralf Handl (SAP): ODATA-871 is resolved as proposed Ralf Handl (SAP): 6.JSON CSDL [8:40am PT] Ralf Handl (SAP): a.Issues for JSON Format for CSDL in New or Open state i.ODATA-862 Represent all type references as JSON Schema types/references
Ralf Handl (SAP): ODATA-862 is OPEN Ralf Handl (SAP): Example for entity sets Ralf Handl (SAP): "entitySets": { "Waldos": {
"entityType": { "$ref": "#/definitions/Schema.Two.Waldo"
}
},
"Freds": {
"entityType": {
"$ref": "#/definitions/Schema.Two.Fred"
},
"navigationPropertyBindings": {
"Waldos": {
"target": "Waldos" },
"MoreWaldos": {
"target": "Namespace.Container/Freds"
},
"EvenMoreWaldos": {
"target": "Namespace.Container/Orders/Items/M.E/Nav"
}
}
}
Ralf Handl (SAP): before "entitySets": { "Waldos": { "entityType": {
"$ref": "#/definitions/Schema.Two.Waldo"
}
},
"Freds": {
"entityType": {
"$ref": "#/definitions/Schema.Two.Fred"
},
"navigationPropertyBindings": {
"Waldos": {
"target": "Waldos" },
"MoreWaldos": {
"target": "Namespace.Container/Freds"
},
"EvenMoreWaldos": {
"target": "Namespace.Container/Orders/Items/M.E/Nav"
}
}
}
Ralf Handl (SAP): "entitySets": { "Waldos": {
"entityType": { "$ref": "#/definitions/Schema.Two.Waldo"
}
},
"Freds": {
"entityType": {
"$ref": "#/definitions/Schema.Two.Fred"
},
"navigationPropertyBindings": {
"Waldos": {
"target": "Waldos" },
"MoreWaldos": {
"target": "Namespace.Container/Freds"
},
"EvenMoreWaldos": {
"target": "Namespace.Container/Orders/Items/M.E/Nav"
}
}
}
Ralf Handl (SAP): "Freds": { "entityType": "Schema.Two.Fred"
},
Ralf Handl (SAP): "functionImports": { "Bar": {
"function": {
"$ref": "#/schemas/Schema.One/functions/Foo"
},
"includeInServiceDocument": true,
"entitySet": "Namespace.Container/Freds"
},
"CreatedEntities": {
"function": {
"$ref": "#/schemas/Model1/functions/CreatedEntities"
},
"entitySet": "Waldos"
}
}
Ralf Handl (SAP): "functions": { "Foo": {
"returnType": {
"type": [
"string",
"null"
],
"maxLength": 42
}
},
Ralf Handl (SAP): "Schema.One": { "actions": {
"Rejection": [
{
},
{
"isBound": true,
"parameters": {
"in": { "$ref": "#/definitions/Schema.One.Waldo"
} }
},
{
"isBound": true,
"parameters": {
"in": {
"$ref": "#/definitions/Schema.One.Waldo"
},
"Reason": {
"type": [
"string",
"null"
]
}
}
}
]
},
Ralf Handl (SAP): JSON Payloads with function advertising: {
"@odata.context": "http://host/service/$metadata#LeaveRequests/$entity",
"#Model.Approval": {},
...
}
Ralf Handl (SAP): Mike: should we include patternProperties in all schemas for entity types and complex types for annotations and for action/function advertisement? Ralf Handl (SAP): Mike to open a Jira issue Mike Pizzo: I move to resolve ODATA-862 as proposed Hubert Heijkers: I second Ralf Handl (SAP): ODATA-862 is resolved as proposed Mike Pizzo: I move we close ODATA_862 as applied. Hubert Heijkers: I second Ted Jones (Red Hat): I second Ralf Handl (SAP): ODATA-862 is closed as applied Ralf Handl (SAP): ii.ODATA-863 ODATA-618 / Represent Terms similar to Types Ralf Handl (SAP): ODATA-863 is OPEN Ralf Handl (SAP): $ref:#/definitions/Namespace.Typename Ralf Handl (SAP): $ref:#/schemas/Namespace/functions/Functionname Ralf Handl (SAP): Defer ODATA-863 until we resolve ODATA-618 Ralf Handl (SAP): iii.ODATA-864 Translate @Core.Description annotations into JSON Schema description keywords Ralf Handl (SAP): "Model1.Size": { "enum": [
"Small",
"Medium",
"Large"
],
"@Core.Description": "Sizes"
},
Ralf Handl (SAP): "Model1.Size": { "enum": [
"Small",
"Medium",
"Large"
],
"description": "Sizes"
},
Ralf Handl (SAP): ODATA-864 is OPEN Mike Pizzo: I move we resolve ODATA-864 as proposed. Hubert Heijkers: I second Ralf Handl (SAP): ODATA-864 is resolved as proposed 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
Ralf Handl (SAP): "Price": { "type": [
"number",
"string",
"null"
],
"format": "decimal",
"precision": 15,
"scale": 3,
"multipleOf": 1e-3,
"minimum": -999999999999.999,
"maximum": 999999999999.999
},
Ralf Handl (SAP): Hubert: precision and scale missing in Example 14: nullable property Price of type Edm.Decimal with precision 15 and scale 3 Ralf Handl (SAP): Mike: add precision and scale to table, comment that these are OData-specific keywords Mike Pizzo: Added to issue: Mike Pizzo: Add "precision/scale" to primitive types table in 4.1.2.1, Primitive Properties. Also add precision, scale and format (decimal) to "Price" in example 14 as per description.
In Example 8, add multipleOf, minimum, maximum, and precision to "DecimalValue"
Price in Example 44 looks correct, just a little weird at first (and thus good to have the example).
(also update numbering of examples)
Ralf Handl (SAP): Ralf/Mike: add comments to example 44 explaining the weirdness Ralf Handl (SAP): ii.ODATA-855 Should we define patterns for some of the primitive types Ralf Handl (SAP): "TimeOfDayValue": { "type": [
"string",
"null"
],
"format": "time",
"precision": 6,
"default": "07:59:59.999"
},
Ralf Handl (SAP): iii.ODATA-856 Add annotations for Min/Max/Pattern Mike Pizzo: Example 15 still has a pattern for "Created" Example 20 still has a pattern for "ExactTimeStamp"
Ralf Handl (SAP): 9.Next meeting [9:50am PT] a.Thursday October 22, 2015 during 8-10am PT?
Ralf Handl (SAP): 10.AOB and wrap up [9:55am PT] From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf Item 7.a.iii: added
ODATA-870 From: Handl, Ralf Item 7.a.iii: added
ODATA-828 From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf Item 6: added “c. Review document” Item 8: corrected to “V4.01” 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 15, 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=39120
2.
Approve agenda [8:05am PT]
3.
Approve minutes from previous meeting(s) [8:10am PT]
a.
Minutes from October 08, 2015 TC meeting:
https://www.oasis-open.org/committees/download.php/56677/odata-meeting-108_on-20151008-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:20am PT]
a.
Issues
for Data Aggregation in New or Open state
i. ODATA-866
3.14 Transformation compute: add reference to numeric promotion rules
b.
Review documents
i. Specification document:
https://www.oasis-open.org/committees/download.php/56661/odata-data-aggregation-ext-v4.0-wd04-2015-10-09.docx
ii. Summary of changes;
https://www.oasis-open.org/committees/download.php/56662/odata-data-aggregation%20CSD03%20Summary%20of%20Non-Material%20Changes.docx
iii. ABNF Changes:
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-abnf.txt?op=diff&rev=729
iv. ABNF Testcases:
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-testcases.xml?op=diff&rev=752
6.
JSON CSDL [8:40am PT]
a.
Issues
for JSON Format for CSDL in New or Open state
i. ODATA-862
Represent all type references as JSON Schema types/references
ii. ODATA-863
ODATA-618 / Represent Terms similar to Types
iii. ODATA-864
Translate @Core.Description annotations into JSON Schema description keywords
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
c.
Review document
i. Specification document:
https://www.oasis-open.org/committees/download.php/56653/odata-json-csdl-v4.0-wd01-2015-10-08.docx
7.
V4.0 Errata 03 [9:00am 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:20am 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 October 22, 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/46401/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]