My understanding is that a CSV has the values separated by commas and records separated by new lines. If my understanding is correct then I don't have a CSV file.

After answering that only then would I consider uploading to CPAN, and then you would know more of how you should name it, knowing you know how others would/could use it.

I would not create a module that uses a non-standard file format when that format is significantly like other formats. For instance, we can give a nod to YAML, seeing it's substantially different from CSV (and has Data::Dumper like functionality built in), although this looks like an incompatible version of CSV that would only create confusion.

Thus, my opinion is... leave it off CPAN entirely until the use cases can be rationalized. And until you think your version is superior to other competing formats. The name should come more easily once you know what it is.

I do not mean to offend
On the contrary, I welcome your feed back.

your module sounds like a solution in search of a problem
My module has solved a problem for me - in my case, at least, there was already a pre-existing problem ;)

Why would someone else ... use this module
...
I would not create a module that uses a non-standard file format
Part of my original question was whether the file format I am using has a name. If the style did have a name it would then make a release to CPAN more acceptable as, IMHO, it would mean enough people produce/use it to give it a name. If it had/has a name it would probably has uses and therefore others may benefit.

Thus, my opinion is... leave it off CPAN entirely until the use cases can be rationalized
I agree with you - there is no point in clogging up the CPAN directory with a pointless module that no-one will ever need, use or care about.

I did originally say that I wanted to release it to CPAN. The Perl community (this includes CPAN, Perlmonks and various Perl mailing lists) have done much to assist me over the years. I finally thought that I could give something back. It would appear that this occasion will have to wait until something more suitable comes along.

Many thanks.

use strict;
use Data::Dumper;

my @blocks = do { local $/='ID:'; <DATA> };
shift @blocks;

my %config;
foreach my $line (@blocks) {
    my ($id) = $line =~ /^(\w+)/;
    my %keys = $line =~ /^(\w+):(\w+)/gms;
    $config{$id} = \%keys;
}

print Dumper(\%config);

__DATA__
HEADER1:value
HEADER2:value
ID:id1
KEY1:A
KEY2:B
KEY3:C
ID:id2
KEY3:E
KEY2:F
ID:id3
KEY5:G

__OUTPUT__
$VAR1 = {
          'id1' => {
                     'KEY3' => 'C',
                     'KEY1' => 'A',
                     'KEY2' => 'B'
                   },
          'id2' => {
                     'KEY3' => 'E',
                     'KEY2' => 'F'
                   },
          'id3' => {
                     'KEY5' => 'G'
                   }
        };
[download]

You mean putting something like this on to CPAN?

No, I don't.

I did say in my original post that I wasn't asking for solutions, and that in the context of the question what was returned did not matter.

My module allows you to specify which of the keys you want returned, which keys are mandatory, whether keys can be repeated for a single ID, what headers key:value pairs are present, what footer pairs, etc.

It's not as simple as the example I gave - that is why it was an example.

My question was aimed at trying to find a name for that style of file. I believe that the files I have are being generated from some db running on some kind of mainframe system. Maybe this format is seen frequently in the mainframe world - I don't know - and so I thought I would throw the question to the world.

Thanks.