InCommon metadata support

[Tom Scavo <>]

Hi Jaime,

Thanks for joining us :-)

On Wed, Mar 18, 2015 at 9:25 AM, Jaime Perez Crespo
<>
 wrote:
>
> * To be able to query the MDX server for a list of all the entities served. 
> When I say “list of entities”, I mean a list of identifiers used by the MDX 
> implementation that can be used to request the metadata of a particular 
> entity (i.e. the entityID or its SHA-1).

An issue was recently filed against mdq-server that would satisfy your
needs: https://github.com/iay/mdq-server/issues/27

The use case we had in mind was to return enough information to be
able to construct a list of links, basically entityID, DisplayName,
and role.

> I understand the first one could be easily disregarded by using the MDX as 
> a standard metadata feed, that is, fetching the whole metadata set it 
> serves, processing, caching, and then proceeding onwards by leveraging the 
> second one.

That was my first thought as well. Before you brought it up, I've
always thought an implementation would fetch the entire aggregate
while booting up and then use the MDQ protocol to keep up to date.

> * To be able to query the MDX server for a list of all the entities 
> *modified since* a specific date. This would allow us to query the server 
> later only for those entities that have been modified since the last 
> request.

That's an interesting option, one we haven't discussed.

In both cases, I guess a more basic question is: Are these
implementation issues or protocol issues? The work we're doing on the
first one, for instance, is still very much in the implementation
phase (i.e., no one has yet proposed a protocol change).

Btw, fetching the entire aggregate *is* specified in the protocol spec.

Tom