Room information was updated by: Stefan
Please register yourselves as usual at https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=39118 Thanks.
Stefan: Voting Members: 1 of 13 (7%) (used for quorum calculation)
anonymous morphed into Matt Borges (SAP)
Stefan: Voting Members: 9 of 13 (69%) (used for quorum calculation)
Stefan: We are quorate
Ralf Handl (SAP): 2.Approve agenda
Ralf Handl (SAP): Agenda is approved
Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [8:10am PT]
a.Minutes from September 24, 2015 TC meeting: https://www.oasis-open.org/committees/download.php/56600/odata-meeting-106_on-20150924-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.Process issues [Issues list: https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA] [8:20am PT]
a.Issues for JSON Format for CSDL in Applied state
Ralf Handl (SAP): i.ODATA-805 Add term to Capabilities vocabulary for supported metadata formats
anonymous morphed into Martin Zurmuehl (SAP)
Ralf Handl (SAP): <Term Name="SupportedMetadataFormats" Type="Collection(Edm.String)" AppliesTo="EntityContainer">
<Annotation Term="Core.Description" String="Media types of supported formats for $metadata, including format parameters" />
<Annotation Term="Core.IsMediaType" />
</Term>
Hubert Heijkers: I move to close ODATA-805 as applied.
Martin Zurmuehl (SAP): I second
Ralf Handl (SAP): ODATA-805 is CLOSED as applied
Ralf Handl (SAP): ii.ODATA-842 Represent primitive types as JSON Schema formats
Ralf Handl (SAP): Example:
"DoubleValue": {
"type": [
"number",
"string",
"null"
],
"format": "double",
"default": 3.1415926535897931
},
Ralf Handl (SAP): Complete syntax:
"Edm.Double": {
"anyOf": [
{
"type": "number",
"format": "double"
},
{
"enum": [
"-INF",
"INF",
"NaN"
]
}
]
},
Ralf Handl (SAP): "Edm.Binary": {
"type": "string",
"format": "base64url",
"pattern": "^([A-Za-z0-9_-]{4})*([A-Za-z0-9_-]{3}[A-Za-z0-9_-]|[A-Za-z0-9_-]{2}[AEIMQUYcgkosw048]=?|[A-Za-z0-9_-][AQgw](==)?)?$"
},
Ralf Handl (SAP): Edm.Byte:
"Model1.SpecialByte": {
"type": "integer",
"format": "uint8"
},
Mike Pizzo: I move we close ODATA-842 as applied
Hubert Heijkers: I second
Ralf Handl (SAP): ODATA-842 is closed as applied
Ralf Handl (SAP): iii.ODATA-843 Nullable as anyOf or as OData-specific keyword
Hubert Heijkers: I move we close ODATA-843 as applied.
Ralf Handl (SAP): "Supplier":{
"anyOf":[{
"$ref":"#/definitions/ODataDemo.Supplier"
}, {
"type":"null"
}
],
Mike Pizzo: I second
Ralf Handl (SAP): ODATA-843 is CLOSED as applied
Ralf Handl (SAP): iv.ODATA-844 Provide JSON versions of the Core, Capabilities, Measures, and Aggregation vocabularies
Ralf Handl (SAP): {
"$schema": "http://docs.oasis-open.org/odata/odata-json-csdl/v4.0/edm.json#",
"odata-version": "4.0",
"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"
},
"Measures": {
"$ref": "#/schemas/Org.OData.Measures.V1"
},
"Org.OData.Measures.V1": {
"@Core.Description": "Terms describing monetary amounts and measured quantities",
"terms": {
"ISOCurrency": {
"type": "Edm.String",
"appliesTo": "Property",
"@Core.Description": "The currency for this monetary amount as an ISO 4217 currency code"
},
"Scale": {
"type": "Edm.Byte",
"appliesTo": "Property",
"@Core.Description": "The number of significant decimal places in the scale part (less than or equal to the number declared in the Scale facet)",
"@Core.RequiresType": "Edm.Decimal"
},
"Unit": {
"type": "Edm.String",
"appliesTo": "Property",
"@Core.Description": "The unit of measure for this measured quantity, e.g. cm for centimeters or % for percentages"
}
}
}
}
}
Ralf Handl (SAP): ODATA-844 is kept in APPLIED state as a reminder to refresh the vocabularies with future changes of the transformation
Ralf Handl (SAP): v.ODATA-845 Translate edmx:Reference/edmx:Include into a schema reference
Ralf Handl (SAP): XML:
<edmx:Reference Uri="http://docs.oasis-open.org/odata/odata/v4.0/os/vocabularies/Org.OData.Core.V1.xml">
<edmx:Include Alias="Core" Namespace="Org.OData.Core.V1" />
</edmx:Reference>
JSON:
"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"
},
Mike Pizzo: I move we close ODATA-845 as applied.
Hubert Heijkers: I second
Ralf Handl (SAP): ODATA-845 is CLOSED as applied
Ralf Handl (SAP): b.Issues for JSON Format for CSDL in New or Open state
Ralf Handl (SAP): i.ODATA-841 Representation of Precision and Scale
Ralf Handl (SAP): For a String{
"type":"string",
"pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,9})?$",
"precision":9
}
Ralf Handl (SAP): For example a property of type Edm.TimeOfDay with precision 9 would be represented as
{
"type":"string",
"pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,9})?$",
"precision":9
}
Mark Biamonte (Progress): I need to drop off the call for today. Will join again next week if we have a call next week
Ralf Handl (SAP): Full example
{
"type":"string",
"pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,9})?$",
"precision":9
}
Ralf Handl (SAP): Now really the full example
{
"type":"string",
"format":"time",
"pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,9})?$",
"precision":9
}
Mike Pizzo: I move we resolve ODATA-841 as proposed.
Hubert Heijkers: I second
Ralf Handl (SAP): ODATA-841 is resolved as proposed
Ralf Handl (SAP): ii.ODATA-855 Should we define patterns for some of the primitive types
Ralf Handl (SAP): -Binary
"pattern": "^([A-Za-z0-9_-]{4})*([A-Za-z0-9_-]{3}[A-Za-z0-9_-]|[A-Za-z0-9_-]{2}[AEIMQUYcgkosw048]=?|[A-Za-z0-9_-][AQgw](==)?)?$"
-Guid
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"
-Date
"pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])$"
-TimeOfDay including Precision
"pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]$" - for Precision=0
"pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?$" for Precision=12
-Duration including Precision
"pattern": "^-?P([0-9]+D)?(T([0-9]+H)?([0-9]+M)?([0-9]+S)?)?$" - for Precision=0
"pattern": "^-?P([0-9]+D)?(T([0-9]+H)?([0-9]+M)?([0-9]+([.][0-9]{1,12})?S)?)?$" - for Precision=12
Mike Pizzo: JSON Schema wiki page for format definitions: https://github.com/json-schema/json-schema/wiki/%22format%22-suggestions
Ralf Handl (SAP): ODATA-855 is OPEN
Mike Pizzo: I move we resolve ODATA-855 as "Won't Fix", in order to keep the schemas smaller/simpler, and given that we can add these patterns later if there is demand.
Hubert Heijkers: I second
Ralf Handl (SAP): ODATA-855 is resolved as WON'T FIX
Ralf Handl (SAP): iii.ODATA-856 Add annotations for Min/Max/Pattern
Ralf Handl (SAP): <edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx" Version="4.0">
<edmx:Reference Uri="http://docs.oasis-open.org/odata/odata/v4.0/os/vocabularies/Org.OData.Core.V1.xml">
<edmx:Include Alias="Core" Namespace="Org.OData.Core.V1" />
</edmx:Reference>
<edmx:DataServices>
<Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Org.OData.Validation.V1" Alias="Validation">
<Annotation Term="Core.Description">
<String>Terms describing validation rules</String>
</Annotation>
<Term Name="Pattern" Type="Edm.String">
<Annotation Term="OData.Description"
String="The pattern that a string property or parameter must match. This SHOULD be a valid regular _expression_, according to the ECMA 262 regular _expression_ dialect." />
</Term>
<Term Name="Minimum" Type="Validation.Limit">
<Annotation Term="OData.Description" String="Minimum value that a property or parameter can have." />
</Term>
<Term Name="Maximum" Type="Validation.Limit">
<Annotation Term="OData.Description" String="Maximum value that a property or parameter can have." />
</Term>
<ComplexType Name="Limit">
<Property Name="Value" Type="Edm.PrimitiveType" Nullable="false" /> <!-- or Edm.Number -->
<Property Name="Exclusive" Type="Edm.Boolean" Nullable="false" DefaultValue="false" />
</ComplexType>
</Schema>
</edmx:DataServices>
</edmx:Edmx>
Ralf Handl (SAP): Example for nested annotation:
<Annotation Term="Validation.Minimum Decimal="3.14">
<Annotation Term="Validation.ExcludeLimit" />
</Annotation>
Ralf Handl (SAP): JSON Schema:
"minimum":"3.14",
"excludeMinimum":true
Ralf Handl (SAP): ODATA-856 is OPEN
Mike Pizzo: I move we resolve ODATA-856 by adding the pattern term as proposed, with minimum and maximum terms of type Edm.Decimal and an annotation "Validation.Exclusive" that can be applied to the minimum and maximum terms.
Martin Zurmuehl (SAP): second
Martin Zurmuehl (SAP): I second
Ralf Handl (SAP): ODATA-856 is resolved with the amended proposal
Ralf Handl (SAP): iv.ODATA-858 Define meaning of MaxLength for String, Binary, and Stream
Ralf Handl (SAP): ODATA-858 is OPEN
Ralf Handl (SAP): Matt: byte length for Binary and Stream
Ralf Handl (SAP): Hubert: agrees
Ralf Handl (SAP): XML MaxLength="333"
Ralf Handl (SAP): JSON Schema maxLength: 444
Ralf Handl (SAP): byteLength: 333
Ralf Handl (SAP): Mike: byte length in XML CSDL for Stream and Binary, Unicode character length for String
Ralf Handl (SAP): octetLength: 444
Ralf Handl (SAP): maxLength: 8 --> octetLength: 4 / 5 / 6
Mike Pizzo: Proposal: In XML, use character length for string and octet length for binary/stream
In JSON Schema, the maxlength of these string properties must be the maximum number of characters in the string representation, so we will add byteLength keywords for binary and stream values as the byte length in octets.
Mike Pizzo: I move we resolve ODATA-858 according to the above proposal.
Matt Borges (SAP): I second
Ralf Handl (SAP): ODATA-858 is resolved as proposed
Ralf Handl (SAP): 6.Next meeting [9:50am PT]
a.Thursday October 08, 2015 during 8-10am PT?
Ralf Handl (SAP): 7.AOB and wrap up [9:55am PT]
Ralf Handl (SAP): Hubert: when will we have the next face-to-face meeting?
Ralf Handl (SAP): Mike: put that on the agenda for next week
Ralf Handl (SAP): Meeting is adjourned
From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org]
On Behalf Of Handl, Ralf
Sent: Dienstag, 29. September 2015 16:26
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2015-10-01
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting
scheduled on
Thursday October 01, 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=39118
2.
Approve agenda [8:05am PT]
3.
Approve minutes from previous meeting(s) [8:10am PT]
a.
Minutes from September 24, 2015 TC meeting:
https://www.oasis-open.org/committees/download.php/56600/odata-meeting-106_on-20150924-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.
Process issues [Issues list:
https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA] [8:20am PT]
a.
Issues
for JSON Format for CSDL in Applied state
i. ODATA-805
Add term to Capabilities vocabulary for supported metadata formats
ii. ODATA-842
Represent primitive types as JSON Schema formats
iii. ODATA-843
Nullable as anyOf or as OData-specific keyword
iv. ODATA-844
Provide JSON versions of the Core, Capabilities, Measures, and Aggregation vocabularies
v. ODATA-845
Translate edmx:Reference/edmx:Include into a schema reference
b.
Issues
for JSON Format for CSDL in New or Open 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.
Issues
for Data Aggregation in New or Open state
i. ODATA-833
Example 40 applies term RecursiveHierarchy term incorrectly
ii. ODATA-851
groupby(): ABNF still allows more than two parameters
iii. ODATA-857
Example 5: use two aggregate expressions
iv. ODATA-860
Move definition of Custom Aggregation Method to separate subsection.
6.
Next meeting [9:50am PT]
a.
Thursday October 08, 2015 during 8-10am PT?
7.
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