id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
710	Consider updating/generalising Software_ID element of BUFR file	Ian Culverwell	Kent Bækgaard Lauritsen	"Stig Syndergaard (DMI) has suggested generalising octet 5 of Sec 4 of a BUFR file, the {{{Software ID}}}, so that it could contain information on the software that produced the data in the first place, as well as the version of ROPP that produced the BUFR file (which is what it stores now.)  In other words, it would combine {{{ROprof%processing_software}}} and {{{ROprof%software_version}}}.

According to Table 5 of http://www.romsaf.org/romsaf_bufr.pdf, 14 bits are available to hold {{{Software ID}}}.  This could store any whole number between 0 and 16383 inclusive.  These 14 bits could also be split into two blocks of 7 bits, each of which could hold a whole number between 0 and 127.  This might be a natural way to hold the two pieces of information.  However it is done, we would need a lookup table to map between ({{{ROprof%processing_software}}}, {{{ROprof%software_version}}}) and {{{Software ID}}}."	enhancement	new	normal	Whenever	ROPP(all)	11.0