Comments (3)
My interpretation is that such a range is acceptable. Implementations should also be able to verify that $equal(60 s, 1 h)
is True
from tosca-community-contributions.
Then perhaps we could change the example in 5.2.2.4.2 to show a mix of type compatible unit values.
from tosca-community-contributions.
It is clear to me that this is the case, that the whole point of scalars is that the unit doesn't matter internally. You can see in Puccini's implementation that every type is internally converted to a "canonical number" (and unit), which is used for comparisons, e.g. the canonical unit for time is seconds. Maybe we need to specify the canonical unit explicitly in TOSCA because it will have an effect on precision during conversions, which could have implications for very large or very small values with different units.
BTW, the original unit and is still preserved in Puccini (it's in the Clout), but in the TOSCA spec it shouldn't matter because we don't enforce any data storage model.
from tosca-community-contributions.
Related Issues (20)
- Add support for declarative policies HOT 1
- Remove domain specific scalars HOT 2
- Define scalar-units as float or integer HOT 1
- Generalise scalar-units defintions HOT 10
- Dynamic group membership HOT 3
- State machine for interfaces HOT 10
- Repository definitions need a way to specify credentials HOT 1
- remove `properties` keyword underneath the `allocation` keyword in requirement assignments
- Is the node field optional or mandatory in a requirement assignment? HOT 1
- $foreach and $exists functions HOT 2
- Change TOSCA Path relationship traversal semantics HOT 1
- Contribution guidelines are inconsistent HOT 4
- Placing glossary at the document start could make a new reader feel unwelcome HOT 2
- Representation Model is poorly defined HOT 1
- Definition of terms section is in no particular order
- Some comments have not been correctly handled when converting to markdown HOT 3
- Are TOSCA reserved keywords are case-sensitive?
- Substitution mapping and selectable nodes
- Spec is inconsistent about version values treated as floating numbers HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tosca-community-contributions.