Re: [foaf-dev] RDF support for anonymous users in Drupal

Thanks Toby and Alex for your feedback,

sioc:has_creator links to a sioc:User by definition, not to a foaf:Agent
>
or foaf:Person.
>
right, so sioc:User it is.

By the way, on http://drupalrdf.openspring.net/node/3 the sioc:reply_of
> links aren't getting picked up. They're "masked" by the
> property="content:encoded" of the parent <div> element. A slightly
> annoying feature of RDFa is that any property which results in an
> rdf:XMLLiteral causes any RDF on descendant elements to be ignored.
>

agreed. that's what I explained at [1] and that's due to Drupal internals.
We're working on a solution which will in fact move the property attribute
one level down on a new tag which will wrap the content. That way the
property attribute will be on a tag at the same level (sibling) as
       <span rel="sioc:reply_of" resource="/node/3" />

that should in theory work and produce the intended RDFa...

Steph.

[1] http://drupal.org/node/538164#comment-2182794

On Fri, Oct 23, 2009 at 12:52 PM, Alexandre Passant <
alexandre.passant@deri.org> wrote:

>
> On 23 Oct 2009, at 17:35, Toby Inkster wrote:
>
>  On Fri, 2009-10-23 at 11:48 -0400, Stephane Corlosquet wrote:
>>
>>> To keep things simple, I'm very tempted to reuse the sioc:User mapping
>>> we already have for the regular registered user. Is it ok not to use a
>>> foaf:Agent or foaf:Person in this case, and link a sioc:User to a
>>> homepage with foaf:page?
>>>
>>
>> sioc:has_creator links to a sioc:User by definition, not to a foaf:Agent
>> or foaf:Person.
>>
>
> Indeed, if you want to use a sioc:User then it should go with
> sioc:has_creator but if you require a foaf:Agent, then use foaf:maker.
> However, both foaf:page / foaf:homepage have owl:Thing as a range so you
> can use it in combination with sioc:User.
> I'd yet avoid foaf:homepage as this is an IFP, and may lead to weird things
> (esp. for untrusted users)
>
> Alex.
>
>
>> By the way, on http://drupalrdf.openspring.net/node/3 the sioc:reply_of
>> links aren't getting picked up. They're "masked" by the
>> property="content:encoded" of the parent <div> element. A slightly
>> annoying feature of RDFa is that any property which results in an
>> rdf:XMLLiteral causes any RDF on descendant elements to be ignored.
>>
>> Possible solution...
>>
>> Drop this:
>>
>>        <span rel="sioc:reply_of" resource="/node/3" />
>>
>> Change this (lines wrapped for readability):
>>
>>        <h3 property="dc:title" datatype="">
>>          <a href="/comment/1#comment-1">a first comment to the blog
>> post</a>
>>        </h3>
>>
>> To this:
>>
>>        <h3 property="dc:title" datatype="">
>>          <a about="/node/3" rel="sioc:has_reply" rev="sioc:reply_of"
>> href="/comment/1#comment-1">
>>            a first comment to the blog post
>>          </a>
>>        </h3>
>>
>> --
>> Toby A Inkster
>> <mailto:mail@tobyinkster.co.uk>
>> <http://tobyinkster.co.uk>
>>
>> _______________________________________________
>> foaf-dev mailing list
>> foaf-dev@lists.foaf-project.org
>> http://lists.foaf-project.org/mailman/listinfo/foaf-dev
>>
>
> --
> Dr. Alexandre Passant
> Digital Enterprise Research Institute
> National University of Ireland, Galway
> :me owl:sameAs <http://apassant.net/alex> .
>
>
>
>
>
>
>