This site is maintained by people involved in the development of calendaring and scheduling standards and/or implementations. Although the content contributors are employed by a range of commercial and non-profit organizations, this site does not represent the views or opinions of those organizations.
-
-
Please note that the authors of this site have not made any attempt to confirm support for any of the implementations, products or services listed on this site.
-
-
-
-
-
-
-
-
- Was this page helpful for you? Please give us Feedback.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/CLAUDE.md b/CLAUDE.md
new file mode 100644
index 0000000..d28da09
--- /dev/null
+++ b/CLAUDE.md
@@ -0,0 +1,115 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+CalConnect DEVGUIDE is a Jekyll-based static site providing a developer's guide for calendaring and scheduling standards (iCalendar, CalDAV, CardDAV, vCard, jsCalendar, iTIP, iMIP). The live site is at https://devguide.calconnect.org.
+
+Uses the shared `jekyll-calconnect-theme` gem for layouts, includes, and design tokens. The theme provides Tailwind CSS v4 via Vite, dark mode support, and documentation sidebar styling.
+
+## Build & Serve Commands
+
+- **Install dependencies:** `bundle install && npm ci`
+- **Build the site:** `bundle exec jekyll build`
+- **Local dev server:** `bundle exec jekyll serve`
+- **Build for production:** `JEKYLL_ENV=production bundle exec jekyll build`
+
+Ruby 3.2, Node.js 24. Jekyll 4.3 with jekyll-vite plugin.
+
+## Deployment
+
+- **GitHub Actions** builds and deploys to GitHub Pages on push to `main`
+- **Firebase** hosting config exists in `firebase.json` (redirect rules)
+- The `_site/` directory is the build output (gitignored)
+
+## Site Architecture
+
+### Theme
+
+Uses `jekyll-calconnect-theme` gem (at `../jekyll-calconnect-theme/`). The theme provides:
+- **Layouts**: `base` (HTML shell), `default` (documentation sidebar), `page` (simple wrapper)
+- **Includes**: `head.html` (fonts, critical CSS, Vite), `header.html`/`footer.html` (stubs), `breadcrumbs.html`, `feedback.html`, `google-analytics.html`
+- **SCSS**: `_sass/calconnect/` partials for documentation layout, sidebar nav, typography, dark mode
+- **Frontend JS**: `theme.js` (dark/light toggle), `navigation.js` (mobile menu)
+- **Assets**: Logo SVGs (purple/white)
+
+Local `_layouts/` and `_includes/` files override the theme.
+
+### Content Collections
+
+Two Jekyll collections drive the site:
+
+- **`pages`** (`_pages/`) — Main content sections. Each top-level section has an index `.md` file and a subdirectory with child pages. Permalink: `/:path/`
+- **`appendixes`** (`_appendixes/`) — Supplementary content (Glossary, Standards, Links, Examples). Permalink: `/Appendix/:path/`
+
+### Page Front Matter (Navigation)
+
+- `parent` — Path to parent page (e.g., `"/"` for top-level, `"/iCalendar-Topics"` for children)
+- `order` — Sort order within siblings
+- `mainParent` — Groups pages under a top-level section for sidebar display
+- `parents` — Semicolon-separated breadcrumb trail in `Title:URL` format
+- `childs` — Comma-separated list of child page titles (for active-state highlighting)
+- `layout` — `default`, `page`, `home`, `toc`, `toc-type`, `post`
+
+### Layouts
+
+- `default` → theme's `base` (head, header, main, footer, Vite JS)
+- `page` → `default` (simple max-width container)
+- `home` → `default` (landing page with hero and icon grid)
+- `toc` → `default` (Table of Contents with hierarchical listing)
+- `toc-type` → `default` (section landing page with breadcrumb, content, and sidebar)
+- `post` → `default` (blog-style article)
+
+### CSS / Frontend
+
+- **Tailwind CSS v4** via Vite + jekyll-vite
+- Entry point: `_frontend/entrypoints/application.css` (Tailwind + `@theme` design tokens)
+- JS entry: `_frontend/entrypoints/application.js` (imports theme.js + navigation.js)
+- Fonts: Inter (body) + JetBrains Mono (code), loaded via Google Fonts
+- Dark mode: class-based (`html.dark`), toggled via `theme.js` with localStorage
+
+### Includes
+
+- `head.html` — Overrides theme: DEVGUIDE-specific title and favicon
+- `header.html` — Overrides theme: DEVGUIDE nav links + dark mode toggle
+- `footer.html` — Overrides theme: DEVGUIDE page/appendix links
+- `script.html` — GA4 tracking (production only)
+- `toc-sidebar.html` — Recursive sidebar navigation (front-matter-driven)
+- `toc-entry.html` — Recursive ToC entry renderer
+- `toc-mainPage-placeholder.html` — Renders child links for section landing pages
+
+### Plugin: PlantUML
+
+`_plugins/jekyll-plantuml.rb` provides a `{% plantuml %}` Liquid tag that generates SVG diagrams using `_bin/plantuml.jar`.
+
+## Content Structure
+
+Top-level sections (each is a `_pages/*.md` index + subdirectory):
+
+| Section | Topics |
+|---|---|
+| iCalendar Topics | Best Practices, Dates/Times, History, Recurrences, Validation |
+| CalDAV | Client/Server implementations, libraries, building clients, FAQs |
+| CardDAV | Client implementations |
+| Scheduling | FreeBusy, iTIP, vAvailability, vPoll |
+| Tasks | Introduction, Component |
+| Time Zones | Best Practices, Sources, TZDS |
+| Data Model | Simple Event, UID, Detailed Description |
+| vCard | vCard 4, vCard 5 |
+| jsCalendar Topics | Introduction, Implementations |
+| iMIP | Internet Scheduling |
+| iTIP | iTIP scheduling |
+| Publishing | Publishing calendars |
+| Other Topics | Calendar spam |
+
+## CI Workflows
+
+- **`build_deploy`** — Builds with Jekyll + Vite and deploys to GitHub Pages on push to `main`
+- **`links`** — Runs lychee link checker on built `_site/` HTML
+
+## Conventions
+
+- Content files are Markdown (`.md`) with YAML front matter
+- 2-space indentation, LF line endings, UTF-8 encoding (`.editorconfig`)
+- Pages with `published: false` in front matter are excluded from navigation
diff --git a/Gemfile b/Gemfile
index 50d536c..f831c05 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,36 +1,24 @@
source "https://rubygems.org"
-# Hello! This is where you manage which Jekyll version is used to run.
-# When you want to use a different version, change it below, save the
-# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
-#
-# bundle exec jekyll serve
-#
-# This will help ensure the proper Jekyll version is running.
-# Happy Jekylling!
+
gem "jekyll", "~> 4.3.4"
-# This is the default theme for new Jekyll sites. You may change this to anything you like.
-gem "minima", "~> 2.5"
-# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
-# uncomment the line below. To upgrade, run `bundle update github-pages`.
-# gem "github-pages", group: :jekyll_plugins
-# If you have any plugins, put them here!
+gem "csv"
+gem "base64"
+gem "jekyll-calconnect-theme", "~> 0.2"
+
group :jekyll_plugins do
gem "jekyll-feed", "~> 0.12"
+ gem "jekyll-sitemap"
gem "jekyll-asciidoc"
+ gem "jekyll-vite"
end
-# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
-# and associated library.
+gem "jekyll-archives"
+
platforms :mingw, :x64_mingw, :mswin, :jruby do
gem "tzinfo", ">= 1", "< 3"
gem "tzinfo-data"
end
-# Performance-booster for watching directories on Windows
gem "wdm", "~> 0.1", :platforms => [:mingw, :x64_mingw, :mswin]
-# Lock `http_parser.rb` gem to `v0.6.x` on JRuby builds since newer versions of the gem
-# do not have a Java counterpart.
gem "http_parser.rb", "~> 0.6.0", :platforms => [:jruby]
-gem 'jekyll-archives'
-gem "jekyll-sass-converter", "~> 2.0"
\ No newline at end of file
diff --git a/TODO.new-style/01-push-calconnect-theme-to-github.md b/TODO.new-style/01-push-calconnect-theme-to-github.md
new file mode 100644
index 0000000..786ea5b
--- /dev/null
+++ b/TODO.new-style/01-push-calconnect-theme-to-github.md
@@ -0,0 +1,9 @@
+# 01 - Push calconnect-theme to GitHub
+
+Create the GitHub repo and push the initial commit.
+
+```bash
+cd /Users/mulgogi/src/calconnect/calconnect-theme
+gh repo create calconnect/calconnect-theme --public --description "Shared Jekyll theme gem for CalConnect sites"
+git push -u origin main
+```
diff --git a/TODO.new-style/02-update-devguide-default-branch.md b/TODO.new-style/02-update-devguide-default-branch.md
new file mode 100644
index 0000000..469cb45
--- /dev/null
+++ b/TODO.new-style/02-update-devguide-default-branch.md
@@ -0,0 +1,8 @@
+# 02 - Update DEVGUIDE default branch to main
+
+Change the default branch from `master` to `main` and update workflows to reference `main`.
+
+**Files:**
+- `.github/workflows/build_deploy.yml` — change trigger branch `master` → `main`, change deploy condition `refs/heads/master` → `refs/heads/main`
+- `.github/workflows/links.yml` — already uses `main` (verify)
+- Update remote HEAD: `git push origin main && git remote set-head origin main`
diff --git a/TODO.new-style/03-migrate-standards-calconnect-org.md b/TODO.new-style/03-migrate-standards-calconnect-org.md
new file mode 100644
index 0000000..d62eab5
--- /dev/null
+++ b/TODO.new-style/03-migrate-standards-calconnect-org.md
@@ -0,0 +1,65 @@
+# 03 - Migrate standards.calconnect.org to Tailwind/Vite
+
+Full migration from Materialize CSS to shared calconnect-theme with Tailwind/Vite.
+
+## Node.js tooling to create
+
+| File | Source |
+|---|---|
+| `package.json` | Same as DEVGUIDE (no Vue deps) |
+| `vite.config.ts` | Same as DEVGUIDE (no Vue plugin) |
+| `postcss.config.js` | Copy from DEVGUIDE |
+| `config/vite.json` | Copy from DEVGUIDE (use port 3038) |
+| `_frontend/entrypoints/application.css` | Tailwind v4 with standards-specific `@source` paths + doc-type/stage color `@theme` tokens |
+| `_frontend/entrypoints/application.js` | Copy from DEVGUIDE |
+| `_frontend/js/theme.js` | Copy from calconnect-theme |
+| `_frontend/js/navigation.js` | Copy from calconnect-theme |
+
+## Config updates
+
+- `Gemfile`: add `calconnect-theme` (path:), add `jekyll-vite`, remove `minima`, `rubocop`
+- `_config.yml`: set `theme: calconnect-theme`, add vite/node excludes
+
+## Layouts to rewrite
+
+| Layout | What to do |
+|---|---|
+| `default.html` | Replace with `layout: base` + `{{ content }}` |
+| `document.html` | Keep Liquid logic, replace Materialize classes with Tailwind |
+| `toc-type.html` | Same as DEVGUIDE: Materialize → `.documentation`/`.docs-nav`/`.nav-items` |
+| `toc.html` | `container` → `max-w-4xl mx-auto` |
+| `page.html` | `container` → `max-w-4xl mx-auto py-8 px-4` |
+
+## Includes to rewrite
+
+| Include | What to do |
+|---|---|
+| `head.html` | Replace with Inter/JetBrains Mono, critical CSS, `{% vite_stylesheet_tag %}` |
+| `header.html` | Materialize nav → Tailwind glass navbar with standards links + dark mode toggle |
+| `footer.html` | Materialize footer → Tailwind grid footer |
+| `script.html` | jQuery/Materialize/init.js → `{% vite_javascript_tag %}` + GA |
+| `document.html` | Keep Liquid logic, replace CSS classes for type badges/stage badges/download buttons |
+| `toc-sidebar.html` | `menu-sidebar` → `nav-items` etc. |
+| `find-doc.html` | Update CSS classes |
+| `copyright.html` | Update CSS classes |
+
+## Doc-type/stage colors
+
+Extract from `_sass/_main.scss` SCSS maps and express as Tailwind `@theme` tokens in `application.css`:
+- standard: #0AC442, directive: #540D6E, guide: #D183C9, specification: #65AFFF, report: #3A405A, amendment: #F26430, corrigendum: #C84630, administrative: #BFAE48, advisory: #BD9391
+- proposal: #39A0ED, working-draft: #2D7393, committee-draft: #2A6B7C, draft-standard: #1C7F7A, final-draft: #53C170, published: #069E2D, withdrawn: #004E64, cancelled: #2E382E
+
+## Files to delete
+
+- `_sass/materialize/` (entire directory)
+- `_sass/main.scss`, `_sass/_main.scss`, `_sass/_metanorma-index.scss`
+- `assets/materialize.scss`, `assets/main.scss`, `assets/metanorma-index.scss`
+- `js/jquery.min.js`, `js/materialize.min.js`, `js/init.js`
+- `fonts/roboto/` (if exists)
+
+## Preserve untouched
+
+- `Makefile`, `scripts/`, `src-documents/`, `bib/`, `bibcoll/`, `csd/`, `_input/`
+- `flake.nix`, `flake.lock`, `.envrc`
+- `_data/` (doesn't exist — navigation is hardcoded)
+- CI workflow (`.github/workflows/build_deploy.yml`) — add Node.js setup step
diff --git a/TODO.new-style/04-integrate-theme-into-calconnect-org.md b/TODO.new-style/04-integrate-theme-into-calconnect-org.md
new file mode 100644
index 0000000..66440a6
--- /dev/null
+++ b/TODO.new-style/04-integrate-theme-into-calconnect-org.md
@@ -0,0 +1,31 @@
+# 04 - Integrate theme into calconnect.org
+
+Remove duplicated files now provided by calconnect-theme gem.
+
+## Config updates
+
+- `Gemfile`: add `gem "calconnect-theme", path: "../calconnect-theme"`, remove `minima`
+- `_config.yml`: change `theme: minima` → `theme: calconnect-theme`
+
+## Files to delete (now in theme)
+
+- `_layouts/base.html`
+- `_layouts/default.html`
+- `_layouts/page.html`
+- `_includes/head.html`
+- `_includes/breadcrumbs.html`
+- `_includes/feedback.html`
+- `_includes/google-analytics.html`
+- `_includes/custom-head.html`
+- `_frontend/js/theme.js`
+- `_frontend/js/navigation.js`
+
+## Files to keep (site-specific overrides)
+
+- `_includes/header.html`, `_includes/footer.html`
+- `_includes/news-card.html`, `_includes/script.html`
+- `_layouts/home.html`, `_layouts/category.html`, `_layouts/news-*.html`
+- `_frontend/entrypoints/application.css` (site-specific @source paths)
+- `_frontend/entrypoints/application.js` (Vue news search)
+- `_frontend/components/`, `_frontend/composables/`
+- `_data/`, `vite.config.ts`
diff --git a/TODO.new-style/05-verify-all-sites.md b/TODO.new-style/05-verify-all-sites.md
new file mode 100644
index 0000000..615f32b
--- /dev/null
+++ b/TODO.new-style/05-verify-all-sites.md
@@ -0,0 +1,5 @@
+# 05 - Verify all three sites build
+
+1. **calconnect.org**: `cd calconnect.org && bundle install && npm ci && bundle exec jekyll build` — verify no regressions
+2. **DEVGUIDE**: `cd DEVGUIDE && bundle install && npm ci && bundle exec jekyll serve` — verify sidebar, dark mode, PlantUML, content
+3. **standards.calconnect.org**: `cd standards.calconnect.org && bundle install && npm ci && bundle exec jekyll build` — verify document rendering, doc-type badges, sidebar
diff --git a/_appendixes/Appendixes.md b/_appendixes/Appendixes.md
deleted file mode 100644
index 381dfa3..0000000
--- a/_appendixes/Appendixes.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: toc-type
-title: "Appendixes"
-order: 2
-parent: "/"
-mainParent: "Appendixes"
----
diff --git a/_appendixes/Glossary.md b/_appendixes/Glossary.md
deleted file mode 100644
index 10e65f5..0000000
--- a/_appendixes/Glossary.md
+++ /dev/null
@@ -1,1066 +0,0 @@
----
-layout: toc-type
-title: Glossary of Terms
-parent: "/Appendix/Appendixes"
-mainParent: "Appendixes"
-parents: 'Appendixes:/Appendix/Appendixes'
-order: 1
-published: true
----
-
-# Calendaring and Scheduling Glossary of Terms
-
-This page is an effort to compile, in one location, a common set of terminology with respect to calendaring and scheduling applications and standards. The document incorporates terminology already existing in calendaring standards such as [RFC5545](https://tools.ietf.org/html/rfc5545) (Internet Calendaring and Scheduling Core Object Specification (iCalendar)), [RFC5546](https://tools.ietf.org/html/rfc6646) (iCalendar Transport-Independent Interoperability Protocol (iTIP)), [RFC6047](https://tools.ietf.org/html/rfc6047) (iCalendar Message-Based Interoperability Protocol (iMIP)), [RFC4791](https://tools.ietf.org/html/rfc4791) (Calendaring Extensions to WebDAV (CalDAV)), [RFC6638](https://tools.ietf.org/html/rfc6638) (Scheduling Extensions to CalDAV (CalDAV)), as well as input from members of the Calendaring and Scheduling Consortium (CalConnect).
-
-Some glossary terms may not appear in published standards today. These are common calendaring terms that are included so that everyone refers to components in the same manner.
-
-As new standards evolve, the glossary will serve as a resource for those creating documents so that all the standards share a common set of terms.
-
-Calendaring and scheduling implementers will be able to utilize the glossary to assist them as they read and decipher calendaring standards. Calendaring and scheduling users will be able to use the glossary to help them better understand the terminology deployed by applications written using calendaring standards.
-
-
- Access control is a system which enables an authority (e.g., user or resource administrator) to control access to different entities in a calendar system. Typically vendors create Preference/Settings options to instantiate access control. Terminology varies considerably across products but broadly speaking access control is usually broken into two areas, read access and write access. Vendor terminology used for read access includes: 'read', 'reviewer', 'proxy read', 'viewer', 'see all', and 'see only freebusy'. Vendor terminology for write access includes: 'write', 'editor', 'proxy write', 'proxy', 'manager', 'administrator', 'designate', 'read/create/edit', 'make changes', 'manage', and 'edit'. (Cp. [Delegate](#delegate) and [Designate](#designate) below.)
-
- A list of access control elements that define access control to a particular calendar system entity. (Reference: [RFC3744](https://tools.ietf.org/html/rfc3744) for its use in a WebDAV context.)
-
- Use of the terms alarm, reminder, alert, and notifications vary by implementation and can represent several things.
- They can represent a setting applied to an event by which a user indicates they want a 'notification' to be triggered to 'remind' them about some event or action (cp. [VALARM](#valarm) in [RFC5545](https://tools.ietf.org/html/rfc5545).
- They can also be used to designate the type of 'alert' that serves as the notification (e.g., email message, audible sound, pop-up window). (Reference [RFC4791 (CalDAV)](https://tools.ietf.org/html/rfc4791), [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.6.6), [RFC5546 (iTip)](https://tools.ietf.org/html/rfc5546).)
-
- Specifies the participants or non-participants (e.g., room or resources) for an event. This property in iCalendar can contain multiple attributes specifying additional information, i.e., role, participation status, group membership, delegation, etc. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.6.4.1).)
-
- The process of configuring clients such as mobile devices or desktop applications to access a service, or class of service, with a minimum of input from the user of the device. See also [Autodiscovery](#autodiscovery).
-
- The process used to determine the services provided by a host, or for a domain, including retrieval of the recommended configuration values for those services. The autodiscovery functionality requires the service provider to declare in a standard way which services are available and what their configuration looks like for the requesting user. See also [Autoconfiguration](#autoconfiguration). (Reference: [draft-daboo-aggregated-service-discovery](https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/).)
-
- Extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing and sharing calendar data based on the iCalendar format. Defined by two specifications, the first, [RFC4791 (CalDAV)](https://tools.ietf.org/html/rfc4791), specifies a calendar access protocol that allows Calendar User Agents to access and manage calendar data. The second specification, RFC 6638, specifies a standard way of performing scheduling transactions with iCalendar-based calendar components. This document defines the "calendar-auto-schedule" feature of CalDAV. (Reference: [RFC 4791](https://tools.ietf.org/html/rfc4791), and [RFC 6638](https://tools.ietf.org/html/rfc6638).)
-
- A collection of calendar items such as events, tasks, journal entries, etc. Examples include a person's or group's schedule, resource availability, and event listings. Typically an individual may own multiple calendars based on the same or different services.
-
- A WebDAV collection used to represent a calendar containing a set of calendar object resources. (Reference: [RFC4791](https://tools.ietf.org/html/rfc4791) and [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.4).)
-
- A WebDAV resource representing an iCalendar component typically stored inside a Calendar Collection (cp. Component). (Reference: [RFC4791](https://tools.ietf.org/html/rfc4791).)
-
- A data repository that may contain several calendars as well as properties and components of those calendars. A local calendar store is on the same device as the calendar user agent ([CUA](#calendar-user-agent)). A remote calendar store is not on the same machine/device as the calendar user agent. (Reference: [RFC3283](https://tools.ietf.org/html/rfc3283).)
-
- 1. Software with which the calendar user communicates with a calendar service or local calendar store to access calendar information.
- 2. Software that gathers calendar data on the Calendar User's behalf.
-
- A way to represent dates as a combination of eras, years, months, weeks, and days in formats used in many different parts of the world. A calendar system also defines the limits for those different quantities and how "date arithmetic" can be done to implement repeating dates. (See [Wikipedia:Calendar](http://en.wikipedia.org/wiki/Calendar) for a description of many different calendar systems.)
-
- The Calendaring and Scheduling Consortium is a non-for-profit partnership between vendors of calendaring and scheduling systems and tools, and users of those tools. Our purpose is to improve all aspects of calendaring and scheduling, in particular interoperability. We do this by improving existing standards, developing new standards, offering interoperability testing for calendaring and scheduling systems and tools, collaborating with other organizations with similar goals, and conducting periodic conferences where engineers and customers meet and interact in a collegial atmosphere. Virtually every important calendaring or calendaring-related standard since the late 2000s has been authored, edited and/or coedited by members of a CalConnect Technical Committee.
-
- The IETF mailing list most commonly used for calendaring and scheduling standards development. See the page at [https://www.ietf.org/mailman/listinfo/calsify](https://www.ietf.org/mailman/listinfo/calsify) to join.
-
- An iCalendar property used to identify the calendar system used to represent dates and times within an iCalendar object. iCalendar currently only defines the GREGORIAN calendar system.
-
- CalWS-REST is a CalConnect Proposal and CalWS-SOAP will be a parallel CalConnect Proposal which define an API of basic operations which allow creation, retrieval, update and deletion of calendar objects. In addition, query and freebusy operations are defined to allow efficient, partial retrieval of calendar data. (Reference: CalWS-REST Restful Web Services Protocol for Calendaring.)
-
- Extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing contact information based on the vCard format. (Reference: [RFC6352](https://tools.ietf.org/html/rfc6352)
-
- The process whereby a group comes to agreement on when and perhaps where to hold a meeting or carry out a task, by identifying the "best" time or location to help maximize participation and minimize inconvenience. For more information see 7 Things You Should Know About Consensus Scheduling. (See [VPOLL](#vpoll).)
-
- A response sent by an Attendee of an event to the event Organizer to propose a change to the event or task such as the scheduled date/time, list of participants, etc. (Reference: [RFC5546](https://tools.ietf.org/html/rfc5546))
-
- In common usage 'delegate' may mean either a person who acts for someone else (cp. [Designate](#designate)) or refer to the act of appointing someone as a representative. The term has very specific meaning in the iCalendar and iTIP RFCs. In iCalendar, delegate means to specify that another individual, rather than oneself, should attend an event (cp. [Delegator](#delegator) and [Delegatee](#delegatee)). In iTIP, delegate means to assign ownership of a task to another individual. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.2.4) and [RFC5546](https://tools.ietf.org/html/rfc5546))
-
- The attribute in iCalendar that specifies the calendar user(s) to whom a calendar user has delegated participation in an event. The actual attribute name is DELEGATED-TO. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.2.5).)
-
- The attribute in iCalendar that specifies the calendar user(s) that have delegated their participation in an event to another calendar user. The actual attribute name is DELEGATED-FROM. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.2.4).)
-
- The DTEND property for a VEVENT calendar component specifies the non-inclusive end of the event. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.6.2.2).)
-
- The DTEND property for a VEVENT calendar component specifies the non-inclusive end of the event. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.6.2.2).)
-
- The DTSTART property for a VEVENT specifies the inclusive start of the event. For recurring events, it also specifies the very first instance in the recurrence set. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.6.2.4).)
-
- A calendar object that is commonly used to represent things that mark time or use time. Examples include meetings, appointments, anniversaries, start times, arrival times, closing times.
-
- The process by which public event data is gathered, formatted and distributed to calendar users. Often this takes the form of public, unauthenticated clients and/or feeds. See [Public Event](#public-event).
-
- A list of free and busy periods for a particular calendar user or resource. Primarily used for scheduling resources or meetings with other people. Time periods may be marked as busy, free, busy-unavailable (sometimes referred to as out of office) and busy-tentative.
-
- The Internet Calendaring and Scheduling Core Object Specification. An IETF standard ([RFC5545](https://tools.ietf.org/html/rfc5545)) for a text representation of calendar data. Scheduling operations are specified in [RFC5546](https://tools.ietf.org/html/rfc5546).
-
- According to IETF [RFC3935](https://tools.ietf.org/html/rfc3935), "The IETF has traditionally been a community for experimentation with things that are not fully understood, standardization of protocols for which some understanding has been reached, and publication of (and refinement of) protocols originally specified outside the IETF process ...The mission of the IETF is to produce high quality, relevant technical and engineering documents that influence the way people design, use, and manage the Internet in such a way as to make the Internet work better. These documents include protocol standards, best current practices, and informational documents of various kinds."
-
- An IETF Standard ([RFC5546](https://tools.ietf.org/html/rfc5546)) that specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendar systems without reference to a specific transport protocol so as to allow multiple methods of communication between systems (see [iMIP](#imip), [iSchedule](#ischedule)).
-
- A draft specification that describes how iTIP messages are exchanged via HTTP (Reference: [Internet Calendar Scheduling Protocol (iSchedule) draft-desruisseaux-ischedule](https://tools.ietf.org/html/draft-desruisseaux-ischedule-05).)
-
- A single event of a larger group of events specified as a recurring event (cp. Recurring). (Reference: [RFC4791 (CalDAV)](https://tools.ietf.org/html/rfc4791) and [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.8.4.4).)
-
- A general term from common usage to convey a request for an attendee's participation in an event. In RFC documents the more specific term is request (cp. [Request](#request)).
-
- A draft specification that defines a JSON representation of vCard data. Reference: [jCard - The JSON format for vCard](https://datatracker.ietf.org/doc/rfc7095/)
-
- From [RFC5545](https://tools.ietf.org/html/rfc5545), one or more descriptive text notes associated with a particular calendar date. Examples of a journal entry include a daily record of a legislative body or a journal entry of individual telephone contacts for the day or an ordered list of accomplishments for the day.
-
- An attachment associated with a calendar component that is stored and managed on a CalDAV server. (Reference [draft-daboo-caldav-attachments](https://tools.ietf.org/html/draft-daboo-caldav-attachments-03).)
-
- An acronym for Multipurpose Internet Mail Extensions, a specification for formatting non-ASCII text message content, including iCalendar data, graphics, audio and video, so that they can be sent over the Internet. MIME is supported by email clients and web browsers (see [RFC2045](https://tools.ietf.org/html/rfc2045), [RFC2046](https://tools.ietf.org/html/rfc2046), [RFC2047](https://tools.ietf.org/html/rfc2047)).
-
- An Internet media type, sometimes a Content-type after the name of a header in several protocols whose value is such a type, is a two-part identifier for file formats on the Internet. The identifiers were originally defined in [RFC2046](https://tools.ietf.org/html/rfc2046) for use in e-mail sent through SMTP, but their use has expanded to other protocols such as HTTP, RTP and SIP and for other uses (e.g., OS-level file type identification for application/file association).
-
- Any calendar system that is not a Gregorian Calendar (e.g., Chinese, Hebrew, Islamic). See [Wikipedia](http://en.wikipedia.org/wiki/Calendar) for a description of many different calendar systems.
-
- A Standards Development Organization primarily focused on web services standards. [OASIS](http://www.oasis-open.org) and CalConnect have reciprocal memberships for joint work on WS-Calendar.
-
- A calendar user who creates a calendar item, requests free/busy information, or published free/busy information. It is an Organizer who invites Attendees. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.8.4.3).)
-
- A calendar containing events for one calendar user (the owner), and typically only accessible to the owner, or others authorized by the owner (cp. Calendar, Public Calendar, Shared Calendar).
-
- A level of importance and/or urgency calendar users can apply to Tasks and Events. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.8.1.9).)
-
- RFCs define the objects and components of their subject which in turn have properties which have values (sometimes referred to as 'property parameters' or 'property attributes'). These "property parameters" contain meta-information about the property or the property value. Property parameters are provided to specify such information as the location of an alternate text representation for a property value, the language of a text property value, the value type of the property value, and other attributes. Throughout this glossary are references to component, property, and attribute following this usage. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.8).)
-
- A calendar containing primarily public events and accessible to anyone or a specific group of calendar users (cp. Calendar, Personal Calendar, Shared Calendar). See [Public Event](#public-event).
-
- An event meant to be published to or distributed to anyone or a specific group of calendar users. These generally differ from personal events in that they contain much more detail about the event, its location, categories and other properties. See Event Publication and Publish.
-
- Generally, to make calendar information, such as freebusy time, available to a select group or to the public. From the RFC for iTIP, "The 'PUBLISH' method in a 'VEVENT' calendar component is an unsolicited posting of an iCalendar object."
-
- An event or task that happens more than once either with a regular interval (ex. daily, weekly, monthly) that can be expressed by a rule or with an explicit series of dates/times.
-
- A broadly used term in multiple RFCs to represent an action. That action may be a query for property values from a client to a server (cp. [RFC4791](https://tools.ietf.org/html/rfc4791), a query between a client and a server that results in object creation, modification, or deletion (cp. [RFC4791](https://tools.ietf.org/html/rfc4791) and [RFC5545](https://tools.ietf.org/html/rfc5545)), and it is the name of a method in iTIP that makes "an explicit invitation to one or more attendees" (among other things, cp. RFC5546). (Reference: [RFC4791](https://tools.ietf.org/html/rfc4791), [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.7.2), [RFC5546](https://tools.ietf.org/html/rfc5546), and Internet Calendar Scheduling Protocol ([iSchedule](#ischedule)).)
-
- A resource in the scheduling context is any shared entity, that can be scheduled by a calendar user, but does not control its own attendance status. Resources can be of "Location", "Equipment", or "Role" type.
-
- Specifies whether there is an expectation of a reply from a specific calendar user (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.2.17).)
-
- Briefly, the process by which organizers and attendees plan events or assign tasks. More specifically the term encompasses the exchange of request/invitations and responses between organizers and attendees of scheduled events, tasks or journal entries.
-
- A calendar that is accessible to multiple calendar users. Typically there is an "owner" and a set of "sharees", some of whom may have read-only access and some of whom might have read/write access (cp. [Calendar](#calendar), [Personal Calendar](#personal-calendar), [Public Calendar](#public-calendar), [Subscribed Calendar](#subscribed-calendar)).
-
- A representation of an item of work assigned to an individual. In [RFC5545](https://tools.ietf.org/html/rfc5545), these are "VTODO" calendar components, which are groupings of component properties and possibly "VALARM" calendar components that represent an action-item or assignment.
-
- Areas of the Earth that have adopted the same local time. Time zones are generally centered on meridians of a longitude, that is a multiple of 15, thus making neighbouring time zones one hour apart. However, the one hour separation is not universal and the shapes of time zones can be quite irregular because they usually follow the boundaries of states, countries or other administrative areas. In [RFC5545](https://tools.ietf.org/html/rfc5545), time zones are represented using "VTIMEZONE" calendar components, each with a Time Zone Identifier (TZID) that can be used to tie a particular date and time to a specific timezone.
-
- A client/server protocol used for distributing Timezone data. The protocol improves the accuracy and speed of distributing timezone data to ensure clients are kept up to date with sometimes rapidly changing definitions. It also allows clients to avoid having a complete database of all timezones - instead they can download timezone data on a case-by-case basis. (Reference [draft-douglass-timezone-service](https://datatracker.ietf.org/doc/html/draft-douglass-timezone-service).)
-
- A VALARM calendar component is a grouping of component properties that is a reminder or alarm for an event or a to-do. For example, it may be used to define a reminder for a pending event or an overdue to-do. VALARMs will thus be included within VEVENT and VTODO components. VAVAILABILITY - An iCalendar component that is used to describe periods of time for which a calendar user is available for scheduling of events. (Reference: [draft-daboo-calendar-availability](https://tools.ietf.org/html/draft-daboo-calendar-availability.)
-
- A text representation of calendar and scheduling data created by the Versit consortium (also, the vCalendar specification). The [RFC5545](https://tools.ietf.org/html/rfc5545) iCalendar specification supersedes the work of vCalendar, though VCALENDAR remains as a component type in the [RFC5545](https://tools.ietf.org/html/rfc5545) iCalendar specification.
-
- An IETF standard for a text representation of contact data. See CardDAV. (Reference: [RFC2426](https://tools.ietf.org/html/rfc2426) vCard V3.0, [RFC6350](https://tools.ietf.org/html/rfc6350) vCard V4.0.)
-
- A VEVENT calendar component represents a scheduled amount of time on a calendar. For example, it can be an activity; such as a one-hour long, department meeting from 8:00 AM to 9:00 AM, tomorrow. Generally, an event will take up time on an individual calendar. The VEVENT is also the calendar component used to specify an anniversary or daily reminder within a calendar.
-
- A grouping of component properties that represents either a request for free or busy time information, a reply to a request for free or busy time information, or a published set of busy time information.
-
- A VJOURNAL calendar component is a grouping of component properties that represent one or more descriptive text notes associated with a particular calendar date. The DTSTART property is used to specify the calendar date with which the journal entry is associated. Examples of a journal entry include a daily record of a legislative body or a journal entry of individual telephone contacts for the day or an ordered list of accomplishments for the day. The VJOURNAL calendar component can also be used to associate a document with a calendar date.
-
- A proposed extension to iCalendar. VPOLL is a new component which allows conducting a "poll" via iTIP exchanges to accomplish consensus scheduling for an event or appointment. See Consensus Scheduling. (Reference: [draft-york-vpoll](https://datatracker.ietf.org/doc/draft-york-vpoll/).)
-
- A VTODO calendar component is a grouping of component properties and possibly VALARM calendar components that represent an action-item or assignment. For example, it can be used to represent an item of work assigned to an individual; such as "turn in travel expense today".
-
- Web Distributed Authoring and Versioning (WebDAV) is an extension of the Hypertext Transfer Protocol (HTTP) that facilitates collaboration between users in editing and managing documents and files stored on World Wide Web servers. See [CalDAV](#caldav) and [CardDAV](#carddav). (Reference: [RF4918](https://tools.ietf.org/html/rfc4918).)
-
- An extension to Web Distributed Authoring and Versioning (WebDAV) that allows efficient synchronization of the contents of a WebDAV collection. (Reference: [RFC6578](https://tools.ietf.org/html/rfc6578).)
-
- An OASIS (Organization for the Advancement of Structured Information Standards) working group tasked with defining a cross-domain standard for passing schedule and interval information between and within services built around CalWS. The product of the working group will be a standard also named [WS-Calendar](http://www.oasis-open.org/committees/workgroup.php?wg_abbrev=ws-calendar) incorporating the CalWS proposal. See [CalWS](#calws).
-
- A standard that defines an XML representation of iCalendar data. (Reference: xCal: The XML format for iCalendar - [RFC6321](https://tools.ietf.org/html/rfc6321).)
-
- A standard that defines an XML representation of vCard data. (Reference: xCard: vCard XML Representation - [RFC6351](https://tools.ietf.org/html/rfc6351).)
-
-
diff --git a/_appendixes/Glossary_2.md b/_appendixes/Glossary_2.md
deleted file mode 100644
index dc9323e..0000000
--- a/_appendixes/Glossary_2.md
+++ /dev/null
@@ -1,444 +0,0 @@
----
-layout: toc-type
-title: Glossary of Terms
-parent: "/Appendix/Appendixes"
-mainParent: "Appendixes"
-parents: 'Appendixes:/Appendix/Appendixes'
-order: 1
-published: false
----
-
-# Calendaring and Scheduling Glossary of Terms
-
-This page is an effort to compile, in one location, a common set of terminology with respect to calendaring and scheduling applications and standards. The document incorporates terminology already existing in calendaring standards such as [RFC5545](https://tools.ietf.org/html/rfc5545) (Internet Calendaring and Scheduling Core Object Specification (iCalendar)), [RFC5546](https://tools.ietf.org/html/rfc6646) (iCalendar Transport-Independent Interoperability Protocol (iTIP)), [RFC6047](https://tools.ietf.org/html/rfc6047) (iCalendar Message-Based Interoperability Protocol (iMIP)), [RFC4791](https://tools.ietf.org/html/rfc4791) (Calendaring Extensions to WebDAV (CalDAV)), [RFC6638](https://tools.ietf.org/html/rfc6638) (Scheduling Extensions to CalDAV (CalDAV)), as well as input from members of the Calendaring and Scheduling Consortium (CalConnect).
-
-Some glossary terms may not appear in published standards today. These are common calendaring terms that are included so that everyone refers to components in the same manner.
-
-As new standards evolve, the glossary will serve as a resource for those creating documents so that all the standards share a common set of terms.
-
-Calendaring and scheduling implementers will be able to utilize the glossary to assist them as they read and decipher calendaring standards. Calendaring and scheduling users will be able to use the glossary to help them better understand the terminology deployed by applications written using calendaring standards.
-
-
- Access control is a system which enables an authority (e.g., user or resource administrator) to control access to different entities in a calendar system. Typically vendors create Preference/Settings options to instantiate access control. Terminology varies considerably across products but broadly speaking access control is usually broken into two areas, read access and write access. Vendor terminology used for read access includes: 'read', 'reviewer', 'proxy read', 'viewer', 'see all', and 'see only freebusy'. Vendor terminology for write access includes: 'write', 'editor', 'proxy write', 'proxy', 'manager', 'administrator', 'designate', 'read/create/edit', 'make changes', 'manage', and 'edit'. (Cp. [Delegate](#Delegate) and [Designate](#Designate) below.)
-
- A list of access control elements that define access control to a particular calendar system entity. (Reference: [RFC3744](https://tools.ietf.org/html/rfc3744) for its use in a WebDAV context.)
-
- Use of the terms alarm, reminder, alert, and notifications vary by implementation and can represent several things.
- They can represent a setting applied to an event by which a user indicates they want a 'notification' to be triggered to 'remind' them about some event or action (cp. [VALARM](#VALARM) in [RFC5545](https://tools.ietf.org/html/rfc5545).
- They can also be used to designate the type of 'alert' that serves as the notification (e.g., email message, audible sound, pop-up window). (Reference [RFC4791 (CalDAV)](https://tools.ietf.org/html/rfc4791), [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.6.6), [RFC5546 (iTip)](https://tools.ietf.org/html/rfc5546).)
-
- Specifies the participants or non-participants (e.g., room or resources) for an event. This property in iCalendar can contain multiple attributes specifying additional information, i.e., role, participation status, group membership, delegation, etc. (Reference: [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.6.4.1).)
-
- The process of configuring clients such as mobile devices or desktop applications to access a service, or class of service, with a minimum of input from the user of the device. See also [Autodiscovery](#Autodiscovery).
-
- The process used to determine the services provided by a host, or for a domain, including retrieval of the recommended configuration values for those services. The autodiscovery functionality requires the service provider to declare in a standard way which services are available and what their configuration looks like for the requesting user. See also [Autoconfiguration](#Autoconfiguration). (Reference: [draft-daboo-aggregated-service-discovery](https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/).)
-
- Extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing and sharing calendar data based on the iCalendar format. Defined by two specifications, the first, RFC4791, specifies a calendar access protocol that allows Calendar User Agents to access and manage calendar data. The second specification, RFC 6638, specifies a standard way of performing scheduling transactions with iCalendar-based calendar components. This document defines the "calendar-auto-schedule" feature of CalDAV. (Reference: [RFC 4791](https://tools.ietf.org/html/rfc4791), and [RFC 6638](https://tools.ietf.org/html/rfc6638).)
-
- A collection of calendar items such as events, tasks, journal entries, etc. Examples include a person's or group's schedule, resource availability, and event listings. Typically an individual may own multiple calendars based on the same or different services.
-
- A WebDAV collection used to represent a calendar containing a set of calendar object resources. (Reference: [RFC4791](https://tools.ietf.org/html/rfc4791) and [RFC5545](https://tools.ietf.org/html/rfc5545#section-3.4).)
-
- A WebDAV resource representing an iCalendar component typically stored inside a Calendar Collection (cp. Component). (Reference: [RFC4791](https://tools.ietf.org/html/rfc4791).)
-
- A data repository that may contain several calendars as well as properties and components of those calendars. A local calendar store is on the same device as the calendar user agent ([CUA](#CUA)). A remote calendar store is not on the same machine/device as the calendar user agent. (Reference: [RFC3283](https://tools.ietf.org/html/rfc3283).)
-