But the spec has separate compliance classes for ordering and referencing because they are orthogonal. We could query the group. Web folders alphabetize the contents of collections, so they are imposing their own ordering on the client side. From the standpoint of the protocol, server-maintained is unordered. We have made it possible.
Current spec says a request fails if it has a Position header on an unordered collection.
We don't want to get into issues about registering server- maintained orderings. It s one thing for the server to declare how it will order, another for client to be able to request a particular server-maintained ordering. Jim D doesn t see use case even for that. Max is implementing a server. Ask him for use case - advertise an ordering that it will use vs. let client choose.