Stuart,
I by no means wanted to scold you for putting up what you did, if it came across like that I'm sorry. I'm just used to the F/OSS culture and if I see a bug, I report it :) Furthermore I think that having some service up and running is a good tool to help one think...
Quoting "Stuart Chalk" <
schalk@unf.edu>:
(...)
In my opinion the discussion here needs to focus on the following
1) What are we trying to accompish with UnitsML by inclusion of the WSDL referencing?
Heh, that one is going to be deep.
2) What parameters are necessary to fulfil the goal in (1)?
The initial discussion focused on wanting to be able to indicate a service that was available to convert a unit.
Thats it. There was no discussion of using the link in a automated fashion to provide a conversion of the unit
on the fly. So, for UnitsML 1.0 what do we feel should be the scope of the WSDLConversionFrom element?
I was down with a serious cold, I hope to post a multi-level suggestion of that on the unitsml ml soon. Personally I think it should be as-automated-as-possible and as-easy-usable-by-machines-as-possible, but I'll post more on that later.
By the way, did you realize that you only replied to myself, and not to the unitsml list? Not sure if that was intended because the above question seems to address the TC as a whole.
Regards,
-Martin