Glen Daniels wrote:
Hm. Well, they MUST have a URI so that the remote stuff will work (i.e.
referencing, editing or deleting, as per the protocol). If they're
going to have a remote URI, that has to evince itself somehow in the API
(whether surfacing all the way to the user or hiding somewhere). It
seems to me returning the URI from addComment() is the right way to do
that, so it can be used as a valid path to delete() at least. I'm
certainly not saying Comments need to be versioned and taggable and all
that, but they are "things with a URI", i.e. resources. I like that the
same pattern would work with local or remote registries.
I wasn't disagreeing with your proposed API- returning the location of
the comment looks good. I was only arguing against the actual URI .. if I
add a comment against resource /r1, I'd like the URI of that comment to be
/r1;comments?n=113 (where 113 is the comment number/id).
How would you suggest deleting a comment via the Java API?
Per above, no disagreement with the Java API.
/tag/foo and /tags is different - those are really queries.
I'm not sure what you mean here?
What I meant is that /tag/foo is really a query meaning give me a list of
all resources that are tagged foo. And /tags is a "special URI" which
returns a list of tags. (I forget whether we even support that.)
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
email: [EMAIL PROTECTED]; cell: +1 650 265 8311 | +94 77 787 6880
"Oxygenating the Web Service Platform."
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
