This wasn't an automated edit.

And I disagree about the tagging here. Because messing in every unit is not only ugly but is just a lot simpler if done on the editing side. OSM is a database AND not necessarily 'readable' by humans (although partly important I of course agree)

A good editor would read the value and convert to the readers preferences. The same for writing the value.

And I agree with you that the mapper is very important (I do not agree on the term 'resource' ;)). And so we should fix the mapping software making converting US short and long tons etc into tons.

Also I do intend to change 'lbs' values because they are a lot more frequent and kind of 'unwikied' standard, so I also do not think 100% that the wiki is OSM.
But e.g. I intend to change 'lb' into 'kg' because such values are also very infrequent.

Why is this harder to use? In fact consuming values like this is very confusing. The mapping software should make it easier with conversion, so I my counter argument is: your mapping software should be improved to make consuming the data easier. And an important btw: such a value '15 us tons' is used VERY rarely world wide (and therefor for US too)

Just have a look here: http://taginfo.openstreetmap.org/keys/maxweight

It has nothing to do with software. The wiki is very explicit when it comes to weight:
Therefore if a maxweight for a country that uses U.S. customary or Imperial measurements is desired, a conversion is required.

maxweight=*

Okay, so please undo.

Sorry, I've placed a note to avoid loosing information, I'm not unsure how to map it. Would you help?

I get:
infinity distance? for way:356352472
infinity distance? for way:360780242
:)

Please review as this road is clearly too long!