[OASIS Issue Tracker] Created: (ODATA-430) Add term Core.ResourcePath to describe unconventional resource paths in CSDL

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

Add term Core.ResourcePath to describe unconventional resource paths in CSDL
----------------------------------------------------------------------------

                 Key: ODATA-430
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-430
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData CSDL, OData URL Conventions , Vocabularies
    Affects Versions: V4.0_CSD01
         Environment: [Proposed]
            Reporter: Ralf Handl
            Priority: Minor
             Fix For: V4.0_CSD02


Currently the resource path for top-level resources (direct children of entity containers) is only represented in the service document, and even there only for most, but not all top-level resources.

Adding resource paths that do not follow the URL conventions to the metadata document has two benefits:
- the resource path can be stated for all top-level resources
- the metadata document  contains a superset of the information contained in the service 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