You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`<scripture_format>` - Which Scripture format the location information is specified against. For example, if the Scripture format is `Usfm`, offsets from the anchor to the specified position are string character index offsets within the USFM representation of the Scripture data.
16
+
-`<location_format?>` - Particulars about the way the anchor is specified. If this is not included, this type is likely a catch-all containing a union of multiple subtypes that all include the same information in different location formats.
17
+
-`<location_anchor?>` - `Book`, `Chapter`, `Verse`, or `Document` - Which kind of more general, well-known position this location is relative to. The more general location "anchor" may be an absolute position: the start of a specified chapter, book, verse; the data in this location type is expected to specify which chapter, book, or verse the location data is relative to. The anchor may also be a specific USJ document, in which case the location type is not expected to specify which document it is relative to. Document-relative positions are only interpretable if you have the document the position is based on; other location types layer over the document-relative types to indicate which document (and therefore which absolute position) the document-relative position is based on. If this is not specified, this type is a union of multiple subtypes that all specify positions in the same Scripture format.
18
+
19
+
Examples:
20
+
21
+
-`UsfmVerseLocation` - Locations relative to the start of a specified verse and at an offset in the USFM representation of the Scripture data
22
+
23
+
-`<scripture_format>` - `USFM` - the information specifying the position relative to the anchor is an offset based on the USFM representation of the Scripture data
24
+
-`<location_format>` - None; this is a union type of multiple subtypes that all specify the same data.
25
+
-`<location_anchor>` - `Verse` - this location specifies a specific verse that its position is relative to
26
+
27
+
-`UsjLocation` - Location whose JSONPath is specified on a USJ document which contains either the entire book or the entire chapter specified and whose offset information is in the USJ representation of the Scripture data
28
+
29
+
-`<scripture_format>` - `USFM` - the information specifying the position relative to the anchor is an offset based on the USFM representation of the Scripture data
30
+
-`<location_format>` - None; this is a union type of multiple subtypes whose subtypes all specify the same data as one another.
31
+
-`<location_anchor>` - None; this is a union type of multiple subtypes that all specify either a USJ book or chapter location
32
+
33
+
- Document-relative locations - various location types that specify a location within some USJ document which is not determinable based on the information in these types
34
+
-`UsjDocumentLocation` - A JSONPath query to an object, string, or property within a USJ document and additional information that point to a specific location in that USJ document.
35
+
- Note: The subtypes of this type do not conform to the naming format specified above. They are all different forms of USJ document-relative locations.
36
+
- JSONPath types - subsets of [JSONPath](https://www.rfc-editor.org/rfc/rfc9535.html) that point to some object, string, or property in a USJ document
37
+
-`ContentJsonPath` - JSON path to an object or text content string in a USJ document.
38
+
-`PropertyJsonPath` - JSON path to a property on an object in a USJ document.
39
+
- Types of USJ document locations - each type is a different format specifying various kinds of locations in a USJ document.
40
+
-`UsjAttributeKeyLocation`
41
+
-`UsjAttributeMarkerLocation`
42
+
-`UsjClosingAttributeMarkerLocation`
43
+
-`UsjClosingMarkerLocation`
44
+
-`UsjMarkerLocation`
45
+
-`UsjTextContentLocation`
46
+
-`UsjNodeAndDocumentLocation` - An object or string in a USJ document and its location in that document.
47
+
- Absolute locations - various location types that specify a location within a determinable document or relative to a specific point in the Scripture data.
48
+
49
+
-`UsfmVerseLocation` - A verse ref and an offset within that verse in USFM space that point to a specific location in USFM.
50
+
-`UsfmVerseRefVerseLocation` - A particular format for specifying a verse ref and an offset within that verse in USFM space that point to a specific location in USFM.
51
+
-`SerializedVerseRef` - Just a verse reference. The offset is implied to be 0, meaning this always points to the very beginning of a verse.
52
+
-`UsjLocation` - A verse ref and a location in USJ space that point to a specific location in USJ. The location in USJ space should be interpreted as starting from either the start of the book or the chapter depending on the type of location used.
53
+
54
+
-`UsjBookLocation` - A verse ref and a location in USJ space that point to a specific location in USJ. The location in USJ space should be interpreted as starting from the start of the book specified.
55
+
-`UsjFlatBookLocation`
56
+
-`UsjVerseRefBookLocation`
57
+
-`UsjChapterLocation` - A verse ref and a location in USJ space that point to a specific location in USJ. The location in USJ space should be interpreted as starting from the start of the chapter specified.
58
+
-`UsjFlatChapterLocation`
59
+
-`UsjVerseRefChapterLocation`
60
+
61
+
## Development
8
62
9
63
When we publish this npm package, then in the root `package.json`, a version can be given to `platform-bible-utils` instead of the existing file link. At that time we will likely need to use `npm link` and `npm unlink` to develop the components ([see here](https://github.com/jasonsturges/vite-typescript-npm-package#development)).
10
64
@@ -44,3 +98,7 @@ npm run build:basic
44
98
```
45
99
46
100
Do not commit changes after running this basic build. Before committing, always run a full build.
101
+
102
+
## Acknowledgements
103
+
104
+
Inspired by https://github.com/jasonsturges/vite-typescript-npm-package
0 commit comments