Map the yaml config to the W3C meta-data ontologies

**Update**: this issue is considerably broader than initially assessed, the output RDF has semantic flaws at various levels that aren't solvable with the current parser. I will start by creating a thorough map between each keyword in the yaml configuration file to classes and predicates in the W3C ontologies (DCat, VCard, Prov, etc). From that map a new parser can be developed with a more direct RDF generation.

I transformed the JSON-LD output to Turtle for legibility (see below). The organisation instance is using the vcard:fn predicate, which is a data property of the Individual class. Basically it says that the full name of EC is "Tom Kralidis". The semantics of VCard must be revised.

```
a vcard:Organization ;
vcard:country-name "Canada" ;
vcard:fn "Tom Kralidis" ;
vcard:hasEmail "foo@bar.tld" ;
vcard:hasOrganizationName "Environment Canada" ;
vcard:hasTelephone "+01-123-456-7890" ;
vcard:locality "Toronto" ;
vcard:postal-code "M3H 5T4" ;
vcard:street-address "4905 Dufferin Street" ;
dcat:accessURL "https://www.ec.gc.ca/" .
```

Start with the YAML configuration keywords and the current parser, then compare its JSON-LD/Turtle output with the cited W3C ontologies, including DCAT, vCard, and PROV. Done means a complete keyword-to-class/predicate map and a parser design that can produce semantically correct RDF without the documented flaws.

Written by the indexing model from the issue text.