Re: FW: Major change to a SIOC term: User is now called UserAccount

This has a knockon effect, which could create new confusion.

Now the creator of a message is a UserAccount.  But this is not sensible.
Accounts do not create messages, User's create messages. A User has a
relationship with an account, e.g. AccountHolder.

There may be confusion between DC-Creator whose domain presumably does not
include Accounts.

Also, is there an OWL Equivalent Class between the depracated class and the
new one, or is one expected to make code changes to handle this?  In some
cases, it may not be practical to change code, e.g. if it is from a vendor.


On Thu, Mar 25, 2010 at 3:43 AM, Breslin, John <>wrote:

> -----Original Message-----
> From: John Breslin []
> Sent: 25 March 2010 10:11
> To: SIOC-Dev
> Subject: Major change to a SIOC term: User is now called UserAccount
> >From
> As per recent discussions on the SIOC developers mailing list and
> requests from many parties requesting clarification of the term
> sioc:User (which has oft been confused with foaf:Person), we are happy
> to announce that the new term sioc:UserAccount  has been added to the
> ontology in replacement of the now-deprecated sioc:User term (in
> revision 1.35 of the SIOC ontology).
> The SIOC specification has been updated accordingly, and knock-on
> effects to SIOC modules have been corrected.
> *We would ask all application maintainers to update your code to
> reflect this change, i.e., replace User with the new term
> UserAccount.*
> We have updated the various figures showing the connections internally
> between SIOC terms, and also between SIOC, FOAF and SKOS.
> Please discuss this change on this thread.
> Thanks!

Received on Tuesday, 30 March 2010 19:27:19 UTC