Thanks for the updates, Aidan. Keep us posted - we definitely want to make sure we are offering high quality feeds / data in as many formats as possible!
Cheers, James On Tue, May 18, 2010 at 6:33 PM, Hogan, Aidan <aidan.ho...@deri.org> wrote: >> 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'. > > @James/StatusNet: my apologies! I've just realised that you don't ever > explicitly reference sioc:User. The problem is with the SIOC vocabulary > itself. This requires no action from you... sorry again ;) > >> 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> > > Just to follow up on this, after discussion with Dan (who will hopefully > correct me if I'm wrong) he would recommend use of the 'accountProfilePage' > URI to actually identify the OnlineAccount, à la: > > <OnlineAccount rdf:about="http://identi.ca/segphault";> > <accountServiceHomepage > rdf:resource="http://identi.ca/";></accountServiceHomepage> > <accountName>segphault</accountName> > <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> > > From my own perspective, I agree that this is perhaps the simplest solution, > giving a very succinct and natural means of using > foaf:account/foaf:OnlineAccount (esp. in RDFa), and more generally removing > the headache of creating a new URI for an OnlineAccount. > > Perhaps one thing that slightly concerns me is when SIOC is considered... In > the above usage, an foaf:OnlineAccount could be informally considered as a > subclass of foaf:Document. Since sioc:UserAccount is a subclass of > foaf:OnlineAccount, this means that you could have statements such as: > > <profileDocA> sioc:follows <profileDocB> . > > ...which seems to me a little bit strange. Again, this is only when including > SIOC into the frame. > > @James/StatusNet, to summarise, this is perhaps not such a clear cut case so > I can't distil a final recommendation. Again, no urgent action required, and > again nice work ;). > > Cheers, > Aidan > -- James Walker :: http://walkah.net/ _______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
