[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tosca-comment] Feedback on TOSCA 1.3 spec
If this is an implementation detail than you are almost guaranteed to have interoperability issues between implementations. As it stands, right now it is valid for a template name to contain a line break or carriageÂreturn. Maybe your TOSCA implementation handles that but quite likely that template would not work properly in some other implementation. I can not think of a single vocabulary or programming language that allows any possible string to be treated as an identifier without some constraints. And your examples of where these identifiers could be used (e.g. "sql key columns, kubernetes deployment names") are actually an argument for restricting their syntax so they could easily work in all those contexts.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]