lisa dusseault lisaosafoundationorg aug 7 2008 348 julian reschke wrote hannes thanks pointers tschofenig hannes nsn fiespoo wrote reading mails unfortunately find strong recommendations seems reading rfc 3205 got confused initially entire discussion started lost also solicited review uri scheme see httpwwwietforgmailarchiveweburireviewcurrentmsg00601html pointed rfc 3205 later decided define lost uri scheme record discussion appsarea meeting vancouver updating bcp56 rfc3205 think conclusion reading need new uri schemes port numbers anything beyond webbrowsing definitively represent ietf consensus today state art even recent ietf specifications caldav atompub whatnot although agree lot tradeoff advice given thread im sure held really kind thing caldav atompub latter definitely involve web servers holding kinds resources http client download simple get thanks content types chance using application content reasonable way caldav atompub make use parts http like delete put post caching auth cookies really extensions http use http special applications im certain designers held view held extension http helping clients access use maybe author web resources happen location documents philosophical position certainly implies use http scheme rest ful decisions however designers view held using http request response transport service otherwise web server implies different approach im using http road taken try help protocol suffering interoperability problems due ignoring extra features http spec writers probably dont initially think using disabling eg see httptoolsietforghtmlrfc5055appendixb could still improved upon benefit interop narrows features http used assumed supported lisa _______________________________________________ ietf mailing list ietfietforg httpswwwietforgmailmanlistinfoietf thu 07 aug 2008 122540 0400 new schemes vs recycling http past lc comments ondraftietfgeoprivhttplocationdelivery08