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] Updated: (ODATA-363) specifiying selected properties in metadataurl is broken

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

Ralf Handl updated ODATA-363:

    Environment: [Applied]  (was: [Resolved])

> specifiying selected properties in metadataurl is broken
> --------------------------------------------------------
>                 Key: ODATA-363
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-363
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData URL Conventions 
>    Affects Versions: V4.0_WD01
>         Environment: [Applied]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_WD01
> The current metadataurl pattern for specifying a subset of properties is broken for selects on expanded navigation props.
> We need to know the projected properties in order to know, for example, whether missing navigation properties are omitted because they matched a convention (in which case they can be constructed on the client) or because they weren't selected (in which case they should not be constructed on the client because they may not match convention)..
> Also, we don't want to have to have the client parse select (and nested expands, etc.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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