[OASIS Issue Tracker] Created: (ODATA-355) Define how property paths are represented in key part of URL

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

Define how property paths are represented in key part of URL
------------------------------------------------------------

                 Key: ODATA-355
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-355
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Sub-task
          Components: OData URL Conventions 
    Affects Versions: V4.0_WD01
         Environment: [Proposed]
            Reporter: Ralf Handl
            Priority: Blocker
             Fix For: V4.0_WD01


The key of an entity is part of the URl path, so we can't use forward slashes for complex key parts:

Problem(Header/ID=42) cannot be used as this defines two path segments Problem(Header and ID=42

Alternatives:
- Problem(Header%2fID=42) 
- Problem(Header-ID=42) 
- Reject ODATA-60 and disallow parts of complex properties as key values

-- 
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