Result for 1E5FD14086D08C49C8AEACADD4BCE58570C71B8A

Query result

Key Value
FileName./usr/share/man/man3/XML::Compile::Util.3pm.gz
FileSize2562
MD53B0EAC984CCB8D84809C3458114FD84A
SHA-11E5FD14086D08C49C8AEACADD4BCE58570C71B8A
SHA-256A199C84BB5915C28EF0378473CD69AC289E51DB334DC3DA3D945AB21458DED0D
SSDEEP48:XF5nVOLPLg2pm99Zhq2jVUMrxWuOFm1DfTR1J4gSZOfjNgkYiWzarUKxYQv:15nKP02pwy2jVUwQg16gBfjEiFtxYQv
TLSHT146516DE070EE2724D781BE6C8AE719361FC2BA11828D531D1F53D8E3268F78D86A4009
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD507590DB2CCB67115DD7172CB2A0CBC27
PackageArchnoarch
PackageDescriptionMany (professional) applications process XML messages based on a formal specification, expressed in XML Schemas. XML::Compile translates between XML and Perl with the help of such schemas. Your Perl program only handles a tree of nested HASHes and ARRAYs, and does not need to understand namespaces and other general XML and schema nastiness. Three serious WARNINGS: * The focus is on *data-centric XML*, which means that mixed elements are not handler automatically: you need to work with XML::LibXML nodes yourself, on these spots. * The *data is not strictly validated*, still a large number of compile-time errors can be reported. Values are checked quite thoroughly. Structure as well. * Imports and includes, as used in the schemas, are NOT performed automatically. Schema's and such are NOT collected from internet dynamically; you have to call XML::Compile::Schema::importDefinitions() explicitly with filenames of locally stored copies. Includes do only work if they have a targetNamespace defined, which is the same as that of the schema it is included into.
PackageNameperl-XML-Compile
PackageRelease1.44
PackageVersion1.63
SHA-1A908290E56A8FD38828F2253BE4F399B40A30D5B
SHA-256D711A69A8D66A6A32CB5DF0F479F8E88F9C71F8A10BF1C747418CF99918C67B5