[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-172) EntitySet may be qualified with namespace or alias and EntityContainer
[ http://tools.oasis-open.org/issues/browse/ODATA-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31852#action_31852 ] Ralf Handl commented on ODATA-172: ---------------------------------- This rule extension would only make sense for entity sets "imported" via a Using element. That the current rules don't allow addressing entity sets imported via Using is an indicator that Using isn't that useful, and I rather think that we should remove Using from the CSDL, or at least restrict it to "importing" types, actions, and functions only. > EntitySet may be qualified with namespace or alias and EntityContainer > ---------------------------------------------------------------------- > > Key: ODATA-172 > URL: http://tools.oasis-open.org/issues/browse/ODATA-172 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData ABNF Construction Rules v1.0, OData URL Conventions v1.0 > Affects Versions: WD01 > Environment: [Proposed] > Reporter: Ralf Handl > Priority: Minor > Fix For: WD01 > > > The current rule for resourcePath allows qualifying an entity set with the name of its entity container, which is necessary if the entity container is not the default container. > Functions and actions can additionally be qualified with the namespace as a prefix to the entity container. This option is missing for entity sets. -- 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]