Documenting TPEN 3 revisions

[cubap]

Moving to TPEN 3 (beta around summer of 2025, as this project is wrapping up) will require some preparation and anticipation.

[cubap]

Summary:

2.8	3.0
t-pen.org/TPEN/manifest/1234 returns a Presentation 2.3 IIIF Manifest	api.t-pen.org/manifest/1234abcdef returns a Presentation 3.0 IIIF Manifest
Manifest represents the most closely defined transcription project.	Manifest is derivative upon request. Project data is most closely defined by an Array of Annotation Collections.
Transcription is only embedded in the Manifest or the /getProjectAsJSON service.	Transcription is stored in store.rerum.io as individual Annotations and Annotation Pages.
All transcription on a page is in the same Annotation List (or Annotation Page with Presi3 flag).	Transcription on a page can have separate layers, each in their own Annotation Page and organized into Annotation Collections.
** Gallery of Glosses Specific **	New Requirement
Presi 2.3 Linked Witness Fragments	parse Presi 3.0 (Manifesto?)
Discrete TPEN Project per layer	Import several layers of annotation per project
Image links almost all depend on /pageImage service	Image links will be behind ?image flags on /line service.
References to external documents must be explicitly applied.	External documents (for example, a Manifest from the British Library) are naturally referenced and supplemented by TPEN content.
Text of annotations is embedded in the Manifest (/manifest) as plaintext	Text service may be available in a variety of ways, including with markup.
t-pen.org controls all exports and available views.	GoG may have its own (especially "readonly") views that represent the transcriptions and fragments.