Archived from groups: comp.ai.edu,comp.ai.games,comp.ai.nat-lang,comp.ai.philosophy,comp.lang.prolog (
More info?)
Eray Ozkural exa wrote:
> patty <pattyNO@SPAMicyberspace.net> wrote in message news:<ZMWDc.122273$eu.2393@attbi_s02>...
>
>>Eray Ozkural exa wrote:
>>
>>>patty <pattyNO@SPAMicyberspace.net> wrote in message news:<%cyDc.103831$Hg2.64452@attbi_s04>...
>>>
>>>
>>>>Eray Ozkural exa wrote:
>>>>
>>>>
>>>>
>>>>>I think you would also be interested in knowledge representation,
>>>>>perhaps as applied to Semantic Web; that's about the only big area I
>>>>>can think of where people want to deploy those big ontologies. (Half
>>>>>seriously, of course, computational ontology is now a basic tool in
>>>>>scientific computing) I can't tell how much AI Semantic Web really is,
>>>>>though.
>>>>>
>>>>
>>>>Yeah there is a lot of logic programming going on now with the Semantic
>>>>Web - see Tim Berners Lee's CWM [1]. One need is fuzzy matching of RDF
>>>>Bnodes (unidentified descriptions) ... i think that is an area that is
>>>>ripe for AI ideas ... and there could be very tangible benefits to
>>>>getting it right.
>>>>
>>>>[1] <http://infomesh.net/2001/cwm/>
>>>
>>>
>>>Ouch. Python! All that XML junk, it's gonna be slow....
>>
>>Yeah it's slow, but not because of python or all that XML junk. It's a
>>demonstration of something (mostly the utility of the N3 language and
>>making inferences) and were Tim to figure out what it should be doing,
>>it could well be speeded up. It *is* (well probably was) a fast way to
>>demonstrate and play with some concepts ... to see if they could be made
>>to work. I cited it here only as an instance of logic programming
>>happening on the Semantic Web. There are other, perhaps more practical,
>>examples, but those are not nearly as accessible.
>
>
> I understand that it's a demonstration. I like Python as a scripting
> language, and I think it's truly much better than visual basic,
> tcl/tk, or perl. It has functional constructs, high level data
> structures, etc. And its libraries I can only applaud; it's a
> beautiful programming environment. Actually, I recommend python to
> those just beginning to program, I think it's a balanced language.
> However, I heard that for big projects it doesn't have a shining
> performance... That was the gist of my remark. Likewise for XML. Even
> in the fastest C++ processors, XML causes a lot of overhead. In KDE
> project, XML UI framework shares a big part of the guilt in
> application startup time.
>
Well i would not disagree with most of that. Strangely enough Tim's CWM
was a rebellion against XML giving us the streamlined N3 language. But
one wonders, as did Pat Hayes, why one does not just use KIF.
Incidentally the Semantic Web does not rest on XML, it rests on triples.
You can, if you are bold enough, use whatever surface language you want.
>
>>The basic question, as i see it, is how do you even do reasoning with
>>the monotonic binary logic of OWL and RDF in the wild west of the
>>democratized web. Are there useful inferences to be computed? If so
>>where are the tools to get the job done?
>
>
> My idea is that, humans are not likely to use Semantic Web tools at
> all. I imagine that first we write some agents that compute the
> semantics and then perhaps some useful inferences can be drawn... I
> think that the "semantics" is not really contained in these ontology
> languages, you need a programming language, not just some forward
> chaining code.
>
Well the semantics of a language are outside of the language. The
semantics is manifested by the game of the usage of the language. I
would think that would apply to programming languages as well.
Where it comes to the semantic web, i've always felt that the graph
*was* the semantics but apparently that idea didn't get legs in the W3C
working group. When you say "some agents that compute the semantics",
if the semantics are the graph, than that works because certainly an
agent can compute the graph. So i will go out on a limb and say "if the
semantic web works, it will be because the semantics are the graph",
Pat's lengthy tomb notwithstanding. Of course the trouble with that is
the graph is *not* supposed to be context sensitive - that is because of
its grounding in URIs which are not supposed to be context sensitive ...
.... look don't get me started ... ok .. ok ...
patty