Right.. we have in the big picture more than just date ranges and trying to
provide a mechanism for clients to "understand" them is complicated--- and few
will ever bother--- if not impossible.... but also delivers little. For general
facet search we need shared sematics for things anyway to make sense.. If a user
at a clothing shop selects "hose"--- a word that means pants in German--- they
want the items that are pants and not fire hoses--- the "Fire Hose" gag from
Bill Dana in his guise as Jose Jimenez comes to mind. The anything goes model does not mean that one can't return (or handle) ISO
defined date ranges if one wishes.. All we have done is say that what  the
server provides in a scan or for a facet it must understand and do what it
intended when it supplied them. This is, I think, already a step above the
supply a term "exactly as its in the index" without a explicit contract to do
(or be able to do) something meaningful (from the perspective of the server)
with them. And remember.. Date ranges are not the only business case for this approach..
Sure.. if all you have are full text terns, dates, date ranges, numbers and
number ranges one might be able to devise something but once we start getting
into the realm of more obscure data types and ranges things get weird.. Do we
really want to start to talk about masking etc.. ISBN ranges anyone? Closed
paths..

On Mon, 25 Oct 2010 16:13:14 +0200, Edo Plantinga wrote

----------------------------------------------------------------------- Van: LeVan,Ralph [mailto:lev...@oclc.org]