Convert remaining documents to publish

[ronaldtse]

• Convert to Metanorma to publish in CalConnect format cc-cal-resource-vcard#2
• Convert to Metanorma to publish in CalConnect format cc-caldav-sync#2
• Convert to Metanorma to publish in CalConnect format cc-caldav-attachments#2
• Convert to Metanorma to publish in CalConnect format cc-calendar-dev-resources#2
• Convert to Metanorma to publish in CalConnect format cc-collection-query#2
• Convert to Metanorma to publish in CalConnect format cc-event-publishing-extensions#2
• Convert to Metanorma to publish in CalConnect format cc-vcard-objectclass#2
• Convert to Metanorma format cc-vpatch#1
• Convert to Metanorma to publish in CalConnect format cc-icalendar-vinstance#2
• Convert to Metanorma to publish in CalConnect format cc-ischedule#2
• Convert to Metanorma to publish in CalConnect format cc-jscalendar#2
• (SKIP) Convert to Metanorma to publish in CalConnect format cc-jscontact#2
• Convert to Metanorma to publish in CalConnect format cc-server-info#2
• Convert to Metanorma to publish in CalConnect format cc-serverside-subscriptions#2
• Convert to Metanorma to publish in CalConnect format cc-streaming-cal-contacts-data#2
• Convert to Metanorma to publish in CalConnect format cc-vcard-schedulable#2
• Convert to Metanorma to publish in CalConnect format cc-valarm-extensions#2
• (SKIP, already done) Convert to Metanorma to publish in CalConnect format cc-dst-recommendations#3

For all of these documents, we need to create a CalConnect version with a document number. We will follow the table below in assigning their numbers.

Document Number	Document Title	Original Link	Thematic Category	Publication Date
CC 51012:2017	CalDAV Synchronization Protocol	GitHub	Calendaring & Scheduling	2017-02-12
CC 51013:2019	CalDAV Attachments Specification	GitHub	Calendaring & Scheduling	2019-01-01
CC 51014:2016	iCalendar Virtual Instances	GitHub	Calendaring & Scheduling	2016-10-28
CC 51015:2020	JSCalendar Format Standard	GitHub	Calendaring & Scheduling	2020-10-16
CC 51016:2018	Streaming Calendaring/Contacts Data	GitHub	Calendaring & Scheduling	2018-08-01
CC 51017:2024	VALARM Extensions for iCalendar	GitHub	Calendaring & Scheduling	2024-07-23
CC 51019:2018	Calendar Developer Resources Guide	GitHub	Calendaring & Scheduling	2018-02-03
CC 51020:2019	Collection Query Mechanism	GitHub	Calendaring & Scheduling	2019-05-30
CC 51021:2021	Event Publishing Extensions	GitHub	Calendaring & Scheduling	2021-03-26
CC 51022:2016	Server Information Schema	GitHub	Calendaring & Scheduling	2016-04-01
CC 51023:2022	Server-Side Subscriptions	GitHub	Calendaring & Scheduling	2022-05-18
CC 58011:2013	Schedulable vCard Extensions	GitHub	vCard/vObject	2013-01-01
CC 58012:2013	Calendaring Resource vCard Extensions	GitHub	vCard/vObject	2013-01-01
CC 58013:2013	vCard Object Class Definitions	GitHub	vCard/vObject	2013-01-01
CC 58020:2016	vPatch for vCard/iCalendar	GitHub	vCard/vObject	2016-10-28

@anermina will handle this. Thanks!

[ronaldtse]

I'm retro-assigning the numbers in these themes:

• 51xxx => Calendar and scheduling
• 58xxx => vCard/vObject

[ronaldtse]

Instructions for building a Metanorma repository for CalConnect document

This is how I used VSCode with Cline to automate this process with Claude Sonnet 3.5. But it will change and/or make up additional content, so you must manually review the content!!

This is the reference change set:

• feat: create metanorma version cc-vcard-schedulable#3

1. Copy the following files from the source repository (cc-vcard-schedulable) to the target repository:

• metanorma.yml
• README.adoc
• sources/*
• .github/workflows
• Gemfile

2. Keep the original files in reference-docs/
3. Look up the above table for the document number.
4. Each document will have a CalConnect and an IETF version.

• Rename the CC version of source/cc-xxx.adoc to sources/cc-{docnumber}.adoc
• Rename the IETF version to the correct short name sources/draft-{name}.adoc

I've used the following prompts:

To convert:

Convert the file reference-docs/draft-*.xml into the format of sources/cc-56010.adoc (rename to 58012) (CalConnect version) and sources/draft-*.adoc (IETF version) in the Metanorma source format.

Both documents are built with content files shared between them at sources/sections/*.adoc. The IETF version has two overridden files at sources/sections-ietf/*.adoc. The differences are: (1) CalConnect version has an Introduction, while the IETF has an Abstract; (2) CalConnect mandates Scope at 1, Normative references in 2, Terms in 3. (3) CalConnect has Normative references in Clause 2 and a Bibliography (informative references) at the end. IETF has an appendix called "References" that contains a subclause "Normative References" and "Informative References". Update metanorma.yml and README.adoc to suit the contents of this updated repository, and retain the structure of README.adoc but only change the title, filenames, abstract.

To verify:

Verify that the IETF document sources/draft-*.adoc with all the includes ends up generating identical content to `reference-docs/*.xml.

Then:

1. Manually verify the source code to see if the content is 100% accurate. Claude does hallucinate and make up/change stuff even though it is correct in many cases.
2. Manually run metanorma site generate to see if it builds, and fix it.
3. Make a PR to push it