RDF-Trine-Node-Literal-XML 0.1
- Released by
- KJETILK
- Version
- Release Date
- 2009-11-18
- Kwalitee
- 134.38
- Core Kwalitee
- 87.5
- LINKS
RDF-Trine-Node-Literal-XML 0.1 Deleted
Kwalitee Issues
- has_readme
-
Add a README to the distribution. It should contain a quick description of your module and how to install it.
- has_changelog
-
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
- has_human_readable_license
-
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
- has_license_in_source_file
-
Add =head1 LICENSE and the text of the license to the main module in your code.
- valid_signature
-
Sign the dist as the last step before creating the archive. Take care not to modify/regenerate dist meta files or the manifest.
Error: Old SIGNATURE detected. Please inform the module author to regenerate SIGNATURE using Module::Signature version 0.82 or newer. gpg: Signature made Wed 18 Nov 2009 07:16:13 AM JST gpg: using DSA key 944FC6A76A6A0BBC gpg: Can't check signature: No public key --- SIGNATURE Wed Nov 18 07:16:24 2009 +++ @@ -1,15 +1,17 @@ -SHA1 78f45d0dd01c8b6b8f68fe0643835ec5fd009538 MANIFEST -SHA1 5a57f35d186d061c3500c67b31320d42c82fa308 MANIFEST.SKIP -SHA1 ffc9edb3e0d36371c9a80dad7b5d7c541966379a META.yml -SHA1 014640626a5c91e5fa06e637860c98e2fc8c032e Makefile.PL +SHA1 6ea06e7920524cede594d32a47dcd8c9ffd60960 MANIFEST +SHA1 8302b1866cf0de3f755b3c64abd61ad923d11158 MANIFEST.SKIP +SHA1 c7735498066b48edc26f6a2d0f014e85f89c64be META.yml +SHA1 36f3ff289b7b77ef0b5a5e211fda6a33ee184159 Makefile.PL SHA1 fd5f3c4f0418efee3b9b16cf8c3902e8374909df inc/Module/Install.pm SHA1 7cd7c349afdf3f012e475507b1017bdfa796bfbd inc/Module/Install/Base.pm SHA1 ba186541bbf6439111f01fc70769cf24d22869bf inc/Module/Install/Can.pm SHA1 aaa50eca0d7751db7a4d953fac9bc72c6294e238 inc/Module/Install/Fetch.pm +SHA256 2bb4751f08d85ce25b62db93090f0672bc047fbb915fca2fffad3f5e977cb487 inc/Module/Install/Include.pm SHA1 3e83972921d54198d1246f7278f08664006cd65d inc/Module/Install/Makefile.pm SHA1 12bf1867955480d47d5171a9e9c6a96fabe0b58f inc/Module/Install/Metadata.pm SHA1 f7ee667e878bd2faf22ee9358a7b5a2cc8e91ba4 inc/Module/Install/Win32.pm SHA1 8ed29d6cf217e0977469575d788599cbfb53a5ca inc/Module/Install/WriteAll.pm -SHA1 96a71b1821a24351eb613c21c4cdec9513c84245 lib/RDF/Trine/Node/Literal/XML.pm +SHA256 0bbc550b8e93990c0d3843fcbc3adf238f98381e07b5b6fabcae1bf4ed4a3deb inc/Test/Signature.pm +SHA1 916948f1b258f4e25c65666095877e8a4fca2ded lib/RDF/Trine/Node/Literal/XML.pm SHA1 4a32b860277df7f42ec67244b4aca1783f55f52a t/00signature.t SHA1 9d9fee380a6912449a07ff053c6862176aeda6a9 t/xmlliteral.t ==> MISMATCHED content between SIGNATURE and distribution files! <==
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- has_known_license_in_source_file
-
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
- meta_yml_has_provides
-
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Modules
| Name | Abstract | Version | View |
|---|---|---|---|
| RDF::Trine::Node::Literal::XML | RDF Node class for XMLLiterals | 0.1 | metacpan |