- From: Keith Waters <kwaters@ftrd.us>
- Date: Fri, 3 Jun 2005 09:27:06 -0400
- To: www-di@w3.org
- Message-Id: <F25435F3-9327-4258-9084-37E889705582@ftrd.us>
Hi Jeremy, This message contains a response to comments on http://www.w3.org/TR/2004/WD-DPF-20041122/ s5. Identical names in different namespaces Figure 2 presents the possibility of the use of identical names in different namespaces. The intent appears to be that DPF should provide a framework in which different properties independently defined by different namespace owners can interoperate. However, the ECMAScript expressions are unable to distinguish namespaces and the semantics of an expression like "gps.gps" is unclear for figure 2. To clarify the text and figure have been modified as follows: Search results may contain properties with the same name and namespace values and so appear to be identical. In order to disambiguate between the two, it is neccessary to compare their parent nodes. For example, there could be two or more GPS systems present with the inter-relation show in Figure 2. [Figure 2. attached] Figure 2. An example GPS hierarchy. For example, if getDPFPropertyList were called on the node pictured above named C:GPS, with a namespaceURI parameter set to NULL, a propertyName parameter set to "GPS", and a deep parameter set to "true", the DPFPropertyList returned would contain two properties with a namespace of A and a name of GPS. These nodes could be disambiguated by comparing their parent attributes.
-Keith Waters
Attachments
- image/png attachment: dpf2.png
Received on Friday, 3 June 2005 13:27:44 UTC