Micah, this is even better than I imagined, your design way exceeds my requirements, it will be very useful--and thanks for the explanation about the schema design.
On Aug 12, 2011, at 2:48 PM, Micah Dubinko wrote: > Shannon, > > The @apply attribute anywhere in Search API indicates that you can point it > at any desired function (with corresponding @ns and @at) to produce whatever > query you want for the empty case. The value of @apply can be any function > local-name, but a few built-in ones are special. > > W3C XML Schema does not handle open enumerations gracefully, so the schema > needs to be more open. > > -m > > On Aug 12, 2011, at 11:42 AM, Shannon wrote: > >> Hello, >> >> Do you see any benefit to allowing a query string in term/empty/@apply >> instead of "all-results" or nothing--instead of all or nothing, the ability >> to default to a particular query? I would prefer to have more control over >> what results are displayed. >> >> On a related note, I notice that the search.xsd schema doesn't specify an >> enumeration for this attribute, and often the API reference provides >> examples but not a comprehensive list of values--have you considered >> expanding the design to include these constraints to assist developers? >> >> Best, >> >> Shannon ([email protected]) >> http://www.facebook.com/uvapress >> http://www.twitter.com/uvapress >> >> _______________________________________________ >> General mailing list >> [email protected] >> http://developer.marklogic.com/mailman/listinfo/general > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
