julian reschke julianreschkegmxde thomson martin wrote hi hannes julian course makes obvious new uri scheme totally pointless recently updated examples lower one upper one martin thomson might provide background issue since also told update drafts interesting looking forward understand reasons martin provide bit background im impartial topic uri schemes uri scheme added request iesg review concerns loss contextual information relating uri used contexts outside context devicelis exchange well theres definitively total disconnect iesg recommendation w3c tags point view see ongoing discussion tag mailing list xri scheme would good organizations could come consistent answers new uri scheme defined needs state identifies resolved identifies http resource resolution done via http seems dont need uri scheme seems fall category apples ical itunes related schemes arent registered uri schemes reason assuming uri necessary reason go full uri request line ensure server able distinguish helds uri matching https uri without server potentially know difference server supposed able differentiate uri identifies something else im sure problem want solve could elaborate isnt custom mime type conneg totally sufficient besides going deploy libraries allow put full uri request line plan deploy software knows uri scheme without absolute uri possibility held http uris could considered equivalent fact would meaningful difference comes protocol exchange rightly pointed ill note isnt difference important certainly wasnt factor discussions lead introduction new scheme yes using absolute uri common practice http anything requests proxies however rfc 2616 requires servers understand support absolute uris sec 512 experience safe thing assume http servers generally treat uri sensibly thats true 1 uri scheme equivalent https whats difference resource identified 2 intend deploy software knows uri scheme br julian _______________________________________________ ietf mailing list ietfietforg httpswwwietforgmailmanlistinfoietf wed 06 aug 2008 040640 0400 past lc comments draftietfgeoprivhttplocationdelivery08