Aus öffentlichen Paketdaten erstellte Orientierung.
Ein Flutter/Dart-Paket, das XML-Daten in JSON-Format konvertiert und mehrere Konvertierungsstandards wie Badgerfish, GData, OpenRally und Parker unterstützt. Es ermöglicht eine nahtlose Integration mit APIs und Diensten, die XML verwenden, indem es diese in eine zugänglichere JSON-Struktur umwandelt. Das Paket ist leichtgewichtig und für den Einsatz auf mehreren Plattformen konzipiert, wodurch es ideal für Apps für Android, iOS, Web, macOS, Windows und Linux ist. Es vereinfacht die Datenanalyse in Anwendungen, die XML-Antworten erhalten.
Anwendungsfälle
XML-API-Antworten analysieren
Konvertierung veralteter XML-Daten in JSON
Integration mit XML-basierten Webdiensten
Datenverwaltung in plattformübergreifenden Anwendungen vereinfachen
Migration von XML zu JSON-Workflows
Hauptmerkmale
Unterstützt mehrere XML-zu-JSON-Konvertierungsstile
Leichtgewichtig und einfach zu integrieren
Plattformübergreifende Kompatibilität
Behandelt verschachtelte XML-Strukturen
Bietet konfigurierbare Konvertierungsoptionen
Geeignet für
Entwickler, die mit XML-APIs arbeiten
Anwendungen, die Datenumwandlung erfordern
Projekte, die von XML zu JSON migrieren
Full-Stack-Dart-Entwickler
Mobile- und Webanwendungen mit strukturierten Daten
Hinweise
Das Konvertierungsverhalten unterscheidet sich je nach Stil (Badgerfish, GData usw.)
Eingabedaten im XML-Format müssen möglicherweise überprüft werden
Nicht geeignet für komplexe XML-Schemata ohne Vorverarbeitung
Die Ausgabestruktur hängt von der gewählten Konvertierungsmethode ab
Nur XML-zu-JSON, keine Rückwärtsfunktion
Original-README
Originaler README-Schnappschuss aus dem verknüpften Quell-Repository. Aktuelle Inhalte finden Sie im Repository.
xml2json
An XML to JSON conversion package.
This package allows the parsing of XML strings and the transformation of the resulting parse
tree into the following XML JSON conventions :-
Parker(optionally with attributes)
Badgerfish
Google Data(GData).
OpenRally
The package uses the xml parser to perform the parsing of XML data into a parse tree.
Exact transforming rules can be found below.
The Parker convention is a lossy but lean conversion from XML into JSON, ideal for lightweight
XML parsing of collections of books, records etc. where attributes and namespace information
is not needed.
Badgerfish and GData both preserve XML information such as attributes and namespaces. These are more
suited to heavyweight XML parsing of say ATOM feeds where this information may be needed.
See the main Xml2Json class for usage.
Xml2Json - details of the JSON output of the transformers
The rules each transformer uses are documented below, following that a global rules section describes
rules all the transformers obey.
Parker
The Parker transformer follows the rules documented here with the following caveats :-
Similar named consecutive elements are grouped under the name of the element, not
anonymously in an array as in the rules above, so :-
This allows grouped elements to be extracted by name in one go, i.e. from above all the
items can be referenced through the 'item' property. This is better for the usage this transform
is suited to, the parsing of simple list like structures of books, records etc that just happen to
be in XML.
There is also an alternative Parker transformer that transforms node elements that have attributes.
The standard Parker transformer should suffice for most use cases.
Badgerfish
The Badgerfish transformer follows the rules documented here, to summarise :-
Element names become object properties
Text content of elements goes in the $ property of an object.
Nested elements become nested properties
Multiple elements at the same level become named array elements.
Attributes go in properties whose names begin with @.
Multiple attributes at the same level become array elements.
Active namespaces for an element go in the element's @xmlns property.
The default namespace URI goes in @xmlns.$.
Other namespaces go in other properties of @xmlns.
Elements with namespace prefixes become object properties, too.
The @xmlns property goes only in the object relative to the element where namespace was declared.
Badgerfish also has the option of using local xml node names by setting the useLocalNameForNodes parameter to true
when transforming.
This has the effect that since the element key("soapenv" in the example below) is implementation dependent (i.e. one manufacturer
will assign "soapenv as the key, while another might assign "ENV"), using the key in the node name makes the
resulting json from xml2json dependent on the implementation as well.
This is the Google Data(GData) format specified here
This is basically the same as Badgerfish except that it drops the @ symbol for attributes and
uses $t instead of just $ for values, also the XML Processing element is included at the top of the
transform.
This is basically the same as Badgerfish except that it drops the @ symbol for attributes and
uses (key/value) format for values, also the XML Processing element is included at the top of the
transform.
Global Rules
Each transformer implements the following rules :-
All JSON output is in the form of strings, numeric literals, true and false become strings.
This allows the output to be 'transmission ready' if needed for RESTful interfaces.
XML Comments are ignored.
CDATA sections are ignored for Parker but translated into '__cdata' properties
for Badgerfish and GData