Result for 10962324D6C66EC4EE0B260E8F070A287FE66A02

Query result

Key Value
FileName./usr/share/man/man1/schema2example.1.gz
FileSize2208
MD5C5C20A8DB4190400C0427969AA3F5F48
SHA-110962324D6C66EC4EE0B260E8F070A287FE66A02
SHA-256C2334D6873E98F9D5CE5C114EF70E2A96BA642C3FEB904024B1D9AA60428CC4B
SSDEEP48:X3dowP6GOn4wkTL0TOcT1ohPwRdhheD2WeokdMp0aFGEFY:9oU6GiMTgTOcqPioDlNkCm
TLSHT1C1415CA6B630210E825934DD136260B314D76237D1C740A660D38E4EE69FD3644030D3
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