Result for 2620C1251215D56F3F6378B3ED3AC0A0A3451020

Query result

Key Value
FileName./usr/share/man/man3/XML::Compile::Schema::Instance.3pm.gz
FileSize3019
MD50A96CC8F0638A904A3D962C27A7F6274
SHA-12620C1251215D56F3F6378B3ED3AC0A0A3451020
SHA-2563EA611753C45C0B1374FAA67C23ADF27AF251F4525A96FB75D8DC4A7D9F312B8
SSDEEP48:X/DOXstljywbhNZyPucNQPxK4RElP8B33XpkFHdoLQvbiRkuNA6TDahOVav4YPH6:b+MgwbRmu/pBRYEFpkpdeM1uS6vahOOG
TLSHT155516D22E4AD07548B5E56F880DA61A417F826934AA97947F80032E00C079BFE7C1E7D
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