The WMO code manuals include many terms that are "reserved"; often for local usage. These are missing from the Registry.
For example, take a look at 0-22-061 'State of the sea' ... in the source txt file (from which the table entries were automatically generated, you'll see rows like:
3436.00,"022061","State of the sea","10-14","Reserved",,,,"Operational"
Sometimes it just says "Reserved", other times "Reserved for local use".
These need to be expanded so that each term is published separately into the Register with "Reserved" status. Note that in some cases, code tables contain hundreds of reserved terms.
The TTL snippet below provides an example for <bufr4/codeflag/0-22-061/10> ... you see that the entity is embedded within the register item - there is no external entity definition. We are essentially creating a dummy entity definition for each reserved concept.
[]
a reg:RegisterItem ;
reg:status reg:statusReserved ;
reg:definition [
reg:entity [
a skos:Concept ;
skos:notation 10 ;
rdfs:label "Reserved"@en ;
dct:description "Reserved for future use."@en
] ;
] ;
reg:notation 10 ;
bufr4-core:FXY "022061" .
The WMO code manuals include many terms that are "reserved"; often for local usage. These are missing from the Registry.
For example, take a look at 0-22-061 'State of the sea' ... in the source txt file (from which the table entries were automatically generated, you'll see rows like:
Sometimes it just says "Reserved", other times "Reserved for local use".
These need to be expanded so that each term is published separately into the Register with "Reserved" status. Note that in some cases, code tables contain hundreds of reserved terms.
The TTL snippet below provides an example for <bufr4/codeflag/0-22-061/10> ... you see that the entity is embedded within the register item - there is no external entity definition. We are essentially creating a dummy entity definition for each reserved concept.