July 3, 2009

Subj3ct.com Beta 2 Released

We have just refreshed Subj3ct.com with Beta 2. We have tried to incorporate the feedback we have had as well as adding some things we think are useful. The highlights are:

* Support for OpenID for signing in
* Ability to create and publish identifiers and indicator pages from with the Subj3ct portal
* A changes feed that can be used to aggregate whats happening in Subj3ct
* Embeddable snippets (RDFa, SKOS etc) on each subject record page that can be used to tag a page with a given subject.
* The start of a user community that currently supports user search
* Ability to process SKOS feeds
* Ability to register feeds without creating an account (this allows users to reference existing SKOS vocabularies that they don't own)
* Updated statistics on the home page and quick links to most recent subjects and some random subjects.
* Bug fixes and performance improvements

We now have 3180 identifiers in 23 feeds and we and others are adding to this all the time.

More stuff to come...

June 29, 2009

A small useful ontology and what it tells us about Web3

Implementing Topic Maps solutions for a variety of people we see many ontologies (information models, domain models, schemas) being used. Out of this we have tried to understand how different approaches are useful for different kinds of customers.

One approach, where the customer is a focused specialist group or small company/department who 'know their stuff' really benefit from having a rich ontology as it says more about what they are doing. These are also the people who want to encode knowledge as something explicit and then use that knowledge as part of the information displayed to users of the system.

At the other end of the scale large organisations tend intially to benefit from a less is more approach. This is typically becuase getting 'political' agreement on what the business does and where the focus should be is much harder at the large scale.

It is this second example I want to pick up on here. The most basic, useful ontology that we see in use consists of just three types; Content, Concept and Person. Concepts can be connected to other concepts as 'broader/narrower' and also 'as related'. Content 'is about' concepts, and 'related to' person. Person can be connected to concepts in a few ways that are often tweaked for the domain. e.g. expert in.

This ontology is not the ultimate base model for explaining everything, but more about being able to usefully cover enough about a domain to promote the things that are important in an information management system. (Things such as faceted search, concept centric, bi-directional linking, multiple names and identifiers. All the findability niceness of Topic Maps.)

This model works well because it has recognised that people and content are two fundamental pillars of the way we work with information. Making the users/ people part of the model is critical to be able to deliver targeted contextualised content. This is the kind of content and knowledge people want to see and have access to.

So now we are moving Topic Maps concepts and approaches from the enterprise to the web and in particular the web3 context how can these ontology lessons inform us about how web3 works and the impact it will have?

Well, the biggest observation is that while web1.0 provides content, web2.0 provides people and content there is an obvious gap and therefor need for the third pillar which is concepts. Having concepts on the web will enable people to group and organise the content around the subjects that are important to them.

Having concepts on the web will provide binding points around which content can be produced and grouped, it will facilitate social networking groups to be organised around concepts. Overall having concepts on the web will provide a new and vast dimension to the experience of using this content management system we call the web.

May 14, 2009

subj3ct.com Released

Today we are proud to have launched Subj3ct.

Subj3ct is a Subject Identity Resolution Service, it provides both a portal for humans to use and an API for developers and applications. We store subject identifiers, equivalent identifiers and also links to web resources that contain structured or unstructured information about a subject.

The resolution service is intended to provide services to:
a) people looking to re-use common identifiers in order to improve interchange
b) application developers who are building the next generation of web applications, where dynamically finding and merging linked data is key

We are starting out in gathering mode, trying to get collections of identifiers registered so that we have a useful set of subjects.

Once we have this we will be creating new features and writing more on how to use the service in building Web 3.0 applications.

In the meantime, we would really appreciate it if people can register subject feeds and just generally provide feedback on the portal and API.

Everything can be found at https://subj3ct.com

Finally, thanks for all the support and encouragement we have received in putting this exciting service together.

The Subj3ct Team