[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [wsrp-wsia] [change request #191] Namespace prefixing
Document: Spec Section: 10.3 Page/Line: 63/12 Requested by: Chris Braun & Rich Thompson (merged 2) Old text: Aggregating multiple Portlets from different sources can potentially result in naming conflicts for various types of elements: named attributes, JavaScript functions and variables, etc. Such tokens SHOULD therefore be encoded to a Portlet-instance specific namespace [A301]. The Portlet MAY do this by prefixing the name of the resource with the namespacePrefix from the RuntimeContext structure. New text: Aggregating multiple Portlets from different sources can potentially result in naming conflicts for various types of elements: named attributes, JavaScript functions and variables, etc. Tokens needing to avoid naming conflicts when appearing multiple times on a page MUST therefore be encoded to a Portlet-instance specific namespace [A301]. The Portlet MAY do this by prefixing the name of the resource with the namespacePrefix from the RuntimeContext structure. We note that the JavaScript examples exclude the possibility of starting such prefixes with a numerical character. Reasoning: [CB] There should be some rules regarding what the consumer can produce for the resulting token syntax. The token should be a valid javascript identifier for example. There may be other rules that we need to apply here as well. For example, if a consumer uses a numeric namespace this would produce invalid javascript in cases where a method or function is being namespaced. [RT] The should relative to how encoding needs to happen isn't strong enough. Propose a MUST on what is required with a MAY on a reasonable technique.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC