[mdx] Joe on 3.1.1

[Tom Scavo]

On Thu, Sep 26, 2013 at 5:08 PM, Ian Young <ian at iay.org.uk> wrote:
>
> On 26 Sep 2013, at 21:18, Tom Scavo <trscavo at gmail.com> wrote:
>
>> I must be missing something. The mapping from entityID to filename
>> happens on the server side. The end client doesn't get to choose the
>> encoding scheme. That is an opaque implementation choice.
>
> With the current spec, the client gets to choose between these three equivalent representations of an entity ID:
>
> A: http://blahblah/the/real/one
>
> B: {md5}98347947924792734982374
>
> C: {sha1}1298381938109238102938102938102938123

What is the use case for B and C?

When you write "MTI," I assume you mean "Mandatory to Implement." Are
B and C MTI? If so, why?

Tom