On Mar 2, 10:03 am, Olivier GENDRIN <[email protected]> wrote: > On Fri, Mar 2, 2012 at 10:52 AM, Alexandre Passant <[email protected]> wrote: > > sioc:sibling is currently defined with sioc:Item as both domain and range. > > I think that's a useful property to model sibling user accounts, e.g. > > creating a direct relation between a Twitter and FB account, w/o > > having to rely on a foaf:Person to link both. > > > Any opinions? Could we remove the domain / range restrictions of > > sioc:sibling to allow such use-cases? > > You should have at least a foaf:agent handling both accounts. It can > be anonymous.
That's my concern. Why should I create an additional triple instead of a direct relation ? <http://twitter.com/foo> sioc:sibling <http://facebook.com/foo> vs [] foaf:account <http://twitter.com/foo> ; <http://facebook.com/foo> . Which also leads to SELECT sibling WHERE { <http:twitter.com/foo> sioc:sibling ?sibing } vs SELECT sibling WHERE { [] sioc:sibling <http:twitter.com/foo> ; sioc:sibling ?sibing . FILTER (?sibling != <http:twitter.com/foo> } Best, Alex. > > -- > Olivier > G.http://identi.ca/lespacedunmatinhttp://www.lespacedunmatin.info/blog/ -- You received this message because you are subscribed to the Google Groups "SIOC-Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en.
