We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The modeling shall depend on what we actually need to tag in the regulation documents.
do we just need to tag subdivisions that express a physical quantity ? (where is the number, where is the unit)
is it just implicitly defining some category (those things which have property larger/smaller than )
and this category can be used as a second tag for a Requirement / Application / Selection / Exception subdivision ?
The text was updated successfully, but these errors were encountered:
hi @maximelefrancois86 Is this still relevant? Is it a "bug" or you're happy to leave it as is?
Sorry, something went wrong.
No branches or pull requests
The modeling shall depend on what we actually need to tag in the regulation documents.
do we just need to tag subdivisions that express a physical quantity ? (where is the number, where is the unit)
is it just implicitly defining some category (those things which have property larger/smaller than )
and this category can be used as a second tag for a Requirement / Application / Selection / Exception subdivision ?
The text was updated successfully, but these errors were encountered: