3.2.7 - User Relative XRIs

["Loren West" <loren.west@epokinc.com>]

Small issue:

User Relative XRIs are described in the text to be
useful for and used by users (human beings) as
"shortcuts" or "speed names".  

But the example is confusing, because the XRI 
isn't relative to "Mary", it's relative to
"@employer".  It's hard for me to think about
the "@employer" user having a "shortcut" XRI
with the value "*Mary/workstation".

It's less confusing (and maybe what was intended)
to think of "Mary" as the user.  The a priori
Identifier Authority for her may be "@employer/Mary",
and User Relative XRI would be "*workstation".

Here's the example from the spec:

   > ...For example, if XRI resolver is pre-configured 
   > with a default community of "@employer/", then the 
   > XRI "xri:*Mary/workstation" would be converted into 
   > "xri:@employer/Mary/workstation".

Which is correct, but not illustrative of Mary as
a user.  It could be more like this:

   > ...For example, if Mary is known as a user with a
   > default Identifier Authority of "@employer/Mary", then  
   > the XRI "xri:*workstation" would be converted into 
   > "xri:@employer/Mary/workstation" for resolution. 

=Loren