Re: How To Handle WebIDs for (X)HTML based Claim Bearing Resources

The foreseeable future is the caveat - and is fine (and traditional) in identity for content class resources

But the dynamics of people is not as with content. The I'd requirements change. I'm not in control of my blogger I'd (it can disappear tommorow, should "get a phone call")

The uk does better than others in official naming. You can go to court and be referred to as your pseudo official nom de plume, street alias, customary monicker. In the web, one has to be able to integrate similar nyms, since u have so little control over them. The identity resolver has to assume you lose ontrol, but can yet provide some stable point of reference. This was of course the xri canonical name argument (addressing life cycle engineering, not just todays locator/resolver/remapper function)

This is why I want the cert as uri in the card,as a data uri. It's a canonical name, that the telco/google/officialdom doesn't control - and thus apes real life (as in thx uk courts example above).

U don't need to be well identified to get sentenced.courts are perfectly happy to sentence the anonymous (but guilty) x. Your record does need to attach to you (as x, y, z), though thru some means of integration.

Sent from my iPhonen 
Letle
On Dec 30, 2011s, at 1:08 AM, "Mo McRoberts" k<mo.mcroberts@bbc.co.uk> wrote:

> 
> On 29 Dec 2011, at 23:26, Jürgen Jakobitsch wrote:
> 
>> hi,
>> 
>> what i can tell from many discussions with customers is that
>> people are kind of picky about their uris.
>> the "cool uri" meme is often the only thing of interest, no matter
>> what technical advantages there are.
> 
> “Cool URIs”[0] mostly means “don’t include transient cruft in your URIs which means you’re very likely to need to change them, causing pain for either you or your users”.
> 
> Do you mean (so-called) “search engine-friendly”[1] URIs? (not that the two necessarily have to conflict)
> 
> We do get quite a bit of pushback about our URIs on http://www.bbc.co.uk/programmes because they use opaque identifiers which result in URIs like this:
> 
> http://www.bbc.co.uk/programmes/b006m86d#programme

> 
> instead of:
> 
> http://www.bbc.co.uk/programmes/eastenders#programme

> 
> The rationale is that the URIs are generated automatically — which will come as no surprise to anybody — and the source data is often imperfect; making the URIs “friendlier” runs the risk of them needing to change when the data is corrected (and so mechanisms have to exist to support that, with an associated cost), or being out of step with the corrected data (unpalatable to editorial people), or that the 'sanitised' form of the title used to generate the URI results in something unfortunate.
> 
> A notorious example of the latter came about on the BBC Recipes site a year or so ago — it took the 'sanitised title' approach — a recipe entitled “Carrots glazed in cumin and orange” was sanitised to an identifier truncated after the “m” in “cumin”, resulting in quite a rude-looking URI.
> 
> However, all of this is somewhat by-the-by. The bottom line is that a published URI is a commitment to the rest of the Web: if somebody is willing to bear the responsibility of ensuring that resolution will result in a sensible response for the foreseeable future (be that a 200, a 3xx, or a 410), then they can insist on picking whatever crazy mixed-up scheme they like, so long as it works. We’ve all done it at some point or another…
> 
> M.
> 
> [0] http://www.w3.org/Provider/Style/URI

> [1] http://www.sitepoint.com/search-engine-friendly-urls/

> 
> -- 
> Mo McRoberts - Technical Lead - The Space,
> 0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E,
> Project Office: Room 7083, BBC Television Centre, London W12 7RJ
> 
> 
> 
> http://www.bbc.co.uk/

> This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
>                    
>

Received on Friday, 30 December 2011 22:28:54 UTC