OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

icom message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Groups - Event "ICOM TC Meeting" modified


Event Title: ICOM TC Meeting

Date: Wednesday, 18 July 2012, 11:30am - 12:30pm ET
Description

Please sign on to ICOM TC chat room   

http://webconf.soaphub.org/conf/room/ICOM-TC

ICOM TC Meeting Conference Call

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)
 


This meeting counts towards voter eligibility.

Agenda

1. Roll Call: Please record your attendance at the meeting.

2. Minutes of the meeting on July 11.

3. Brief report by Ken Baclawski on public review of committee specification
draft.  The tickets were requested last week, and a notice of the public review
should be distributed in a few days.

4. Java.net articles.  Part 1 of the OpenICOM article series is at
http://today.java.net/article/2011/03/21/openicom-jpa-framework-integrated-collaboration-environments-part-1.
The title of the article was “OpenICOM: A JPA Framework for Integrated Collaboration Environments, Part 1.”

Eric has suggested the following sequels to part 1 (exact titles will be part of the discussion):

OpenICOM: ICOM UML Model and JPA POJO Representation, Part 2

OpenICOM: ICOM OWL DL and JPA POJO transformations, Part 3

OpenICOM: ICOM RDF Model, Part 4

Some issues are: Who should be included as authors?  What sections would each
contributor be working on?  What should the titles be?

5. Issues for the translation to OWL as part of ICOM v2 and for the java.net article series.
 (a) bi-directional relationships: how should they be specified in the standards document?
 (b) ambiguities: icom_content:Attachment is ambiguous. Should there be a policy for these?
 (c) disjointness conditions: how should they be specified?
 (d) modules: The modules do not coincide with the namespaces.
 (e) description: The description is out of date with the rest of the standard.
 (f) annotation properties for relating classes and properties with their metadata.
 (g) additional property type "Any".

6. If there is time, plan for ICOM v2 to define social network model. (see the TC Charter http://www.oasis-open.org/committees/icom/charter.php)

7. As time allows, continue discussion of the goals of the TC and plans for dissemination.

8. AOB
 



Owner: Ken Baclawski
Group: OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC
Sharing: This event is shared with the OASIS Open (General Membership), and General Public groups. Public Event Link
BEGIN:VCALENDAR
CALSCALE:GREGORIAN
METHOD:PUBLISH
VERSION:2.0
PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
CATEGORIES:MEETING
STATUS:CONFIRMED
TRANSP:OPAQUE
DTSTAMP:20120717T000000Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20120718T113000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20120718T123000
SEQUENCE:1
SUMMARY:ICOM TC Meeting
DESCRIPTION:\n	Please sign on to ICOM TC chat room  
  \n	\n	http://webconf.soaphub.org/conf/room/ICOM-TC\n	\n	ICOM
  TC Meeting Conference Call\n\n	InterCall Conference id:
  9128348\n	\n	InterCall Password: ICOMTC (426682)\n	\n	From
  the AMER region dial:\n	\n	                +1
  866-682-4770\n	\n	                +1 408-774-4073\n	\n	From
  the EMEA region dial:\n	\n	                +44 (0)
  2081181001 (UK)\n	\n	                +44 (0) 8444936817
  (UK)\n	\n	                +353 (0) 1 247 5650 (Dublin)\n	\n	
                 +33 (0) 176728936  (Paris)\n	\n	From the APAC
  region dial:\n	\n	                +61 2 8064 0613
  (Australia)\n	 \n\nAgenda: \n	1. Roll Call: Please record
  your attendance at the meeting.\n	\n	2. Minutes of the
  meeting on July 11.\n	\n	3. Brief report by Ken Baclawski on
  public review of committee specification\n	draft.  The
  tickets were requested last week\, and a notice of the
  public review\n	should be distributed in a few days.\n	\n	4.
  Java.net articles.  Part 1 of the OpenICOM article series is
  at\n	http://today.java.net/article/2011/03/21/openicom-jpa-framework-integrated-collaboration-environments-part-1.\n	The
  title of the article was &ldquo\;OpenICOM: A JPA Framework
  for Integrated Collaboration Environments\, Part
  1.&rdquo\;\n	\n	Eric has suggested the following sequels to
  part 1 (exact titles will be part of the
  discussion):\n	\n	OpenICOM: ICOM UML Model and JPA POJO
  Representation\, Part 2\n	\n	OpenICOM: ICOM OWL DL and JPA
  POJO transformations\, Part 3\n	\n	OpenICOM: ICOM RDF
  Model\, Part 4\n	\n	Some issues are: Who should be included
  as authors?  What sections would each\n	contributor be
  working on?  What should the titles be?\n	\n	5. Issues for
  the translation to OWL as part of ICOM v2 and for the
  java.net article series.\n	 (a) bi-directional
  relationships: how should they be specified in the standards
  document?\n	 (b) ambiguities: icom_content:Attachment is
  ambiguous. Should there be a policy for these?\n	 (c)
  disjointness conditions: how should they be specified?\n	
  (d) modules: The modules do not coincide with the
  namespaces.\n	 (e) description: The description is out of
  date with the rest of the standard.\n	 (f) annotation
  properties for relating classes and properties with their
  metadata.\n	 (g) additional property type
  &quot\;Any&quot\;.\n	\n	6. If there is time\, plan for ICOM
  v2 to define social network model. (see the TC Charter
  http://www.oasis-open.org/committees/icom/charter.php)\n	\n	7.
  As time allows\, continue discussion of the goals of the TC
  and plans for dissemination.\n	\n	8. AOB\n	 \nGroup: OASIS
  Integrated Collaboration Object Model for Interoperable
  Collaboration  Services (ICOM) TC\nCreator: Ken Baclawski
URL:https://www.oasis-open.org/apps/org/workgroup/icom/event.php?event_id=33326
UID:https://www.oasis-open.org/apps/org/workgroup/icom/event.php?event_id=33326
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]