Potlach Feast

Stu Weibel’s post on ‘List Making Meets Redirection’ prompted me to comment on some of the Active PURL work (PURLs with associated services) we at Zepheira has been developing. Example ‘Active PURLs’ might be notification to publishers of problems with target URLs (basically a link-checker for PURLs), notification to readers of updates to target PURLs (a “what’s new” feed for PURLs), etc. More specifically the architecture allows for an open marketplace to grow around such associations with PURLs (or PURL patterns) and services.

While I only touched briefly on this work in my comment, David Wood has expanded on this in his blog and given additional context on the potential business applicability of this approach.

Perhaps the most interesting use of Active PURLs to enterprises might be the ability to provide standardized RDF metadata about SOA Web Services as well as relational databases. UDDI is so broken, we might as well fix it with existing SemWeb standards. That is not a new idea, but the application of Active PURLs to the problem is.

Applying the lessons and standards of the web back inside the enterprise makes sense for managing evolution, supporting collaboration and more effectively delivering products and services. More and more businesses are starting to realize the true benefit of being *in* the Web, not just on it.

For a long time I’ve been thinking how useful it would be to give PURLS to people as a key part for managing evolving social networks. And now that the new purl work we’re doing at Zepheira (which is downright scary-good due to in part a rock solid engineering team and the use of NetKernel as a key underlying technology) will include support for identification of non-document resources, this will soon be possible.

Recently, Brian has been reflecting on his building of some very cool FOAF tools. And now whats even cooler is that it looks like Brian is on the case …

This exercise has also inspired me to make some progress on my goal to create some good tools to lower the bar to FOAF usage. I am going to leverage the PURLS work that we are doing for the OCLC. This will allow us to create permanent, resolvable names for ourselves that transcend where we currently hang our hats*. This will allow the networks to be more resilient. As many links as I am finding, there have been a ton of broken links (presumably people who have moved on) that would have enriched the result set even further!

I suspect he’ll have a production ready system in place by sometime tomorrow

15 years ago, I was involved in series of discussions at the IETF regarding technical standards related to identifying resources in decentralized environments. Acronyms such as “URI”, “URN”, “URL”, “URC” (and occasionally the phrase “you are kidding?!”) where constantly thrown around with much heated debate regarding requirements, protocols, semantics and capabilities for each of these technologies. URLs (Uniform Resource Locators … the global identifiers that start with ‘http:’, ‘mailto:’, ‘ftp:’, etc) were increasingly becoming prevalent as people found the immediate feedback of merging “clickability” and global “addressability” an attractive one. The others standards, however, were not so lucky.

At that time, the library community was starting to focus on issues related to cataloging and managing Web resources. Relaxing link integrity (404 file not found) and making it easier for people to create these URLs was one of the reasons the Web had succeeded where other hyperlinking systems had failed. This relaxation, however, caused problems for effective cataloging, managing and relating of resources. Spending time, effort and money to do this only to find the resource is no longer available because it had been moved, etc. was a serious issue to individuals in the library community focused on describing and providing effective access to relevant digital resources.

A solution to this problem was developed by OCLC; PURLs - Persistent URLs. PURLs provided a level of indirection that allows the underlying Web addresses of resources to change over time without negatively affecting systems that depend on them. Persistence is not an technological issue as much as one of social and organizational commitment. The PURL software provided the simple technological solution, and made it available for others to use, but it was OCLC running the purl.org service that provided the organizational commitment that helped make it possible for others to create and share persistent identifiers.

OCLC has been running the purl.org services for more than 12 years; there are very few services I can think of that can make such a claim. The Library community has in many ways been ahead of the general curve for managing data. A barrier for weaving these ideas, however, into various other non-library applications is that the code behind this service has largely been the same for the past 12 years as well. I’m quite pleased to note, however, that this is in the process of changing. More specifically, the following press release explains whats going on.

DUBLIN, Ohio, July 11, 2007—OCLC Online Computer Library Center, Inc. and Zepheira, LLC announced today that they will work together to rearchitect OCLC’s Persistent URL (PURL) service to more effectively support the management of a “Web of data.”

This re-architecture will not only make it easier for folks to embed PURLs within existing applications, it will also be updated to reflect the current understanding of Web architecture as defined by the World Wide Web Consortium (W3C). This new software will provide the ability to permanently identify networked information resources, such as Web documents, as well as non-networked resources such as people, organizations, concepts and scientific data. This capability will represent an important step forward in the adoption of a machine-processable “Web of data” enabled by the Semantic Web.

One of the most important principles for Zepheira is that developments towards a Semantic Web can be carefully tuned and scaled to meet the immediate needs of businesses, while valuable experience from solving enterprise needs can bring focus to Semantic Web efforts. I’m pleased to see this work underway and very much look forward to what capabilities the new PURL work will help enable in the next 12 years (and beyond).

Several folks have asked me privately about Zepheira … more specifically what we do, how to pronounce it and where the name came. The following is a poor attempt to minimize future inquiries

Ok, first, what is it… the home page captures some of this:

Zepheira provides solutions to integrate, navigate and manage data across personal, group and enterprise boundaries to save time and money. Our team are experts in applying Semantic Web standards and knowledge management technologies to address your specific data integration challenges.

Not quite a full answer, but close. For those interested in more details, Zepheira’s services page may be additionally useful.

Secondly… how to pronounce it:

zepheira : ze-fear’-a

see… that wasn’t so hard

And finally, where did the name come from…

Naming things in general is difficult- companies even more so.

I’m fortunate enough to be part of a team of industry leaders who have come together to help provide effective solutions to address various data integration, collaboration and knowledge exchange challenges. During the discussion on what to call ourselves, we found ourselves discussing a wide range of inter-related topics including philosophy, values, experiences, lessons learned and future goals. James Lipton’s Inside the Actors Studio questions, care of Bernard Pivot, we found equally insightful In the process of sharing our individual views on various subjects we collectively recognized that while each of us are respected industry leaders in various areas, we also shared a deep passion for the arts. We found that everyones ‘hobby’ was incredibly artistic in nature - pottery, woodworking, sculpting, music, poetry, martial arts, weaving / fabric, photography, etc.

I own only one piece of “serious” art (something I paid money for). It’s a painting from an Armenian artist named Vakhtang. My wife and I stumbled upon this piece independently in Sausalito and it holds a special place in our hearts. I walk past it everyday and everyday I pause briefly to breath it in. It’s a bit of a daily ritual of mine; viewing this piece makes me pause, reflect and subsequently feel a bit better about life, the universe and everything.

The painting is called ‘Zepheira’.

It was one of those ‘ah ha!’ moments that we as a team had and it came together instantly: “Zepheira, ‘The Art of Data’”. It simply felt right.