[Ietf-not43] Constructing an all-inclusive <domain> response

[Andrew Newton]

Chris Ambler wrote:

> The unfortunate part is that this creates a lot of extra work for this
> particular application (which is a non-trivial use of the standard).

It seems fairly trivial to use entity-class + entity-name (or some 
combination of authority + registry-type + ... depending on your scope) 
as a key for a hash table of the entities.

> Would it be possible to define a schema whereby entities can be replaced by
> the actual elements that they would reference? An "I promise that there are
> no circular references and you need not go back to the service for more
> data" schema, if you will?

In my opinion, this is not a good direction.  Database practices 
generally tells us that normalization is a good thing.  What you are 
suggesting makes the relationships less clear when an entity appears 
multiple times in a response.

-andy