Re: [foaf-dev] foaf robots as People?
Melvin Carvalho <[email protected]> Mon, 9 Mar 2015 09:37:39 +0100
| Newsgroups | gmane.comp.web.rdfweb |
|---|---|
| Message-ID | <CAKaEYh+xD14xjzJAnB8p9mQHRBLVgt8tjPxE1Md0t84qygyTxw@mail.gmail.com> |
--===============1534432765561156427== Content-Type: multipart/alternative; boundary=001a11c32cf069e6f60510d6f2ff --001a11c32cf069e6f60510d6f2ff Content-Type: text/plain; charset=UTF-8 On 9 March 2015 at 09:35, Melvin Carvalho <[email protected]> wrote: > > > On 9 March 2015 at 00:27, Patrick Logan <[email protected]> wrote: > >> In that case it would seem the spec, via "real or imaginary", gives room >> for that decision. >> >> My preference might be to use my own class for your purpose, and draw the >> line for Persons a little stricter. But I can see your point about that >> causing other complications, especially if you've no other reason to use >> your own namespace, classes, etc. >> > Currently what I do is I share my key with a process, it logs in as me and > posts. But I think a better solution is to give it its own identity and > have some kind of access control permissions to let it make updates. > > On systems like facebook people are often imitated by robots, so I think > in practical terms it's going to be a grey area. > > But seems to me the "correct" way is to use Agent. That distinction might > soften into unimportant over time, tho, maybe ... > Note: in the chat area I've built, anyone in my "knows" can make a post. But I can only "know" a Person. So if the robot is an agent is not a person, there's a whole new layer needed. > > >> On Mar 8, 2015 4:14 PM, "Melvin Carvalho" <[email protected]> >> wrote: >> >>> >>> >>> On 9 March 2015 at 00:12, Patrick Logan <[email protected]> wrote: >>> >>>> > >>>> > Can I make them a Person? >>>> > >>>> >>>> In what ways would this make a difference to the systems or people >>>> working with the data? >>>> >>> >>> well im working on a social system with timelines, apps etc. Id like to >>> give the robot the same abilities as a person has, viewing, writing etc. >>> without having to change whole bunches of code. The easiest way to do this >>> would be to make the robot type Agent and Person ... is it too much a >>> stretch do you think? >>> >>> > --001a11c32cf069e6f60510d6f2ff Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo= te">On 9 March 2015 at 09:35, Melvin Carvalho <span dir=3D"ltr"><<a href= =3D"mailto:[email protected]" target=3D"_blank">melvincarvalho@gmail= .com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma= rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt= r"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><span clas= s=3D"">On 9 March 2015 at 00:27, Patrick Logan <span dir=3D"ltr"><<a hre= f=3D"mailto:[email protected]" target=3D"_blank">patrickdlogan@gmail.= com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar= gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">= In that case it would seem the spec, via "real or imaginary", giv= es room for that decision. </p> <p dir=3D"ltr">My preference might be to use my own class for your purpose,= and draw the line for Persons a little stricter. But I can see your point = about that causing other complications, especially if you've no other r= eason to use your own namespace, classes, etc.</p></blockquote></span><div>= Currently what I do is I share my key with a process, it logs in as me and = posts.=C2=A0 But I think a better solution is to give it its own identity a= nd have some kind of access control permissions to let it make updates.<br>= <br></div><div>On systems like facebook people are often imitated by robots= , so I think in practical terms it's going to be a grey area.<br><br></= div><div>But seems to me the "correct" way is to use Agent.=C2=A0= That distinction might soften into unimportant over time, tho, maybe ...<b= r></div></div></div></div></blockquote><div><br></div><div>Note: in the cha= t area I've built, anyone in my "knows" can make a post.=C2= =A0 But I can only "know" a Person.=C2=A0 So if the robot is an a= gent is not a person, there's a whole new layer needed.<br></div><div>= =C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo= rder-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"g= mail_extra"><div class=3D"gmail_quote"><div></div><span class=3D""><div>=C2= =A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde= r-left:1px #ccc solid;padding-left:1ex"><div><div> <div class=3D"gmail_quote">On Mar 8, 2015 4:14 PM, "Melvin Carvalho&qu= ot; <<a href=3D"mailto:[email protected]" target=3D"_blank">melvi= [email protected]</a>> wrote:<br type=3D"attribution"><blockquote clas= s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad= ding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div cla= ss=3D"gmail_quote">On 9 March 2015 at 00:12, Patrick Logan <span dir=3D"ltr= "><<a href=3D"mailto:[email protected]" target=3D"_blank">patrickd= [email protected]</a>></span> wrote:<br><blockquote class=3D"gmail_quote" = style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><sp= an><p dir=3D"ltr">><br> > Can I make them a Person?<br> ></p> </span><p dir=3D"ltr">In what ways would this make a difference to the syst= ems or people working with the data?<br></p></blockquote><div><br></div><di= v>well im working on a social system with timelines, apps etc.=C2=A0 Id lik= e to give the robot the same abilities as a person has, viewing, writing et= c. without having to change whole bunches of code.=C2=A0 The easiest way to= do this would be to make the robot type Agent and Person ... is it too muc= h a stretch do you think? <br></div></div><br></div></div> </blockquote></div> </div></div></blockquote></span></div><br></div></div> </blockquote></div><br></div></div> --001a11c32cf069e6f60510d6f2ff-- --===============1534432765561156427== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ foaf-dev mailing list foaf-dev-RyYwo1q5J+qsOXdr9/[email protected] http://lists.foaf-project.org/mailman/listinfo/foaf-dev --===============1534432765561156427==--