Rescheduled: CMIS Atom WG (con't) (Jun 12 08:00 AM PDT in 877 421 0029 pc433623)

[Al Brown <albertcbrown@us.ibm.com>]

BEGIN:VCALENDAR
X-LOTUS-CHARSET:UTF-8
VERSION:2.0
PRODID:-//Lotus Development Corporation//NONSGML Notes 8.5.1//EN_S
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Pacific
BEGIN:STANDARD
DTSTART:19501105T020000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19500312T020000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID="Pacific":20090612T080000
DTEND;TZID="Pacific":20090612T090000
TRANSP:OPAQUE
DTSTAMP:20090609T155628Z
SEQUENCE:1
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;CN="Al Brown/Costa Mesa/IBM"
 ;RSVP=FALSE:mailto:albertcbrown@us.ibm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE
 :mailto:cmis@lists.oasis-open.org
CLASS:PUBLIC
DESCRIPTION;ALTREP="CID:<FFFF__=07BBFF43DFC417158f9e8a93df938@us.ibm.com>":D
 iscuss XSDs + hierarchy\n\nOn hierarchy\, the atom community seems to 
 have consensus that the generic inlining is useful.  It is also useful
  for CMIS for non-hierarchy.  For example\, as a mechanism to include 
 allowable actions or relationships.  Since that will probably be adopt
 ed\, it probably makes more sense to leverage that mechanism than crea
 te a different simpler/less verbose mechanism.
SUMMARY:CMIS Atom WG (con't)
LOCATION:877 421 0029 pc 433623\nuk 0808 234 1969\nde 0800 181 6323\nc
 h 0800 564 331
ORGANIZER;CN="Al Brown/Costa Mesa/IBM":mailto:albertcbrown@us.ibm.com
UID:364DB33269790A98882575CF0062ADE9-Lotus_Notes_Generated
X-LOTUS-BROADCAST:FALSE
X-LOTUS-UPDATE-SEQ:1
X-LOTUS-UPDATE-WISL:$L:1;$B:1;$R:1;$E:1;$W:1;$O:1;$M:1;$S:2
X-LOTUS-NOTESVERSION:2
X-LOTUS-NOTICETYPE:U
X-LOTUS-APPTTYPE:3
X-LOTUS-CHILD_UID:04CF030D620AE976882575D000579185
END:VEVENT
END:VCALENDAR
Discuss XSDs + hierarchy

On hierarchy, the atom community seems to have consensus that the generic inlining is useful.  It is also useful for CMIS for non-hierarchy.  For example, as a mechanism to include allowable actions or relationships.  Since that will probably be adopted, it probably makes more sense to leverage that mechanism than create a different simpler/less verbose mechanism.

c095640.ics