Update extracted files (#427)

Co-authored-by: Dave Thaler <[email protected]>

extracted-files/tags/NO

@@ -10,8 +10,11 @@ standard tag: 'NO'
 
 specification:
   - Did not happen
-  - An enumerated value from set `https://gedcom.io/terms/v7/enumset-EVEN`
+  - |
+    An enumerated value from set `https://gedcom.io/terms/v7/enumset-EVEN`
     identifying an event type which did not occur to the superstructure's subject.
+    A specific payload `NO XYZ` should only appear where `XYZ` would be legal.
+
     See `NON_EVENT_STRUCTURE` for more details.
   - |
     Indicates that a specific type of event, given in the payload, did not happen

extracted-files/tags/type-Age

@@ -49,6 +49,16 @@ specification:
     be unaware of these traditions or may fail to convert them to the round-down
     convention, errors in age of up to a year are common.
 
+    <div class="note">
+
+    Because age payloads are intended to allow recording the age as it was recorded
+    in records that could contain errors, odd ages such as `8w 30d`, `1y 400d`,
+    `1y 30m`, etc. are permitted. Some applications might convert these to more
+    standard forms; if so, it is recommended that they use a `PHRASE` substructure
+    to hold the original form.
+
+    </div>
+
     Age payloads may also be omitted entirely if no suitable form is known but a
     substructure (such as a `PHRASE`) is desired.
 

extracted-files/tags/type-FilePath

@@ -0,0 +1,56 @@
+%YAML 1.2
+---
+lang: en-US
+
+type: data type
+
+uri: https://gedcom.io/terms/v7/type-FilePath
+
+specification:
+  - |
+    The file path data type describes where an digital file is located in a
+    machine-readable way. Syntactically, the payload is a URI reference as defined
+    by [RFC 3986], or a valid URL string as defined by the [WHATWG URL
+    specification]. That is, it can be an absolute or relative URL, optionally
+    with a fragment string.
+
+    Version 7.0 only supports the following URLs:
+
+    - A URL with scheme `ftp`, `http`, or `https` refers to a **web-accessible
+      file**.
+
+    - A URL with scheme `file` refers to either a **local file** or a **non-local
+      file**, as defined by [RFC 8089]. Local file URLs must not be used in
+      [FamilySearch GEDZIP] and should be avoided in datasets that are expected
+      to be shared on the web or with unknown parties, but may be appropriate for
+      close collaboration between parties with known similar file structures.
+
+    - A URI reference with all of the following:
+
+      - no scheme
+      - not beginning with `/` (U+002F)
+      - not containing any path segments equal to `..` (U+002E U+002E)
+      - not containing a reverse solidus character (U+005C `\`) or `banned`
+        character, either directly or in escaped form
+      - no query or fragment
+
+      refers to a **local file**. If the dataset is part of a [GEDZIP file], the
+      URL of the local file is a zip archive filename; otherwise, the URL of a
+      local file is resolved with *base* equal to the directory containing the
+      dataset.
+
+      It is recommended that local files use the directory prefix `media/`, but
+      doing so is not required.
+
+      For compatibility with [GEDZIP] and related formats, it is recommended that
+      the following file paths not be used:
+
+      - `gedcom.ged`
+      - `MANIFEST.MF`
+      - any URL beginning `META-INF/`
+
+    Additional URLs may be supported in future versions of this specification.
+
+    The URI for the `FilePath` data type is
+    `https://gedcom.io/terms/v7/type-FilePath`.
+...