Extensibility

[jonathanrobie]

Treedown currently has two extensibility mechanisms:

1. The set of labels will be configurable. Ideally, we want related projects to use the same labels for the sake of interoperable queries and building communities of understanding, but some projects will need to use their own labels or add new labels that have not yet been adopted into core.

2. Extension expressions allow keyword / value pairs in parentheses. Keywords can be prefixed, e.g. extensions that indicate the semantic function of an adjunct might be use a prefix to indicate a set of semantics associated with a project. An adjunct might also be used to indicate the status of an analysis - proposed, approved, etc. Multiple extensions can occur in a single extension expression.

Example:

+ τότε          ( adj:class=time, ana:status=proposed )
    v λέγει
    io αὐτῷ
    s ὁ Ἰησοῦς

[jtauber]

I do like having an extensibility mechanism but I think we may want to distinguish when it's:

• elaborating a line
• elaborating a word
• a milestone like a verse number

I like the approach of extensions being keyword/value pairs.

[jonathanrobie]

We could use a scope keyword in extensions. "The scope of the constituent this line starts" is probably the most important one, and might be default. Something like:

( scope=constituent, dg=topic )
( scope=word, dg=focus )