Friday, June 15, 2007

What We Need Is Some Uniform Way to Identify a Resource...

Stephen is right that from the point of view of web architecture, giving each session at NECC an opaque tag (e.g., n07s643) is completely fucked:

The way it should have been done in the first place: each event has an associated URL. Blog posts, etc., can link to (or 'refer to') that URL. In the metadata (ie., the RSS) for an event URL (which now has the same status as a blog post, right?) you can add some event data ('start','finish','location') and indicate event structure ('parent').

1 comment:

Vicki Davis @coolcatteacher said...

Don't you think that although the tags are confusing, that having them is better than having nothing. Your proposal may make sense to you but not to me. Theirs obviously makes sense to them, but too many indian and no chief means no standard and no tag aggregation. I'm finding the aggregation helpful.

I hope they do simplify it next year-- of course we have to start somewhere.