Discussion: Introduction of the Concept of Parser Directives

If(when) we introduce something like Schema Definitions we need a way to tell a possible parser, etc to tell what and where they can find the schema.

I suggest we introduce the concept of Parser Directives.

In many usages like in programming languages look like some special comments. So I suggest the following syntax if(when) we provide a built in official specification of Schema Definitions:

    <CommentSequence><CommentSequence>TAML.Schema   <Place to find the Schema>

Alternatively if the <CommentSequence> turns out to be something not fitting in this case I suggest the following syntax:

    <CommentSequence>#TAML.Schema   <Place to find the Schema>

Notes:

The Parser Directive is divided into a <Namespace> and a <DirectiveName> by a .
The Parser Directive should be a resolvable package name in the environment the parser utilizes
The <Namespace> token TAMLis reserved for official specified Parser Directives only
Projects can define custom Parser Directives that the official Parser can resolve through package manager and invoke there function
If there are custom Parser Directives there is a need for defining specification for how to interact with the resolvable package

The aspects of custom Parser Directives being able to interact with the parser I would say would be a "down the line" feature that won't be in a 1.0 release version.

Additionally there would have to be the discussion about that we only allow Parser Directives on top of the TAML file to make parsing the actual file not way more complicated or slow than it hast to be.

The goal of introducing the concept of Parser Directives early in this project would be that there is an official syntax for such things already and nobody that needs such a feature is inventing there own syntax and make things looking messy.

csharpfritz / TAML

Discussion: Introduction of the Concept of Parser Directives #25