comment on

I don't find this any better than the equivalent Makefile.PL:

# This file provides instructions for packaging.

@prefix : <http://purl.org/NET/cpan-uri/terms#> .

<http://purl.org/NET/cpan-uri/dist/all-your-base-are-belong-to/project
+>
    :perl_version_from _:main ;
    :version_from _:main ;
    :readme_from _:main ;
    :test_requires "Test::More 0.61", "File::Basename", "File::Spec", 
+"Data::Dumper" ;
    :requires "parent", "version 0.77".

_:main <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#fileN
+ame> "lib/all/your/base/are/belong/to.pm" .
[download]

Worse, apparently your packaging script just bundles a bunch of RDF-parsing modules, then calls them from Makefile.PL, so an ordinary CPAN author has to learn your nonstandard RDF system to contribute to your modules. Perl already has at least 3 widely-used formats to describe a module: ExtUtils::MakeMaker, Module::Build, and Module::Install; people should think hard before adding yet another.

In reply to Re^2: Project Metadata Model by educated_foo
in thread Project Metadata Model by Xiong

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks