Thursday, March 04, 2004

SWIG Summary

Semantic Web Interest Group "Just about every tool in the Adobe arsenal is now able to embed RDF into their primary artifacts. It's ironic, of course, that a core web technology, RDF, still isn't really embeddable into the core web data format, HTML; but it can easily be embedded into Adobe artifacts...there are two reasons why Adobe customers want metadata embedded in digital artifacts. The first, obvious, reason is to support automated workflow. If you've ever worked in a graphics shop or design house, you know that workflow management is absolutely critical to profitability. The second, less obvious, reason is intelligent syndication. What a real-time OWL-powered pub-sub application needs, of course, is rich RDF metadata attached or linked to artifacts of the Web: images, video and sound files, as well as XHTML documents."

"...we're at the point now where the basic knoweldge representational mechanisms -- RDF and OWL -- are formalized; where mechanisms for the creation of RDF and OWL are coming online and into place; and where there is increasing awareness of and interest in the SW. What we need, then, is the "uniform means of interaction" for the SW that HTTP provides for the Web. What we need is a reasonable specification that we can give both to RDF tool makers and to to Python and Perl and Java and C# and Ruby programmers; and we need to say to them, "implement this specification in your tool or your language; then your users and programmers will be able to uniformly access resource representations on the Semantic Web". That will be a happy day, indeed."

Also talks about how Boeing are using OWL in the battlefield.
Post a Comment