[mdx] MDQ questions

[Ian Young]

On 31 Oct 2013, at 17:16, David Waite <dwaite at pingidentity.com> wrote:

> Clarification on section 3.2.1:

Welcome!

> This section says that if multiple IDs are supplied the result is the intersection of the IDs. I take this to mean that if I have a tag “foo” as a collection, and entity IDs “bar” and “baz”, of which only “baz” is associated with that tag, then:
> 
> /entities/foo #returns baz
> /entities/bar #returns bar
> /entities/foo+baz #returns baz
> /entities/foo+bar #returns 404 to indicate no results - bar is not tagged with foo
> /entities/bar+baz #returns 404 to indicate no results, bar and baz are different entities and thus have no intersection

That's all correct, yes.

> There is no query for the tags above that would allow me to perform a union operation, where I get both bar and baz back. Correct?

Correct.

> Also, is there any guidance around ID ordering to promote caching?

There's nothing in there just now.

> /entities/foo+bar and /entities/bar+foo are equivalent commands but not equivalent URLs, and thus would not share cache. Recommending or requiring ordering would promote cache hits.

I can see what you're saying. I guess my first question would be whether you have a significant use case for the union operator that we should talk about; I think we've regarded it as fairly peripheral up to this point, which may be why it hasn't had much attention.

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5943 bytes
Desc: not available
URL: <http://lists.iay.org.uk/pipermail/mdx-iay.org.uk/attachments/20131031/fc35ba98/attachment.bin>