lisa dusseault lisaosafoundationorg believe instigated creation new uri scheme held thats say however iesg required solution elaborate martin said raised issues uri scheme added review solutions might work instead new uri schemes discussions started bar san diego unminuted list email issues trying help wg address http uri found email blog etc operating system launches web browser however web browser doesnt know formulate held request even know wouldnt know whenwhether location uris appear another context lets say another protocol data format helpful able limit kind uris appear context limiting saying uris must uri scheme easy way problems solved ways besides defining new uri scheme said new uri scheme help problems highlight issue regular http requests eg get without body standardized interoperable held ok use new uri scheme target http request thats welldefined point http extensibility theory im aware major client server library limitations would prevent use practice made explicit document defines uri schemes believe implicit obvious im aware w3c tag recommendations new uri schemes tr says good practice reuse uri schemes specification reuse existing uri scheme rather create new one provides desired properties identifiers relation resources notes say example need demonstrate bar uris new schemes want huge value add debate whether example big valueadd whether http uri fails express client needs custom get request given caveats lack official iesg ietf position believe theres consistency w3c tag recommendations ietf usage potentially specific usage lisa aug 5 2008 423 pm 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 assuming uri necessary reason go full uri request line ensure server able distinguish helds uri matching https uri without server potentially know difference 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 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 cheers martin message designated recipient may contain privileged proprietary otherwise private information received error please notify sender immediately delete original unauthorized use email prohibited mf2 _______________________________________________ ietf mailing list ietfietforg httpswwwietforgmailmanlistinfoietf _______________________________________________ ietf mailing list ietfietforg httpswwwietforgmailmanlistinfoietf wed 06 aug 2008 144443 0400 past lc comments draftietfgeoprivhttplocationdelivery08