For
discussions in the TC meeting today, I have gathered the main definitions of
SIOC ontology and Beehive Object Model.
Definitions
of SIOC Community, Site, Space from http://www.w3.org/Submission/sioc-spec/:
Class: sioc:Community
Community
- Community is a high-level concept that defines an online community and what
it consists of.
A
Community may consist of different types of objects (people, sites, etc.)
joined by a common topic, interests or goals.
A
Community is different from a Site: a Site describes a single community site
whilst a Community can consist of a number of Sites and other resources
described in SIOC or other ontologies (e.g., FOAF). Community is linked to its
constituent parts using the property dcterms:hasPart.
Class: sioc:Site
Site - A Site can be
the location of an online community or set of communities, with Users and
Usergroups creating Items in a set of Containers. It can be thought of as a
web-accessible data Space.
|
sub-class-of: |
|
|
in-range-of: |
|
|
in-domain-of: |
A Site is
the location of an online community or set of communities, with Users in
Usergroups creating content therein. While an individual Forum or group of
Forums are usually hosted on a centralised Site, in the future the concept of a
"site" may be extended (for example, a topic Thread could be formed
by Posts in a distributed Forum on a peer-to-peer environment Space).
Class: sioc:Space
Space - A Space is a
place where data resides, e.g., on a website, desktop, fileshare, etc.
|
in-range-of: |
|
|
in-domain-of: |
A Space
is defined as being a place where data resides. It can be the location for a
set of Containers of content Items, e.g., on a Site, personal desktop, shared
filespace, etc. Any data object that resides on a particular Space can be
linked to it using the sioc:has_space property.
Definitions
of Beehive Community, Workspace, Scope from http://www.oracle.com/technology/products/beehive/pdf/beehiveobjectmodel_icom.pdf
Entity ::= Scope
Addressable ::= Scope
Scope =>
[Template] :
Ref Template,
[Description] :
richtext,
RoleDefinitions :
{PartRef RoleDefinition},
AssignedRoles :
{PartRef AssignedRole},
Groups :
{PartRef Group},
A scope is a logical region or
neighborhood in the universe of entities. The scope contains the roles and
groups. The scope also contains the library of markers. As a container, the
scope can contain templates, workflows, etc., to define the administrative
boundary.
Scope ::= Community
Community =>
Actors :
{PartRef Actor},
Agents :
{PartRef Agent},
Organizations
:
{PartRef Organization},
Workspaces :
{PartRef Workspace}
A community is a set of actors
and agents that share a common set of workspaces and are governed by a common
set of policies.
Community ::= Enterprise
Enterprise => ;
Community ::= Organization
Organization =>
Parent :
getParent():Community
An organization is a sub-space
under an enterprise. Organizations can be nested to form hierarchies.
Administrative policies associated with parent organizations flow down into
child organizations and workspaces.
Scope ::= Workspace
Workspace =>
[Description] :
richtext,
Elements :
{Part Folder},
Parent :
getParent():Community,
[Trash] :
Part Trash,
[Inbox] :
getInbox():Folder,
[DefaultCalendar] :
getDefaultCalendar():Calendar,
[DefaultTaskList] :
getDefaultTaskList():TaskList,
[DefaultAddressBook] :
getDefaultAddressBook():AddressBook,
[DefaultConference] :
getDefaultConference():Conference,
[ReminderList] :
getReminderList():Folder,
[SubscriptionList] :
getSubscriptionList():Folder,
[NotificationList] :
getNotificationList():Folder
A workspace is a scope that
defines a logical scope of work for users. All workspaces must have a name (the
Name attribute from Entity is not optional). Each workspace is addressable
individually (and they may have a variety of ways of being addressed). Every
workspace is created from a template that specifies an initial configuration
for the workspace. Changes to the template can propagate to existing workspaces
created from that template.
Regards,
Eric
From: Eric Chan
Sent: Tuesday, June 09, 2009 11:43 AM
To: icom@lists.oasis-open.org
Subject: Agenda for ICOM TC Meeting on June 10, 9:00 - 10:00 AM PST
Agenda
1.
Roll Call
2.
Approve draft minutes from May 13 and 27 TC Meetings
http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/200906/msg00000.html
http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/200905/msg00003.html
3.
Discuss to reconcile Beehive object model of workspace
(Figures 1 and 2) and SIOC ontology (Figure 3) to define the ICOM workspace
4.
Discuss the feasibility of JPA and Jenabean prototypes
for ICOM
5.
AOB
Please sign on to ICOM TC chat room http://webconf.soaphub.org/conf/room/ICOM-TC Biweekly ICOM TC Meeting Conference Call Info:Date: Wednesday, 10 June, 2009Time: 09:00am - 10:00am PST Event Description: Meeting id: 451034 Meeting Password: ICOMTC (426682) From the AMER region dial: +1 888-967-2253 +1 650-607-2253 From the APAC region dial: +61 2 8817 6100 From the EMEA region dial: +44 1189249000 +353 1 803 3333 Sponsor: Oracle
Figure 1 Beehive
Object Model of Community
Figure 2 Beehive Object
Model of Workspace
Figure 3 SIOC Ontology
Best regards,Eric