[OASIS Issue Tracker] (ODATA-923) $expand (or $include) for $metadata to include referenced schemas

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

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

Michael Pizzo edited comment on ODATA-923 at 7/21/16 3:04 PM:
--------------------------------------------------------------

Questions: 

1) Do we want/need a way to support all namespaces referenced by elements within a particular namespace?  i.e., the closure of all namespaces needed to understand the types within a particular namespace, without calling in all the other namespaces that may be part of the referenced documents?  i.e., Customers/*?

2) Do we want a way to exclude certain namespaces? (i.e., prefixing with a minus sign (-) )

3) Should the odata namespaces (especially core) be included by "*" or should we require explicitly including them (since they will be in most schemas but probably don't need to be fetched each time)?

4) If we include the schemas inline we'll want to use the aliases defined in the referencing document for the "alias" attribute of the inlined <Schema> element, but that can result in ambiguity (i.e., if the referenced document uses the same alias name for a different schema).

Scenario-wise, what the client really wants is the ability to get the metadata necessary to understand a particular response.  So, given a context, it wants to (minimally) get back the recursive set of types referenced by that context (and probably wouldn't really care about any additional types defined in the namespaces used by the referenced types).

Also note, service can't just include referenced files; it has to make sure there are no conflicts in the defined aliases.


was (Author: mikep):
Questions: 

1) Do we want/need a way to support all namespaces referenced by elements within a particular namespace?  i.e., the closure of all namespaces needed to understand the types within a particular namespace, without calling in all the other namespaces that may be part of the referenced documents?  i.e., Customers/*?

2) Do we want a way to exclude certain namespaces? (i.e., prefixing with a minus sign (-) )

3) Should the odata namespaces (especially core) be included by "*" or should we require explicitly including them (since they will be in most schemas but probably don't need to be fetched each time)?

4) If we include the schemas inline we'll want to use the aliases defined in the referencing document for the "alias" attribute of the inlined <Schema> element, but that can result in ambiguity (i.e., if the referenced document uses the same alias name for a different schema).. 

> $expand (or $include) for $metadata to include referenced schemas
> -----------------------------------------------------------------
>
>                 Key: ODATA-923
>                 URL: https://issues.oasis-open.org/browse/ODATA-923
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> After being able to partition large services into smaller ones using cross-service navigation we might want to support requesting multiple of these small files in one request, similar to expanding an entity and including related entities.



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