RDF-Server 0.08 Latest
Kwalitee Issues
- meta_yml_conforms_to_known_spec
-
Take a look at the META.yml Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.yml accordingly.
Error: Expected a list structure (author) [Validation: 1.3]
- no_broken_auto_install
-
Upgrade the bundled version of Module::Install to at least 0.89, but preferably to the most current release. Alternatively, you can switch to another build system / installer that does not suffer from this problem. (ExtUtils::MakeMaker, Module::Build both of which have their own set of problems.)
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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::Server | toolkit for building RDF servers | 0.08 | metacpan |
RDF::Server::Constants | useful constants used by the framework | metacpan | |
RDF::Server::Exception | exception classes | metacpan | |
RDF::Server::Formatter | handles rendering an object in a particular format | metacpan | |
RDF::Server::Formatter::Atom | Work with Atom documents | metacpan | |
RDF::Server::Formatter::JSON | Work with JSON documents | metacpan | |
RDF::Server::Formatter::RDF | Work with RDF/RSS documents | metacpan | |
RDF::Server::Interface | defines how the server speaks over the protocol | metacpan | |
RDF::Server::Interface::REST | REST interface | metacpan | |
RDF::Server::Model::RDFCore | metacpan | ||
RDF::Server::Protocol | defines how RDF::Server communicates with the world | metacpan | |
RDF::Server::Protocol::Embedded | methods to use RDF::Server in another program | metacpan | |
RDF::Server::Protocol::FCGI | FastCGI protocol handler for RDF::Server | metacpan | |
RDF::Server::Protocol::HTTP | POE-based standalone HTTP server | metacpan | |
RDF::Server::Resource::RDFCore | metacpan | ||
RDF::Server::Role::Container | renderable resource that holds resources | metacpan | |
RDF::Server::Role::Handler | manages handling part of a URL path | metacpan | |
RDF::Server::Role::Model | triple store role | metacpan | |
RDF::Server::Role::Mutable | requirements for a mutable resource | metacpan | |
RDF::Server::Role::Renderable | role for resources that can be rendered | metacpan | |
RDF::Server::Role::Resource | expectations of a resource object | metacpan | |
RDF::Server::Semantic | metacpan | ||
RDF::Server::Semantic::Atom | RDF service with Atom-ic semantics | metacpan | |
RDF::Server::Semantic::Atom::Category | supports use of Atom category documents | metacpan | |
RDF::Server::Semantic::Atom::Collection | supports use of Atom collection documents | metacpan | |
RDF::Server::Semantic::Atom::Handler | metacpan | ||
RDF::Server::Semantic::Atom::Service | supports use of Atom service documents | metacpan | |
RDF::Server::Semantic::Atom::Types | Atom-specific types | metacpan | |
RDF::Server::Semantic::Atom::Workspace | metacpan | ||
RDF::Server::Semantic::RDF | RDF semantic for the RDF::Server framework | metacpan | |
RDF::Server::Semantic::RDF::Collection | metacpan | ||
RDF::Server::Semantic::RDF::Handler | metacpan | ||
RDF::Server::Semantic::RDF::Types | metacpan | ||
RDF::Server::Types | Moose types used by the RDF::Server framework | metacpan | |
RDF::Server::XMLDoc | convenience class for managing XML documents | metacpan |
Provides
Name | File | View |
---|---|---|
RDF::Server::Resource::RDFCore::Types | lib/RDF/Server/Resource/RDFCore.pm | metacpan |