Hello all,
I attached two UML diagrams that
show the mappings between ICOM ontology and FOAF + SIOC ontologies for the use
case described in Deirdre’s email. I will provide another UML diagram to
describe the access control scenario in the use case.
Regards,
Eric
From: Lee, Deirdre
[mailto:Deirdre.Lee@deri.org]
Sent: Friday, June 04, 2010 7:03 AM
To: Eric Chan; icom@lists.oasis-open.org
Subject: RE: [icom] Agenda for ICOM TC Meeting on June 2, 9:00 - 10:00
AM PDT
Hi all,
Here is the updated version of
the scenario, the new paragraph in yellow deals with access-control, forums,
and messaging. Laura and I shall look into how this can be modeled using the
RDF ICOM model.
Regards,
Deirdre
-----------------------------------------------------------------------
Deirdre Lee
DERI
IDA BusinessPark, Lower Dangan,
Galway, Ireland
deirdre.lee@deri.org
skype: deirdrelee
+353 91 495336
-----------------------------------------------------------------------
From: Eric Chan
[mailto:eric.s.chan@oracle.com]
Sent: 02 June 2010 16:56
To: Eric Chan; icom@lists.oasis-open.org
Subject: RE: [icom] Agenda for ICOM TC Meeting on June 2, 9:00 - 10:00
AM PDT
Agenda item: Review the proposal
for new classes in the subject branch.
a)
ICOM includes the concept of Actor of a site. An ICOM
Actor is a FOAF Person who has one or more user accounts for the site in
question. In other words, the ICOM actors of a site are a subset of the FOAF
persons in a federation of sites. We can define the ICOM Person, which is
similar to FOAF Person. We can also define the ICOM ExternalPerson of a site to
complement the ICOM Actor. The ICOM Person is the union of the two disjoint
sets: Actor and ExternalPerson. External persons are FOAF persons who
don’t have user accounts for the site in question.
b)
A FOAF Agent can have ID’s such as skypeID,
msnChatID, icqChatID, yahooChatID, aimChatID, and jabberID. These are addresses
that can be represented by URI’s. The different types of ID’s can
be represented by URI schemes, for example “xmpp:”,
“skype:”, “msn:”, “icq:”,
“yahoo:”, “aim:”, “jabber:”, etc. The
mbox property of FOAF Agent can also be represented by the URI for
“mailto:” scheme. ICOM defines the concept of Addressable to
represent the entities that possess one or more URI addresses. The ICOM
Actor, Group, ExternalPerson, and BookableResource shall be subclasses of
Addressable, so that they can possess the FOAF ID’s and mbox properties.
c)
An ICOM Actor can have a personal space and the default
inbox in the personal space to receive the messages sent to any of the
addresses of the actor. Thus ICOM ontology extends the FOAF ontology by
associating the folders to receive the messages sent to the FOAF ID’s and
mbox.
d)
We can introduce ICOM Agency to represent the FOAF
Organization (a subclass of FOAF Agent) which is not a Person. The
organizations, such as DERI, Oracle, Cisco, OASIS, can each be represented by
an ICOM Agency. ICOM Agency is a subclass in the ICOM Subject branch.
e)
DERI can be also represented by an instance of ICOM
Community. The DERI community can hold the default space and inbox for messages
sent to DERI agency. Furthermore, this DERI community can be a container of
employees and students spaces as well as project spaces. The ICOM
Community and Space are subclasses of Addressable.
f)
The proposals d) and e) imply that an organization such
as DERI or Oracle can each be represented by two individuals, one individual is
of type ICOM Agency and another individual is of type ICOM Community. The DERI
agency is a subject (one which as an mbox address) whereas DERI community is a
container (one which has a space and inbox to hold the messages delivered to
DERI’s mbox address).
g)
We can introduce a separate concept called
PhysicalLocation to represent the physical addresses, such as street addresses,
P.O. boxes, and GPS locations. We will not represent the physical addresses by
URI’s. URI’s will represent the Internet addresses such as the FOAF
ID’s and mbox.
h)
ICOM Group can represent the FOAF Group.
i)
ICOM Artifact can represent the FOAF Document. The
foaf:PersonalProfileDocument can be represented by artifacts in the
actor’s personal space. The Person’s workplaceHomepage can refer to
the profile document of a community representing the person’s
organization.
Regards,
Eric
From: Eric Chan
Sent: Wednesday, June 02, 2010 12:43 AM
To: icom@lists.oasis-open.org
Subject: [icom] Agenda for ICOM TC Meeting on June 2, 9:00 - 10:00 AM
PDT
Agenda
1. Roll Call
2. Approve draft minutes from May 12, 19, and 26 TC
Meetings
http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/201005/msg00004.html
http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/201006/msg00000.html
http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/201006/msg00001.html
3. Mapping between ICOM and SIOC+FOAF ontologies
4. ICOM use cases for the workshop
5. AOB
Please sign on to ICOM TC chat room
http://webconf.soaphub.org/conf/room/ICOM-TC
ICOM TC Meeting Conference Call
Date: Wednesday, 2 June, 2010
Time: 09:00am - 10:00am PDT
InterCall Conference id: 9128348
InterCall Password: ICOMTC (426682)
From the AMER region dial:
+1 866-682-4770
+1 408-774-4073
From the EMEA region dial:
+44 (0) 2081181001 (UK)
+44 (0) 8444936817 (UK)
+353 (0) 1 247 5650 (Dublin)
+33 (0) 176728936 (Paris)
From the APAC region dial:
+61 2 8064 0613 (Australia)
For your local numbers, please check additional global
access numbers listed at http://www.intercall.com/oracle/access_numbers.htm
