| From | Sent On | Attachments |
|---|---|---|
| Eric Chan | Oct 9, 2009 12:26 pm |
| Subject: | [icom] Draft Minutes of ICOM TC Meeting, September 30, 2009 | |
|---|---|---|
| From: | Eric Chan (eric...@oracle.com) | |
| Date: | Oct 9, 2009 12:26:30 pm | |
| List: | org.oasis-open.lists.icom | |
Minutes of ICOM TC Meeting, September 30, taken by Eric S. Chan
Agenda
1. Roll Call
2. Review the OO and RDF model
3. AOB
1. The following eligible members were present
Deirdre Lee
Laura Dragan
Rafiul Ahad
Eric Chan
2. Review the OO and RDF model
The participants reviewed two open issues from the September 16 TC meeting:
1. how to represent abstract class and interface in RDF
2. how to interpret the distinguished properties inherited from super-classes in
RDF.
Deirdre and Laura would explore the following two ideas:
For issue 1, introduce an RDF schema extension to declare certain RDF classes as
abstract class to emulate the notions of abstract class and interface in UML.
Examples of abstract classes in the proposal are Entity, Scope, Subject, and
Artifact. Examples of interfaces are Parental, Container, and Accessor. (See
Figure 1 of http://wiki.oasis-open.org/icom/Categorisation).
For issue 2, introduce an RDF schema extension to declare certain RDF properties
as abstract property, analogous to the notion of abstract class for issue 1. For
example, hasElementOfFolder is an abstract property to be overridden by concrete
properties such as hasElementOfHeterogeneousFolder, hasElementOfCalendar,
hasElementOfAddressBook, etc. Any instance of hasElementOfFolder property must
also be an instance of one of the concrete sub-properties. Through some axioms
for abstract property, the hasElementOfCalendar property can be the only
property applicable to Calendar. Thus we can restrict the elements of Calendar
to the range of hasElementOfCalendar property. Similarly, the elements of
AddressBook can be restricted to the range of hasElementOfAddressBook property.
3. AOB
The meeting was adjourned.





