[tranparent?] content negotiation

[Al Gilman <asgilman@xxxxxxxxxxxxxxxx>]

This may be an issue that you resolved long ago, but I want to
put in a plug for seamless integration of an escape to manual
decision.

In other words, if "transparent content negotiation" means "morph
selection transparent to the user" I would like suggest that the
registry is to support features for [not necessarily transparent]
content negotiation, and that TCN is the subset of content
negotiation where the negotiation process closes on a deal
without ever querying the user.

This is inspired by the "cup of coffee" case discussed earlier.

If the user requests a cup of coffee with whipped cream and no
milk, and the server only knows the characteristic definition
containing no whipped cream, then the fact that all the other
requested characteristics can be satisfied by the legacy type
could be basis for a user query "We don't have whipped cream,
would you like milk in your coffee?"

Al Gilman