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

      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

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: