Parents (Total: 9)

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

Key	Value
MD5	A54DA1E1F6577EF6A240E4ED493B10B4
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	lp153.1.10
PackageVersion	1.63
SHA-1	3B75274485732C5FA0DFF7435197FF62D2EC6217
SHA-256	3B84B425EBC1F0480C22A90E6D36BF8D085A0AC0195BADE5799080DDC8984437

Key	Value
MD5	C067011903DEC4BA827DBEB66FFAB861
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	1.36
PackageVersion	1.63
SHA-1	F0FA43DE0D1C257E52254C22EA1D8E1152FAEE4E
SHA-256	A25F895C05DA3A67E02AA8F8369AB7E274938BD934F5D5882DFABFBF412CAE3B

Key	Value
MD5	4D83E114DEE25AE03ADBBF61C46F6C5F
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	lp150.1.1
PackageVersion	1.63
SHA-1	3CEF37275AA142C890D6604ADF581BBC41AEB5A9
SHA-256	A155FDCC14AFEFF192BC7258C9384C5608DBB0DA24B33D13A74FB7DE26E5AE9A

Key	Value
MD5	BB75B074952253404593CD41FF7B2787
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	1.38
PackageVersion	1.63
SHA-1	6E8405978A17FA99FB4E095ECF273402B867C078
SHA-256	8AE5657129D61BEC48FFA4D4ED72476873DBDEA42B69647F294761216F77D6C4

Key	Value
MD5	BC97E5CA482EEC1D7371D1672D77DABD
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	1.2
PackageVersion	1.63
SHA-1	26D2CFC6C0C50B222F861C49145AFEC929B44FC8
SHA-256	AEA8FF90A989E3AA9008413F748B63261BA7E857FF92976E283F715899F8192E

Key	Value
MD5	A975294F7CDBCC8257AE43FF8E09FD26
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	lp151.1.1
PackageVersion	1.63
SHA-1	B6270AC511FE7C19D094FD853D3ADCCF27394FD9
SHA-256	3F8D2CF19B8114EA6369581F6CC46B3559443C7D92CC2B72D9D7D3987B932BFB

Key	Value
MD5	E29B0C888489D1F518C8B359A8A7E202
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	1.8
PackageVersion	1.63
SHA-1	BABD2B20E7A6C9F61EB44D6197ADC4D6528E177F
SHA-256	214488BD4BBCD94B048384B87C537B8F172EDEB97A8F0BDCD2B9E7D950E8C64E

Key	Value
MD5	A501421CB861092E174BFAC521B30EF4
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	lp152.1.1
PackageVersion	1.63
SHA-1	204E393FC4D981C5BF45AF74BD6FB6A27CCBA342
SHA-256	62DCE93917C6FB9EAD9A8A4F3F63F1BB290E1210F9A279B784FF680E33EAB211

Key	Value
MD5	86CFAFEC931D4070D92E19218FA59FA3
PackageArch	noarch
PackageDescription	Many (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.
PackageName	perl-XML-Compile
PackageRelease	1.1
PackageVersion	1.63
SHA-1	541AB915BE8CE6AEAC98D45B7B80484F83CDBDA3
SHA-256	AD96F3E7E48103525D51F6EC5549C6125B586A018A80BC6587546807618EE47C