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: [OASIS Issue Tracker] (ODATA-1002) Add build in functions operating on collections of primitive (and complex?) types

    [ https://issues.oasis-open.org/browse/ODATA-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64297#comment-64297 ] 

George Ericson commented on ODATA-1002:

Suggest looking at UML, specifically see discussions on collections (11.6) in OCL: http://www.omg.org/spec/OCL/ISO/19507/PDF/ 
There the difference between
- Collection: Abstract supertype of Set, OrderedSet, Bag, and Sequence
- Set: Math set, no duplicates, not ordered
- OrderedSet: Set that is ordered
- Bag: Duplicates allowed, not ordered.
- Sequence: Ordered collection, duplicates allowed
OCL (11.7) defines rules for comparing each.

> Add build in functions operating on collections of primitive (and complex?) types
> ---------------------------------------------------------------------------------
>                 Key: ODATA-1002
>                 URL: https://issues.oasis-open.org/browse/ODATA-1002
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData ABNF Construction Rules, OData Protocol, OData URL Conventions
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Hubert Heijkers
>              Labels: Proposed
>             Fix For: V4.01_CSD02
> I'm getting more asks for people wanting to filter against properties representing a collection of primitive type, most notably Collection(Edm.String).
> Things like equal to, not equal to and containing a value or subset are the operations that people are looking to do the most. The size of the array they can get around by using /$count.
> Short of coming up with something ourselves I was wondering if this is a more generic ask and if we could maybe guide implementations as to how to support this kind of functionality in a more generic way.  

This message was sent by Atlassian JIRA

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