id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1112	<bound> vs. <bounds>	bob@…	framm	"The API used to output <bounds request_minlat='' request_minlon='' request_maxlat='' request_maxlon='' /> in the map request. I'm trying to get it supported again (http://trac.openstreetmap.org/ticket/1011) as osmarender really needs it to function at it's best.

It would be nice if josm also used <bounds> instead of <bound>, and also dropping box='' in favor of four separate values as you then only need the xml-parser that's already required and not a separate comma-separated parser (yes, it's actually non-trivial in xslt).

Perhaps josm could use request_{min,max}{lat,lon} parameters when reading from the api, and, if it has to generate them for itself, output just {min,max}{lat}{lon}? That sounds like a pretty correct way to handle things.

TomH wants us to clean up the inconsistencies here before he fixes the ticket so I'd appreciate somebody at least having a look at it pretty soon.
"	enhancement	closed	major		Core		fixed