Wednesday, June 11, 2008

Tired

I'm really tired! I'm taking two classes during the month of June so I can graduate in August. I come home from work and go straight to the computer and start on school work. I'm taking 725 Knowledge Management and 753 Reference Seminar. I like both classes, especially the reference seminar. Right now, we're using Second Life Virtual Library that our college has set up. It's very cool and a bit fun if I do say so myself. This class is why I started blogging. We are supposed to be up to date on web 2.0. I hate to admit it, but I'm not as up to date as I want to be. I'm trying really hard though!!!

Another thing we're discussing in 726 are Topic Maps. This website was created by Steve Pepper from Ontopia. Steve Pepper and Lars Garshol, from what I understand, are the Topic Map gurus. I have to say though, "I don't get it." Maybe I'm overthinking it, but I dunno...We're working on a project for an SLM topic map and I have no clue where to begin. If there is anyone out there who could give me some insight, I would be sooooo appreciative.

Anyway, I started this blog wanting to talk about how tired I am and look where I wind up. Oh well, maybe I'm gonna be a real liberrian afterall.

2 comments:

SystemPoke said...

In its simplest form, Topic Maps is a standard for defining and exchanging data models. A data model is basically objects and relationships between them, creating a small "map" (hence the "map" in Topic Maps) of a nugget of knowledge.

I've got another intro at http://shelter.nu/art-007.html which might help you a bit further. It's not actually complex once you step above a certain threshold. We like to say that there's a paradigm shift involved in how you think about information systems, in that we elevate the traditional data model of relational databases, lift it out of the hardcoded base, and as such force every Topic Mapped system to accept flexibilty at the core.

In other words, Topic Maps application are by their very nature designed for change, exchange, models and complexity, whereas others hardcode the application into their databases and programming languages.

It is as simple as a strong focus on relationships between things, as opposed to the normal focus of the thing itself. Hope this helps a little.

Jana said...

Thanks so much Alex!