Tuesday, January 18, 2005

Planning for Tomorrow's Web

Tomorrow's Semantic Web: Understanding What We Mean "If you're going to trust the answers from something, you've got to be able to understand why you should trust them. The web is also moving to being explainable, more capable of filtering, and more capable of executing services."

"Once I have just simple ontologies, so just taxonomies, just the subclass-superclass relationship, I can start to empower a lot of applications in ways that I couldn't before. I get to have the benefit of a shared vocabulary. It benefits things like search engines because you see more usage of the same terms, authors use the controlled vocabulary, users get encouraged to use a controlled vocabulary, databases leverage it, programs don't have to do translation between the terms—so we're all speaking the same language."

"These days if I'm doing an application that is looking to get into those more complicated ontologies at some point down the road—possibly not today but in a year where I want to exploit that information—I typically aim to encode in OWL, the ontology web language, because it sits on top of, it extends the fairly well used vocabularies of XML and RDF, and RDFS, to have more expressive power. And it gives me the ability to encode terms in a precise language where I can count on the semantics."
Post a Comment