Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One major problem RDF has is that people hate anything with namespaces. It's a "freedom is slavery" kind of thing. People will accept it grudgingly if Google says it will help their search rankings or if you absolutely have to deal with them to code Java but 80% of people will automatically avoid anything if it has namespaces. (See namespaces in XML)

Another problem is that it's always ignored the basic requirements of most applications like:

1. Getting the list of authors in a publication as refernces to authority records in the right order (Dublin Core makes the 1970 MARC standard look like something from the Starship Enterprise)

2. Updating a data record reliably and transactionally

3. Efficiently unioning graphs for inference so you can combine a domain database with a few database records relevant to a problem + a schema easily

4. Inference involving arithemtic (Godel warned you about first-order logic plus arithmetic but for boring fields like finance, business, logistics that is the lingua franca, OWL comes across as too heavyweight but completely deficient at the same time and nobody wants to talk about it)

things like that. Try to build an application and you have to invent a lot of that stuff. You have the tools to do it and it's not that hard if you understand the math inside and out but if you don't oh boy.

If RDF got a few more features it would catch up with where JSON-based tools like

https://www.couchbase.com/products/n1ql/

were 10 years ago.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: