Drupal user profiles in RDFa
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Drupal user profiles in RDFa
by Stephane Corlosquet
::
Rate this Message:
Hi all,
I'm checking the RDFa markup we have chosen for Drupal 7 and want to make sure it's optimal, given that it won't be able to change it after the code freeze (which in one week!). In particular I'd like to discuss the case of the user markup which is used to describe the author or a page or comment. "User profile" in this email refers to the concept of sioc:User / foaf:OnlineAccount. Drupal has 3 main cases which all have different markup. 1. If the administrator of the site decided to make the user profile pages public, then the author will be a link to the author profile page http://example.org/user/23. The original markup is: <a href="/user/23" title="View user profile." class="username">John</a> We have 2 options to add RDFa to this link which both return the same RDF data: <a href="/user/1" rel="sioc:has_creator foaf:maker" title="View user profile." class="username"><span resource="/user/1" typeof="sioc:User" property="foaf:name">Henry</span></a> or <span rel="sioc:has_creator foaf:maker"><a href="/d7sprint/user/1" typeof="sioc:User" property="foaf:name" title="View user profile." class="username">Henry</a></span></span> Question for the RDFa ninjas reading this: is there a way to embed all this information without adding a span tag either inside or outside the a existing a tag. I'm asking this because adding extra markup is frown upon by Drupal themers as it might break some CSS rules or have unintended effects, so if we can do without it it's best. To understand the risk of adding an extra span, take a long at the second option above: if there is a CSS rule on "a span" path targetting other markup on the site, then name of the author will suddenly be affected by this rule, while it would not in the original non-RDFa markup. Unfortunately there is no "blank" tag which maybe would have been helpful here by not interacting with CSS. Such "blank" HTML tag would have been useful in this case to wrap RDFa markup and ensure it is not targeted by any CSS rule (this could be a convention at least). 2. If the user profile pages are not accessible then only the name of the author will be displayed and we are missing the URL of her profile page, or rather I should say we can generate a URI for the user profile, but resolving it would lead to a 403 Access denied. The default Drupal markup in this case is simply: <span class="username">John</span> I see 3 alternatives to annotate this in RDFa: 2.1 Use a markup similar to the one above, but the cons is that the user profile URI will not be dereferencable (and hereby breaking one of the Linked Data principles). It will return a 403 Access denied. <span rel="sioc:has_creator foaf:maker" class="username"><span resource="/user/1" typeof="sioc:User" property="foaf:name">Henry</span></span> 2.2 Same as 2.1 but without the resource attribute hence generating a bnode. I always try hard to avoid generating these, but if this is no work around, then we'll have to use it. <span rel="sioc:has_creator foaf:maker" class="username"><span resource="/user/1" typeof="sioc:User" property="foaf:name">Henry</span></span> 2.3 We don't introduce the concept of user profile and simply link the page to a name (literal). <span class="username" property="foaf:maker">Henry</span> I don't like 2.3 because it's not as meaningful from an RDF perspective. Also, we don't have the same choices in the RDF properties we can use due to the domain which is now a literal, which would be a problem in the context of Drupal since the page -> author relationship gets the same set of RDF properties no matter what the case is (between 1, 2 or 3). So I'd rather use 2.1 or 2.2. but we've got to decide between the best of the two: a non dereferencable URI or a bnode? I like the non referencable URI because we can uniquely identify the author outside the scope of the page, but I wonder how the parsers will react when trying to resolve the URI. 3. In the case of a non registered user leaving a comment, Drupal offers to leave her name, homepage and email address (though the email address is not displayed for privacy reasons). The default markup is: <a href="http://openspring.net/" rel="nofollow" class="username">Stephane Corlosquet (not verified)</a> We don't have a user profile URI here, but a homepage which is usually linked to a foaf:Person. Here we have multiple options again to describe the author of a comment. I'm not sure we should directly link a page to a foaf:Person, should we?. Do we have to generate a foaf:OnlineAccount /sioc:User URI here based on the homepage by adding #user to it? use a bnode? opinions? Stephane. |
|
|
Re: Drupal user profiles in RDFa
by Toby Inkster-4
::
Rate this Message:
On 11 Oct 2009, at 16:09, Stephane Corlosquet wrote:
> We have 2 options to add RDFa to this link which both return the > same RDF data: > > <a href="/user/1" rel="sioc:has_creator foaf:maker" title="View > user profile." class="username"><span resource="/user/1" > typeof="sioc:User" property="foaf:name">Henry</span></a> > > or > > <span rel="sioc:has_creator foaf:maker"><a href="/d7sprint/user/1" > typeof="sioc:User" property="foaf:name" title="View user profile." > class="username">Henry</a></span></span> foaf:maker is probably not what you want. foaf:maker's range is foaf:Agent, whereas a sioc:User is not a foaf:Agent, it's an account that a foaf:Agent holds. > Question for the RDFa ninjas reading this: is there a way to embed > all this information without adding a span tag either inside or > outside the a existing a tag. <a href="/user/1" title="View user profile." about="/user/1" typeof="sioc:User" rev="sioc:has_creator" resource="" property="foaf:name">Henry</a> > 2.1 Use a markup similar to the one above, but the cons is that > the user profile URI will not be dereferencable (and hereby > breaking one of the Linked Data principles). It will return a 403 > Access denied. > > <span rel="sioc:has_creator foaf:maker" class="username"><span > resource="/user/1" typeof="sioc:User" property="foaf:name">Henry</ > span></span> I think this is the right thing to do. > 3. In the case of a non registered user leaving a comment, Drupal > offers to leave her name, homepage and email address (though the > email address is not displayed for privacy reasons). The default > markup is: > > <a href="http://openspring.net/" rel="nofollow" > class="username">Stephane Corlosquet (not verified)</a> > > We don't have a user profile URI here, but a homepage which is > usually linked to a foaf:Person. Here we have multiple options > again to describe the author of a comment. I'm not sure we should > directly link a page to a foaf:Person, should we?. Do we have to > generate a foaf:OnlineAccount /sioc:User URI here based on the > homepage by adding #user to it? use a bnode? opinions? Assuming that you're still wanting to avoid that <span> element, the following would be reasonably consistent with the markup for people who have accounts: <a href="http://openspring.net/" about="_:bnode_001" typeof="sioc:User" rev="sioc:has_creator" resource="" property="foaf:name" content="Stephane Corlosquet" >Stephane Corlosquet (not verified)</a> This does *not* use the address <http://openspring.net/> in any triples though. It's ignored. If we include that <span>, then we can use the openspring.net address: <span rel="sioc:has_creator"> <a typeof="sioc:User" rel="foaf:page" href="http://openspring.net/" property="foaf:name" content="Stephane Corlosquet" >Stephane Corlosquet (not verified)</a> </span> (Note that I've used foaf:page instead of foaf:homepage because the latter is a very strong assertion, being an IFP. Stick with foaf:page for user-submitted content, otherwise OWL inference on your data will start to throw up some very strange conclusions.) -- Toby A Inkster <mailto:mail@...> <http://tobyinkster.co.uk> |
|
|
Re: Drupal user profiles in RDFa
by Lin Clark
::
Rate this Message:
Hey Stephane,
Regarding #1, I tried this: <a resource="path_to_node" property="foaf:name" typeof="sioc:User" class="username" title="View user profile." rel="sioc:creator_of foaf:made" about="user/1" href="/user/1">Henry</a> I used the inverse of created_by and maker so that there was only one subject, the user. It isn't as intuitive when you look at it, which is a shame, but the Check RDFa browser tool returns: <http://xmlns.com/foaf/0.1/name> "Henry" Which I think includes all the same information, let me know if I missed anything.On Sun, Oct 11, 2009 at 11:09 AM, Stephane Corlosquet <scorlosquet@...> wrote: Hi all, |
|
|
Re: Drupal user profiles in RDFa
by Steven Pemberton-3
::
Rate this Message:
On Sun, 11 Oct 2009 17:09:52 +0200, Stephane Corlosquet
<scorlosquet@...> wrote: > Hi all, > > I'm checking the RDFa markup we have chosen for Drupal 7 and want to make > sure it's optimal, given that it won't be able to change it after the > code freeze (which in one week!). In particular I'd like to discuss the > case of the user markup which is used to describe the author or a page > or comment. Thanks for the chance to feedback! > "User profile" in this email refers to the concept of sioc:User / > foaf:OnlineAccount. Drupal has 3 main cases which all have different > markup. > > > 1. If the administrator of the site decided to make the user profile > pages public, then the author will be a link to the author profile page > http://example.org/user/23. The original markup is: > > <a href="/user/23" title="View user profile." class="username">John</a> > > We have 2 options to add RDFa to this link which both return the same RDF > data: > > <a href="/user/1" rel="sioc:has_creator foaf:maker" title="View user > profile." class="username"><span resource="/user/1" typeof="sioc:User" > property="foaf:name">Henry</span></a> > > or > > <span rel="sioc:has_creator foaf:maker"><a href="/d7sprint/user/1" > typeof="sioc:User" property="foaf:name" title="View user profile." > class="username">Henry</a></span></span> I'm assuming the /dsprint7 is a typo here, otherwise they wouldn't have the same triples. So the triples they produce are like: <http://www.w3.org/basedoc.html> <http://sioc.org/has_creator> <http://www.w3.org/user/1> . <http://www.w3.org/basedoc.html> <http://foaf.org/maker> <http://www.w3.org/user/1> . <http://www.w3.org/user/1> <http://foaf.org/name> "Henry" . <http://www.w3.org/user/1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://sioc.org/User> . Of the two I slightly prefer the second, with the outer <span>, since the URI doesn't have to get repeated. If it weren't for the @typeof, you could do it all in one go: <a href="/user/3" rel="sioc:has_creator foaf:maker" title="View user profile." class="username" property="foaf:name">Steven</a> but of course the @typeof changes the subject. > Question for the RDFa ninjas reading this: is there a way to embed all > this > information without adding a span tag either inside or outside the a > existing a tag. I'm asking this because adding extra markup is frown > upon by > Drupal themers as it might break some CSS rules or have unintended > effects, > so if we can do without it it's best. At the cost of repeating the URI, but with the advantage that it doesn't risk messing up your CSS, you don't have to nest the extra span: <a href="/user/1" rel="sioc:has_creator foaf:maker" title="View user profile." class="username" property="foaf:name">Henry</a> <span about="/user/1" typeof="sioc:User"></span> So this is a non-nested version of your first solution. > 2. If the user profile pages are not accessible then only the name of the > author will be displayed and we are missing the URL of her profile page, > or rather I should say we can generate a URI for the user profile, but > resolving it would lead to a 403 Access denied. The default Drupal > markup in > this case is simply: > <span class="username">John</span> > > I see 3 alternatives to annotate this in RDFa: > > 2.1 Use a markup similar to the one above, but the cons is that the > user > profile URI will not be dereferencable (and hereby breaking one of the > Linked Data principles). It will return a 403 Access denied. > > <span rel="sioc:has_creator foaf:maker" class="username"><span > resource="/user/1" typeof="sioc:User" > property="foaf:name">Henry</span></span> > > 2.2 Same as 2.1 but without the resource attribute hence generating a > bnode. I always try hard to avoid generating these, but if this is no > work > around, then we'll have to use it. > > <span rel="sioc:has_creator foaf:maker" class="username"><span > resource="/user/1" typeof="sioc:User" > property="foaf:name">Henry</span></span> > > 2.3 We don't introduce the concept of user profile and simply link the > page to a name (literal). > > <span class="username" property="foaf:maker">Henry</span> > > I don't like 2.3 because it's not as meaningful from an RDF perspective. > Also, we don't have the same choices in the RDF properties we can use > due to > the domain which is now a literal, which would be a problem in the > context > of Drupal since the page -> author relationship gets the same set of RDF > properties no matter what the case is (between 1, 2 or 3). So I'd rather > use > 2.1 or 2.2. but we've got to decide between the best of the two: a non > dereferencable URI or a bnode? I like the non referencable URI because we > can uniquely identify the author outside the scope of the page, but I > wonder > how the parsers will react when trying to resolve the URI. I think you're worrying too much about the 403s. The triples are true, whether or not you try to dereference the URIs: <http://www.w3.org/basedoc.html> <http://sioc.org/has_creator> <http://www.w3.org/user/1> . <http://www.w3.org/basedoc.html> <http://foaf.org/maker> <http://www.w3.org/user/1> . <http://www.w3.org/user/1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://sioc.org/User> . <http://www.w3.org/user/1> <http://foaf.org/name> "Henry" . What you may want to avoid is making them *easy* to dereference. Then I would use a span+@resource instead of an a: <span resource="/user/1" rel="sioc:has_creator foaf:maker" title="Inaccessible user profile" class="username" property="foaf:name">Henry</a> <span about="/user/1" typeof="sioc:User"></span> > 3. In the case of a non registered user leaving a comment, Drupal offers > to leave her name, homepage and email address (though the email address > is not displayed for privacy reasons). The default markup is: > > <a href="http://openspring.net/" rel="nofollow" class="username">Stephane > Corlosquet (not verified)</a> > > We don't have a user profile URI here, but a homepage which is usually > linked to a foaf:Person. Here we have multiple options again to describe > the author of a comment. I'm not sure we should directly link a page to a > foaf:Person, should we? No. > Do we have to generate a foaf:OnlineAccount > /sioc:User URI here based on the homepage by adding #user to it? use a > bnode? opinions? In the absence of other information I prefer to use rel="foaf:isPrimaryTopicOf" to identify a person from their homepage. (See http://www.w3.org/MarkUp/2009/rdfa-for-html-authors) Hope this helps. Best wishes, Steven Pemberton > > Stephane. |
|
|
Re: Drupal user profiles in RDFa
by Toby Inkster-4
::
Rate this Message:
On 12 Oct 2009, at 12:42, Toby Inkster wrote:
>> 2.1 Use a markup similar to the one above, but the cons is that >> the user profile URI will not be dereferencable (and hereby >> breaking one of the Linked Data principles). It will return a 403 >> Access denied. >> >> <span rel="sioc:has_creator foaf:maker" class="username"><span >> resource="/user/1" typeof="sioc:User" property="foaf:name">Henry</ >> span></span> > > I think this is the right thing to do. You want @about here though. @about is for setting subjects, @resource is for setting objects. (It's possible to use them the other way around, but not a good idea usually.) My point though, was that, yes, I think it's fine to use URIs here which currently resolve to 403. That's an accurate representation of the situation (that the data exists but access is denied). -- Toby A Inkster <mailto:mail@...> <http://tobyinkster.co.uk> |
|
|
Re: Drupal user profiles in RDFa
by Stephane Corlosquet
::
Rate this Message:
Hi,
Thank you all for your feedback, that's excellent! :) On a side-note people still haven't agreed if the URIs of profile Yes, I asked the same question to Dan Brickley during DrupalCon Paris, and he said it was ok to do that.That's also simpler to grasp for people with little background in RDF. Alternatively you could get rid of the span by just not declaring the That was also my first take on this, but I changed my mind as some plugins or UI tool can take advantage of the typeof values. There exist plugins which target specific attributes on RDFa pages and format them depending on their value, e.g. sioc:User of a page in a special form (with a logo, popup or whatever - I know Michael Hausenblas or Alexandre Passant have an example for this). Relying on reasoning and dereferencing is too much to expect and would slow down such interface. I'd like to get more opinions on the 3 third case where anonymous visitor can leave comments. I agree that using foaf:homepage here is inappropriate due to the IFP, and since we do not control what URI people will put in there we should be careful. Options suggested so far: 1. bnode typed sioc:User or foaf:Agent to cover the case where it's a link to a company homepage. 2. link this bnode to the "homepage" URI with foaf:isPrimaryTopicOf, foaf:page or rdfs:seeAlso. foaf:isPrimaryTopicOf is also an IFP, so I think we should avoid it. rdfs:seeAlso is good though somewhat generic. foaf:page seems the most appropriate here and does not imply strong assumptions. What do you think? Stephane. On Mon, Oct 12, 2009 at 7:48 AM, Steven Pemberton <Steven.Pemberton@...> wrote:
|
| Free embeddable forum powered by Nabble | Forum Help |
