Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encoding "Terms and definitions" sub-sections in Amendments #1258

Open
manuelfuenmayor opened this issue Dec 11, 2024 · 2 comments
Open

Encoding "Terms and definitions" sub-sections in Amendments #1258

manuelfuenmayor opened this issue Dec 11, 2024 · 2 comments
Assignees

Comments

@manuelfuenmayor
Copy link

manuelfuenmayor commented Dec 11, 2024

The format of a "Terms and definitions" sub-section is different to the rest.

From ISO 8601 Amendment 1:

We need a way to encode the type of sub-sections for Amendments.

This is a sample of the current encoding method we've been using:

[change=add,locality="clause=3.1.2.16"]
== 3.1.2

Add the following terminological entries after 3.1.2.13:

[change=add,locality="clause=3.1.2.14"]
== 3.1.2.14 canonical form
autonumber:example[1]
autonumber:termnote[1]

date and time expression where all its time scale components are _normalised_
(3.1.2.15)

[NOTE%termnote]
The canonical form of a date and time expression implies it contains minimal
underflow and no overflow.

Which renders:

This issue relates to #1251

@ronaldtse
Copy link
Contributor

I've added a link to the document (this is now published) where this occurs:

@opoudjis
Copy link
Contributor

The amend syntax currently provides the replacement text as a blockquote. This will not work when the replacement text is an entire clause, as that violates the syntactic constraint on well-nested clauses: an alternate syntax will be needed for clauses as replacement text.

Note that any such clausal replacement text will need to be "deactivated" with regard to interacting with numbering, and possibly even depth calculation for titles: they may be syntactically subclauses, but they need to be inert with regard to interacting with the remainder of the document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants