[OASIS Issue Tracker] Updated: (ODATA-181) Referencing/reusing a model element from a different schema does not require to "include" this schema via a Using element

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

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

Michael Pizzo updated ODATA-181:
--------------------------------

       Proposal: Resolve by defining semantics of Reference and Using as defined in the model references document discussed at the Zurich Face to Face (reference to be inserted).  (was: Define "in scope" to mean: defined in the same metadata document (multiple Schema elements can be contained in the same Edmx document) or defined in a metadata document referenced with an edmx:Reference element.

Section 7.3.2: shorten the first sentence to:

A navigation property MUST specify a value for the Type attribute. The value of the type attribute MUST resolve to an entity type or a collection of an entity type in scope.

Section 18.4: rephrase second paragraph to: 

The type must be in scope, i.e. if a SimpleIdentifier is used, the type MUST be defined in the same schema, and if a QualifiedName is used, the type MUST be defined in the schema identified by the namespace or alias portion of the qualified name, and the identified schema MUST be part of the same metadata document or MUST have been referenced with edmx:Reference.)
    Environment: [Proposed]

> Referencing/reusing a model element from a different schema does not require to "include" this schema via a Using element
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-181
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-181
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: WD01
>
>
> Sections 7.3.2 and 18.4 require that a type from another schema can only be used when the other schema has been "merged" into the current schema.
> This is overly restrictive. Reusing a single model element from another schema should not force to include all model elements from that schema.

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