A Taxonomy of Social Networking Data
At the Internet Governance Forum in Sharm El Sheikh this week, there was a conversation on social networking data. Someone made the point that there are several different types of data, and it would be useful to separate them. This is my taxonomy of social networking data.
from Schneier on Security: A Taxonomy of Social Networking Data.
Follow the link for a useful breakdown of data in any community site or service.
One of my collegaues called the other day and asked if we still relied on the distinction between intensional and extensional sets (really intensionally and extensionally defined sets). Yes, even more so now.
from Intensional and Extensional Sets.
If you don’t know the difference (I didn’t) then it’s worth reading.
The problem from my standpoint is that MODS has some really odd, library-specific, design choices that I don’t think map very well to the wider world. A central concept like mods:name, with mods:role as a child of that, really makes no sense, and conflicts with more common modeling you see in DC, FRBR ,etc.
It’s semantics are also really loose.
So you have to ask yourself, just how linked could a MODS view in RDF really be?
from Conversation with Bruce D’Arcus on Motivation for MODS Ontology.
Are you writing multi-tenant software? Are you using RDF at all? Do you want to keep track of your tenants?
You might want to comment on the first draft of the new Multi-Tenant Configuration Schema.
This schema attempts to describe a simple set of concepts and relationships about tenants within a multi-tenant software system. It avoids anything that would constitute application configuration, but will happily co-exist with classes and properties to do that. The documentation is sparse currently, awaiting questions and comment so that I can expand on areas that require further explanation. Comment here, or email me.
AIISO, AIISO-Roles and Participation, ontologies I developed with others at Talis and at VoCamp are picked up by JISC’s Building the Research Information Infrastructure (BRII) : JISC.
Working on our current project, Nad and I have been modelling resource lists – think course reading lists, but containing more than just reading material. A list is simply a collection of resources grouped into sections and annotated by the academic to give students guidance when using the list.
A resource list can take much more than just books. We’re using Bibliontology to model the resources, so more or less anything can be accurately described. We’ve requested a couple of additions and are still debating those.
The structure of the list is described using a new ontology which we’ve published on vocab.org, but with a purl.org base URI. The ontology lives here: http://purl.org/vocab/resourcelist/schema
It also works just fine with the AIISO ontology we published a few days ago – so you can say which parts of your institution are using which lists.