Namespace in encode-xml changes order

[TobiasNx]

The order of the namespace input is not the same as given in the option of the flux modul:

https://metafacture.org/playground/?flux=inputFile%0A%7Copen-file%0A%7Cas-lines%0A%7Cdecode-json%0A%7Cfix%28transformationFile%29%0A%7Cencode-xml%28recordtag%3D%22%22%2Croottag%3D%22mets%3Amets%22%2Cattributemarker%3D%22@%22%2Cvaluetag%3D%22value%22%2C+namespaces%3D%22__default%3Dhttp%3A//www.w3.org/TR/html4/\ndcterms%3Dhttp%3A//purl.org/dc/terms/creator\ndv%3Dhttp%3A//dfg-viewer.de/\nvl%3Dhttp%3A//visuallibrary.net/vl\nvls%3Dhttp%3A//semantics.de/vls\nmarcxml%3Dhttp%3A//www.loc.gov/MARC21/slim\nepicur%3Durn%3Anbn%3Ade%3A1111-2004033116\noai%3Dhttp%3A//www.openarchives.org/OAI/2.0/\nzvdd%3Dhttp%3A//zvdd.gdz-cms.de/\nmets%3Dhttp%3A//www.loc.gov/METS/\nvlz%3Dhttp%3A//visuallibrary.net/vlz/1.0\nmods%3Dhttp%3A//www.loc.gov/mods/v3\nxlink%3Dhttp%3A//www.w3.org/1999/xlink\nxmlns%3Amix%3Dhttp%3A//www.loc.gov/mix/v20\ndc%3Dhttp%3A//purl.org/dc/elements/1.1/%22%29%0A%7Cprint%0A%3B&transformation=move_field%28%22_id%22%2C+%22id%22%29%0Amove_field%28%22a%22%2C+%22title%22%29%0Apaste%28%22creator%22%2C+%22b.v%22%2C+%22b.n%22%2C+%22~aus%22%2C+%22c%22%29%0Aretain%28%22id%22%2C+%22title%22%2C+%22creator%22%29%0A%0A&data=%7B%22a%22%3A+%22Faust%22%2C+%22b%22%3A+%7B%22n%22%3A+%22Goethe%22%2C+%22v%22%3A+%22JW%22%7D%2C+%22c%22%3A+%22Weimar%22%7D%0A%7B%22a%22%3A+%22R%C3%A4uber%22%2C+%22b%22%3A+%7B%22n%22%3A+%22Schiller%22%2C+%22v%22%3A+%22F%22%7D%2C+%22c%22%3A+%22Weimar%22%7D

[dr0i]

Don't know exactly what you mean ("namespace input" ?) but the order of namespaces in XML is arbitrary.

[TobiasNx]

If arbitrary, then we can close.

Don't know exactly what you mean ("namespace input" ?) but the order of namespaces in XML is arbitrary.

What i mean is the value of the namespace option: namespaces=. See the example in the OP.