With regard to aliases about the syntax.
Do we allow for ability to specify patterns rather than specific ones?
Full URI? Or like Turtle - prefix__name?
Can we build modules to interpret vanilla CF compliant netCDF?
Jim’s code solves this using separate prefixes/aliases file, which is currently bound to a tool and a convention with CF for examples.
- bounds attribute for coord variable, climatology attribute, values have grammar and referencing other variables and/or dimensions based on arcane rules
Could we build a general framework and build modules for the content?
How would those modules work?
With regard to aliases about the syntax.
Do we allow for ability to specify patterns rather than specific ones?
Full URI? Or like Turtle - prefix__name?
Can we build modules to interpret vanilla CF compliant netCDF?
Jim’s code solves this using separate prefixes/aliases file, which is currently bound to a tool and a convention with CF for examples.
Could we build a general framework and build modules for the content?
How would those modules work?