[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 答复: RE: [tosca] One question about Namespace Alias and URI.
Hi Yuanxing
In tosca-simple-profile-yaml, the namespace Alias is needed because it relates to
tosca_definitions _version.
In tosca-nfv-profile, as we discussed and agreed, the
tosca_definitions _version
value will always set to the namespace Alias of tosca-simple-profile-yaml to represent a specific TOSCA grammar version used in the template, so it is not needed
to create a new namespace Alias for tosca-nfv-profile. In general, the conclusion is that in tosca-nfv-profile, it will only specify a namespace URI and a namespace prefix.
Regards shitao 发件人: feng.yuanxing@zte.com.cn [mailto:feng.yuanxing@zte.com.cn]
Hi, It confused me and I wonder why "alias" was removed. If I understand correctly, the alias is necessary. If we remove the alias from the spec, what shall we use to define the tosca_definition_version below? Would that be the whole URI? That's too long. tosca_definitions _version: tosca_simple_profile_for_nfv_1_0 description: service template of a VDU # Human readable description of the Vdu. topology_template: inputs: Thanks, Feng yuanxing
原始邮件 发件人: <lauwers@ubicity.com>; 收件人:冯远兴10034308;
<lishitao@huawei.com>; 抄送人: <tosca@lists.oasis-open.org>; 日
期
:2017年11月21日
13:24 主
题
:RE: [tosca] One question about Namespace Alias and URI. Hi Shitao, Based on our latest namespace discussions, I believe the “alias” is no longer needed. You would only ever use the fully qualified URI (from the Target Namespace)
or the prefix. Chris From:
tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
On Behalf Of feng.yuanxing@zte.com.cn Hi all, I noticed that namespace URI and alias in TOSCA NFV Profile Specification is defined. And we use the alias in the sample template as below. On yesterday's nfv call, we decided
to remove the alias. Is that alias the same one referred in the following table?
tosca_definitions _version: tosca_simple_profile_for_nfv_1_0 description: service template of a VDU # Human readable description of the Vdu. topology_template: inputs: |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]