-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: V4.0_WD01
-
Fix Version/s: V4.0_WD01
-
Component/s: ABNF, URL Conventions
-
Labels:None
-
Environment:
[Proposed]
-
Proposal:
-
Resolution:
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.
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Proposal |
Extend resourcePath rule: resourcePath = [ [namespace "." ] entityContainerName "." ] entitySetName [ collectionNavigation ] / ... |
Extend resourcePath rule: resourcePath = [ [namespace "." ] entityContainerName "." ] entitySetName [ collectionNavigation ] / ... Accepted: https://www.oasis-open.org/committees/download.php/47919/odata-meeting-21_on-20130117-minutes.html#odata-172 |
| Reporter | Ralf Handl [ ralfhandl ] | Ralf Handl [ handl ] |
| Assignee | Ralf Handl [ handl ] |
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.