Semantic Wave Blog
News feeds and commentary by Jamie Pitts
« April 2004 | Main | June 2004 »

May 22, 2004

The Vision Thing

Paul Ford wrote in his XML.com article covering WWW2004:

... But in the short term, while no one can fully agree on what the Semantic Web is, the need for a clearly articulated vision is of essence in order to move the Semantic Web further. It is surprising to see that its leading evangelist is also uncertain as to whether Semantic Web's immediate destiny is on the server or the desktop. Source.
Who needs a vision when each of us knows our own way? After all, the first web was not initiated with the issuance of a convincing vision statement, nor was the first steam engine, car, or personal computer.

Invention all starts with a very personal vision about how to solve a problem, followed by months of grueling work -- work make easier by exploiting available standards, tools, and ideas. I see the W3C, perl, apache, linux, and other open developer communities as the great givers of standards, tools, and ideas of our time. But they are catalysts, not drivers.

While I am skeptical of vision -- often found in the businesses and their feeder communities, I do enjoy and benefit from absorbing the visions of leaders such as Tim Berners Lee. But a "big idea" such as the semantic web does not need a clearly articulated vision to become widely adopted.

What it needs is what we already have.

Posted by Jamie Pitts at 4:23 PM | TrackBack

May 20, 2004

Slashdot Discusses Next Generation Web

The real utility in reading this slashdot discussion is to understand the common objections of (and answers to) semantic web doubters. It's ironic that slashdotters are not discussing the widespread use of semantic web concepts in the blogosphere!

Posted by Jamie Pitts at 5:20 PM | TrackBack

May 19, 2004

PIKII

Marc Canter posted an excerpt from A Personal Information and Knowledge Infrastructure Integrator. This academic paper is chock full of interesting (but familiar) ideas. PIKII is an information management system which, essentially, is the social software/ blogging / semweb scene of the near-future.

Weblogging adapts hypertext features

Nodes:
Encapsulated units of content in any MIME type format identifiable by W3C-compliant protocols and data structures.

Transclusion:
XML RSS-based syndication distributes content across multiple venues.

Link types:
Static and dynamic URIs for tracking and addressing comments, posts and news with time/date stamps and associative properties identifiable using information retrieval methods.

Backlinks:
Trackback and HTTP-referrer linking provides bidirectional links.

Annotation:
A core attribute of many blog posts and the syndication format is a link, often directly connectable to a content-level XML node. Source.

Posted by Jamie Pitts at 3:12 PM | TrackBack

May 17, 2004

Creative Namespaces and Syntactic Sugar

Tim O'Brian reminds us in Creative Class Naming to add some flair to the namespaces that refer to our in-code data and actions. I have used this technique on many occasions, especially for ideas which may be dificult to explain (or to remember!). By way of O'Reilly Dev Blogs.

You may not think that your company's fancy e-commerce system can afford to have an object named Bouncer, but I urge you to reconsider. Bouncer communicates the idea better that AuthenticationEnforcementObject or ServletSecurityFilter. Source
Amen to that.

Then there is syntactic sugar. Our friends =~ and && may not have a lot of flair, but help reduce the caffeine intake required to maintain a developer's interest in the task at hand. They add a lot of expressiveness to the code, not to mention compactness.

Let's invent some new characters.

Perl 6 has just about exhausted every combination of non-alpha characters, yet perl programmers want more. During one particularly long afternoon at Java, I was thinking about how unicode could be used to create new symbolic representations of the oft-used functions and classes in perl. Ok, I admit it. I was fantasizing about perl. It gets worse.

In text editors such as gvim, and instance of DBI could look like a stack of pancakes. The foreach would be represented by a loopy arrow. CGI, a spider web. XML::DOM, a who knows what. WebObjects Builder expresses this concept a bit in the page editor. This wacky, programmers-only character set could lead to quite an interesting keyboard (as if the shift key weren't enough trouble for some people).

Posted by Jamie Pitts at 10:08 PM | TrackBack

May 12, 2004

Regular XML RDF

Dave Beckett pointed to Regular XML RDF, which he presented at XML Europe 2004. With a nod to Turtle short-hand and to the RDF/XML Syntax Spec, he illustrated a clearer and more verbose expression of subject-predicate-object statements in XML.

There is quite a gap between RDF the system and RDF the format. Call me slow or just plain new to this, but it takes a bit of a mental flip to transform one into the other. Mr. Beckett's approach allows the programmer to understand both the intent of the RDF system as well as the meaning of the information at hand.

<graph xmlns="http://ilrt.org/discovery/2004/03/rxr/">
  <triple>
    <subject uri="http://purl.org/net/dajobe/"/>
    <predicate uri="http://purl.org/dc/elements/1.1/creator"/>
    <object>Dave Beckett</object>
  </triple>
</graph>

Source. Posted by Jamie Pitts at 5:12 AM | TrackBack

May 6, 2004

Casual Ontology Development

Members of the Mindswap Project have posted Lifecycle of a Casual Web Ontology Development Process for presentation at the WWW2004 WE-SW Workshop.

The paper begins with an interesting description of a short-hand version of OWL which is designed for rapid entry and clarity.

We limit expressivity (i.e. no support for nested restrictions etc) to maintain readability, yet provide sufficient building blocks to construct a basic ontology model quickly, that can be refined later using a more powerful ontology editing tool. A more formal approach to our shorthand notation is being developed at the side. Source.

Lifecycle then describes a design scenario in which Mindswap's SWOOPed toolkit is used to search for and import terms related to the ontology under construction.

Having found related concepts/properties that the user could potentially use in the ontology being created, the editor interface must provide the user with the ability to either link to the data directly (with or without importing the entire external ontology) or borrow a specific subset of it (using a copy-paste mechanism). Source.

Posted by Jamie Pitts at 7:38 PM | TrackBack

May 5, 2004

Distributing the Load of the Semantic Web

Ben Hammersley has put together a cool egoboo tracker for authors, culling data from Amazon, Technoratti, AllConsuming, and others (by way of Cory Doctorow). It is an interesting way to re-combine information.

Unfortunately, the Auctorial Ego Tracker is somewhat slow due to the fact that it assembles the source data in real-time. But it got me thinking about the use of web resources. As real-time meaning aggregators gain in popularity, they will begin to put a much heavier load on web services as well as web servers simply hosting RDF and XML files. If open source applications and useage practices are not developed to distribute the load, the power (and necessity) of well-funded intermediary services such as Google will continue to grow.

It is not surprising that one leading discussion among bloggers concerns the inefficient and potentially overwhelming consumption of RSS feeds. William Grosso's Sunday Afternoon Thoughts on the Design of RSS Aggregators does a good job of explaining this problem and offering solutions.

Some recent approaches to addressing interaction limitations actually borrow ideas from the internet, usenet, and web build-out, including pDNS and RSS over BitTorrent. There is also an interesting discussion on www-rdf-interest about distributing RDF queries.

On a related note, I have recently been sketching out how a small web community might maintain some sort of RDF cache / router / query platform to buffer the interaction between its members and the greater semantic web.

Posted by Jamie Pitts at 7:08 PM | TrackBack

May 4, 2004

Bible Study

I have always believed that Bible study groups are a great source of ideas for the semantic web. These small communities use techniques for referencing, discussing, and bringing meaning to text that were developed long before information became a science.

The Holy Bible as Placeless Content is not only an excellent exploration of the semantic web practices of Bible scholarship, but also a very decent set of practical useage scenarios.

But certain tools are build to make it easier for Bible-enthusiasts to live their christian faith.
  • Normative Identifiers (aka Uris)
  • Cross References (aka Hyperlinks)
  • Blogging
  • Indices (aka Search Engines)
  • Chain Systems (aka Link Collections)
  • Excessive Quoting (aka blogrolling)
  • Source.

I look forward to spending more time delving into how Christians and other followers of "the Book" have implemented the semantic web.

Posted by Jamie Pitts at 6:40 PM | TrackBack

May 3, 2004

PeoplesDNS

Joel De Gan of PeoplesDNS has posted Whats the problem with FOAF?. He intends to add centralization, private information, social circumstance, and groups - all through his FOAF dns concept. It looks like he will use the RELATIONSHIP (the older one?) and Trust ontologies in this effort.

I am very interested in how community centers will use concepts such as pDNS and what their role in the development of open social networking will be. Social "routers" will be able to provide a level of customization (of information, participation, formality, and privacy) which will be required to break social networking away from the big social networks.

PeopleDNS will use a "De Gan Filter" to handle the anticipated large dataset. Last week, Danny Ayers posted a brief summary of De Gan's implementation of bloom filters.

Posted by Jamie Pitts at 2:51 PM | TrackBack

May 2, 2004

Mozdex Announced

Byron Miller has posted an overview on Kuro5hin about the Mozdex search engine, a service that will provide open information about their page ranking strategy. The indexing process is performed by Nutch, while the search app runs on Tomcat and Lucene. He ends with this open question (for which there are many responses):

Do you think it is actually feasible to work on a process that stays ahead of the cheaters or do you believe it will be something doomed to fail just because its competing against the likes of Yahoo or Google? Source.

Posted by Jamie Pitts at 12:34 AM | TrackBack

Archives

 January 2008
 November 2007
 October 2007
 September 2007
 August 2007
 June 2007
 May 2007
 April 2007
 March 2007
 February 2007
 January 2007
 December 2006
 November 2006
 October 2006
 September 2006
 August 2006
 July 2006
 May 2006
 April 2006
 March 2006
 February 2006
 January 2006
 November 2005
 October 2005
 September 2005
 August 2005
 June 2005
 May 2005
 April 2005
 March 2005
 January 2005
 December 2004
 November 2004
 October 2004
 September 2004
 August 2004
 July 2004
 June 2004
 May 2004
 April 2004
 March 2004


Small picture of Jamie Pitts When I talk about the semantic web, I feel a lot like Linus. No, not Linus Torvalds. I meant the other one. - JP


whoami?

Projects:
  Winnow My Bloglines Down
  Memecat
  Listgasm


Curently Reading

cover The Art of Unix Programming
Eric Raymond

Semantic People
Danny Ayers
Dave Beckett
Tim Berners-Lee
Tim Bray
Dan Brickley
Marc Canter
Paul Ford
Seth Ladd
Seb Paquet
Clay Shirky
Roland Tanglao
Dave Winer

Syndication:
 RSS Version 1.0
 RSS Version 0.91


Recent Entries
 The Vision Thing
 Slashdot Discusses Next Generation Web
 PIKII
 Creative Namespaces and Syntactic Sugar
 Regular XML RDF
 Casual Ontology Development
 Distributing the Load of the Semantic Web
 Bible Study
 PeoplesDNS
 Mozdex Announced

Categories
 AI
 Blogs
 Business
 Data Munging
 Development
 Formats
 How-To
 Ideas
 Languages
 Law
 Ontologies
 OWL
 People
 Products
 Projects
 QOTD
 RDF
 Research
 Social Software
 SRM
 Standards
 Thinking Out Loud
 Trends
 Twitter
 Visualization
 W3C
 Web Services
 Wikis


Creative Commons License
This weblog is licensed under a Creative Commons License.

Powered by Movable Type

Copyright © Jamie Pitts