Convert genericode XML to genericode JSON
This stylesheet supports only a subset of genericode XML in the conversion
to JSON syntax.
Text output
Invocation parameters and input file
The input file is an instance of a subset of the genericode XSD model
for genericode XML. Empirical evidence is this subset is a commonly-used
subset meeting the needs of many users.
Supported at this time is only simple lists with multiple rows of multiple
columns of simple values, not any complex values as defined by genericode.
The invocation can include verbose=yes to serialize the list of code values
as verbose as the introductory material. When not verbose (the default) the
list of codes is simplified.
Indication of whether or not the code list values are explicit
Main logic
Get things going
Annotations serialize the application info based on the namespaces in use.
Most elements can be transliterated.
Column sets serialize the column and key components separately
Column sets serialize the column and key components separately
Column references are handled explicitly
When not verbose, the list of codes is simplified
Housekeeping, etc.
Generic serializations simply create property strings.
Note that this does not handle attributes and elements of the same name
and namespace.
Note that this does not handle mixed content.
The invoker of this is putting the content in a list, so the name isn't
needed.
Handle a given generic element
Which nodes are not to be handled
Handle generic content of elements
A pushed text node is ignored as it is assumed to be indentation.
The identity template is used to copy all nodes not already being handled
by other template rules.
Return the XPath of the given node
The node to report on
/
[]
/@