Skip to content

Commit eac9d29

Browse files
ronaldtseronaldtse
committed
chore: clean up
1 parent 6b3183b commit eac9d29

31 files changed

Lines changed: 609 additions & 498 deletions

‎.github/workflows/generate.yml‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
name: generate
2+
3+
on:
4+
push:
5+
branches: [ main ]
6+
pull_request:
7+
workflow_dispatch:
8+
9+
permissions:
10+
contents: read
11+
pages: write
12+
id-token: write
13+
14+
concurrency:
15+
group: "pages"
16+
cancel-in-progress: true
17+
18+
jobs:
19+
build:
20+
runs-on: ubuntu-latest
21+
container:
22+
image: metanorma/metanorma:latest
23+
steps:
24+
- name: Checkout
25+
uses: actions/checkout@v4
26+
27+
- name: Cache Metanorma assets
28+
uses: actions-mn/cache@v1
29+
30+
- name: Metanorma generate site
31+
uses: actions-mn/build-and-publish@v2
32+
with:
33+
agree-to-terms: true
34+
destination: gh-pages
35+
deploy:
36+
if: ${{ github.ref == 'refs/heads/main' }}
37+
environment:
38+
name: github-pages
39+
url: ${{ steps.deployment.outputs.page_url }}
40+
runs-on: ubuntu-latest
41+
needs: build
42+
steps:
43+
- name: Deploy to GitHub Pages
44+
id: deployment
45+
uses: actions/deploy-pages@v4

‎.gitignore‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
.DS_Store
2+
*.abort
3+
*.err
4+
relaton/
5+
.vscode/
6+
.ruby-lsp/
7+
Gemfile.lock
8+
iev/
9+
_site/

‎Gemfile‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
source "https://rubygems.org"
2+
3+
gem "metanorma-cli"

‎Makefile‎

Lines changed: 0 additions & 28 deletions
This file was deleted.

‎sources/cc-58020.adoc‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ include::sections/02-normative-references.adoc[]
3131

3232
include::sections/03-terms.adoc[]
3333

34+
include::sections/03-conventions.adoc[]
35+
3436
include::sections/03-overview.adoc[]
3537

3638
include::sections/04-patch.adoc[]

‎sources/sections-ietf/00-abstract.adoc‎

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,16 @@
11
[abstract]
22
== Abstract
33

4-
This document defines a new iCalendar <<RFC5545>> component that allows small "patches" to be applied to
5-
large iCalendar data objects, to allow for efficient data updates. It also describes how this
6-
new component can be used with the CalDAV calendar data access protocol <<RFC4791>>.
4+
This document defines a new iCalendar <<RFC5545>> component that allows small
5+
"patches" to be applied to large iCalendar data objects, to allow for efficient
6+
data updates. It also describes how this new component can be used with the
7+
CalDAV calendar data access protocol <<RFC4791>>.
78

89
[NOTE,title=Open Issues]
910
====
10-
* Do we need/want to handle individual values in multi-valued properties/parameters?
11-
* What media type do we advertise in `Accept-Patch` header? Just `text/calendar`? Currently using `text/calendar; component=VPATCH; optinfo=PATCH-VERSION:1`
11+
* Do we need/want to handle individual values in multi-valued
12+
properties/parameters?
13+
* What media type do we advertise in `Accept-Patch` header? Just
14+
`text/calendar`? Currently using `text/calendar; component=VPATCH;
15+
optinfo=PATCH-VERSION:1`
1216
====

‎sources/sections-ietf/02-conventions.adoc‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
[[conventions-used-in-this-document]]
22
== Conventions Used in This Document
33

4-
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
5-
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in
4+
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
5+
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
6+
interpreted as described in
67
<<RFC2119>>.
78

8-
The notation used in this memo is the ABNF notation of <<RFC5234>> as used by iCalendar <<RFC5545>>. Any
9-
syntax elements shown below that are not explicitly defined in this specification come from
10-
iCalendar <<RFC5545>> and Calendar Availability <<RFC7953>>.
9+
The notation used in this memo is the ABNF notation of <<RFC5234>> as used by
10+
iCalendar <<RFC5545>>. Any syntax elements shown below that are not explicitly
11+
defined in this specification come from iCalendar <<RFC5545>> and Calendar
12+
Availability <<RFC7953>>.

‎sources/sections-ietf/98-references.adoc‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
[bibliography]
21
== References
32

43
[bibliography]

‎sources/sections/00-abstract.adoc‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
[abstract]
22
== Abstract
33

4-
This document defines a new iCalendar <<RFC5545>> component that allows small "patches" to be applied to
5-
large iCalendar data objects, to allow for efficient data updates. It also describes how this
6-
new component can be used with the CalDAV calendar data access protocol <<RFC4791>>.
4+
This document defines a new iCalendar <<RFC5545>> component that allows small
5+
"patches" to be applied to large iCalendar data objects, to allow for efficient
6+
data updates. It also describes how this new component can be used with the
7+
CalDAV calendar data access protocol <<RFC4791>>.

‎sources/sections/01-intro.adoc‎

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
11
[[introduction]]
22
== Introduction
33

4-
The iCalendar <<RFC5545>> data format is in widespread use to represent calendar data. iCalendar data can
5-
grow large (e.g., a family calendar containing events over a period of several years). Updating
6-
large resources over the network currently requires the entire data to be sent - even if the
7-
change itself is minor.
4+
The iCalendar <<RFC5545>> data format is in widespread use to represent calendar
5+
data. iCalendar data can grow large (e.g., a family calendar containing events
6+
over a period of several years). Updating large resources over the network
7+
currently requires the entire data to be sent - even if the change itself is
8+
minor.
89

9-
This specification defines a new iCalendar component that can be used to "patch" (incrementally
10-
update) iCalendar data in an efficient manner. When combined with the HTTP PATCH method <<RFC5789>>, it can
11-
be used to update calendar object resources on a CalDAV <<RFC4791>> server, or any resource on an HTTP
12-
server that contains iCalendar data.
10+
This specification defines a new iCalendar component that can be used to "patch"
11+
(incrementally update) iCalendar data in an efficient manner. When combined with
12+
the HTTP PATCH method <<RFC5789>>, it can be used to update calendar object
13+
resources on a CalDAV <<RFC4791>> server, or any resource on an HTTP server that
14+
contains iCalendar data.

0 commit comments

Comments
 (0)