User Contexts: distinguishing needs from preferences - prioritization

This is based on my action item to review ISO 24751 for potential requirements
of interest in the User Contexts work.

ISO 24751 enables the priority of each need/preference to be asserted. More
specifically, it distinguishes needs (which must be satisfied for a resource
to be accessible to the user in a given situation) from preferences. Optional
and prohibited adaptations are also distinguished, but I think the most useful
distinction is that between "required" and "preferred" items.

Our User Contexts API, as currently drafted, treats all needs and preferences
equally, whereas application authors might want "hard" requirements (i.e.,
needs) to be distinguished from preferences.

I don't think this issue can be easily resolved in isolation from use cases
and the wider questions currently before the group regarding what should be
included in the User Contexts specification. It is, however, a design decision
that should be made deliberately and with an understanding of its
implications.

Received on Wednesday, 16 October 2013 01:40:13 UTC