[Registry-dev] extensible searching API

[Jonathan Marsh]

Sorry to be late catching up on this.

If all queries return resources (mashups, users, tags, comments), do I have
to go outside the query language to return a calculated value like "average
rating"?  If so, is it still reasonably possible to execute queries like "My
mashups which my friends have rated (on average) 4 or higher?"  i.e. where a
calculated value is part of an intermediate query result?

I don't think we need to expose this level of searchability to end users
right now, but I'm interested in a model that will allow the UI to execute
some pretty sophisticated general purpose queries as well as expose some
query "templates" to the user through a search form.

Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
 
> -----Original Message-----
> From: registry-dev-bounces at wso2.org [mailto:registry-dev-
> bounces at wso2.org] On Behalf Of Sanjiva Weerawarana
> Sent: Monday, September 17, 2007 1:34 AM
> To: Chathura C. Ekanayake
> Cc: registry-dev at wso2.org
> Subject: Re: [Registry-dev] extensible searching API
> 
> Chathura C. Ekanayake wrote:
> >
> > Comments and Tags are not represented by Resource class instances.
> > According to above approach we have to make them Resources. But I
> think
> >  we can keep the Comments and Tags table in the data model and load
> the
> >  data from those tables to Resource instances.
> >
> > We can't use ...resource1/comments URL as resource1 could have a
> child
> >  resource named comments. So I think we have to use
> > ..resource1?comments.
> 
> Whether we implement as actual resources underneath or not, we can
> still
> give a resource view of them (essentially give them URIs). Each comment
> too can be its own resource .. resource1?comments[=1,2,...]
> 
> >> I'm not quite sure what you mean here exactly.  If you mean the tags
> >>  that have been applied to a given resource, that's just
> >> "...resource1/tags" or something like it.  The data representation
> of
> >>  the tags resource itself should be a list of tags (that the
> >> authenticated user has access to), and that can if you wish include
> >> the # of taggings for each tag.  Alternately (or additionally) the
> >> representation for "...registry/tags/checkThisOut", which should be
> a
> >>  list of URLs for resources that have a given tag, can also include
> >> the # of taggings.  Did that cover your case?
> >
> > Yes, that covered my use case :)
> 
> Cool; +1 from me too!
> 
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> email: sanjiva at wso2.com; cell: +94 77 787 6880; fax: +1 509 691 2000
> 
> "Oxygenating the Web Service Platform."
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev