Dynamic metadata resolution and transformed identifiers

[Brent Putman]

On 10/31/14 6:29 PM, Cantor, Scott wrote:
> The slightly problematic thing is that you're coupling the transform used
> on the server-side for implementation reasons with the one used in the
> client.

Yes, acknowledged.  It is implicitly assuming that the metadata source
would say "we're going to publish it this way (hash + hex, etc)", and
the client would then conform to whatever that was.  Not any different
than any other proprietary non-spec protocol, but no coding involved.


>
> The {SHA1} thing is a special case since it had to be made interoperable
> for artifact binding use, so it's required to implement.
Yes.

> In practice, it takes not much more than a simple bash script to take a
> URL-encoded entityID parameter in the URL and decode-then-hash it into the
> filename to return. I've done it, in fact.

True.  Either works.  I'm all about options...