Contrary to popular mythology, an OSF standard GUID can well be
utterly unique.

The value behind using a GUID is not in readability, it's in
programmatic accessibility. Why bother forcing the use of horribly
inefficient string processing on a URI when tools against the hex
bytes are orders of magnitude faster?

They're not expected to *EVER* be typed nor viewed by human beings.
Just something that let's the machinery do it's thing.

As for disasters, frameworks have value, regardless of what the
overly simplistic folks would have you believe.

-Bill Kearney

> GUID is a unique indentifier? except that it's not a global
address,
> it something useful inside a local system.
>
> we have these already in terms of these funny URI/URL thingy's
>
> GUID's are badly over used by developers, they are not user
friendly,
> they provide no useful information and they are horrible to type...
>
> how many websites have you seen where developers create article
id's
> using GUID's
>
> please keep rss simple, this guid's idea sounds like the disaster
> that happened when people mixed RDF into RSS...