CREATE-1a

This example is just like CREATE-1 except that that the RELCALID of the
calendar we are trying to create is not specified.  In this case, the CAP
server assigns the RelativeCalUID to the newly created calendars. So, the
calendar can be successfully created in multiple containers on the same CS.

C: 10 SENDDATA
S: 10 2.0.1
C: CONTENT-TYPE: text/calendar;method=create;component=VCOMMAND
C: Content-Transfer-Encoding:7bit
C:
C: BEGIN:VCALENDAR
C: VERSION:2.1
C: BEGIN:VCOMMAND
C: METHOD:CREATE;VCALENDAR;cap://cal.example.com/,relcal4,://bobo.ex.com/,relcal5,cap://cal.example.com/relcal8,relcal9
C: BEGIN:VCALENDAR

    # The "RELCALUID" property is not specified in this example.

C: NAME:CHARSET=us-ascii;LANGUAGE=EN-us:Bill's Soccer Team
C: OWNER:capcar:bill
C: OWNER:capcar:mary
C: CALMASTER:mailto:bill@example.com
C: PREFERRED-TZID:US_PST
C: BEGIN:VCAR
C: CARID:12345
C: GRANT;CN="Bill Jones":principal=capcar:bill;action=ALL;object=all
C: GRANT;cn="Mary Jones":principal=capcar:mary;action=read;object=all
C: END:VCAR
C: END:VCALENDAR
C: END:VCOMMAND
C: END:VCALENDAR
C: .
S: 10 6.0 cap://cal.example.com/
S: 10 2.0 cap://cal.example.com/relcal4 cap://cal.example.com/rand1234
S: 10 3.1.4 cap://bobo.ex.com/
S: 10 6.2 cap://cal.example.com/relcal5
S: 10 3.1.5 cap://cal.example.com/relcal8
S: 10 2.0 cap://cal.example.com/relcal9 cap://cal.example.com/rand4567

    # This example differs from the Create1 example in that the calendar was
    # succesfully created on relcal9.  This is because in the other example we
    # tried to create multiple calendars with the same RelativeCalUID. But in
    # this case, the server to assigned the RelativeCalUIDs for the new
    # calendars.