Proposal for simplifying usage of h5import
------------------------------------------

1. h5import <infile> [<infile> ...] -o[utfile] <outfile>

This command accepts one or more input files and creates a 
single H5 output file. All parameters are default initialized
as follows.

Defaults:
	PATH - 'h5dataset'
        INPUT-CLASS - FP
	INPUT-SIZE - 32
        RANK - 3
	DIMENSION-SIZES - 5 5 5 
	OUTPUT-CLASS - FP
	OUTPUT-SIZE - 32
	OUTPUT-ARCHITECTURE - NATIVE
	OUTPUT-BYTE-ORDER   - NATIVE	
	
	No compression 
	No chunking
	No external storage
	No extended dimensions
	

2. A configuration file can be used to override all defaults.
The command-line syntax is as follows:

h5import <infile> -c[onfig] <configfile> 
		  [<infile> -c[config] <configfile>...]  
				      -o[utfile] <outfile>

All options can be specified in the configuration file. 
(Refer to specification of h5import 
/afs/ncsa/web/HDF/htdocs/rfc/h5tools/h5import.txt)

The required options are
	INPUT-CLASS
	INPUT-SIZE
        RANK
	DIMENSION-SIZES

The defaults for other options are
	PATH - 'h5dataset'
	OUTPUT-CLASS - 	'IN' if INPUT-CLASS is 'TEXTIN' or 'IN'
			'FP' if INPUT-CLASS is 'TEXTFP' or 'TEXTFPE' 
			or 'FP'
			'UIN' if INPUT-CLASS is 'TEXTUIN' or 'UIN'
	
	OUTPUT-SIZE - same as INPUT-SIZE
	OUTPUT-ARCHITECTURE / OUTPUT-BYTE-ORDER - NATIVE

	No compression 
	No chunking
	No external storage
	No extended dimensions
	
NOTES 
1. Sample configuration files for enabling compression, 
chunking, external storage, extended dimensions and other options
will be provided with the distribution for user convenience.

2. The idea of overriding defaults using command-line arguments 
is unweildy on account of the number of options available. They can be
overrridden in a convenient way using the configuration file which 
serves the purpose of clubbing all command-line arguments in a single 
file.