OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [xdi] How to get from =markus/+email to the actual data


So I was going to ask  "I understand then that the $ would be dual-purposed to mean an anonymous user if it's at the root of a message, and the root of the special XRI space if it's in the message?", then I re-read your first sentence and it seems like $ is already dual-purposed: (a) root of reserved space, (b) current context.  So if I do an update to the local $ space (binding variables for example) how do I distinguish between updating the '$' space and updating the current context? I'm guessing that's done by whether or not $ appears as the single subsegment in a segment or whether it's part of a larger segment?
 
I had assumed (my problem right there :) from our previous discussions that we were using $$ to mean current context in order to preserve single purpose of $.
 
So then what you and Markus are suggesting is that $ have one of 3 purposes, depending on context:
  If it's at root of a message - it means the sender is the anonymous user
  If it's in a message and it's the only subsegment in a specified segment then it's the root of special space
  If it's in a message and it's a subsegment in a larger segment then it means the current context
 
What do you think of the following alternative, and is it too late to consider?
  =anon, anywhere, it means the sender is the anonymous user. An issue with this that may require a different version is that =anon is registered via ReadNotify.com.  Registrant might be willing to give it up given circumstances either for free or fee. 
  $, anywhere, means the root of the reserved space
  $$, anywhere, means the current context. Since variables are completely contextual this also is root of the variable namespace (last bit's a little dodgey, but I think it works).
 
Bill
 

From: drummond.reed@gmail.com [drummond.reed@gmail.com] On Behalf Of Drummond Reed [drummond.reed@cordance.net]
Sent: Monday, October 05, 2009 8:15 PM
To: Barnhill, William [USA]
Cc: Markus Sabadello; Giovanni Bartolomeo; OASIS - XDI TC
Subject: Re: [xdi] How to get from =markus/+email to the actual data

$ is actually the perfect XRI for anonymous access because it represents "self" or "the current context". And it's not only already reserved, it is the root of the XRI reserved space for system/special XRIs.

So $/$get//=markus/+email is simply requesting anonymous access to =markus/+email, whereas =giovanni/$get//=markus/+email is =giovanni requesting access (which would be granted if =markus link contract is to $, i.e., any context).

=Drummond

On Mon, Oct 5, 2009 at 3:28 AM, Barnhill, William [USA] <barnhill_william@bah.com> wrote:
Could this be solved by specifying a reserved i-name (might need to deal with them if someone has registered it already) of =anon or =unknown or some such?
 
Then a message from =giovanni is : =giovanni/$get//=markus/+email
and a message from an anonymous sender is =anon/$get//=markus/+email
 
The reasoning behind this is that =anon is still a valid invidivual i-name as i-names specify an individual identity and I think the anonymous user is an identity, in the same way that the null set is a special kind of set.
 
Bill

From: markus.sabadello@gmail.com [markus.sabadello@gmail.com] On Behalf Of Markus Sabadello [markus.sabadello@xdi.org]
Sent: Monday, October 05, 2009 4:50 AM
To: Giovanni Bartolomeo
Cc: Drummond Reed; OASIS - XDI TC
Subject: Re: [xdi] How to get from =markus/+email to the actual data

Yes I guess that's still kind of an open question.. You're right, if =giovanni is sending the message, then you would do
=giovanni/$get//=markus/+email

But sometimes you don't have a sender authority, or you want the sender to be anonymous. I'm not sure if we ever talked about this situation... I'm usually using "$" for an "anonymous" sender. Maybe there are better ideas?

Markus

On Mon, Oct 5, 2009 at 9:22 AM, Giovanni Bartolomeo <giovanni.bartolomeo@uniroma2.it> wrote:
Hello, one simple question regarding the subject "$" in the statement

$/$get//=markus/+email

is "$" referring to the authority which originates this message? E.g. if I'd be that authority, would the above statement be the same as

=giovanni/$get//=markus/+email

?

Thanks,
Giovanni

Def. Quota "Drummond Reed" <drummond.reed@cordance.net>:




On Thu, Oct 1, 2009 at 1:38 PM, Markus Sabadello
<markus.sabadello@xdi.org>wrote:

Hello XDI TC,

Someone asked me a question about the XDI4j library in Higgins and about
how XDI endpoints relate to XRI resolution. So I put together some commented
sample code which uses OpenXRI and XDI4j:
http://wiki.eclipse.org/XDI4j_Tutorial_6

The task is, given an XRI such as =markus/+email and nothing else, how do
you actually find and read the value (the e-mail address)?

Step by step, the code does the following:
1. It resolves the authority part of the XRI (=markus) using standard XRI
resolution with an XDI service type, i.e. it looks for an XDI endpoint in
the i-name's XRD.
2. After discovering that endpoint, it prepares and sends an XDI message
which looks like this:
$
  $get
     /
        =markus
           +email
3. The XDI endpoint answers with the statement that matches the $get query:
=markus
  +email
     "markus.sabadello@gmail.com"
4. In the end, the code prints out the literal from that statement.

In total, a few simple lines of actually working code that should
demonstrate how XRI and XDI work together.

Markus






----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]