atom feed29 messages in org.oasis-open.lists.xriRE: [xri] Property, rel comparison
FromSent OnAttachments
Eran Hammer-LahavJan 25, 2010 9:04 am 
Eran Hammer-LahavJan 25, 2010 9:06 am 
Scott CantorJan 25, 2010 9:16 am 
Eran Hammer-LahavJan 25, 2010 9:20 am 
Scott CantorJan 25, 2010 9:37 am 
Breno de MedeirosJan 25, 2010 9:44 am 
Scott CantorJan 25, 2010 10:24 am 
Drummond ReedJan 26, 2010 12:08 am 
Scott CantorJan 26, 2010 6:59 am 
Drummond ReedJan 26, 2010 7:31 am 
Breno de MedeirosJan 26, 2010 8:31 am 
Scott CantorJan 26, 2010 8:38 am 
Breno de MedeirosJan 26, 2010 8:57 am 
Scott CantorJan 26, 2010 9:00 am 
Breno de MedeirosJan 26, 2010 9:06 am 
Scott CantorJan 26, 2010 9:13 am 
Breno de MedeirosJan 26, 2010 9:19 am 
Eran Hammer-LahavJan 26, 2010 9:20 am 
Eran Hammer-LahavJan 26, 2010 9:24 am 
Breno de MedeirosJan 26, 2010 9:29 am 
Scott CantorJan 26, 2010 9:38 am 
Breno de MedeirosJan 26, 2010 9:42 am 
Scott CantorJan 26, 2010 10:02 am 
Eran Hammer-LahavJan 26, 2010 12:26 pm 
Eran Hammer-LahavJan 26, 2010 12:32 pm 
Scott CantorJan 26, 2010 12:44 pm 
Scott CantorJan 26, 2010 12:46 pm 
Breno de MedeirosJan 26, 2010 1:02 pm 
Scott CantorJan 26, 2010 1:47 pm 
Subject:RE: [xri] Property, rel comparison
From:Scott Cantor (cant@osu.edu)
Date:Jan 26, 2010 9:00:11 am
List:org.oasis-open.lists.xri

Breno de Medeiros wrote on 2010-01-26:

Is the rule for subject comparison going to be completely generic, or have special cases? But I agree, that's a reasonable point.

The rules for subject matching will probably have to use scheme-specific matching.

Isn't that part of standard normalization?

Search engines would really like if people referred to the same subject with the same string always, but unfortunately they do not. If we can't tolerate mismatches like http://example.com:80 and http://Example.com/ it may lead to serious interop issues.

I know that's definitely covered by normalization but maybe you have other things in mind also?

-- Scott