Result for 19D66F8F039774CDC93F2B0018FB9450A131CB59

Query result

Key Value
FileName./usr/share/man/man3/XML::Compile::Schema::NameSpaces.3pm.gz
FileSize3292
MD583411F9449C5D6565C3F6CAFEF0EDAB0
SHA-119D66F8F039774CDC93F2B0018FB9450A131CB59
SHA-2561D76E325915348A7F94B0E2448DD32B9B07AB1A6E0D3C5E5B05F597AE1DBB025
SSDEEP48:XBZqN1HKLeuLpJbaf/Wk9sFiXlZPR2rkXXfPM9GejmtM1WACbsh+W5dE/4E4:RoN1qLeqAuzFIP52rkXXM9GejmmCbpU
TLSHT1DB615B094EBC60C2654BD71AE8A69083664FF935630932DA984D78855B234A631FC3FA
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
MD5DFFE658C2EE844C3684CFF734F2B5B7A
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.47
PackageVersion1.63
SHA-125C2A5E26E61ADCC2BE9D993D3445392B1E5EB48
SHA-25697A5D9379DB3E90FD276DDBEF04FCCD2F8F920300CA9D0389644ACD2CDA2417E