Is your task related to a problem? Please describe.
Currently, due to the SAMM rules an Aspect name MustBeInCamelCaseFormat.
This makes perfect sense, since the Aspect name will be used for the generation of corresponding Java or other programming language ClassName.
However, for better readability of corresponding aspect model filenames, would it be possible if we could have the option to use dashes: '-' or underscores: '_' to separate such long and not that human friendly fielnames, so for example:
an aspect model: MustBeInCamelCaseFormat would have its filename like: Must_Be_In_Camel_Case_Format.ttl or Must-Be-In-Camel-Case-Format.ttl.
In addition to this, maybe we could even keep all separate words in lower case like: must-be-in-camel-case.ttl or must_be_in_camel_case.ttl or any combination of these, as long as when it is processed, i.e. remove dashes and underscores, and set to upper case first character for each word, to result in: MustBeInCamelCaseFormat.
Further more, but probably not to push it that far, it might even be more handy if lets say all of the above is provided, i.e. the filename has some dashes and underscores and converts propely to its define Aspect model name, but in addition it has some extra note like: Must-Be-In-Camel-Case-Format-under-construction-not-to-be-released.ttl.
When the above filename is processed it will result in: MustBeInCamelCaseFormatUnderConstructionNotToBeReleased then as long as its Aspect model name: MustBeInCamelCaseFormat is the prefix of its "processed" filename: MustBeInCamelCaseFormatUnderConstructionNotToBeReleased the model can be considered valid since its Aspect model name is the prefix of its related filename.
Describe the solution you'd like
Suggested behavior is provided in above examples.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your task related to a problem? Please describe.
Currently, due to the SAMM rules an Aspect name MustBeInCamelCaseFormat.
This makes perfect sense, since the Aspect name will be used for the generation of corresponding Java or other programming language ClassName.
However, for better readability of corresponding aspect model filenames, would it be possible if we could have the option to use dashes: '-' or underscores: '_' to separate such long and not that human friendly fielnames, so for example:
an aspect model: MustBeInCamelCaseFormat would have its filename like: Must_Be_In_Camel_Case_Format.ttl or Must-Be-In-Camel-Case-Format.ttl.
In addition to this, maybe we could even keep all separate words in lower case like: must-be-in-camel-case.ttl or must_be_in_camel_case.ttl or any combination of these, as long as when it is processed, i.e. remove dashes and underscores, and set to upper case first character for each word, to result in: MustBeInCamelCaseFormat.
Further more, but probably not to push it that far, it might even be more handy if lets say all of the above is provided, i.e. the filename has some dashes and underscores and converts propely to its define Aspect model name, but in addition it has some extra note like: Must-Be-In-Camel-Case-Format-under-construction-not-to-be-released.ttl.
When the above filename is processed it will result in: MustBeInCamelCaseFormatUnderConstructionNotToBeReleased then as long as its Aspect model name: MustBeInCamelCaseFormat is the prefix of its "processed" filename: MustBeInCamelCaseFormatUnderConstructionNotToBeReleased the model can be considered valid since its Aspect model name is the prefix of its related filename.
Describe the solution you'd like
Suggested behavior is provided in above examples.
Describe alternatives you've considered
N/A
Additional context
N/A