156:
55:, element names can be originated and changed to reflect the type of information contained in the document. This level of flexibility may cause problems if separate documents encode different kinds of information, but use the same identifiers for the element names.
132:
In the preceding example, there is enough information in the structure of the document itself (which is specified by the "root" element) to provide a means of unambiguously resolving element names.
58:
For example, the following sample document defines the basic semantics for a "person" document and a "book" document. Both of these use a "title" element, but the meaning is not the same:
129:
title element is being requested. Failure to do so would give rise to a naming collision on the title element (as well as any other elements that shared this unintended similarity).
218:
may also be used to refer to a system in which a single name or identifier is open to multiple interpretations by different layers or processing. The notion of a
125:
For an application to allow a user to correctly query for and retrieve the "title" element, it must provide a way to unambiguously specify
226:
practice to avert undesired clashes. Note that its use in the networking field is superficially similar, but quite different in reality.
40:
142://root/person/title ;; the formal title for a person //root/book/title ;; the title of a book
199:
181:
270:
166:
17:
177:
223:
173:
8:
250:
36:
214:
245:
235:
264:
43:, and such unambiguous resolution is a requirement of the underlying system.
28:
240:
219:
32:
184:. Statements consisting only of original research should be removed.
136:
52:
262:
46:
200:Learn how and when to remove this message
263:
149:
27:is a circumstance where two or more
145:
13:
14:
282:
154:
1:
256:
222:has been widely adopted as a
105:HarryPotterAndTheCursedChild
7:
229:
180:the claims made and adding
10:
287:
47:Example: XML element names
15:
60:
39:cannot be unambiguously
271:Programming constructs
224:software programming
16:For other uses, see
251:Delimiter collision
135:For example, using
165:possibly contains
210:
209:
202:
167:original research
278:
215:collision domain
205:
198:
194:
191:
185:
182:inline citations
158:
157:
150:
146:Collision domain
121:
118:
115:
111:
108:
104:
101:
98:
95:
91:
88:
84:
81:
77:
74:
70:
67:
64:
25:naming collision
286:
285:
281:
280:
279:
277:
276:
275:
261:
260:
259:
232:
206:
195:
189:
186:
171:
159:
155:
148:
143:
123:
122:
119:
116:
113:
109:
106:
102:
99:
97:</person>
96:
93:
89:
86:
82:
79:
75:
72:
68:
65:
62:
49:
21:
12:
11:
5:
284:
274:
273:
258:
255:
254:
253:
248:
246:XML Namespaces
243:
238:
236:Name collision
231:
228:
208:
207:
190:September 2007
162:
160:
153:
147:
144:
141:
107:</title>
87:</title>
80:</lname>
73:</fname>
66:<person>
61:
48:
45:
9:
6:
4:
3:
2:
283:
272:
269:
268:
266:
252:
249:
247:
244:
242:
239:
237:
234:
233:
227:
225:
221:
217:
216:
204:
201:
193:
183:
179:
175:
169:
168:
163:This article
161:
152:
151:
140:
138:
133:
130:
128:
120:</root>
117:</book>
114:</isbn>
103:<title>
83:<title>
76:<lname>
69:<fname>
59:
56:
54:
44:
42:
38:
34:
30:
26:
19:
18:Name conflict
213:
211:
196:
187:
164:
134:
131:
126:
124:
110:<isbn>
100:<book>
94:</age>
63:<root>
57:
50:
24:
22:
112:ABCD1234567
90:<age>
35:or a given
31:in a given
29:identifiers
257:References
174:improve it
241:Namespace
220:namespace
212:The term
178:verifying
33:namespace
265:Category
230:See also
41:resolved
172:Please
78:Davolio
137:XPath
127:which
71:Nancy
37:scope
176:by
85:Dr.
53:XML
51:In
267::
139::
92:29
23:A
203:)
197:(
192:)
188:(
170:.
20:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.