Extensions in YAML

[opoudjis]

I need to specify

<bibdata>
...
  <ext>
    <ics><code> 25.040.40</code></ics>
    <price-code>XL</price-code>
  </ext>
</bibdata>

in Relaton YAML for metanorma/metanorma-iso#1217 . I've written:

title:
  - type: main
    content: STEP Module and Resource Library (SMRL)
type: standard
edition: "11"
docid:
  - type: SMRL
    id: 2024(E)
date:
  - type: published
    "on": 2024
ext:
  ics:
    code: 25.040.40
  price-code: XL
copyright:
   owner:
     name: International Organization for Standardization
     abbreviation: ISO
     url: www.iso.org
   from: '2024'
contributor:
  - organization:
      name: International Organization for Standardization
      url: www.iso.org
      abbreviation: ISO
    role:
      type: publisher

The Relaton YAML parser appears to be ignoring ext. Is that the case?

[andrew2net]

@opoudjis we didn't have ext in YAML at the beginning. I started adding new elements that belong to ext in XML into the ext YAML element. But most of elements under ext in XML are root in YAML. I planned to move all the elements to YAML ext with new Relaton powered with lutaml-model.

[opoudjis]

Right. This will indeed need to be fixed, because people need to be able to predict what the YAML looks like if they data enter it, and the XML grammar is the only way to until now. There is a need from this to document Relaton YAML, although I can make do with handcrafting Relaton XML and converting it back to YAML.

ext/price-code is defined for IEC, but I see it is being ignored still when converting Relaton XML back to YAML; I assume that's expected?

  <ext>
    <ics><code>1.2.3</code></ics>
    <price-code>XML</price-code>
  </ext>

converts to just

ics:
- code: 1.2.3

[andrew2net]

In relaton v1.20.0 all flavor data moved under ext section in YAML