v1.0 update (#294)

Co-authored-by: Thibault Clérice <thibault.clerice@inria.fr>

Author: PonteIneptique

Cookbook.md

@@ -13,9 +13,10 @@ To link a manifest to a catalog entry, we recommend using the Dublin Core Terms
 ```json
 {
     "@context": {
-        "@vocab": "https://distributed-text-services.github.io/specifications/context/1.0.0draft-2.json",
+        "@vocab": "https://dtsapi.org/context/v1.0.json",
         "sc": "http://iiif.io/api/presentation/2#"
     },
+    "dtsVersion": "1.0",
     "@id": "/a/collection/uri",
     "@type" : "Resource",
     "title" : "A title",
@@ -44,9 +45,10 @@ The operation is really close to the [previous one](#link-manifests-to-a-catalog
 ```json
 {
     "@context": {
-        "@vocab": "https://distributed-text-services.github.io/specifications/context/1.0.0draft-2.json",
+        "@vocab": "https://dtsapi.org/context/v1.0.json",
         "sc": "http://iiif.io/api/presentation/2#"
     },
+    "dtsVersion": "1.0",
     "@id":"/api/dts/navigation/?id=/a/text/id&level=2",
     "citeDepth" : 2,
     "level": 2,

FAQ.md

@@ -2,15 +2,20 @@
 
 ## What is DTS?
 
-DTS is an API for collections of TEI documents.
+DTS is an API for collections of documents.
 
-## Why does TEI need an API for collections?
+## Can DTS provide an API for TEI collections?
 
 DTS provides a standard way for clients to interact with collections of TEI documents. A standard API allows users to access many text collections using the same client software. It also allows editors to publish text collections in a usable way that existing clients can use.
 
+## Can I use DTS if I don't publish my texts in TEI/XML?
+
+Yes (since 1.0's first release candidate). The DTS Collection and Navigations endpoints can be used to provide navigation capabilities across
+collections of texts and within a textual document regardless of the data format.
+
 ## Where can I download DTS and start using it?
 
-You can’t.  DTS defines the way that programs communicate with each other. An end-user will use this software.  For software developers, there are libraries that support DTS, they are listed [here](../index.html#reference-implementations).
+You can’t. DTS defines the way that programs communicate with each other. An end-user will use this software. For software developers, there are libraries that support DTS, they are listed [here](../#reference-implementations).
 
 ## What can clients do with these documents?
 
@@ -34,10 +39,6 @@ DTS is a REST API that works a lot like a web browser.  When client software mak
 
 DTS is built like you would build a website: everything is discoverable, sorted so that users (clients) can easily find what they want. On top of that, it uses vocabularies that are linked and shared and which you can find all over the web of data.
 
-## What is Hydra?  Why Hydra?
-
-Hydra provides a good framework for building REST APIs.  We wanted to use a standard instead of starting from scratch. We wanted good support for JSON and pure hypermedia-based APIs. Hydra provides core functionality and provides extensibility that allows us to customize to fit our model.  (We tried three or four other approaches before choosing Hydra.  We know there are religious debates about APIs, this one worked well for our use cases.)
-
 ## If I implement the DTS API for my text collection what does it enable?
 
 Implementing the DTS API enables consumers of the data to easily retrieve:
@@ -67,14 +68,6 @@ Yes.
 
 Yes.
 
-## Can I use DTS if I don't publish my texts in TEI/XML?
-
-Yes, partially.
-
-The DTS Collection and Navigations endpoints can be used to provide navigation capabilities across
-collections of texts and within a textual document regardless of the data format. However, the Document endpoint only supports
-TEI texts.
-
 ## What is the relationship between DTS and CTS? Are they redundant?
 
 The Distributed Text Services effort was inspired, informed and influenced by the [Canonical Text Services protocol](http://cite-architecture.github.io/cts/) (CTS). CTS has allowed many classical, canonical texts encoded in TEI to be made available in a machine-actionable, linked open data fashion. However, the CTS API is tightly coupled to the CTS URN identifier system which does not support citation systems used by more modern content or other forms of writing, such as papyri or inscriptions. The API also does not adhere to modern community standards for Web APIs.

README.md

@@ -4,11 +4,9 @@
 [<i class="fa fa-bug"></i> Raise Issues and Ask Questions](https://github.com/distributed-text-services/specifications/issues){: .btn .btn--info .btn--x--small}
 [<i class="fa fa-file-code"></i> Check Source and Propose Changes](https://github.com/distributed-text-services/specifications){: .btn .btn--info .btn--x--small}
 
-## Distributed Text Services 1.0 Release Candidate Published – July 11, 2025
+## Distributed Text Services 1.0 Published – February 13, 2026
 
-After years of development, independent implementations, interoperability testing, and a public comment period, the Distributed Text Services Technical Committee is pleased to announce the publication of the Distributed Text Services 1.0 Release Candidate (RC1).
-
-We strongly encourage you to implement DTS now and share your feedback. The specification is feature-complete and stable, and we expect only minor clarifications before the final 1.0 release in three months (11/10/2025). Early adoption will ensure your projects are ready and help the community validate the standard in real-world use.
+After years of development, independent implementations, interoperability testing, and a release candidate period, the Distributed Text Services Technical Committee is pleased to announce the publication of the Distributed Text Services v1.0.
 
 ## What is DTS?
 
@@ -26,9 +24,9 @@ See the [FAQ](FAQ.html) for more information and a list of frequently asked ques
 
 DTS specifies 3 distinct operation endpoints:
 
-- Navigation _across texts_ is supported by the [Collection Endpoint](versions/1.0rc1/#collection-endpoint)
-- Navigation _within a text_ is supported by the [Navigation Endpoint](versions/1.0rc1/#navigation-endpoint)
-- Retrieval of complete or partial texts is supported by the [Document Endpoint](versions/1.0rc1/#document-endpoint)
+- Navigation _across texts_ is supported by the [Collection Endpoint](versions/v1.0/#collection-endpoint)
+- Navigation _within a text_ is supported by the [Navigation Endpoint](versions/v1.0/#navigation-endpoint)
+- Retrieval of complete or partial texts is supported by the [Document Endpoint](versions/v1.0/#document-endpoint)
 
 The Collection and Navigation endpoints return JSON-LD. The Document endpoint is specified to return TEI/XML of the requested text or fragment.
 
@@ -54,7 +52,7 @@ This list includes implementations that should be generic enough to be compatibl
 
 ## Conformance Evaluation
 
-Matteo Romanello built a toolkit to evaluate implementation against the specifications: <https://github.com/mromanello/DTS-validator>.
+Matteo Romanello built a toolkit to evaluate implementation against the specifications: <https://github.com/distributed-text-services/validator>.
 
 ## Known Corpora Accessible via the DTS API
 

_data/navigation.yml

@@ -1,7 +1,7 @@
 # main links
 main:
   - title: "API Documentation"
-    url: "versions/1.0rc1/"
+    url: "versions/v1.0/"
   - title : "Organization"
     url: "Organization.html"
   - title : "Cookbook"

changelogs.md

@@ -1,6 +1,33 @@
 Changelogs
 ==========
 
+# 1-alpha to 1.0
+
+- 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.
+  - Removed ambiguity around the section "Handling Requests with No Matching `CitableUnit`s at the Requested Level(s)" ([Issue 268](https://github.com/distributed-text-services/specifications/issues/268))
+  - Clarified the behaviour of `?down=0` while no `start/end`/`ref` are provided (=400 Bad Request Error) ([Issue 269](https://github.com/distributed-text-services/specifications/issues/269))
+  - Allow `CitableUnit` to have `@id` for Linked Data usages ([Issue 274](https://github.com/distributed-text-services/specifications/issues/274)).
+  - Clarify that headers of the Entry Endpoint SHOULD be JSON+LD ([Issue 272](https://github.com/distributed-text-services/specifications/issues/272)).
+  - Clarify that `MetadataObject` MUST have their vocabularies defined, either by the main `@context` property if they are reusing base DTS vocabulary (including Dublin Core Terms) or by their own `@context` property.
+- 2024-08-08
+  - Made `citeType` required for `CiteStructure` objects.
+  - Removed `maxCiteDepth` everywhere, including in the example.
+- 2024-08-06
+  - Removed `maxCiteDepth` from Collection objects at the Collection endpoint now that we have a `CitationTree` object at the Resource level.
+  - Harmonized the properties for `Resource` objects between the Collection and Navigation endpoints. This involves adding required `document` and `navigation` properties, as well as allowing additional optional properties. Also removed the `document` and `navigation` properties from the `Navigation` object since these URI templates are now part of the `Resource` object.
+  - Added `view` properties for paginated responses to the Collection and Navigation endpoints. Added a `Pagination` object type to provide the pagination links.
+- 2024-05-24
+  - Removed `totalItems` from the Collection Endpoints (See https://github.com/distributed-text-services/specifications/issues/248, problem pointed out by @kbrueckmann)
+  - `passage` property (URI template) moved to `document` for consistency between Collection and Navigation endpoint (See https://github.com/distributed-text-services/specifications/issues/249, problem pointed out by @philippepons)
+    - Harmonized the examples to have the resource already populated, as per Collection URI Templates
+  - `collection` property (URI template) added to `Collection` and `Resource` object (See https://github.com/distributed-text-services/specifications/issues/250, problem pointed out by @philippepons)
+  - Fixed a typo in the Entry endpoint table, where it referenced Resources.
+
 # 1-draft2 to 1-alpha
 
 ## Hydra