Should we allow multiple path segments or @key properties in a model definition?

[markcowl]

This came up as part of #110

Currently, multiple path segments designated on a model is disallowed. Is there a need to allow multiple path segments for a key:

• For composite keys (i.e. when there are multiple keys, but no parent resource)
  • possible example: Compute VM Gallery
  • How do we express ordering in the path segments without a route string (for autoroute)?
• If there are alternate paths to accessing the resource
  • this is a common pattern for ODATA APIs

Additionally, should we separate '@key' from path segments, and should we allow multiple `@key' properties in a model

• This comes up in arrays of complex types. The 'id' of a particular instance may be made up of multiple properties (e.g. firstName, lastName)
  • should we allow this
  • Is there any important ordering in keys (last name, first name, for example) that we want to preserve?

[markcowl]

potential solutions

• empty parent resource

[markcowl]

Thgis sprint:

• • links to specs with this issue

[markcowl]

Need to collect data on how many specs would benefit from this

[timotheeguerin]

Examples:

• Device update today -> Potential idea
• General scenarios

[markcowl]

Proposal here: https://gist.github.com/markcowl/d316ff4566aa04c5332c33402fbd218c