Updated metadata and documentation

Also created the XML::Axk::Bundle namespace.

Changes

@@ -1,5 +1,14 @@
 Revision history for XML-Axk
 
+0.001009    2019-04-26
+        Updated metadata
+
+0.001008    2019-02-22
+        Non-trial release of 0.001007
+
+0.001007-TRIAL    2019-02-16
+        Fixed per cpantesters results
+
 0.001006    2019-02-14
         No substantive changes
 

MANIFEST

@@ -3,6 +3,7 @@ Changes
 lib/XML/Axk.pm
 lib/XML/Axk/App.pm
 lib/XML/Axk/Base.pm
+lib/XML/Axk/Bundle.pod
 lib/XML/Axk/Core.pm
 lib/XML/Axk/DOM.pm
 lib/XML/Axk/L/L0.pm

Makefile.PL

@@ -147,6 +147,12 @@ my %opts = (
             },
         },
 
+        x_authority => 'cpan:CXW',
+        x_contributors => [
+			# Use CPAN emails where possible, so MetaCPAN will pick them up.
+			'Christopher White <[email protected]>',
+        ],
+
         $provides ? (provides => $provides) : (),
 
     }, #META_MERGE

lib/XML/Axk.pm

@@ -5,20 +5,12 @@ use strict;
 use warnings;
 use XML::Axk::Base;
 
-our $VERSION = '0.001008';
-
-#use parent 'Exporter';
-#our (@EXPORT, @EXPORT_OK, %EXPORT_TAGS);
-#BEGIN {
-#    @EXPORT = qw();
-#    @EXPORT_OK = qw();
-#    %EXPORT_TAGS = (
-#        default => [@EXPORT],
-#        all => [@EXPORT, @EXPORT_OK]
-#    );
-#}
+our $VERSION = '0.001009';
+our $AUTHORITY = 'cpan:CXW';
 
+1;
 # Docs {{{1
+__END__
 
 =head1 NAME
 
@@ -32,7 +24,4 @@ embedded usage in other Perl scripts.
 =cut
 
 # }}}1
-
-1;
-__END__
 # vi: set fdm=marker: #

lib/XML/Axk/App.pm

@@ -8,7 +8,7 @@ use XML::Axk::Core;
 # Semantic versioning, packed per Perl rules.  Must always be at least one
 # digit left of the decimal, and six digits right of the decimal.  For
 # prerelease versions, put an underscore before the last three digits.
-our $VERSION = '0.001008';
+our $VERSION = '0.001009';
 
 use Getopt::Long qw(GetOptionsFromArray :config gnu_getopt);
 

lib/XML/Axk/Bundle.pod

@@ -0,0 +1,14 @@
+=head1 NAME
+
+XML::Axk::Bundle - namespace for plugin bundles
+
+=head1 SYNOPSIS
+
+Axk can be extended with bundles.  A bundle may implement a new backend
+or language, for example.  For ease of installation, bundles should be
+distributed as CPAN distributions under the C<XML::Axk::Bundle::> namespace.
+For example, a new language might be C<XML::Axk::Bundle::LangFoo>.
+
+Names in the C<Bundle> namespace are first-come, first-served.  Authors are
+requested to name language bundles starting with C<L> and backend bundles
+starting with C<B>, but other than that, have fun!

lib/XML/Axk/Core.pm

@@ -11,7 +11,7 @@ use XML::Axk::Base qw(:all);
 use XML::Axk::Preparse;
 use Data::Dumper;
 
-our $VERSION = '0.001008';
+our $VERSION = '0.001009';
 
 =encoding UTF-8
 

lib/XML/Axk/Language.pm

@@ -82,6 +82,7 @@ sub import {
 # }}}1
 1;
 # === Documentation ===================================================== {{{2
+__END__
 
 =pod
 
@@ -105,11 +106,6 @@ When implementing a language:
             updater => sub { ... } );
     }
 
-If all you need is the registry:
-
-    use XML::Axk::Language ();
-    # Then do something with @XML::Axk::Language::SP_Registry.
-
 =head1 OPTIONS
 
 C<target>: the name of the package to load the script parameters (SPs) into

lib/XML/Axk/Object/TinyDefaults.pm

@@ -11,7 +11,7 @@ use Data::Dumper;
 use Import::Into;
 
 our $ObjTiny;
-our $VERSION = '0.001008';
+our $VERSION = '0.001009';
 
 BEGIN {
     require parent;