timbl's blog | Decentralized Information Group (DIG) Breadcrumbs
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 78 people (-23 private), first by anonymouse user on 2006-03-02
- Beefer on 2009-06-09 - Tags semantic_web , blog , timbl
- Franciscomarinas on 2009-02-22 - Tags w3c , blog
- Tisopo on 2009-01-14 - Tags no_tag
- Yukonsyl on 2009-01-13 - Tags information , mashups , reuse , semantic , web
- Dgovoni on 2008-12-30 - Tags web2.0 , research , reference , technology , standards , internet , blog , semantic-web , tim-berners-lee , W3C
Public Sticky notes
To play with semantic web links, I made a toy semantic web browser, Tabulator. Toy, because it is hacked up in Javascript (a change from my usual Python) to experiment with these ideas. It is AJAR - Asynchronous Javascript and RDF. I started off with Jim Ley's RDF Parser and added a little data store. The store understands the mimimal OWL
Highlighted by dcorking
People have, since it started, complained about the fact that there is junk on the web. And as a universal medium, of course, it is important that the web itself doesn't try to decide what is publishable. The way quality works on the web is through links.
It works because reputable writers make links to things they consider reputable sources. So readers, when they find something distasteful or unreliable, don't just hit the back button once, they hit it twice. They remember not to follow links again through the page which took them there. One's chosen starting page, and a nurtured set of bookmarks, are the entrance points, then, to a selected subweb of information which one is generally inclined to trust and find valuable. A great example of course is the blogging world. Blogs provide a gently evolving network of pointers of interest. As do FOAF files. I've always thought that FOAF could be extended to provide a trust infrastructure for (e..g.) spam filtering and OpenID-style single sign-on and its good to see things happening in that space.
Highlighted by davidjennings
Some things are clearer with hindsight of several years. It is necessary to evolve HTML incrementally. The attempt to get the world to switch to XML, including quotes around attribute values and slashes in empty tags and namespaces all at once didn't work. The large HTML-generating public did not move, largely because the browsers didn't complain. Some large communities did shift and are enjoying the fruits of well-formed systems, but not all. It is important to maintain HTML incrementally, as well as continuing a transition to well-formed world, and developing more power in that world.
Highlighted by ironick
contenders
Highlighted by tisopo
The Semantic Web will not supersede the current Web. They will coexist.
Highlighted by takuya514
One thing to always remember is that the Web of the future will have BOTH documents and data. The Semantic Web will not supersede the current Web. They will coexist. The techniques for searching and surfing the different aspects will be different but will connect.
Highlighted by djiezes
The benefit of the Semantic Web is that data may be re-used in
ways unexpected by the original publisher.
Highlighted by yukonsyl
when a Semantic Web start-up either feeds data to others who reuse it in
interesting ways, or itself uses data produced by others, then we start to see
the value of each bit increased through the network effect.
Highlighted by yukonsyl
The benefit of the Semantic Web is that data may be re-used in ways unexpected by the original publisher. That is the value added. So when a Semantic Web start-up either feeds data to others who reuse it in interesting ways, or itself uses data produced by others, then we start to see the value of each bit increased through the network effect.
Highlighted by djiezes
So if you are a VC funder or a journalist and some project is being sold to you as a Semantic Web project, ask how it gets extra re-use of data, by people who would not normally have access to it, or in ways for which it was not originally designed. Does it use standards? Is it available in RDF? Is there a SPARQL server?
Highlighted by djiezes
It should be easier to make those mashups by just pulling RDF (maybe using RDFa or GRDDL) or using SPARQL, rather than having to learn a new set of APIs for each site and each application area.
Highlighted by djiezes
Public Comment
on 2006-07-26 by sylvaincomte
on 2006-08-07 by phreaky
on 2006-08-18 by brotherjohn
on 2006-10-23 by alesmv
on 2006-10-24 by kgl0903
on 2006-12-30 by iconolith