From: naudts g. <nau...@ya...> - 2004-10-05 11:31:12
|
Hallo, I suppose Jos means to encode as: :1 a RDF:List; RDF:first :2; RDF:rest :1a. :1a RDF:first :3; RDF:rest :1b. :1b RDF:first :4; RDF:rest RDF:nil. However then the nodes :1, :2, :1a, :3, :1b, :4 cannot oocur in any other triple as list elements; suppose you read a rule from another site: :1 a RDF:List; RDF:first :2; RDF:rest :1a. :1a RDF:first :3; RDF:rest RDF:nil. you obtain a clear inconsistency. Greetings, Guido. --- jos...@ag... wrote: > Hi, Antonio > > I've looked to your encoding of > eulermoz/tests/n3/example.n3 > in RDF/XML (using eulermoz/tests/n3/index.xul) and > when one > transforms that back into N3 (which is more readable > to me :)) > one gets > > > @prefix : <urn:clerk:anon#> . > @prefix NS3: > <http://www.agfa.com/w3c/euler/authen.axiom#> . > @prefix NS4: > <http://www.w3.org/2000/10/swap/log#> . > @prefix RDF: > <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . > > <INSTITUTION> NS3:subscribed <MAILINGLIST>; > NS3:w3cmember <http://www.w3.org> . > > <PERSON> NS3:authenticated <MAILINGLIST>; > NS3:member <INSTITUTION> . > > <http://www.agfa.com> NS3:subscribed > <mailto:w3c...@w3...>; > NS3:w3cmember <http://www.w3.org> . > > <mailto:jos...@ag...> NS3:member > <http://www.agfa.com> . > > :1 a RDF:Seq; > RDF:_1 :2; > RDF:_2 :3; > RDF:_3 :4; > NS4:implies :5 . > > :2 a RDF:Statement; > RDF:object <INSTITUTION>; > RDF:predicate NS3:member; > RDF:subject <PERSON> . > > :3 a RDF:Statement; > RDF:object <http://www.w3.org>; > RDF:predicate NS3:w3cmember; > RDF:subject <INSTITUTION> . > > :4 a RDF:Statement; > RDF:object <MAILINGLIST>; > RDF:predicate NS3:subscribed; > RDF:subject <INSTITUTION> . > > :5 a RDF:Seq; > RDF:_1 :6 . > > :6 a RDF:Statement; > RDF:object <MAILINGLIST>; > RDF:predicate NS3:authenticated; > RDF:subject <PERSON> . > > :Rule0 a RDF:Seq; > RDF:_1 :1; > RDF:_2 :5; > NS4:forAll <INSTITUTION>, > <MAILINGLIST>, > <PERSON> . > > > and this is indeed an RDF graph. > The trouble however is that this entails for > instance something like > > > @prefix : <urn:clerk:anon#> . > @prefix NS3: > <http://www.agfa.com/w3c/euler/authen.axiom#> . > @prefix NS4: > <http://www.w3.org/2000/10/swap/log#> . > @prefix RDF: > <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . > > <INSTITUTION> NS3:subscribed <MAILINGLIST>; > NS3:w3cmember <http://www.w3.org> . > > <PERSON> NS3:authenticated <MAILINGLIST>; > NS3:member <INSTITUTION> . > > <http://www.agfa.com> NS3:subscribed > <mailto:w3c...@w3...>; > NS3:w3cmember <http://www.w3.org> . > > <mailto:jos...@ag...> NS3:member > <http://www.agfa.com> . > > :1 a RDF:Seq; > RDF:_1 :2; > RDF:_3 :4; > NS4:implies :5 . > > :2 a RDF:Statement; > RDF:object <INSTITUTION>; > RDF:predicate NS3:member; > RDF:subject <PERSON> . > > :4 a RDF:Statement; > RDF:object <MAILINGLIST>; > RDF:predicate NS3:subscribed; > RDF:subject <INSTITUTION> . > > :5 a RDF:Seq; > RDF:_1 :6 . > > :6 a RDF:Statement; > RDF:object <MAILINGLIST>; > RDF:predicate NS3:authenticated; > RDF:subject <PERSON> . > > :Rule0 a RDF:Seq; > RDF:_1 :1; > RDF:_2 :5; > NS4:forAll <INSTITUTION>, > <MAILINGLIST>, > <PERSON> . > > > which is an encoding of > > > @prefix log: <http://www.w3.org/2000/10/swap/log#>. > @prefix rdfs: > <http://www.w3.org/2000/01/rdf-schema#>. > @prefix rdf: > <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. > @prefix : > <http://www.agfa.com/w3c/euler/authen.axiom#>. > > <mailto:jos...@ag...> :member > <http://www.agfa.com>. > <http://www.agfa.com> :w3cmember > <http://www.w3.org>. > <http://www.agfa.com> :subscribed > <mailto:w3c...@w3...>. > > {?PERSON :member ?INSTITUTION. > ?INSTITUTION :subscribed ?MAILINGLIST} > => > {?PERSON :authenticated ?MAILINGLIST}. > > > which can be false (true premis and false > conclusion) and so > your encoding is inconsistent (one can derive a > falsehood). > > The only valid encoding I see right now is with RDF > lists > (as one can always make sure that RDF lists are > valid). > > Another point is that a premis and conclusion are > sets > of triples, but one could use eg:Set (subclass of > rdf:List). > > > kind regards, > jos > > -- > Jos De Roo, AGFA http://www.agfa.com/w3c/jdroo/ > > PS it should be the case that the euler path > inferencing is implemented in > http://cvs.sourceforge.net/viewcvs.py/eulermoz/eulermoz/tests/prolog/prolog.js?rev=1.5&view=auto > > > > > > "antonio.lopez" <ant...@pt...> > Sent by: > eul...@li... > 04/10/2004 14:01 > Please respond to antonio.lopez > > > To: Jan Grant <fr...@io...>, > eulermoz developers > <eul...@li...> > cc: (bcc: Jos > De_Roo/AMDUS/MOR/Agfa-NV/BE/BAYER) > Subject: [Eulermoz-developers] ¿Can > you give us a hand? > > > Hello all. > > We please to annouce N3 scanner a parser are > commeted at sourceforge CVS > repository. > === message truncated === __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail |