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-618) Allow using term names in positions that allow type names


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

Ralf Handl commented on ODATA-618:
----------------------------------

This becomes tricky for terms that declare a base term: for annotations this means that there must be an annotation with the base term whenever there is an annotation with the "derived/extended" term. 
What would this mean if a term with a base term is used as the type of a property:
- must there be a property on the same level that is typed with the base term? 
- or is the base term ignored?
- or is it forbidden that terms with a base term are used as types? 
Model evolution: is adding a BaseTerm to an existing term a compatible or a breaking change?

> Allow using term names in positions that allow type names
> ---------------------------------------------------------
>
>                 Key: ODATA-618
>                 URL: https://issues.oasis-open.org/browse/ODATA-618
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_OS
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Extension, Usability
>             Fix For: V4.01_WD01
>
>
> Terms have a declared type plus additional semantics, so using term names in place of type names seems natural.



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