A small lyrical digression. Looking at the history of the web, you understand what they did in
good cities: first they laid down the main sidewalks. In addition to this, people trodden comfortable paths. And then these paths (where people are comfortable) were asphalted, and everything worked out well. So in the web. At first, there appeared rather poor HTML, which until now has grown into almost universal and perfect tool. Because they finished it in such a way that it would be convenient, based on experience, and not on poking a finger into the sky.
So, the W3C looked at how people tied to the same FOAF address, OpenID, and anything else decided to standardize it all and make it smarter.
They set themselves the task - to standardize
URIs here I will give the conclusions of their latest draft.
')
For example, there is Example Inc. Corporation. Alice and Bob work there.
www.example.comthe homepage of Example Inc.
www.example.com/people/alicethe homepage of Alice
www.example.com/people/bobthe homepage of Bob
We formulate the problem?Suppose the company wants to show off and publish information about Alice in N3 format
<Alice-URI> a foaf: Person;
foaf: name "Alice";
foaf: mbox <mailto: alice@example.com>;
foaf: homepage <http://www.example.com/people/alice>
By all rules, the RDF <URI-Alice> should contain a link to it. But where is the link? At
www.example.com/people/alice is impossible, because according to the rules <URI-Alice> a foaf: Person; It must contain a link to the person.
Read more on my blog >>