I take the point about the ability to set things up quickly, but this just points to the fact that we have some way to go on a number of strands. But we all know we on the right path. I would say that focusing in on some of the huge range of potential applications that you couldn't do with a relational database will help move things along more.
On ontology here is my experience. You need a solid ontology that describes your domain at precisely the right level to represent domain knowledge to establish key relationships but which supports specialisation below this level. This level is just at the point above which the domain varies. However after going down the specialisation route we have found a more accessible and portable approach. We have used an ontology that does precisely the above but used it to create a set of ready made constructs for key domain concepts that are uncontentious. A particular concept may have a number of alternative constructs from which an organisation can select as appropriate. We then avoid the need to specialise the constructs using sub classes and sub properties and instead provide a mechanism for plugging in local vocabularies. This transfers the issue of co-referencing ontology extensions to co-referencing vocabularies. This is far more accessible for two reasons. Firstly, the contextualisation of the non-specialised elements provide enough knowledge representation to perform the co-referencing. Secondly, there are many vocabulary co-referencing initiatives that are becoming more mature and accessible. The plugin approach is supported by typing whole event constructs and reification of key properties with local terminology, people and place authorities, but also terminology unique to the organisation (Institutional context). For example, the production of something may have a generalised property of "carried out by". This could be specialised in a large number of ways. Instead we can look at the local specialisations and use them as a vocabulary to either type the full event or to reify the property itself. E.g. "designed by". This process avoids a whole range of issues and also has the potential to be built into accessible implementation tools useful for organisations without technical resources. It means that we can start producing the applications that we can't do with relational databases and which operate across many different datasets robustly. How does this sound? Dominic Sent from Yahoo! Mail on Android
