- From: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
- Date: Fri, 14 Dec 2012 09:39:27 -0500
- To: Toby Inkster <tai@g5n.co.uk>
- Cc: Henry Story <henry.story@bblfish.net>, public-webid Group <public-webid@w3.org>
- Message-Id: <635E013A-E72D-4C75-8BFA-5CC283F52705@openlinksw.com>
On Dec 8, 2012, at 02:03 PM, Toby Inkster wrote: > On Sat, 8 Dec 2012 17:35:35 +0100 > Henry Story <henry.story@bblfish.net> wrote: > >> http://www.w3.org/2005/Incubator/webid/wiki/WebID_Definition/hash2 > > FWIW, I don't think WebID should place any restrictions on users' > choice of URI; just as it shouldn't place any restrictions on what > ciphers are used for the TLS sessions established. > > I'm not saying that restrictions should not exist. People shouldn't be > using, say, a Caesar cipher (look it up if you don't know) for TLS; but > restrictions on TLS ciphers should happen in the TLS specs, not in > WebID. > > The WebID spec is the wrong *layer* to address this sort of issue. It's > an issue that needs resolving (even if that resolution might be that > the status quo is OK) at the linked open data level; or maybe even at > URI. > > So WebID shouldn't place restrictions on what URIs people choose to > identify themselves with. I don't even think we should require > HTTP/HTTPS; if people choose to use an FTP URI, chances are that most > existing implementations of WebID would cope. If they choose to use > an NNTP URI... well, I tend to be in favour of giving people enough rope > to fashion themselves the very best noose possible. > > Be liberal in what you accept; be conservative in what you omit. The > spec should accept whatever URIs people want to use; how-to guides > should steer people towards sane options. > > -- > Toby A Inkster > <mailto:mail@tobyinkster.co.uk> > <http://tobyinkster.co.uk> +1000 Ted -- A: Yes. http://www.guckes.net/faq/attribution.html | Q: Are you sure? | | A: Because it reverses the logical flow of conversation. | | | Q: Why is top posting frowned upon? Ted Thibodeau, Jr. // voice +1-781-273-0900 x32 Senior Support & Evangelism // mailto:tthibodeau@openlinksw.com // http://twitter.com/TallTed OpenLink Software, Inc. // http://www.openlinksw.com/ 10 Burlington Mall Road, Suite 265, Burlington MA 01803 Weblog -- http://www.openlinksw.com/blogs/ LinkedIn -- http://www.linkedin.com/company/openlink-software/ Twitter -- http://twitter.com/OpenLink Google+ -- http://plus.google.com/100570109519069333827/ Facebook -- http://www.facebook.com/OpenLinkSoftware Universal Data Access, Integration, and Management Technology Providers
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 14 December 2012 14:39:54 UTC