|John Bradley||Nov 23, 2008 11:24 am|
|Markus Sabadello||Nov 23, 2008 3:58 pm|
|John Bradley||Nov 23, 2008 4:14 pm|
|Drummond Reed||Nov 23, 2008 11:09 pm|
|Chasen, Les||Nov 24, 2008 5:07 am|
|Peter Davis||Nov 24, 2008 6:11 am|
|John Bradley||Nov 24, 2008 9:02 am|
|Victor Grey||Nov 24, 2008 10:22 am|
|John Bradley||Nov 24, 2008 10:46 am|
|Schleiff, Marty||Nov 24, 2008 11:00 am|
|Drummond Reed||Nov 24, 2008 11:07 am|
|Chasen, Les||Nov 24, 2008 11:35 am|
|Drummond Reed||Nov 24, 2008 12:10 pm|
|Schleiff, Marty||Nov 24, 2008 12:22 pm|
|Drummond Reed||Nov 24, 2008 12:43 pm|
|Drummond Reed||Nov 24, 2008 12:48 pm|
|Chasen, Les||Nov 24, 2008 12:57 pm|
|Victor Grey||Nov 24, 2008 1:56 pm|
|John Bradley||Nov 24, 2008 2:05 pm|
|Chasen, Les||Nov 24, 2008 2:10 pm|
|Drummond Reed||Nov 24, 2008 3:33 pm|
|John Bradley||Nov 24, 2008 4:21 pm|
|Subject:||Re: [xri] GCS Characters|
|From:||John Bradley (jbra...@mac.com)|
|Date:||Nov 24, 2008 9:02:11 am|
Certainly some apps will use XRI natively.
I think the point Drummond is trying to make is that in the UI for XDI server a user is unlikely to confuse a XRI with a email address.
Outside of XRI aware apps they would be circulating as HXRI as they are today so that legacy apps can do something with them.
The above are both relative URI in that the email would be
mailto://jbra...@microsoft.com though most apps don't present them that way.
Is this something that the UI for XRI aware apps can deal with?
Note that mailto://jbra...@microsoft.com may also resolvable to meta- data via XRD.
On 24-Nov-08, at 5:07 AM, Chasen, Les wrote:
In past emails I thought we said that the native xri would also still exist. So you could still have =drum...@microsoft.com for applications that understand xri.
From: Drummond Reed To: 'John Bradley' ; 'Markus Sabadello' Cc: 'OASIS XRI TC' Sent: Mon Nov 24 02:09:59 2008 Subject: RE: [xri] GCS Characters
John’s right - =drum...@microsoft.com is just as valid an XRI as @microsoft.com=drummond, and has the same type of global inference. It’s a reference to the organization in the context of the individual, and I can think of lots of uses for such a reference.
However I think Steve’s original concern is no longer an issue under the new XRI-as-relative-URI architecture, because the XRI bound to a base URI is no longer going to be confused with an email address. Examples:
In fact, even an ordinary email address when included in the path of a (non-mailto) URI is no longer an email address – it’s just a path.
From: John Bradley [mailto:jbra...@mac.com] Sent: Sunday, November 23, 2008 4:15 PM To: Markus Sabadello Cc: OASIS XRI TC; David Orchard Subject: Re: [xri] GCS Characters
You might want to do it for some malicious reason.
If we don't preclude it, the syntax is valid stupid or not.
If @microsoft.com=drummond is a subject in Microsoft's authority server that it is inferring has something to do with =Drummond then why wouldn't =drum...@microsoft.com be a subject in =Drummond's authority server hat he is inferring has something to do with the global @Microsoft.com
If we allow it someone will use it and if it can be misused someone will.
Steve's quite legitimate question is will the benefits of saying
=drum...@Microsoft.com vs =drummond*(@microsoft.com) outweigh the possible social engineering dangers that are introduced.
We need a clear answer to that. The answer may well be yes they do, but we need to consider it carefully.
On 23-Nov-08, at 3:58 PM, Markus Sabadello wrote:
Why would you ever want to put a company into the context of an individual (what does =drum...@microsoft.com mean??). To me it makes sense only the other way round, i.e. @microsoft.com=drummond.
And something that never appears anywhere can hardly confuse people, or? :)
On Sun, Nov 23, 2008 at 7:25 PM, John Bradley <jbra...@mac.com> wrote:
I spent some time on the phone yesterday with Steve Churchill reviewing the
proposal on GCS symbols in XRI 3.0.
This in 2.0 would be represented as: =drummond*(@microsoft.com) http://xri.net/=drummond*(@microsoft.com)
In removing the need for parenthesizing cross-references we run the risk of people misconstruing direct concatenated XRI as email addresses or otherwise trying to read the first XRI segment from right to left.
The problem is alleviated slightly by having the XRI bound to a scheme.
This is a social engineering problem rather than a actual resolution issue.
--------------------------------------------------------------------- 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