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-326) include-annotations should allow inclusion (or exclusion) of specific terms


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

Michael Pizzo updated ODATA-326:
--------------------------------

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

> include-annotations should allow inclusion (or exclusion) of specific terms
> ---------------------------------------------------------------------------
>
>                 Key: ODATA-326
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-326
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Applied]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: V4.0_WD01
>
>
> The odata.include-annotations preference allows the client to specify which annotations are included in the response payload.
> We include annotations by specifying the namespace of the annotation, but there may be cases where only one (or a few number) of the annotations within a (potentially large) namespace are desired.
> We should support specifying individual annotations using namespace.termname.
> Note that we currently say that, if you just specify a namespace, you include only the terms located directly in that namespace, while if you specify namespace.* you include all annotations within that namespace and nested namespaces. We may introduce an ambiguity if we allow namespace.termname where the service needs to know the difference between a namespace name and a term name in order to differentiate. If this is an issue we can:
> 1) just use namespace.* for everything within a namespace (recursively) and not differentiate between direct and nested, or
> 2) disambiguate by the case where I want everything directly contained by a namespace (i.e., myroot/mynamespace/.)
> 3) disambiguate the case where I want a term (i.e., namespace@termname)

-- 
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]