Thanks, DJ. This was on the list of things to do but we indeed forgot to create a JIRA for it...
On Thu, Jun 8, 2017 at 8:24 AM, Ran Ziv <[email protected]> wrote: > Hi DJ, > > Sounds good. Feel free to create a new JIRA yourself! And thanks for > posting on the dev list before creating this issue. > One small note, I'd personally think of this as a "story" rather than a > "bug" - We don't yet claim to be 100% TOSCA complaint, and we're familiar > with several other missing spec sections implementations at the moment. > > Let me know if you need any help. > Tal might have more to add on this (Type qualified name) as well. > > Thank you > Ran > > > On Wed, Jun 7, 2017 at 3:35 PM, D Jayachandran < > [email protected]> > wrote: > > > Hi, > > > > TOSCA Simple Yaml 1.0 profile specification supports usage of the > > following Namespace Alias > > > > 1. Shorthand Name > > 2. Type Qualified Name > > 3. Type URI > > > > ARIA currently supports only "Shorthand Name" and "Type URI". The support > > for "Type Qualified Name" is missing which is required to adhere with the > > TOSCA Simple yaml 1.0 specifications. Could this be considered as bug > and a > > JIRA issue opened for this ? > > We would like to start our contribution with this. > > > > > > Regards, > > DJ > > > > > -- Tal Liron Senior Engineer [email protected] | +1 (773) 828-9339 Cloudify | http://getcloudify.org <http://getcloudify.org?utm_source=signaturesatori&utm_medium=email&utm_campaign=general_signature> <https://twitter.com/CloudifySource> <https://www.linkedin.com/groups/8467478> <https://github.com/cloudify-cosmo> <https://github.com/cloudify-cosmo> [image: Azure Webinar] <http://getcloudify.org/webinars/Azure-plugin-for-cloudify-webinar.html?utm_source=signaturesatori&utm_medium=email&utm_campaign=general_signature>
