Skip to content

Fix Citation Tree unclear sistuation #289

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.

Sign up for GitHub

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

Merged
monotasker merged 2 commits into from
Feb 11, 2026
Merged

Fix Citation Tree unclear sistuation #289

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b0c42fe
Fix Citation Tree unclear sistuation
PonteIneptique Feb 4, 2026
6ee925a
Update Citation Tree Summary
PonteIneptique Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion versions/1.0rc1/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,9 @@ Specifications

## Changelogs

- 2026-02-04
- Fixed ([Issue 271](https://github.com/distributed-text-services/specifications/issues/271)) to have extensions and dublinCore be nested JSON LD properties
- Clarification on the fact that Citation Trees without a reference represent the same document.
- 2025-07-11 : 1.0 Release Candidate 1 !
- 2025-04-17
- Fixed formatting issues.
Expand Down Expand Up @@ -88,7 +91,9 @@ The Distributed Text Services API implements one root [Entry point](#entry-endpo

### Citation Tree

When discussing a text, it is common to use labels to identify sections of the text. When referring to pages, for example, we might identify them with numbers. In other situations we might divide the text into logical structures that are hierarchically organized. For example, we might identify "Paragraph 4" within "Section D" which falls within "Chapter 1." In both cases, these structuring labels form citation trees, though with different depths. (A depth of 1 for "pages" and a depth of 3 for "chapter"/"section"/"paragraph.")
When discussing a text, it is common to use labels to identify sections of the text. When referring to pages, for example, we might identify them with numbers. In other situations we might divide the text into logical structures that are hierarchically organized. For example, we might identify "Paragraph 4" within "Section D" which falls within "Chapter 1." In both cases, these structuring labels form citation trees, though with different depths. (A depth of 1 for "pages" and a depth of 3 for "chapter"/"section"/"paragraph.").

A Citation Tree in the DTS specification is a model for interpreting references. Each Citation Tree maps the possible hierarchical relationships between different kinds of reference identifiers in a given document.

The depth of a citation tree can be uneven. In a Ph.D. thesis, for example, the introduction may not be subdivided, while a chapter will often have subdivisions.

Expand Down Expand Up @@ -1934,6 +1939,7 @@ For parameter combinations and potential errors, see [Link](#)

- The `resource` query parameter **MUST** be provided.
- The `tree` query parameter **MUST** be omitted to address the default `CitationTree` of a `Resource`.
- The `tree` query parameter **MUST** not have effects on the response if used without a `ref`, or a `start` and a `end` parameters
- The `tree` query parameter **MUST** be provided to address a `CitableUnit` within a different `CitationTree` from the default.
- The `ref` query parameter **CANNOT** be used in combination with `start` and `end`.
- The `start` query parameter **MUST** be used in combination with `end`.
Expand Down