|
Having had my own personal epiphany regarding RDF late last year I now see no reason not to use RDF as and where appropriate. The key to that statement is 'as and where appropriate'. While working for large corporate customers, any data model that contains information that could/should be shared within the business or sold-on to other companies is an ideal candidate for RDF.
The extensive activity in areas such as Dubline Core, FOAF and the like are just what I need because they provide me with useful, off-the-peg, vocabularies that allow me to get on with my job and add value to the work I do for my customers.
However, the bain of my life - how I am actually allowed to do my job would benifit greatly from the ability to capture data in a sematically useful way. All those lost notes, annotations, links and info about how, why and where things went wrong and how we fixed them. Being able to query that kind of knowledge repository would really make a difference to me and is a pet project of mine that is yet to take flight.
If you want to get into the Semantic Web and feel the benifit, deploy it internally within your business, use the tools that are avaiable now to improve your processes and pass the knowledge and experience on to your customers by building them semantically aware solutions.
|