CPAN::Groonga

aPOD::JSON;

our $VERSION = 'v0.5.0';

# ABSTRACT: The JSON Formatted MetaPOD Spec

our $AUTHORITY = 'cpan:KENTNL'; # AUTHORITY











sub implementation_class { return 'MetaPod::Format::JSON' }

-8

=head1 NAME

MetaPOD::JSON - The JSON Formatted MetaPOD Spec

=head1 VERSION

version v0.5.0

=head1 SYNOPSIS

This is mostly a documentation stub, documenting the C<JSON> Formatted version of Met

:Format::JSON>|MetaPOD::Format::JSON >>

=begin MetaPOD::JSON v1.1.0

{ "namespace":"MetaPOD::JSON" }


=end MetaPOD::JSON

=for Pod::Coverage implementation_class

=head1 Using MetaPOD::JSON in your 

the MetaPOD format

=head1 VERSION

version v0.5.0

=begin MetaPOD::JSON v1.1.0

{ "namespace":"MetaPOD::Spec" }


=end MetaPOD::JSON

=head1 Specifying MetaPOD

=head2 FORMATS

A FORMAT is a MetaPOD 

Where C<$1> is the name of the MetaPOD C<FORMAT>

e.g:

    =begin MetaPOD::JSON

    { JSON DATA }

    =end MetaPOD::JSON

These may, or may not, correspond to real world parser names, but the actu

 is more an indication of a I<specification>

And it may be that a C<MetaPOD::JSON> declaration loads MetaPOD::Format::JSON

=head2 VERSIONS

A VERSION as part of a Segment declaration B<must> come af

ENTNL');
$bundle->configure;

my @stopwords = (qw(
   MetaPOD deduplicated behaviour unrecognised JSON namespace behaviours directionally
));
for my $var (@stopwords) {
  $bundle->add_or_append_policy