progress on MeetingRecords, trouble migrating from cyc:subEvents to sumo:part

Adam, calendar folks,

Calendars have a certain overlap with
  http://esw.w3.org/topic/MeetingRecords

Charles and I were talking about representing action items
as ical:Vtodo objects.

I started in that direction...
I adopted some conventions when writing up
the minutes...
   http://www.w3.org/2001/sw/DataAccess/ftf3-brs
and then wrote
  http://www.w3.org/2001/sw/DataAccess/grokftf.xsl
which produces
  http://www.w3.org/2001/sw/DataAccess/ftf3-brs-formal

I'm comfortable with cyc's time/event ontology
  http://www.cyc.com/cycdoc/vocab/time-vocab.html
and I started along the lines of
  meeting cyc:subEvents agendum1.
  agendum1 cyc:subEvents decision1_1, action1_2.
  action1-1 tbd:owner fred.

but then I thought revisit the cyc vs sumo issue; I was
happy to find sumo:FormalMeeting, sumo:Resolution and such
using the browser
  http://berkelium.teknowledge.com:8080/sigma/index.html
linked from the (apparent) SUMO home page...
  http://ontology.teknowledge.com/

and I tried replacing
  meeting cyc:subEvents agendum1.
with
  meeting sumo:part agendum1.

only to realize that sumo:part goes the other way:

  ?PART sumo:part ?WHOLE.

This is inside-out w.r.t. using XSLT to go from
XHTML to RDF/XML. I disocvered several other
ways in which sumo doesn't follow the
  http://esw.w3.org/topic/RoleNoun
convention; e.g. sumo:title and sumo:names
go the other way; that rubs hard against RDF's limitation
regarding literals in the subject position.

I don't know whether it's feasible to change SUMO in this respect;
I can imagine that would be a lot of work and disruption.
But it would make working with SUMO in RDF/XML much nicer.

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E