> Thanks for the notice, Aidan!  I've pushed a simple fix to exclude
> mbox_sha1sum for users without an email address "on file". We'll make
> sure to roll it into our next release.

Excellent news. Thanks for the fix James!

> Let us know if there's anything else we can clean up!

There are two other small issues -- incidentally, neither of which are
in any way your fault ;).

The first relates to the recent deprecation by SIOC of sioc:User [1].
This is not a major issue by any means, but of course it would be great
to see the new sioc:UserAccount class used instead. Should be a case of
simply replacing any reference to 'sioc:User' with 'sioc:UserAccount'.

The second issue is a little trickier and relates to use of the
foaf:accountProfilePage property which does not exist in FOAF. That
said, and referring to [2], I think that the information given by that
property is quite valuable. For the moment, I would leave this as is on
your side James.

To try find a more permanent solution, I've CC'd the guys over at FOAF. 

@FOAF-DEV. Would you consider adding a property
'foaf:accountProfilePage' to FOAF? Or would you recommend a different
property for the following usage:

<OnlineAccount rdf:about="http://identi.ca/user/269#acct";>
    <accountServiceHomepage
rdf:resource="http://identi.ca/";></accountServiceHomepage>
    <accountName>segphault</accountName>
    ***<accountProfilePage
rdf:resource="http://identi.ca/segphault";></accountProfilePage>***
    <sioc:account_of
rdf:resource="http://identi.ca/user/269";></sioc:account_of>
    <sioc:follows
rdf:resource="http://identi.ca/user/1020#acct";></sioc:follows>
</OnlineAccount>

I'd be hesitant to use foaf:isPrimaryTopicOf here, since both the
Person/Agent and OnlineAccount/UserAccount could both have claims to
being the primary topic of [3] (and subsequently be consolidated). I
guess I'd lean towards a new property in FOAF 'foaf:accountProfilePage'
with
* domain foaf:OnlineAccount
* range foaf:Document
* type InverseFunctionalProperty
* subPropertyOf page
...which would IMO be safer than using/extending upon
foaf:isPrimaryTopicOf.

Cheers,
Aidan
- http://pedantic-web.org/

[1] http://sioc-project.org/node/341
[2] http://identi.ca/whataboutbob/foaf
[3] http://identi.ca/segphault

> On Fri, May 14, 2010 at 6:44 AM, Hogan, Aidan <[email protected]>
> wrote:
> > Hi folks,
> >
> > Firstly, warm thanks for exporting RDF/XML. I've had a look at some
of
> > the FOAF/SIOC exports and I can safely say that you've done a very
nice
> > job.
> >
> > There's one small problem though that it would be great to see
fixed. It
> > seems that for users who don't enter an email, you export the value
[1]
> > for mbox_sha1sum: the sha1 of the 'mailto:' string. Sample documents
> > include [2,3]. This is problematic for reasons discussed in [4].
> > Ideally, if you don't have the email for a user, you should just
omit
> > the foaf:mbox_sha1sum value.
> >
> > If you've any questions, please don't hesitate to ask.
> >
> > (CC'd are the pedantic-web group who co-ordinate efforts on
improving
> > the quality of RDF published on the Web - http://pedantic-web.org/)
> >
> > Cheers,
> > Aidan
> >
> > [1] 08445a31a78661b5c746feff39a9db6e4e2cc5cf
> > [2] http://identi.ca/whataboutbob/foaf
> > [3] http://www.opensourcetweet.com/manishmittal/foaf
> > [4] http://pedantic-web.org/fops.html#ifps
> > _______________________________________________
> > StatusNet-dev mailing list
> > [email protected]
> > http://lists.status.net/mailman/listinfo/statusnet-dev
> >
> 
> 
> 
> --
> James Walker :: http://walkah.net/ :: http://james.status.net/
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to