danbri_dna: There are 330+ tests, a source rdf file with context node urn:actor:Myers-Mike.
GNUWookie: Contains """"{ :Dog rdfs:subClassOf :Animal . :x a [ daml:complimentOf :Animal ] } log:implies { { :x a :Dog } a log:Falsehood } .""""
GNUWookie: I dont get how this daml:complimentOf is being implemented
GNUWookie: The CWM does not have any complementOf handling built in
GNUWookie: (as far as I know)
GNUWookie: This mail also contains a possible implementation
GNUWookie: {compliment =~ complement.} log:proof: [ bad spellers of the world : UNTIE ! }
GNUWookie: """" " <http://www.daml.org/2001/03/daml+oil.daml#complementOf> a >rdf:Property; for complementOf(X, Y) read: X is the complement of Y; if>something is in Y,> then it's not in X, and vice versa.> cf OIL NOT"""
GNUWookie: This mail Here from Jos describes a possible implementation in OwlRules
GNUWookie: """"owl:complementOf a rdf:Property,owl:SymmetricProperty;rdfs:domain rdfs:Class;rdfs:range rdfs:Class .""""
GNUWookie: So we need to define the SymmetricProperty First """" {:p a owl:SymmetricProperty .:s :p :o .} log:implies {:o :p :s . } .""""
GNUWookie: Ahh this ontAx looks like what i need.
GNUWookie: I think that this must be a common problem. Maybe cwm needs a --filterout=foo.n3 option that will emit all the statements that dont match that filter.
GNUWookie: I dont get how this daml:complimentOf is being implemented
GNUWookie: The CWM does not have any complementOf handling built in
GNUWookie: (as far as I know)
GNUWookie: This mail also contains a possible implementation
GNUWookie: {compliment =~ complement.} log:proof: [ bad spellers of the world : UNTIE ! }
GNUWookie: """" " <http://www.daml.org/2001/03/daml+oil.daml#complementOf> a >rdf:Property; for complementOf(X, Y) read: X is the complement of Y; if>something is in Y,> then it's not in X, and vice versa.> cf OIL NOT"""
GNUWookie: This mail Here from Jos describes a possible implementation in OwlRules
GNUWookie: """"owl:complementOf a rdf:Property,owl:SymmetricProperty;rdfs:domain rdfs:Class;rdfs:range rdfs:Class .""""
GNUWookie: So we need to define the SymmetricProperty First """" {:p a owl:SymmetricProperty .:s :p :o .} log:implies {:o :p :s . } .""""
GNUWookie: Ahh this ontAx looks like what i need.
GNUWookie: I think that this must be a common problem. Maybe cwm needs a --filterout=foo.n3 option that will emit all the statements that dont match that filter.
dajobe: far more than you ever want to know about RDF/XML and syntaxes for RDF
dajobe: rejected by the International "semantic web" conference, the fools! :)
dajobe: rejected by the International "semantic web" conference, the fools! :)
GNUWookie: ""I do understand the concerns of the opponents of introspection however, if you apply introspection to an existing language then all the programs written in that language become theoretically a target for a GPL circumvention attack. This is true and I can understand that people don't like the thought that their programs will be introspectable without their permission.""
GNUWookie: I think that being able to iterate over the structure of the program is a freedom provided by logic langages. As soon as you have an rdf representation of your program, then it is open to people making proofs over it. These proofs are not always viewable as derivitive works of the compiler that produced the rdf or the input program that was introspected. As soon as you release your code onto the net under a F/OSS language it is fair to app
GNUWookie: I dont think that the GPL allows any restriction on how the programs code is processed. That is a foreign idea to people who live off of controlling others with licenses and agreements. They should not publish their code under the GPL or F/OSS license if they have a problem with advances in compiler technology.
GNUWookie: Eventually the compilers will become good as to obsolete all other compilers. The semantic web promises to deliver the tools to process the huge amounts of data generated by the introspection process. These inference engines coupled with mailing lists and bugreports, cvs logs and other meta data extracted from the development tools will provide an great new use case for the semantic web.
GNUWookie: People are always trying to make tools to somehow extract semantics out of the existing webpages. I think this is like the proverbial squeezing water out of stones. By using the introspector you are flooded with such large amounts of input about the world around you, encoded into facts in c programs that you are much more able to use the tools of the semantic web.
GNUWookie: That is why I think the introspector is important to the semantic web researchers.It brings the future much closer by finally providing a almost infinite well of metadata to test on, and a sizable range of discourse.
GNUWookie: Each program is describing the terms of some field of discourse, in the names of the functions and and data structures you have primitive ontologies. In the usage of these structure you can find the relationships beween these labels.
GNUWookie: When all of this is cross referenced against each other, and plugged into the wordnet, you will have an enormous pool of valid and tested ontologies, with millions of instances to test your algorithms on.
GNUWookie: I think that being able to iterate over the structure of the program is a freedom provided by logic langages. As soon as you have an rdf representation of your program, then it is open to people making proofs over it. These proofs are not always viewable as derivitive works of the compiler that produced the rdf or the input program that was introspected. As soon as you release your code onto the net under a F/OSS language it is fair to app
GNUWookie: I dont think that the GPL allows any restriction on how the programs code is processed. That is a foreign idea to people who live off of controlling others with licenses and agreements. They should not publish their code under the GPL or F/OSS license if they have a problem with advances in compiler technology.
GNUWookie: Eventually the compilers will become good as to obsolete all other compilers. The semantic web promises to deliver the tools to process the huge amounts of data generated by the introspection process. These inference engines coupled with mailing lists and bugreports, cvs logs and other meta data extracted from the development tools will provide an great new use case for the semantic web.
GNUWookie: People are always trying to make tools to somehow extract semantics out of the existing webpages. I think this is like the proverbial squeezing water out of stones. By using the introspector you are flooded with such large amounts of input about the world around you, encoded into facts in c programs that you are much more able to use the tools of the semantic web.
GNUWookie: That is why I think the introspector is important to the semantic web researchers.It brings the future much closer by finally providing a almost infinite well of metadata to test on, and a sizable range of discourse.
GNUWookie: Each program is describing the terms of some field of discourse, in the names of the functions and and data structures you have primitive ontologies. In the usage of these structure you can find the relationships beween these labels.
GNUWookie: When all of this is cross referenced against each other, and plugged into the wordnet, you will have an enormous pool of valid and tested ontologies, with millions of instances to test your algorithms on.
jql: The module allows RDF statements to be made with very simple Perl expressions, without having to worry about the RDF engine running in the background
jql: I'll be putting it on CPAN for download
jql: The overview includes a quick sample of how the Dublin Core would be stated within Perl
jql: I'll be putting it on CPAN for download
jql: The overview includes a quick sample of how the Dublin Core would be stated within Perl