Attendees numbered about 35, and came from widely varying backgrounds from librarian to linguist to professor to student to CTO, though uniformly geeky. With SemTech this week, the timing was right, and the number of international attendees was impressive.

In community development, nothing gets completely decided just because a few people met. But progress happens. The first day was largely exploratory, but also covered plenary topics that nearly everyone was interested in. Namely:

• Finding, choosing, and knowing when to create vocabularies
• Mapping from one vocabulary to another
• RDBMS to RDF mapping

Much of the shared understanding of these discussions is captured on various wiki pages connected to the one at the top of this article.

For day 2, we split into smaller working groups with more focused topics. I sat in on a discussion of Common Tag (which still feels too complex to me, but does fulfill a richer use case than rel-tag). Next, some vocabulary design, planning a microformat (and eventual RDF vocab) to represent code documentation: classes, functions, parameters, and the like. Tantek Çelik espoused the “scientific method” of vocab design: would a separate group, in similar circumstances, come up with the same design? If the answer is ‘yes’, then you probably designed it right. The way to make that happen is to focus on the basics, keeping everything as simple as possible. If any important features are missed, you will find out quickly. The experience of getting the simple thing out the door will provide the education needed to make the more complicated follow-on version a success.

From the wrap-up: if you are designing a vocabulary, the most useful thing you can do is NOT to unleash a fully-formed proposal on the world, but rather to capture the discussion around it. What were the initial use cases? What are people currently doing? What design goals were explicitly left off the table, or deferred to a future verson, or immediately shot down? It’s better to capture multiple proposals, even if fragmentary, and let lots of people look them over and gravitate toward the best design.

Lastly, some cool things overheard:

“Relational databases? We call those ‘legacy’.”

“The socially-accepted schema is fairly consistent.”

“It’s just a map, it’s not the territory.”

-m

At the same time, I’m getting hounded by recruiters–five so far just this week.

So let me put these two forces against each other and see if they cancel out. To any former Yahoos: get in touch with me and I’ll do what I can to hook you up with a cool opportunity. This offer is good for June and July–after that I can’t reasonably say I’ll have time for matchmaking. Send me your CV via email and I’ll get started. No promises on results, but I’ll do what I can. :-)

-m

that one would be able to ask a computer any factual question, and have it compute the answer.

Which has proved to be quite distant from reality. Instead

But armed with Mathematica and NKS [A New Kind of Science] I realized there’s another way: explicitly implement methods and models, as algorithms, and explicitly curate all data so that it is immediately computable.

It’s not easy to do this. Every different kind of method and model—and data—has its own special features and character. But with a mixture of Mathematica and NKS automation, and a lot of human experts, I’m happy to say that we’ve gotten a very long way.

I’m still a SearchMonkey guy at heart, so I wonder how much Wofram’s team is familiar with existing Semantic Web research and practice–because at a high level this seems very much like RDF with suitable queries thereupon. If that’s a good characterization, that’s A Good Thing, since practical application has been one of SemWeb’s weak spots.

-m

But why can’t I get Yahoo! Go for iPhone? I’m gobsmacked that such a strategic app isn’t available this far into the game. Yahoo! Go was first announced in 2006. Then 2007. Then 2008. Maybe 2009 will be the year. -m

There’s still a place for a simpler syntactic approach to embedding RDF in HTML, as evidenced by projects like Yahoo! SearchMonkey. And eRDF is still the only game in town when it comes to annotating RDF within HTML-without-the-X.

One thing the RDFa folks did was define src as a subject-bearing node, rather than an object. At first I didn’t like this inversion, but the more I worked with it, the more it made sense. When you have an image, which can’t have children in (X)HTML, it’s very often useful to use the src URL as the subject, with a predicate of perhaps cc:license.

So I propose one single change to eRDF 1.1. Well, actually several changes, since one thing leads to another. The first is to specify that you are using a different version of eRDF. A new profile string of:

"http://purl.org/NET/erdf11/profile"

The next is changing the meaning of a src value to be a subject, not an object. Perhaps swapping the subject and object. Many existing uses of eRDF involving src already involve properties with readily available inverses. For example:

<!-- eRDF 1.0 -->
<img class="foaf.depiction" src="http://example.org/picture" />

<!-- eRDF 1.1 -->
<img src="http://example.org/picture" class="foaf.depicts" />

With the inherent limitations of existing syntax, the use case of having a full image URL and a license URL won’t happen. But XHTML2 as well as a HTML5 proposal suggest that adding href to many attributes might come to pass. In which case this possibility opens:

<img src="http://example.org/picture" class="cc.license"
href="http://creativecommons.org/licenses/by/2.0/" />

Comments? -m

Does your site use RDFa yet? -m

Because they need Yahoo. They need search share–the deal with Google only puts on more pressure. But they also need a non-schizophrenic brand under which to put all their audience attractors. In short, I’d say MSFT has been terrible at tactics (and non-intimidation-based negotiating), and YHOO has been mediocre at strategy and terrible at execution. Maybe they are meant for each other…

Prediction: by the end of the year 1) some kind of deal happens, and 2) Yang is out as CEO. $28.

Disclosure: I still hold long YHOO shares

Disclosure: The irony of this post is not lost on me

-m

I’ve free of such influence for six weeks now. What Yahoo! services do I still use? Which ones not so much?

Yahoo Answers: not so much. Even the 1 point-per-day for visiting doesn’t entice me. If I had a burning question that would be a good fit for a community answer, I’d go back.

Yahoo Mail: all the time. I used Yahoo mail long before I worked there, and I’ll be using it long after.

Yahoo News: almost daily. Still a good collection of global, national, and local news.

My Yahoo & Finance: multiple times daily. I’ve peeked at iGoogle, but the Y is too comfy, and the competion isn’t easy enough to get comfortable with. But often the page takes up to 30 seconds to load. If that doesn’t improve, I’ll leave.

Yahoo Search: still my default. But only because of tweaks I put in place with SearchMonkey. The baseline quality of results is right on par with Google. I still recommend Y search to friends and family.

Yahoo Maps: rarely used. Google maps is just better, particularly street view.

Yahoo 360: Abandoned. Tons of site bugs, no fixes on the horizon. In fact, they’ve announced shuttering of the service, to be replaced with some unspecified alternative. But who knows when that will happen? So the Meadblog is on hold until further notice. I’ll still check once in a while for postings from friends and family.

Yahoo front page: Still use it to check whether wireless is working. Most often with ping, not HTTP though. :-)

What Yahoo services do you still use? Comment below. -m

Update: a few more inspired by the comments.

Delicious: still use, mainly through the browser extension.

Flickr: still use, but I’m not much of a photos guy. I’ll be using it again shortly to upload screenshots for a blog-post tutorial I’m writing.

So Jerry (or whoever is on deck as CEO), you should probably look into this mobile thing and see what’s up with leadership there and whether anything is salvageable… -m

For example, to see every hAtom-bearing page that mentions ‘dubinko’ use the query [searchmonkeyid:com.yahoo.uf.hatom dubinko]. Works similarly for hCard, hCalendar, hReview, and XFN. I’m sure more are coming soon too. -m