Draft Minutes of ICOM TC Meeting, October 12, 2011

[Eric Chan <eric.s.chan@oracle.com>]

Minutes of ICOM TC Meeting, October 12, taken by Eric S. Chan

 

Agenda

1. Roll Call

2. Approve draft minutes of TC Meetings on September 14 and 28.

3. Review and schedule ballot for CSPRD02, RDF ontology, and UML annotated Java classes

4. Discuss formal declaration of namespace URI’s in RDF and JAXB (see addendum below)

5. AOB

 

1. The following eligible members were present

 

Laura Dragan

Patrick Durusau

Peter Yim

Eric Chan

 

2. Approve draft minutes of TC Meetings on September 14 and 28.

 

 Approved.

 

3. Review and schedule ballot for CSPRD02, RDF ontology, and UML annotated Java classes

 

Discussed about under-specifying RDFS Property Definitions for some of the properties. For example, we may omit the specification of domain or range for some of the RDFS property definitions so that the definitions can be subsequently extended using owl:unionOf and owl:Restriction. Please refer to the discussion thread in http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/201110/msg00005.html.

 

Reviewed the property definitions that need owl:unionOf and owl:Restriction, such as memberGroup, memberActor, assignedGroup, etc.

 

do not specify domain for memberGroup to allow OWL 2 model to specify the domain more precisely

e.g. memberGroup : (Scope | Group) -> Group 

 

do not specify domain for location to allow OWL 2 model to specify the domain more precisely

e.g. location : (Resource | Presence) -> Location 

 

use different properties for

space: community -> space

personalSpace : User -> Space

resourceSpace : Resource -> Space

 

specify [parent : Entity -> Entity]

                parent : Scope -> Community   (can be specified using owl:restriction in OWL 2 model)

 

specify [element : Container -> Item]

element : Space -> SpaceItem is a restriction where (Space subclassOf Container) and (SpaceItem subclassof Item).

 

Review icom:Contact in relation to vCard; consequence of this analysis:

 

decide whether to re-factor Contact to Contact and PersonContact

 

how to extend vCard property. We may extend vCard properties, which follow a naming convention that is not compatible with Java, i.e. vCard uses a dash “-“ as in given-name, family-name, street-address (see http://www.w3.org/TR/vcard-rdf/). We may let icom properties extend vCard properties, e.g. icom_vcard:familyName can be a sub-property of vcard:family-name.

 

the domain of vCard properties are vCard class. icom:Contact is a counterpart of vCard. icom:Person is not a vCard  but it can use the same properties as icom:Contact , i.e. icom:familyName can be a property of both icom:Contact and icom:Person. Can a property such as icom_vcard:familyName, which is a sub-property of vcard:family-name, be applied to icom:Person when icom:person is disjoint from vCard?

 

 

It is desirable to define Participant, EntityAddress, Location, etc., as blank nodes whenever possible. Rdf blank nodes may work like embedded objects in OO persistent frameworks.

 

4. Discuss formal declaration of namespace URI’s in RDF and JAXB (see addendum below)

 

5. AOB

 

Eric to schedule a TC Meeting in the following week.

 

TC Meeting was adjourned.