OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Updated: (TOSCA-21) TOSCA-20 Issue 6: "id" vs "name"

     [ http://tools.oasis-open.org/issues/browse/TOSCA-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Lipton  updated TOSCA-21:

    Component/s: Spec

> TOSCA-20 Issue 6: "id" vs "name"
> --------------------------------
>                 Key: TOSCA-21
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-21
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Sub-task
>          Components: Spec
>    Affects Versions: CSD03
>            Reporter: Tobias Kunze 
>            Assignee: Tobias Kunze 
>             Fix For: CSD03
> This issue actually has three possible solutions:
>    1. Keep "id" and drop "name" (or make it optional); same for XML and YAML
>    2. Keep "name" and drop "id" (or make it optional); same for XML and YAML
>    3. Adopt solution (1) for XML and (2) for YAML; define translation between formats
> Aspects to consider are, among potential others:
>    A. Uniqueness of identifiers
>    B. Scope of uniqueness: local to the template or global
>    C. Enforcement or validation of uniqueness
>    D. Familiarity of construct
>    E. Culture ("geeky" vs "user-friendly")
>    F. Likelihood of acceptance
>    G. Simplicity
> During our call on 2012-06-07, is seemed that
> i. There was consensus that (A) is required but (B) only at the local level; import of external identifiers can occur either namespaced or optimistically
> ii. There was consensus that (C) uniqueness must be enforced. However, there was disagreement on where it should be enforced. Derek suggested that implementations should make use of XML's enforcement of the uniqueness of the "id" attribute. I suggested that this could be trivially carried out by the implementation itself, quite possibly with better error messages. Some of the argument may have rested on (D) Familiarity of users with the XML "id" attribute.
> iii. There was a difference in (E) among the TC

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]