RE: "so-called" keyword and layer 3

[Yves Arrouye <yves@realnames.com>]

> 4.	As suggested in John's draft, ALL layer 2 service will have to
> return tuples that contain all the standardized facets. However, specific
> layer two services that don't care about one or many standardized
facet(s),
> would still be allowed to return result tuples with blank or "missing"
> values for the facets that they want to disregard. For example, although
> RealNames would let registrants specify their category value at
> registration
> time (to be used in the context of discovery as a layer 3 service), as a
> layer 2 service, it would "blank" the category facet value of its results
> in
> order to enable "direct navigation" (as described by Mr Ko)

Or you could always return the category facet value, but not make it part of
the set of facets that are required for direct navigation. If we note
non-key facets as name*, we could have { common-name, geography, language,
category* }. The advantage of letting the application not use a facet,
rather than blank it out, is that it still enables someone to display and
peruse the category information from a result set, yet does not force them
to use it for querying.

YA