metafacture-core
metafacture-core copied to clipboard
Core package of the Metafacture tool suite for metadata processing.
The `file` attribute in the `` statement should except the same URL patterns as defined in the xinclude specification for the `href` attribute. This makes for a more consistent user...
The `files` attribute in the `` statement should except the same URL patterns as defined in the xinclude specification for the `href` attribute. This makes for a more consistent user...
The decoders work directly on character arrays. This can be problematic if the input data contains unicode characters which must be represented by a high/low surrogate pair. In this case...
Currently, the XmlDecoder loads referenced DTDs and fails on broken links. It would be useful when automatic DTD loading becomes a configurable XmlDecoder option.
The xinclude-handling in the Metamorph schema seems to have some issues. For instance, Metamorph requires that the `macros` element is specified before the first rules element. However, it is possible...
The blacklist and whitelist functions in metamorph should support lists in the same way the lookup function does.
Issue #219 fixes the problem that Java resources could not be referenced correctly in x-include statements in Metamorph. This problems is fixed in commit 356cb7844e3f21a3c92c62d46d1e234bd41374c0. It is still not possible,...
The `ObjectToLiteral` module should be renamed to `ObjectInLiteralWrapper`. The corresponding flux command (`object-to-literal`) should be changed to `wrap-in-literal`.
Add a setting which allows flux users to change the log level. The default log level should be info not debug.
The behaviour you observed is a bug indeed, @ah641054: Using wormholes users can combine data from multiple flows: ``` Flow A -> @wormhole; Flow B -> @wormhole; @wormhole -> Flow...