Github user ahgittin commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/682#issuecomment-109988207
@alasdairhodge that's the tosca mindset, it's great for systems but not for
users. a single format which many people don't know about (really a `T` in the
middle??) is going to make it hard for people.
nearly all the feedback from users has been to the contrary: blueprints
are best when intuitive and forgiving, so long as there isn't a risk associated
or leaky complexity.
it *is* good to recommend one way to do things, and we have been guilty of
showing too many. so i'm happy to recommend ISO 8601 but i think almost any
human would rather see a space in the middle instead of the ugly `T`. (of
course the weirder your format the riskier it is, such as the weird examples in
the test case.)
we definitely can't rely on locale delimiters as the ultimate arbiter as
sharing across servers is important.
btw ISO 8601 supports bizarre things like `2015-156` for the 156th day of
the year. and it mandates a `P` prefix for durations `P3H`. these would not
be popular.
OTOH being able to express a stabilization delay as `2m 30s` is extremely
popular. similarly `4g` for RAM instead of `4096` (where you used to have to
look up the fact that it is `mB`).
let's not make users' lives difficult!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
