| From | Sent On | Attachments |
|---|---|---|
| Eran Hammer-Lahav | Jan 25, 2010 9:04 am | |
| Eran Hammer-Lahav | Jan 25, 2010 9:06 am | |
| Scott Cantor | Jan 25, 2010 9:16 am | |
| Eran Hammer-Lahav | Jan 25, 2010 9:20 am | |
| Scott Cantor | Jan 25, 2010 9:37 am | |
| Breno de Medeiros | Jan 25, 2010 9:44 am | |
| Scott Cantor | Jan 25, 2010 10:24 am | |
| Drummond Reed | Jan 26, 2010 12:08 am | |
| Scott Cantor | Jan 26, 2010 6:59 am | |
| Drummond Reed | Jan 26, 2010 7:31 am | |
| Breno de Medeiros | Jan 26, 2010 8:31 am | |
| Scott Cantor | Jan 26, 2010 8:38 am | |
| Breno de Medeiros | Jan 26, 2010 8:57 am | |
| Scott Cantor | Jan 26, 2010 9:00 am | |
| Breno de Medeiros | Jan 26, 2010 9:06 am | |
| Scott Cantor | Jan 26, 2010 9:13 am | |
| Breno de Medeiros | Jan 26, 2010 9:19 am | |
| Eran Hammer-Lahav | Jan 26, 2010 9:20 am | |
| Eran Hammer-Lahav | Jan 26, 2010 9:24 am | |
| Breno de Medeiros | Jan 26, 2010 9:29 am | |
| Scott Cantor | Jan 26, 2010 9:38 am | |
| Breno de Medeiros | Jan 26, 2010 9:42 am | |
| Scott Cantor | Jan 26, 2010 10:02 am | |
| Eran Hammer-Lahav | Jan 26, 2010 12:26 pm | |
| Eran Hammer-Lahav | Jan 26, 2010 12:32 pm | |
| Scott Cantor | Jan 26, 2010 12:44 pm | |
| Scott Cantor | Jan 26, 2010 12:46 pm | |
| Breno de Medeiros | Jan 26, 2010 1:02 pm | |
| Scott Cantor | Jan 26, 2010 1:47 pm |
| Subject: | RE: [xri] Property, rel comparison | |
|---|---|---|
| From: | Eran Hammer-Lahav (er...@hueniverse.com) | |
| Date: | Jan 26, 2010 9:24:42 am | |
| List: | org.oasis-open.lists.xri | |
-----Original Message----- From: Breno de Medeiros [mailto:bre...@google.com] Sent: Tuesday, January 26, 2010 8:32 AM To: Drummond Reed Cc: Scott Cantor; Eran Hammer-Lahav; xr...@lists.oasis-open.org Subject: Re: [xri] Property, rel comparison
What is the benefit of establishing one rule to compare URIs as 'subject' and one for other headings?
Will it improve interop? If it leads people to implement subject comparison as byte-by-byte, I think not.
I strongly disagree. Subject comparison is always application specific and
should be noted as such. We already have processing rules for trust purposes and
I am sure it will extend to pretty much any application that uses subjects.
Subject point to a resource and therefore are scheme-specific and obey by those
rules.
Relation types and property types URIs on the other hand are strings structured
like URIs. They should follow the same rules as XML namespaces and should not be
normalized. There is no reason what-so-ever for anyone to use different
variations of these URIs - that's where interop breaks.
Either way, the property type questions should be resolved the same way the
relation type question, and that is going to come from Web Linking since we
already bound it to that.
EHL
On Tue, Jan 26, 2010 at 07:32, Drummond Reed <drum...@xdi.org> wrote:
My position on this is simple. XRD is headed into, we hope, extremely wide usage. Therefore our URI comparison policy should be whatever has been proven in practice to best support interop.
If character-by-character comparison = highest degree of interop, as Scott says, then we better have a good reason to adopt any another policy.
=Drummond
On Tue, Jan 26, 2010 at 6:59 AM, Scott Cantor <cant...@osu.edu> wrote:
Drummond Reed wrote on 2010-01-26:
2) We don't have consensus yet about the best URI comparison approach to define.
The current "default" position IMHO is Breno's statement, but I agree with Eran that we really should be explicit in the text anyway.
I'm willing to argue that URIs used solely as identifiers (i.e., not Subject) should be compared like XML namespaces, character for character. Apparently there's pushback on that, so I guess if there's nobody else that agrees with me, I would suggest we add text along the lines that Breno suggested.
I will say, again, that I have not seen any significant interop issues arise from using binary comparison because people treat them as constants.
-- Scott
-- --Breno
+1 (650) 214-1007 desk +1 (408) 212-0135 (Grand Central) MTV-41-3 : 383-A PST (GMT-8) / PDT(GMT-7)
--------------------------------------------------------------------- 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





