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-1005) Make sure we have capabilities for all new 4.01 functionality


     [ https://issues.oasis-open.org/browse/ODATA-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-1005:
------------------------------

    Description: 
Do this in conjunction with conformance, so clients have a way to determine which optional parts of 4.01 are supported by a service.

things to consider:
- PATCH/DELETE with filter
- POST/PATCH/DELETE with type cast segment
- POST/PATCH/PUT with system query options to shape response
- PATCH using delta response format
- nested collections in delta payload (as delta or replacement)
- Deep insert/update operations
- eq/ne null comparisons for nav properties w/max cardinality of 1 (should this be must?)
- implicit aliasing of parameters
- in operator, divby,
- negative indexes for substring
- key-as-segment (Core vocab, applies to EntityContainer, similar to ConventionalIDs and DereferenceableIDs)
- use of count of filtered/searchced collection in a common expression
- equal/non-equal structural comparison
- PUT/DELETE to $ref of a collection-valued nav prop
- POST to collections of complex/primitive types
- $search for all collections
- headers and query options without prefix, case-insensitive query options
- $compute
- indexing into ordered collections and positional insert with $index
- batch referencing features
- JSON batch format
- use of instance annotations in query options
- $expand for stream properties and media resources

  was:
Do this in conjunction with conformance, so clients have a way to determine which optional parts of 4.01 are supported by a service.

things to consider:
- PATCH/DELETE with filter
- POST/PATCH/DELETE with type cast segment
- PATCH using delta response format
- nested collections in delta payload (as delta or replacement)
- Deep insert/update operations
- eq/ne null comparisons for nav properties w/max cardinality of 1 (should this be must?)
- implicit aliasing of parameters
- in operator, divby,
- negative indexes for substring
- key-as-segment (Core vocab, applies to EntityContainer, similar to ConventionalIDs and DereferenceableIDs)
- use of count of filtered/searchced collection in a common expression
- equal/non-equal structural comparison
- PUT/DELETE to $ref of a collection-valued nav prop
- POST to collections of complex/primitive types
- $search for all collections
- headers and query options without prefix, case-insensitive query options
- $compute
- indexing into ordered collections and positional insert with $index
- batch referencing features
- JSON batch format
- use of instance annotations in query options
- $expand for stream properties and media resources


> Make sure we have capabilities for all new 4.01 functionality
> -------------------------------------------------------------
>
>                 Key: ODATA-1005
>                 URL: https://issues.oasis-open.org/browse/ODATA-1005
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.01_CSD01
>         Environment: Proposed
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: V4.0_CSD02
>
>
> Do this in conjunction with conformance, so clients have a way to determine which optional parts of 4.01 are supported by a service.
> things to consider:
> - PATCH/DELETE with filter
> - POST/PATCH/DELETE with type cast segment
> - POST/PATCH/PUT with system query options to shape response
> - PATCH using delta response format
> - nested collections in delta payload (as delta or replacement)
> - Deep insert/update operations
> - eq/ne null comparisons for nav properties w/max cardinality of 1 (should this be must?)
> - implicit aliasing of parameters
> - in operator, divby,
> - negative indexes for substring
> - key-as-segment (Core vocab, applies to EntityContainer, similar to ConventionalIDs and DereferenceableIDs)
> - use of count of filtered/searchced collection in a common expression
> - equal/non-equal structural comparison
> - PUT/DELETE to $ref of a collection-valued nav prop
> - POST to collections of complex/primitive types
> - $search for all collections
> - headers and query options without prefix, case-insensitive query options
> - $compute
> - indexing into ordered collections and positional insert with $index
> - batch referencing features
> - JSON batch format
> - use of instance annotations in query options
> - $expand for stream properties and media resources



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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