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] Issue Comment Edited: (ODATA-302) Clarify scope uniqueness for EntityContainer name


    [ http://tools.oasis-open.org/issues/browse/ODATA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32787#action_32787 ] 

Ralf Handl edited comment on ODATA-302 at 3/20/13 5:41 AM:
-----------------------------------------------------------

Good point! This actually applies to all schema children. They are by definition local to the schema and always addressed with qualified names. 

This is especially the case for the entity container and already reflected in the URL qualification rules for entity containers, so I changed the proposal to reflect the current state.

      was (Author: ralfhandl):
    Good point!
  
> Clarify scope uniqueness for EntityContainer name
> -------------------------------------------------
>
>                 Key: ODATA-302
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-302
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Evan Ireland
>            Assignee: Ralf Handl
>            Priority: Minor
>
> CSDL spec (2013-03-12) says:
> 12.1.1 The Name Attribute
> The entity container MUST provide a unique SimpleIdentifier value for the Name attribute.
> ---
> It isn't clear whether this uniquess is within the scope of the Schema, or the entire metadata document. For example, consider:
> <edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx";
>            Version="4.0">
>   <edmx:DataServices DataServiceVersion="4.0" >
>     <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm"; Namespace="ODataDemo1">
>       <EntityContainer Name="DemoService" IsDefaultEntityContainer="false">
>       </EntityContainer>
>     </Schema>
>     <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm"; Namespace="ODataDemo2">
>       <EntityContainer Name="DemoService" IsDefaultEntityContainer="false">
>       </EntityContainer>
>     </Schema>
>   </edmx:DataServices>
> </edmx:Edmx>
> Note how there are two DemoService containers, each is unique within the scope of its parent Schema. However DemoService is not unique within the metadata document.

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