[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (TOSCA-60) Primer - All MATERIAL Contributions
[ http://tools.oasis-open.org/issues/browse/TOSCA-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lipton updated TOSCA-60:
------------------------------
Proposal: (was: The W3C TAG http://www.w3.org//tag/doc/qnameids section 4.2 warns that "Because there is some possibility of variation in the way namespace bindings are established, even if a QName can be identified in content, it may be difficult or impossible to determine what {URI, local-name} it represents. The mapping may depend on the context in which it occurs. Therefore, at the very least, it is important for specifications to identify the mapping algorithm that they have chosen. Specifications that use QNames to represent {URI, local-name} pairs MUST describe the algorithm that is used to map between them." TOSCA QName values are found in attributes (@type, DerivedFrom/@typeRef) and those values then must uniquely select something. Both the specification and the primer should explain in TAG-required detail how this selection (or referential) process works.)
Environment: (was: QName reference mechanism (used in finding types for typed objects or for finding supertypes of types)
W3C TAG suggestions in http://www.w3.org/2001/tag/doc/qnameids
)
Resolution: (was: For example: When a CapabilityType named PluginContainerCapabililty has a Derived/From/@typeRef value of "ns1:ContainerCapability" the prefix ns1's current URI mapping value is used to find an element with that value in its @targetNamespace value,(namely "http://docs.oasis-open.org/tosca/ns/2011/12/ToscaCoreTypes";) and an @name value of "ContainerCapability"
Another example: The relationshipTemplate with the id "SugarCrmApp_ConnectsTo_SugarCrmDb" has a QName value "ns1:MySqlDbConnection" in its @type attribute. This value establishes a reference to <RelationshipType name="MySqlDbConnection" targetNamespace="http://docs.oasis-open.org/tosca/ns/2011/12/ToscaCoreTypes";> ... <RelationshipType>)
Comment from Dale Moberg (moved from another section):
QName reference mechanism (used in finding types for typed objects or for finding supertypes of types)
W3C TAG suggestions in http://www.w3.org/2001/tag/doc/qnameids
PROPOSAL: The W3C TAG http://www.w3.org//tag/doc/qnameids section 4.2 warns that "Because there is some possibility of variation in the way namespace bindings are established, even if a QName can be identified in content, it may be difficult or impossible to determine what {URI, local-name} it represents. The mapping may depend on the context in which it occurs. Therefore, at the very least, it is important for specifications to identify the mapping algorithm that they have chosen. Specifications that use QNames to represent {URI, local-name} pairs MUST describe the algorithm that is used to map between them." TOSCA QName values are found in attributes (@type, DerivedFrom/@typeRef) and those values then must uniquely select something. Both the specification and the primer should explain in TAG-required detail how this selection (or referential) process works.
RESOLUTION: For example: When a CapabilityType named PluginContainerCapabililty has a Derived/From/@typeRef value of "ns1:ContainerCapability" the prefix ns1's current URI mapping value is used to find an element with that value in its @targetNamespace value,(namely "http://docs.oasis-open.org/tosca/ns/2011/12/ToscaCoreTypes";) and an @name value of "ContainerCapability"
Another example: The relationshipTemplate with the id "SugarCrmApp_ConnectsTo_SugarCrmDb" has a QName value "ns1:MySqlDbConnection" in its @type attribute. This value establishes a reference to <RelationshipType name="MySqlDbConnection" targetNamespace="http://docs.oasis-open.org/tosca/ns/2011/12/ToscaCoreTypes";> ... <RelationshipType>
> Primer - All MATERIAL Contributions
> ------------------------------------
>
> Key: TOSCA-60
> URL: http://tools.oasis-open.org/issues/browse/TOSCA-60
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Task
> Components: Primer
> Reporter: Paul Lipton
> Assignee: Dale Moberg
>
> This issue is a bucket for ALL MATERIAL contributions such as explanatory paragraphs, examples, etc.
> IMPORTANT: ALL contributions will be aggregated by the Primer editors and considered for approval by the TC, although they may work with contributors to align style, format, etc. No contribution will be discarded without the approval of the contributor.
> * See this email for details on the Primer development process, etc.: https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201211/msg00003.html)
> See TOSCA-16 for ALL NON-MATERIAL suggestions such as spelling and grammar changes.
--
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]