From 8654a4e7efab3787575d7327706d4cc721228d8b Mon Sep 17 00:00:00 2001
From: bigbass1997 <bigbass1997.website@gmail.com>
Date: Wed, 16 Apr 2025 23:07:21 -0500
Subject: Added TXT alternate in <front> and added a contributions section
 linking to the document's source repo.

---
 src/docs/tasd-spec-0001.xml | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'src')

diff --git a/src/docs/tasd-spec-0001.xml b/src/docs/tasd-spec-0001.xml
index ae4fac0..d8f4f61 100644
--- a/src/docs/tasd-spec-0001.xml
+++ b/src/docs/tasd-spec-0001.xml
@@ -13,6 +13,7 @@
   symRefs="true"
   sortRefs="true"
   version="3">
+  <link href="https://tasd.io/index.txt" rel="alternate"/>
   <front>
     <title abbrev="TASD File Format Specification">TASD File Format Specification Version 1</title>
     <seriesInfo name="Internet-Draft" stream="independent" value="draft-tasd-v0001-00" status="informational"/>
@@ -46,6 +47,10 @@
       <t>The Tool Assisted Speedrun Dump (<strong>TASD</strong>) interchange format is a file format for storing data that enables "Tool Assisted Speedruns" or "Tool Assisted Superplays" to be played on physical video game hardware using TAS replay devices.  Created to be hardware and software agnostic, the <strong>TASD</strong> interchange format uses a key-based, binary, packet format to break up pieces of information into easily-parsable and forward-compatible chunks. The format is extensible by simply defining additional keys or value types as necessary. When parsing the file, software can skip any packets whose key is unknown or unsupported.</t>
       <t>Packets of a given type can be used multiple times or completely omitted as needed. This reusability eliminates the need of a predefined delimiter to separate pieces of data.</t>
       <t>While files generated by emulator dump scripts should provide as much information as possible, they may be unable to provide everything. Since packets are optional, the file can be expanded later with any additional data as desired. No intermediary file format is necessary.</t>
+      <section numbered="true" toc="default">
+        <name>Contributions</name>
+        <t>This document's source XML can be found at <eref target="https://github.com/tasd-org/tasd-spec"/>. All specification issues and additions should be addressed there.</t>
+      </section>
       <section numbered="true" toc="default">
         <name>Overview and Preliminaries</name>
         <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
-- 
cgit v1.2.3