explain ontology restrictions

[Lukas113]

I've looked into odahub-ontology to define parameters. There are also additional options to set something like lower_limit, upper_limit or allowed_value, which is great. With tools like that I was thinking, are these restrictions automatically set to certain ontology-items like PointOfInterestRA? In the dev-guide-doc I've found the following statement:

"""
it is possible to customize the parameter by adding annotation the input parameter with an MMODA ontology item as a comment (after the hash sign, #http://odahub.io/ontology#AngleDegrees in the reference example of the Source_region_radius parameter. This may be useful for checking the validity of the user inputs. For example, the sky angle in degrees (defined by the #http://odahub.io/ontology#AngleDegrees) should be a float number and can take values between 0 and 360.
"""

With only this, I'm not sure about the following things:

• Is a limit & allowed-values run-time validation-check performed by oda? If yes, what are the restrictions set for each item (don't see anything in doc, so I just can make assumptions). If no, I think it's worth to say that explicitly.
• Is a dtype run-time check performed by oda? What about coercion (e.g. int -> float). Are None-types allowed? What happens if a field is empty (NoneType, empty String, what about numeric-values)?