Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » EODM - POC to extract relationships
EODM - POC to extract relationships [message #61088] Mon, 13 November 2006 15:07 Go to next message
Sai [Srinivasan Sairam] is currently offline Sai [Srinivasan Sairam]Friend
Messages: 36
Registered: July 2009
Member
Hello,
I am evaluating / doing a Proof Of Concept for extracting relationships from
triples. I am looking for some (step by step) tutorial .... is there any
tutorial that walks through / explains the OWL / RDF reasoner ? I looked in
the samples ... but thats bit "cryptic" :-(

This is what I am trying to achieve : I want to give a bunch of triples to
the (OWL or RDF) reasoner : something like
{V1, V3}, {V5, V7}, {V9, V11}
{V1, V2}, {V5, V4}, {V9, V6}

I want the reasoner to tell me that there exists relationship between : (V2,
V3) and (V4, V7) and (V6, V11)

Is there any sample that demonstrates something similar to this ...

Any help would be very much appreciated. ...

Thanks

Sai

================================

Sai (Srinivasan Sairamachandran)

GXS http://www.gxs.com

Srinivasan.Sairam@gxs.com

(248)879-0691

================================
Re: EODM - POC to extract relationships [message #61112 is a reply to message #61088] Mon, 13 November 2006 15:20 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: merks.ca.ibm.com

Sai,

It would be best asked on the EODM newsgroup, which I've added to the list.


Srinivasan Sairam wrote:

>Hello,
>I am evaluating / doing a Proof Of Concept for extracting relationships from
>triples. I am looking for some (step by step) tutorial .... is there any
>tutorial that walks through / explains the OWL / RDF reasoner ? I looked in
>the samples ... but thats bit "cryptic" :-(
>
>This is what I am trying to achieve : I want to give a bunch of triples to
>the (OWL or RDF) reasoner : something like
>{V1, V3}, {V5, V7}, {V9, V11}
>{V1, V2}, {V5, V4}, {V9, V6}
>
>I want the reasoner to tell me that there exists relationship between : (V2,
>V3) and (V4, V7) and (V6, V11)
>
>Is there any sample that demonstrates something similar to this ...
>
>Any help would be very much appreciated. ...
>
>Thanks
>
>Sai
>
>================================
>
>Sai (Srinivasan Sairamachandran)
>
>GXS http://www.gxs.com
>
>Srinivasan.Sairam@gxs.com
>
>(248)879-0691
>
>================================
>
>
>
>
Re: EODM - POC to extract relationships [message #62564 is a reply to message #61088] Thu, 23 November 2006 02:46 Go to previous messageGo to next message
Yang Yang is currently offline Yang YangFriend
Messages: 10
Registered: July 2009
Junior Member
This is a multipart message in MIME format.
--=_alternative 000F37F64825722F_=
Content-Type: text/plain; charset="US-ASCII"

Sai,

The EODM RDF Reasoner is implemented by the RDF reasoning rules with graph
algorithm and the OWL Reasoner is impleneted with the structural
subsumption algorihtm which currently only support TBox reaonsing. In
fact, I am not understand the example you mentioned. Is {V1, V3} a triple?
If yes, what is the property between them?



>Hello,
>I am evaluating / doing a Proof Of Concept for extracting relationships
from
>triples. I am looking for some (step by step) tutorial .... is there any
>tutorial that walks through / explains the OWL / RDF reasoner ? I looked
in
>the samples ... but thats bit "cryptic" :-(
>
>This is what I am trying to achieve : I want to give a bunch of triples
to
>the (OWL or RDF) reasoner : something like
>{V1, V3}, {V5, V7}, {V9, V11}
>{V1, V2}, {V5, V4}, {V9, V6}
>
>I want the reasoner to tell me that there exists relationship between :
(V2,
>V3) and (V4, V7) and (V6, V11)
>
>Is there any sample that demonstrates something similar to this ...
>
>Any help would be very much appreciated. ...
>
>Thanks
>
>Sai
>
>================================
>
>Sai (Srinivasan Sairamachandran)
>
>GXS http://www.gxs.com
>
>Srinivasan.Sairam@gxs.com
>
>(248)879-0691
>
>================================
>

--=_alternative 000F37F64825722F_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Sai,</font>
<br>
<br><font size=2 face="sans-serif">The EODM RDF Reasoner is implemented
by the RDF reasoning rules with graph algorithm and the OWL Reasoner is
impleneted with the structural subsumption algorihtm which currently only
support TBox reaonsing. In fact, I am not understand the example you mentioned.
Is {V1, V3} a triple? If yes, what is the property between them? </font>
<br>
<br>
<br>
<br><tt><font size=2>&gt;Hello,<br>
&gt;I am evaluating / doing a Proof Of Concept for extracting relationships
from<br>
&gt;triples. &nbsp;I am looking for some (step by step) tutorial .... is
there any<br>
&gt;tutorial that walks through / explains the OWL / RDF reasoner ? &nbsp;I
looked in<br>
&gt;the samples ... but thats bit &quot;cryptic&quot; :-(<br>
&gt;<br>
&gt;This is what I am trying to achieve : I want to give a bunch of triples
to<br>
&gt;the (OWL or RDF) reasoner : something like<br>
&gt;{V1, V3}, {V5, V7}, {V9, V11}<br>
&gt;{V1, V2}, {V5, V4}, {V9, V6}<br>
&gt;<br>
&gt;I want the reasoner to tell me that there exists relationship between
: (V2,<br>
&gt;V3) and (V4, V7) and (V6, V11)<br>
&gt;<br>
&gt;Is there any sample that demonstrates something similar to this ...<br>
&gt;<br>
&gt;Any help would be very much appreciated. ...<br>
&gt;<br>
&gt;Thanks<br>
&gt;<br>
&gt;Sai<br>
&gt;<br>
&gt;================================<br>
&gt;<br>
&gt;Sai (Srinivasan Sairamachandran)<br>
&gt;<br>
&gt;GXS http://www.gxs.com<br>
&gt;<br>
&gt;Srinivasan.Sairam@gxs.com<br>
&gt;<br>
&gt;(248)879-0691<br>
&gt;<br>
&gt;================================<br>
&gt;</font></tt>
<br>
--=_alternative 000F37F64825722F_=--
Re: EODM - POC to extract relationships [message #63661 is a reply to message #62564] Mon, 04 December 2006 20:09 Go to previous messageGo to next message
Sai [Srinivasan Sairam] is currently offline Sai [Srinivasan Sairam]Friend
Messages: 36
Registered: July 2009
Member
This is a multi-part message in MIME format.

------=_NextPart_000_000A_01C717B6.29F1FD00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I apologize for not replying (clarifying my question) earlier ...=20
I have a Java application is being fed by to seperate (input) streams. =
During the parsing / processing of those, I will come across some =
business rules like, V1 =3D V3 from the first stream and another rule =
like, V2 =3D V1 from the second stream. From this, I want to infer that =
there is a relationship between V2 and V3. I want to know how to =
represent this in RDF XML. If my understanding is correct (from the =
primer and some reading), I can represent them as tripes as
{V1 equal V3} and {V2 equals V3}

In RDF / XML as :

<?xml version=3D"1.0"?>

<rdf:RDF=20
xmlns:rdf=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs=3D"http://www.w3.org/2000/01/rdf-schema#"
xmlns:gxs=3D"http://www.gxs.com">

<rdf:Description rdf:about=3D"http://www.gxs.com/V1">
<gxs:equals rdf:resource=3D"http://www.gxs.com/V3" />=20
</rdf:Description>

<rdf:Description rdf:about=3D"http://www.gxs.com/V2">
<gxs:equals rdf:resource=3D"http://www.gxs.com/V1" />=20
</rdf:Description>
=20
</rdf:RDF>

Is this correct? If so, how can I use the reasoner to infer that there =
is a relationship between V2 and V2

Thanks

Sai
<yangyy@cn.ibm.com> wrote in message =
news:ek321q$oti$1@utils.eclipse.org...

Sai,=20

The EODM RDF Reasoner is implemented by the RDF reasoning rules with =
graph algorithm and the OWL Reasoner is impleneted with the structural =
subsumption algorihtm which currently only support TBox reaonsing. In =
fact, I am not understand the example you mentioned. Is {V1, V3} a =
triple? If yes, what is the property between them?=20



>Hello,
>I am evaluating / doing a Proof Of Concept for extracting =
relationships from
>triples. I am looking for some (step by step) tutorial .... is there =
any
>tutorial that walks through / explains the OWL / RDF reasoner ? I =
looked in
>the samples ... but thats bit "cryptic" :-(
>
>This is what I am trying to achieve : I want to give a bunch of =
triples to
>the (OWL or RDF) reasoner : something like
>{V1, V3}, {V5, V7}, {V9, V11}
>{V1, V2}, {V5, V4}, {V9, V6}
>
>I want the reasoner to tell me that there exists relationship between =
: (V2,
>V3) and (V4, V7) and (V6, V11)
>
>Is there any sample that demonstrates something similar to this ...
>
>Any help would be very much appreciated. ...
>
>Thanks
>
>Sai
>
=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>
>Sai (Srinivasan Sairamachandran)
>
>GXS http://www.gxs.com
>
>Srinivasan.Sairam@gxs.com
>
>(248)879-0691
>
=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>=20

------=_NextPart_000_000A_01C717B6.29F1FD00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4937.800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I apologize for not replying =
(clarifying my=20
question) earlier ... </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I have a Java application is being fed =
by to=20
seperate (input) streams.&nbsp; During the parsing / processing of =
those, I will=20
come across some business rules like, V1 =3D V3 from the first stream =
and another=20
rule like, V2 =3D V1 from the second stream.&nbsp; From this, I want to =
infer that=20
there is a relationship between V2 and V3.&nbsp; I want to know how to =
represent=20
this in RDF XML.&nbsp; If my understanding is correct (from the primer =
and some=20
reading), I can represent them as tripes as</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>{V1 equal V3} and {V2 equals =
V3}</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In RDF / XML as :</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&lt;?xml =
version=3D"1.0"?&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&lt;rdf:RDF <BR>&nbsp;xmlns:rdf=3D"<A=20
href=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns">http://www.w3.org/199=
9/02/22-rdf-syntax-ns</A>#"<BR>&nbsp;xmlns:rdfs=3D"<A=20
href=3D"http://www.w3.org/2000/01/rdf-schema">http://www.w3.org/2000/01/r=
df-schema</A>#"<BR>&nbsp;xmlns:gxs=3D"<A=20
href=3D"http://www.gxs.com">http://www.gxs.com</A>"&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; &lt;rdf:Description =
rdf:about=3D"<A=20
href=3D"http://www.gxs.com/V1">http://www.gxs.com/V1</A>"&gt;<BR>&nbsp;=20
&nbsp;&lt;gxs:equals rdf:resource=3D"<A=20
href=3D"http://www.gxs.com/V3">http://www.gxs.com/V3</A>" /&gt; =
<BR>&nbsp;=20
&lt;/rdf:Description&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; &lt;rdf:Description =
rdf:about=3D"<A=20
href=3D"http://www.gxs.com/V2">http://www.gxs.com/V2</A>"&gt;<BR>&nbsp;=20
&nbsp;&lt;gxs:equals rdf:resource=3D"<A=20
href=3D"http://www.gxs.com/V1">http://www.gxs.com/V1</A>" /&gt; =
<BR>&nbsp;=20
&lt;/rdf:Description&gt;<BR>&nbsp; <BR>&lt;/rdf:RDF&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is this correct?&nbsp; If so, how can I =
use the=20
reasoner to infer that there is a relationship between V2 and =
V2</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Sai</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>&lt;<A =
href=3D"mailto:yangyy@cn.ibm.com">yangyy@cn.ibm.com</A>&gt; wrote in=20
message <A=20
=
href=3D"news:ek321q$oti$1@utils.eclipse.org">news:ek321q$oti$1@utils.ecli=
pse.org</A>...</DIV><BR><FONT=20
face=3Dsans-serif size=3D2>Sai,</FONT> <BR><BR><FONT face=3Dsans-serif =
size=3D2>The=20
EODM RDF Reasoner is implemented by the RDF reasoning rules with graph =

algorithm and the OWL Reasoner is impleneted with the structural =
subsumption=20
algorihtm which currently only support TBox reaonsing. In fact, I am =
not=20
understand the example you mentioned. Is {V1, V3} a triple? If yes, =
what is=20
the property between them? </FONT><BR><BR><BR><BR><TT><FONT=20
size=3D2>&gt;Hello,<BR>&gt;I am evaluating / doing a Proof Of Concept =
for=20
extracting relationships from<BR>&gt;triples. &nbsp;I am looking for =
some=20
(step by step) tutorial .... is there any<BR>&gt;tutorial that walks =
through /=20
explains the OWL / RDF reasoner ? &nbsp;I looked in<BR>&gt;the samples =
.... but=20
thats bit "cryptic" :-(<BR>&gt;<BR>&gt;This is what I am trying to =
achieve : I=20
want to give a bunch of triples to<BR>&gt;the (OWL or RDF) reasoner :=20
something like<BR>&gt;{V1, V3}, {V5, V7}, {V9, V11}<BR>&gt;{V1, V2}, =
{V5, V4},=20
{V9, V6}<BR>&gt;<BR>&gt;I want the reasoner to tell me that there =
exists=20
relationship between : (V2,<BR>&gt;V3) and (V4, V7) and (V6,=20
V11)<BR>&gt;<BR>&gt;Is there any sample that demonstrates something =
similar to=20
this ...<BR>&gt;<BR>&gt;Any help would be very much appreciated.=20
=
....<BR>&gt;<BR>&gt;Thanks<BR>&gt;<BR>&gt;Sai <BR>&gt;<BR>&gt;=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=
=3D=3D<BR>&gt;<BR>&gt;Sai=20
(Srinivasan Sairamachandran)<BR>&gt;<BR>&gt;GXS=20
=
http://www.gxs.com<BR>&gt;<BR>&gt;Srinivasan.Sairam@gxs.com<BR>&gt;<BR>&g=
t;(248)879-0691<BR>&gt;<BR>&gt;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>&gt; </FONT></TT=
>=20
<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000A_01C717B6.29F1FD00--
Re: EODM - POC to extract relationships [message #63913 is a reply to message #63661] Thu, 07 December 2006 02:06 Go to previous messageGo to next message
Yang Yang is currently offline Yang YangFriend
Messages: 10
Registered: July 2009
Junior Member
This is a multipart message in MIME format.
--=_alternative 000B93FE4825723D_=
Content-Type: text/plain; charset="US-ASCII"

Hi sai,

Now I understand your question. :-)

First of all, the RDF triples that you showed did represent the {V1 equal
V3}... However, a RDF/RDFS reasoner only support standard RDF/RDFS
reasoning, which are defined by RDF/RDFS semantics. You can reference
http://www.w3.org/TR/rdf-mt/ (chapter 7 shows the entailment rules that
standard RDF/RDFS reasoner use). Therefore, a standard RDF/RDFS reasoner
can not make reasoning that you want, because it does not understand the
semantic of user-defined terminology such as "gxs:equals".

To support user defined business rules, you can use a external rule-based
engine. I think that can solve your problem.





--=_alternative 000B93FE4825723D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi sai,</font>
<br>
<br><font size=2 face="sans-serif">Now I understand your question. :-)</font>
<br>
<br><font size=2 face="sans-serif">First of all, the RDF triples that you
showed did represent the {V1 equal V3}... However, a RDF/RDFS reasoner
only support standard RDF/RDFS reasoning, which are defined by RDF/RDFS
semantics. You can reference http://www.w3.org/TR/rdf-mt/ &nbsp;(chapter
7 shows the entailment rules that standard RDF/RDFS reasoner use). &nbsp;Therefore,
a standard RDF/RDFS reasoner can not make reasoning that you want, because
it does not understand the semantic of user-defined terminology such as
</font><font size=2 face="Arial">&quot;gxs:equals</font><font size=2 face="sans-serif">&quot;.
</font>
<br>
<br><font size=2 face="sans-serif">To support user defined business rules,
you can use a external rule-based engine. I think that can solve your problem.</font>
<br>
<br>
<br>
<br>
<br>
--=_alternative 000B93FE4825723D_=--
Re: EODM - POC to extract relationships [message #63939 is a reply to message #63913] Thu, 07 December 2006 04:31 Go to previous message
Sai [Srinivasan Sairam] is currently offline Sai [Srinivasan Sairam]Friend
Messages: 36
Registered: July 2009
Member
This is a multi-part message in MIME format.

------=_NextPart_000_000C_01C7198E.B1084C70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello=20
Thanks for getting back to me. It is very much appreciated. =20

However, I have few follow-up questions / clarifications :

As I mentioned earlier, from the two Java streams, I will be getting the =
rules like, V1 =3D V3 and V2 =3D V1. (In terms of business terminology, =
I could say, V1 is mapped to V3 and V2 is mapped to V1. So, we can =
infer a mapping between V3 and V2)=20

I was thinking of constructing RDF XML on the fly and use the reasoner. =
Would it be possible to "some how" represent this relationship using =
standard RDF/RDFS semantics (so that the standard RDF/RDFS reasoner =
could be used to infer relations) ? How to represent them in using =
standard RDF?
=20
You also mentioned about external rule-based engine ... can you please =
point to one of them? Is Pellet Owl Reasoner support this type of =
scenario ? (http://www.mindswap.org/2003/pellet/index.shtml)

To give a detailed (business) picture ... I am thinking of using RDF =
reasoner to reason business documents and their mappings. For example, =
assume that you are electronically receiving an Invoice and processing =
that. In this scenario, you will come across business rules like :=20

InvoiceNumber =3D (take the values from position 10 to 15 from the =
stream) [This is analogous to V1 =3D V3]

ReferenceNumber =3D InvoiceNumber [This is analogous to V2 =3D =
V1]

From the above statements, you can infer that=20
ReferenceNumber =3D (take the values from position 10 to 15 from the =
stream) [This is analogous to V2 =3D V3]

Your advice and help is very much appreciated.

Thanks

Sai
<yangyy@cn.ibm.com> wrote in message =
news:el7sv7$evn$1@utils.eclipse.org...

Hi sai,=20

Now I understand your question. :-)=20

First of all, the RDF triples that you showed did represent the {V1 =
equal V3}... However, a RDF/RDFS reasoner only support standard RDF/RDFS =
reasoning, which are defined by RDF/RDFS semantics. You can reference =
http://www.w3.org/TR/rdf-mt/ (chapter 7 shows the entailment rules that =
standard RDF/RDFS reasoner use). Therefore, a standard RDF/RDFS =
reasoner can not make reasoning that you want, because it does not =
understand the semantic of user-defined terminology such as =
"gxs:equals".=20

To support user defined business rules, you can use a external =
rule-based engine. I think that can solve your problem.=20





------=_NextPart_000_000C_01C7198E.B1084C70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4937.800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>Hello=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>Thanks=20
for getting back to me.&nbsp; It is very much appreciated.&nbsp;=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006></SPAN></FONT>&nbsp;</DIV >
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>However, I have few follow-up questions /=20
clarifications :</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>As I=20
mentioned earlier, from the two Java streams, I will be getting the =
rules like,=20
V1 =3D V3 and V2 =3D V1.&nbsp; (In terms of business terminology, I =
could say, V1 is=20
mapped to V3 and V2 is mapped to V1.&nbsp; So, we can infer a mapping =
between V3=20
and V2) </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>I was=20
thinking of constructing RDF XML on the fly and use the reasoner.&nbsp; =
Would it=20
be possible to "some how" represent this relationship using standard =
RDF/RDFS=20
semantics (so that the standard RDF/RDFS reasoner could be used to infer =

relations) ?&nbsp; How to represent them in using standard =
RDF?<BR>&nbsp;<BR>You=20
also&nbsp;mentioned about external rule-based engine ... can you please =
point to=20
one of them?&nbsp; Is Pellet Owl Reasoner support this type of scenario =
? (<A=20
href=3D"http://www.mindswap.org/2003/pellet/index.shtml">http://www.minds=
wap.org/2003/pellet/index.shtml</A>)</SPAN></FONT></DIV >
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>To=20
give a detailed (business) picture ... I am thinking of using RDF =
reasoner to=20
reason business documents and their mappings.&nbsp; For example, assume =
that you=20
are electronically receiving an Invoice and processing that.&nbsp; In =
this=20
scenario, you will come across business rules like : =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>&nbsp;&nbsp;&nbsp; InvoiceNumber =3D (take =
the values=20
from position 10 to 15 from the stream)&nbsp; [This is analogous to V1 =
=3D=20
V3]</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>&nbsp;&nbsp;&nbsp; ReferenceNumber =3D=20
InvoiceNumber&nbsp;&nbsp;&nbsp; [This is analogous to V2 =3D=20
V1]</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>From=20
the above statements, you can infer that&nbsp;<BR>&nbsp;&nbsp;&nbsp;=20
ReferenceNumber =3D (take the values from position 10 to 15 from the=20
stream)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&am p;nbsp;&nbsp;[This is analogous to =
V2 =3D=20
V3]</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>Your=20
advice and help is very much appreciated.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>Thanks</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006></SPAN></FONT>&nbsp;</DIV >
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>Sai</SPAN></FONT></DIV></DIV >
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>&lt;<A =
href=3D"mailto:yangyy@cn.ibm.com">yangyy@cn.ibm.com</A>&gt; wrote in=20
message <A=20
=
href=3D"news:el7sv7$evn$1@utils.eclipse.org">news:el7sv7$evn$1@utils.ecli=
pse.org</A>...</DIV><BR><FONT=20
face=3Dsans-serif size=3D2>Hi sai,</FONT> <BR><BR><FONT =
face=3Dsans-serif size=3D2>Now=20
I understand your question. :-)</FONT> <BR><BR><FONT face=3Dsans-serif =

size=3D2>First of all, the RDF triples that you showed did represent =
the {V1=20
equal V3}... However, a RDF/RDFS reasoner only support standard =
RDF/RDFS=20
reasoning, which are defined by RDF/RDFS semantics. You can reference=20
http://www.w3.org/TR/rdf-mt/ &nbsp;(chapter 7 shows the entailment =
rules that=20
standard RDF/RDFS reasoner use). &nbsp;Therefore, a standard RDF/RDFS =
reasoner=20
can not make reasoning that you want, because it does not understand =
the=20
semantic of user-defined terminology such as </FONT><FONT face=3DArial =

size=3D2>"gxs:equals</FONT><FONT face=3Dsans-serif size=3D2>". =
</FONT><BR><BR><FONT=20
face=3Dsans-serif size=3D2>To support user defined business rules, you =
can use a=20
external rule-based engine. I think that can solve your =
problem.</FONT>=20
<BR><BR><BR><BR><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000C_01C7198E.B1084C70--
Re: EODM - POC to extract relationships [message #595531 is a reply to message #61088] Mon, 13 November 2006 15:20 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 31770
Registered: July 2009
Senior Member
Sai,

It would be best asked on the EODM newsgroup, which I've added to the list.


Srinivasan Sairam wrote:

>Hello,
>I am evaluating / doing a Proof Of Concept for extracting relationships from
>triples. I am looking for some (step by step) tutorial .... is there any
>tutorial that walks through / explains the OWL / RDF reasoner ? I looked in
>the samples ... but thats bit "cryptic" :-(
>
>This is what I am trying to achieve : I want to give a bunch of triples to
>the (OWL or RDF) reasoner : something like
>{V1, V3}, {V5, V7}, {V9, V11}
>{V1, V2}, {V5, V4}, {V9, V6}
>
>I want the reasoner to tell me that there exists relationship between : (V2,
>V3) and (V4, V7) and (V6, V11)
>
>Is there any sample that demonstrates something similar to this ...
>
>Any help would be very much appreciated. ...
>
>Thanks
>
>Sai
>
>================================
>
>Sai (Srinivasan Sairamachandran)
>
>GXS http://www.gxs.com
>
>Srinivasan.Sairam@gxs.com
>
>(248)879-0691
>
>================================
>
>
>
>


Ed Merks
Professional Support: https://www.macromodeling.com/
Re: EODM - POC to extract relationships [message #596075 is a reply to message #61088] Thu, 23 November 2006 02:46 Go to previous message
Yang Yang is currently offline Yang YangFriend
Messages: 10
Registered: July 2009
Junior Member
This is a multipart message in MIME format.
--=_alternative 000F37F64825722F_=
Content-Type: text/plain; charset="US-ASCII"

Sai,

The EODM RDF Reasoner is implemented by the RDF reasoning rules with graph
algorithm and the OWL Reasoner is impleneted with the structural
subsumption algorihtm which currently only support TBox reaonsing. In
fact, I am not understand the example you mentioned. Is {V1, V3} a triple?
If yes, what is the property between them?



>Hello,
>I am evaluating / doing a Proof Of Concept for extracting relationships
from
>triples. I am looking for some (step by step) tutorial .... is there any
>tutorial that walks through / explains the OWL / RDF reasoner ? I looked
in
>the samples ... but thats bit "cryptic" :-(
>
>This is what I am trying to achieve : I want to give a bunch of triples
to
>the (OWL or RDF) reasoner : something like
>{V1, V3}, {V5, V7}, {V9, V11}
>{V1, V2}, {V5, V4}, {V9, V6}
>
>I want the reasoner to tell me that there exists relationship between :
(V2,
>V3) and (V4, V7) and (V6, V11)
>
>Is there any sample that demonstrates something similar to this ...
>
>Any help would be very much appreciated. ...
>
>Thanks
>
>Sai
>
>================================
>
>Sai (Srinivasan Sairamachandran)
>
>GXS http://www.gxs.com
>
>Srinivasan.Sairam@gxs.com
>
>(248)879-0691
>
>================================
>

--=_alternative 000F37F64825722F_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Sai,</font>
<br>
<br><font size=2 face="sans-serif">The EODM RDF Reasoner is implemented
by the RDF reasoning rules with graph algorithm and the OWL Reasoner is
impleneted with the structural subsumption algorihtm which currently only
support TBox reaonsing. In fact, I am not understand the example you mentioned.
Is {V1, V3} a triple? If yes, what is the property between them? </font>
<br>
<br>
<br>
<br><tt><font size=2>&gt;Hello,<br>
&gt;I am evaluating / doing a Proof Of Concept for extracting relationships
from<br>
&gt;triples. &nbsp;I am looking for some (step by step) tutorial .... is
there any<br>
&gt;tutorial that walks through / explains the OWL / RDF reasoner ? &nbsp;I
looked in<br>
&gt;the samples ... but thats bit &quot;cryptic&quot; :-(<br>
&gt;<br>
&gt;This is what I am trying to achieve : I want to give a bunch of triples
to<br>
&gt;the (OWL or RDF) reasoner : something like<br>
&gt;{V1, V3}, {V5, V7}, {V9, V11}<br>
&gt;{V1, V2}, {V5, V4}, {V9, V6}<br>
&gt;<br>
&gt;I want the reasoner to tell me that there exists relationship between
: (V2,<br>
&gt;V3) and (V4, V7) and (V6, V11)<br>
&gt;<br>
&gt;Is there any sample that demonstrates something similar to this ...<br>
&gt;<br>
&gt;Any help would be very much appreciated. ...<br>
&gt;<br>
&gt;Thanks<br>
&gt;<br>
&gt;Sai<br>
&gt;<br>
&gt;================================<br>
&gt;<br>
&gt;Sai (Srinivasan Sairamachandran)<br>
&gt;<br>
&gt;GXS http://www.gxs.com<br>
&gt;<br>
&gt;Srinivasan.Sairam@gxs.com<br>
&gt;<br>
&gt;(248)879-0691<br>
&gt;<br>
&gt;================================<br>
&gt;</font></tt>
<br>
--=_alternative 000F37F64825722F_=--
Re: EODM - POC to extract relationships [message #596490 is a reply to message #62564] Mon, 04 December 2006 20:09 Go to previous message
Sai [Srinivasan Sairam] is currently offline Sai [Srinivasan Sairam]Friend
Messages: 36
Registered: July 2009
Member
This is a multi-part message in MIME format.

------=_NextPart_000_000A_01C717B6.29F1FD00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I apologize for not replying (clarifying my question) earlier ...=20
I have a Java application is being fed by to seperate (input) streams. =
During the parsing / processing of those, I will come across some =
business rules like, V1 =3D V3 from the first stream and another rule =
like, V2 =3D V1 from the second stream. From this, I want to infer that =
there is a relationship between V2 and V3. I want to know how to =
represent this in RDF XML. If my understanding is correct (from the =
primer and some reading), I can represent them as tripes as
{V1 equal V3} and {V2 equals V3}

In RDF / XML as :

<?xml version=3D"1.0"?>

<rdf:RDF=20
xmlns:rdf=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs=3D"http://www.w3.org/2000/01/rdf-schema#"
xmlns:gxs=3D"http://www.gxs.com">

<rdf:Description rdf:about=3D"http://www.gxs.com/V1">
<gxs:equals rdf:resource=3D"http://www.gxs.com/V3" />=20
</rdf:Description>

<rdf:Description rdf:about=3D"http://www.gxs.com/V2">
<gxs:equals rdf:resource=3D"http://www.gxs.com/V1" />=20
</rdf:Description>
=20
</rdf:RDF>

Is this correct? If so, how can I use the reasoner to infer that there =
is a relationship between V2 and V2

Thanks

Sai
<yangyy@cn.ibm.com> wrote in message =
news:ek321q$oti$1@utils.eclipse.org...

Sai,=20

The EODM RDF Reasoner is implemented by the RDF reasoning rules with =
graph algorithm and the OWL Reasoner is impleneted with the structural =
subsumption algorihtm which currently only support TBox reaonsing. In =
fact, I am not understand the example you mentioned. Is {V1, V3} a =
triple? If yes, what is the property between them?=20



>Hello,
>I am evaluating / doing a Proof Of Concept for extracting =
relationships from
>triples. I am looking for some (step by step) tutorial .... is there =
any
>tutorial that walks through / explains the OWL / RDF reasoner ? I =
looked in
>the samples ... but thats bit "cryptic" :-(
>
>This is what I am trying to achieve : I want to give a bunch of =
triples to
>the (OWL or RDF) reasoner : something like
>{V1, V3}, {V5, V7}, {V9, V11}
>{V1, V2}, {V5, V4}, {V9, V6}
>
>I want the reasoner to tell me that there exists relationship between =
: (V2,
>V3) and (V4, V7) and (V6, V11)
>
>Is there any sample that demonstrates something similar to this ...
>
>Any help would be very much appreciated. ...
>
>Thanks
>
>Sai
>
=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>
>Sai (Srinivasan Sairamachandran)
>
>GXS http://www.gxs.com
>
>Srinivasan.Sairam@gxs.com
>
>(248)879-0691
>
=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>=20

------=_NextPart_000_000A_01C717B6.29F1FD00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4937.800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I apologize for not replying =
(clarifying my=20
question) earlier ... </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I have a Java application is being fed =
by to=20
seperate (input) streams.&nbsp; During the parsing / processing of =
those, I will=20
come across some business rules like, V1 =3D V3 from the first stream =
and another=20
rule like, V2 =3D V1 from the second stream.&nbsp; From this, I want to =
infer that=20
there is a relationship between V2 and V3.&nbsp; I want to know how to =
represent=20
this in RDF XML.&nbsp; If my understanding is correct (from the primer =
and some=20
reading), I can represent them as tripes as</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>{V1 equal V3} and {V2 equals =
V3}</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In RDF / XML as :</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&lt;?xml =
version=3D"1.0"?&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&lt;rdf:RDF <BR>&nbsp;xmlns:rdf=3D"<A=20
href=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns">http://www.w3.org/199=
9/02/22-rdf-syntax-ns</A>#"<BR>&nbsp;xmlns:rdfs=3D"<A=20
href=3D"http://www.w3.org/2000/01/rdf-schema">http://www.w3.org/2000/01/r=
df-schema</A>#"<BR>&nbsp;xmlns:gxs=3D"<A=20
href=3D"http://www.gxs.com">http://www.gxs.com</A>"&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; &lt;rdf:Description =
rdf:about=3D"<A=20
href=3D"http://www.gxs.com/V1">http://www.gxs.com/V1</A>"&gt;<BR>&nbsp;=20
&nbsp;&lt;gxs:equals rdf:resource=3D"<A=20
href=3D"http://www.gxs.com/V3">http://www.gxs.com/V3</A>" /&gt; =
<BR>&nbsp;=20
&lt;/rdf:Description&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; &lt;rdf:Description =
rdf:about=3D"<A=20
href=3D"http://www.gxs.com/V2">http://www.gxs.com/V2</A>"&gt;<BR>&nbsp;=20
&nbsp;&lt;gxs:equals rdf:resource=3D"<A=20
href=3D"http://www.gxs.com/V1">http://www.gxs.com/V1</A>" /&gt; =
<BR>&nbsp;=20
&lt;/rdf:Description&gt;<BR>&nbsp; <BR>&lt;/rdf:RDF&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is this correct?&nbsp; If so, how can I =
use the=20
reasoner to infer that there is a relationship between V2 and =
V2</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Sai</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>&lt;<A =
href=3D"mailto:yangyy@cn.ibm.com">yangyy@cn.ibm.com</A>&gt; wrote in=20
message <A=20
=
href=3D"news:ek321q$oti$1@utils.eclipse.org">news:ek321q$oti$1@utils.ecli=
pse.org</A>...</DIV><BR><FONT=20
face=3Dsans-serif size=3D2>Sai,</FONT> <BR><BR><FONT face=3Dsans-serif =
size=3D2>The=20
EODM RDF Reasoner is implemented by the RDF reasoning rules with graph =

algorithm and the OWL Reasoner is impleneted with the structural =
subsumption=20
algorihtm which currently only support TBox reaonsing. In fact, I am =
not=20
understand the example you mentioned. Is {V1, V3} a triple? If yes, =
what is=20
the property between them? </FONT><BR><BR><BR><BR><TT><FONT=20
size=3D2>&gt;Hello,<BR>&gt;I am evaluating / doing a Proof Of Concept =
for=20
extracting relationships from<BR>&gt;triples. &nbsp;I am looking for =
some=20
(step by step) tutorial .... is there any<BR>&gt;tutorial that walks =
through /=20
explains the OWL / RDF reasoner ? &nbsp;I looked in<BR>&gt;the samples =
.... but=20
thats bit "cryptic" :-(<BR>&gt;<BR>&gt;This is what I am trying to =
achieve : I=20
want to give a bunch of triples to<BR>&gt;the (OWL or RDF) reasoner :=20
something like<BR>&gt;{V1, V3}, {V5, V7}, {V9, V11}<BR>&gt;{V1, V2}, =
{V5, V4},=20
{V9, V6}<BR>&gt;<BR>&gt;I want the reasoner to tell me that there =
exists=20
relationship between : (V2,<BR>&gt;V3) and (V4, V7) and (V6,=20
V11)<BR>&gt;<BR>&gt;Is there any sample that demonstrates something =
similar to=20
this ...<BR>&gt;<BR>&gt;Any help would be very much appreciated.=20
=
....<BR>&gt;<BR>&gt;Thanks<BR>&gt;<BR>&gt;Sai <BR>&gt;<BR>&gt;=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=
=3D=3D<BR>&gt;<BR>&gt;Sai=20
(Srinivasan Sairamachandran)<BR>&gt;<BR>&gt;GXS=20
=
http://www.gxs.com<BR>&gt;<BR>&gt;Srinivasan.Sairam@gxs.com<BR>&gt;<BR>&g=
t;(248)879-0691<BR>&gt;<BR>&gt;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>&gt; </FONT></TT=
>=20
<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000A_01C717B6.29F1FD00--
Re: EODM - POC to extract relationships [message #596605 is a reply to message #63661] Thu, 07 December 2006 02:06 Go to previous message
Yang Yang is currently offline Yang YangFriend
Messages: 10
Registered: July 2009
Junior Member
This is a multipart message in MIME format.
--=_alternative 000B93FE4825723D_=
Content-Type: text/plain; charset="US-ASCII"

Hi sai,

Now I understand your question. :-)

First of all, the RDF triples that you showed did represent the {V1 equal
V3}... However, a RDF/RDFS reasoner only support standard RDF/RDFS
reasoning, which are defined by RDF/RDFS semantics. You can reference
http://www.w3.org/TR/rdf-mt/ (chapter 7 shows the entailment rules that
standard RDF/RDFS reasoner use). Therefore, a standard RDF/RDFS reasoner
can not make reasoning that you want, because it does not understand the
semantic of user-defined terminology such as "gxs:equals".

To support user defined business rules, you can use a external rule-based
engine. I think that can solve your problem.





--=_alternative 000B93FE4825723D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi sai,</font>
<br>
<br><font size=2 face="sans-serif">Now I understand your question. :-)</font>
<br>
<br><font size=2 face="sans-serif">First of all, the RDF triples that you
showed did represent the {V1 equal V3}... However, a RDF/RDFS reasoner
only support standard RDF/RDFS reasoning, which are defined by RDF/RDFS
semantics. You can reference http://www.w3.org/TR/rdf-mt/ &nbsp;(chapter
7 shows the entailment rules that standard RDF/RDFS reasoner use). &nbsp;Therefore,
a standard RDF/RDFS reasoner can not make reasoning that you want, because
it does not understand the semantic of user-defined terminology such as
</font><font size=2 face="Arial">&quot;gxs:equals</font><font size=2 face="sans-serif">&quot;.
</font>
<br>
<br><font size=2 face="sans-serif">To support user defined business rules,
you can use a external rule-based engine. I think that can solve your problem.</font>
<br>
<br>
<br>
<br>
<br>
--=_alternative 000B93FE4825723D_=--
Re: EODM - POC to extract relationships [message #596615 is a reply to message #63913] Thu, 07 December 2006 04:31 Go to previous message
Sai [Srinivasan Sairam] is currently offline Sai [Srinivasan Sairam]Friend
Messages: 36
Registered: July 2009
Member
This is a multi-part message in MIME format.

------=_NextPart_000_000C_01C7198E.B1084C70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello=20
Thanks for getting back to me. It is very much appreciated. =20

However, I have few follow-up questions / clarifications :

As I mentioned earlier, from the two Java streams, I will be getting the =
rules like, V1 =3D V3 and V2 =3D V1. (In terms of business terminology, =
I could say, V1 is mapped to V3 and V2 is mapped to V1. So, we can =
infer a mapping between V3 and V2)=20

I was thinking of constructing RDF XML on the fly and use the reasoner. =
Would it be possible to "some how" represent this relationship using =
standard RDF/RDFS semantics (so that the standard RDF/RDFS reasoner =
could be used to infer relations) ? How to represent them in using =
standard RDF?
=20
You also mentioned about external rule-based engine ... can you please =
point to one of them? Is Pellet Owl Reasoner support this type of =
scenario ? (http://www.mindswap.org/2003/pellet/index.shtml)

To give a detailed (business) picture ... I am thinking of using RDF =
reasoner to reason business documents and their mappings. For example, =
assume that you are electronically receiving an Invoice and processing =
that. In this scenario, you will come across business rules like :=20

InvoiceNumber =3D (take the values from position 10 to 15 from the =
stream) [This is analogous to V1 =3D V3]

ReferenceNumber =3D InvoiceNumber [This is analogous to V2 =3D =
V1]

From the above statements, you can infer that=20
ReferenceNumber =3D (take the values from position 10 to 15 from the =
stream) [This is analogous to V2 =3D V3]

Your advice and help is very much appreciated.

Thanks

Sai
<yangyy@cn.ibm.com> wrote in message =
news:el7sv7$evn$1@utils.eclipse.org...

Hi sai,=20

Now I understand your question. :-)=20

First of all, the RDF triples that you showed did represent the {V1 =
equal V3}... However, a RDF/RDFS reasoner only support standard RDF/RDFS =
reasoning, which are defined by RDF/RDFS semantics. You can reference =
http://www.w3.org/TR/rdf-mt/ (chapter 7 shows the entailment rules that =
standard RDF/RDFS reasoner use). Therefore, a standard RDF/RDFS =
reasoner can not make reasoning that you want, because it does not =
understand the semantic of user-defined terminology such as =
"gxs:equals".=20

To support user defined business rules, you can use a external =
rule-based engine. I think that can solve your problem.=20





------=_NextPart_000_000C_01C7198E.B1084C70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4937.800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>Hello=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>Thanks=20
for getting back to me.&nbsp; It is very much appreciated.&nbsp;=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006></SPAN></FONT>&nbsp;</DIV >
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>However, I have few follow-up questions /=20
clarifications :</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>As I=20
mentioned earlier, from the two Java streams, I will be getting the =
rules like,=20
V1 =3D V3 and V2 =3D V1.&nbsp; (In terms of business terminology, I =
could say, V1 is=20
mapped to V3 and V2 is mapped to V1.&nbsp; So, we can infer a mapping =
between V3=20
and V2) </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>I was=20
thinking of constructing RDF XML on the fly and use the reasoner.&nbsp; =
Would it=20
be possible to "some how" represent this relationship using standard =
RDF/RDFS=20
semantics (so that the standard RDF/RDFS reasoner could be used to infer =

relations) ?&nbsp; How to represent them in using standard =
RDF?<BR>&nbsp;<BR>You=20
also&nbsp;mentioned about external rule-based engine ... can you please =
point to=20
one of them?&nbsp; Is Pellet Owl Reasoner support this type of scenario =
? (<A=20
href=3D"http://www.mindswap.org/2003/pellet/index.shtml">http://www.minds=
wap.org/2003/pellet/index.shtml</A>)</SPAN></FONT></DIV >
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>To=20
give a detailed (business) picture ... I am thinking of using RDF =
reasoner to=20
reason business documents and their mappings.&nbsp; For example, assume =
that you=20
are electronically receiving an Invoice and processing that.&nbsp; In =
this=20
scenario, you will come across business rules like : =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>&nbsp;&nbsp;&nbsp; InvoiceNumber =3D (take =
the values=20
from position 10 to 15 from the stream)&nbsp; [This is analogous to V1 =
=3D=20
V3]</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>&nbsp;&nbsp;&nbsp; ReferenceNumber =3D=20
InvoiceNumber&nbsp;&nbsp;&nbsp; [This is analogous to V2 =3D=20
V1]</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>From=20
the above statements, you can infer that&nbsp;<BR>&nbsp;&nbsp;&nbsp;=20
ReferenceNumber =3D (take the values from position 10 to 15 from the=20
stream)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&am p;nbsp;&nbsp;[This is analogous to =
V2 =3D=20
V3]</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D238272404-07122006>Your=20
advice and help is very much appreciated.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>Thanks</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006></SPAN></FONT>&nbsp;</DIV >
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238272404-07122006>Sai</SPAN></FONT></DIV></DIV >
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>&lt;<A =
href=3D"mailto:yangyy@cn.ibm.com">yangyy@cn.ibm.com</A>&gt; wrote in=20
message <A=20
=
href=3D"news:el7sv7$evn$1@utils.eclipse.org">news:el7sv7$evn$1@utils.ecli=
pse.org</A>...</DIV><BR><FONT=20
face=3Dsans-serif size=3D2>Hi sai,</FONT> <BR><BR><FONT =
face=3Dsans-serif size=3D2>Now=20
I understand your question. :-)</FONT> <BR><BR><FONT face=3Dsans-serif =

size=3D2>First of all, the RDF triples that you showed did represent =
the {V1=20
equal V3}... However, a RDF/RDFS reasoner only support standard =
RDF/RDFS=20
reasoning, which are defined by RDF/RDFS semantics. You can reference=20
http://www.w3.org/TR/rdf-mt/ &nbsp;(chapter 7 shows the entailment =
rules that=20
standard RDF/RDFS reasoner use). &nbsp;Therefore, a standard RDF/RDFS =
reasoner=20
can not make reasoning that you want, because it does not understand =
the=20
semantic of user-defined terminology such as </FONT><FONT face=3DArial =

size=3D2>"gxs:equals</FONT><FONT face=3Dsans-serif size=3D2>". =
</FONT><BR><BR><FONT=20
face=3Dsans-serif size=3D2>To support user defined business rules, you =
can use a=20
external rule-based engine. I think that can solve your =
problem.</FONT>=20
<BR><BR><BR><BR><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000C_01C7198E.B1084C70--
Previous Topic:extending EvaluationVisitorImpl
Next Topic:General architecture question on performance
Goto Forum:
  


Current Time: Sun Feb 28 07:52:11 GMT 2021

Powered by FUDForum. Page generated in 0.01737 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top