@SaMatra: My assumption is that "world coordinates" used by these new commands are not tied to the terrain level nor sea level, but rather separate "engine" coordinates. However, there has to be a defined offset between the engine space and the terrain level or sea level, i.e. [0,0,0] in engine space could actually be above or below sea level, and it's what these commands would use to convert vectors.
I'm not sure I understand what you mean with the ASL stuff. ASL space is not object-specific, it's simply a vector relative the to flat sea level. You can have [0,0,100] which means 100m above sea at X=0 and Y=0.
The positions returned and used by getPosASL and setPosASL are, however, object-specific indeed, due to the orientation of the object altering the Z component, depending on the bounding center or LandContact vertices when available.
I guess we'll have to wait and see what "World" really means in relation to those commands.