Data::Mapper is an implementation of Data Mapper Pattern described in PofEAA, written by Martin Fowler, and is kind of a ORM, but not limited only to it, that is, this module just relates some data to another; for example, data from a database to Perl's objects.
This module, actually, merely defines a simple convention how to make relations between some data to another, and now has only one adapter implementation: Data::Mapper::Adapter::DBI.
See https://github.com/kentaro/data-mapper for details.
This module just adds URL resources at PrePAN into META.yml. I hope metacpan.org would read metadata from META files and make a link back to PrePAN page from there.
I sent a pull-req to metacpan authors to add a link to PrePAN from metacpan if available.
I wrapped discussion on the problem at below.
Even if we validate user inputs on client-side according to client-side form validation spec. defined in HTML5, we still need do same thing on server-side. It results that there're redundant validation rules around. How about regarding client-side form validation as some common format for describing validation rules both for client-side and server-side?
This distribution consists of 2 parts modules below:
This module has been kinda proof-of-concept thing yet.
Amon2::Auth handler for Hatena auth (Hatena OAuth Spec.).
It might be better for the code to be directly in Amon2::Auth distribution. Should I send a pull-req rather than creating such an independent distribution? > @tokuhirom