During the VAIA course we received the following feedback:

it's a well-known shorthand in standard YAML... the use of square brackets here for YARRML conflicts that YAML shorthand

Array brackets conflict with standard YAML as it is a shorthand for arrays.
Just putting it here so we can incorporate this later.

For the yarrrml spec, it might be okay to use graph instead of graphs as a keyword, more info about this discussion at oeg-upm/yatter#78

E.g. the following should be correct, following the spec (currently the spec only mentions graphs)

mappings:
  test:
    graph: https://example.com/$(id)
    s: https://example.com/$(id)
    po:
      - [a, ext:Test]

The examples through out the spec need to be made consistent:

• Usage of spaces: XXX ;/XXX . vs XXX;/XXX.
• Placing of a YY:XXXX class types in Turtle examples. Sometimes they are on the same line, sometimes a new line

The current spec provides for each example a translation from YARRRML to the corresponding mapping in RML.
The conditions is the only section where this translation is not provided.

I've used Matey to see an example of the output but considering we have a new RML-FNML specification it would be great to know if it covers the requirements for the conditions (as I saw in Matey's output, I think currently it's purely supported by FNML) or we would also need to update the core spec to explicitly add the conditions.

Change the FNML profile and RML-FNML translations to be compliant with the spec of the CG

According to R2RML, in a string template "There SHOULD be at least one pair of unescaped curly braces.", i.e. at least one reference.

However, the YARRRML spec says "A template contains 0 or more constant strings and 0 or more references to data in a data". IMO the second 0 should be a 1, to be compliant w.r.t. R2RML.

The target section is not defined in this spec while in the (rml.io) YARRRML appears: https://rml.io/yarrrml/spec/#targets.

We need to include it here