[OASIS Issue Tracker] (ODATA-639) MetadataService.edmx: Schema annotations have to be represented inline

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Michael Pizzo updated ODATA-639:
--------------------------------

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

This is actually already covered in [CSDL]. In the target attribute of the Annotations element we list the possible targets (the list does not include the schema element) and say that "Most of the not uniquely identifiable EDM elements can still be annotated using a nested edm:Annotation element."

To address any possible specific confusion with the Schema element, I changed this to "The Schema element and most of the not uniquely identifiable EDM elements can still be annotated using a nested edm:Annotation element."

> MetadataService.edmx: Schema annotations have to be represented inline
> ----------------------------------------------------------------------
>
>                 Key: ODATA-639
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-639
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL
>    Affects Versions: V4.0_OS
>         Environment: [Applied]
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> Only model elements identifyable with a target path can be represented within the Annotations entity set. Schema elements don't fall into this category because A.B.C could be a schema name as well as the name of element C in schema A.B



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