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] Commented: (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=32806#action_32806 ] 

Evan Ireland commented on ODATA-302:

We may need to therefore clarify CSDL 19.3 (2013-03-19), which currently has two rules:

  Rule (paragraph) 1: "For model elements that are direct children of a schema: the namespace or alias of the schema that defines the model element, followed by a dot and the name of the model element, see rule qualifiedTypeName in [OData-ABNF]."

  Rule (paragraph) 2:"For model elements that are direct children of an entity container: the qualified name of the entity container, followed by a dot and the name of the model element, see rules, qualifiedActionName and qualifiedFunctionName in [OData-ABNF]."

Firstly, it is not clear that both rules (rather than just the second rule) apply to children of an entity container, i.e. that they must be doubly-qualified as "SchemaNamespace/EntityContainer/SomeThing".

Secondly, the second rule refers to the ABNF for qualifiedActionName and qualifiedFunctionName, but the ABNF reads as:

  qualifiedActionName   = namespace "." action   [ "(" parameterTypeNames ")" ]
  qualifiedFunctionName = namespace "." function [ "(" parameterTypeNames ")" ]

We can assume that "namespace" here refers to a Schema namespace, rather than an EnityContainer name. Since Actions/Function (as opposed to ActionImport/Functionimport) are defined directly in a Schema, not nested in an EntityContainer, we should not mention them in the second paragraph which pertains only to entity containers.

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