484:
worth including in an article, or as a means of categorizing. For instance, if lying on US 66 is a trivial fact about a place, then there should be no category for settlements on that route (that's a CFD issue, not AFD, of course). Unfortunately there seems to be no clear consensus on how notability applies to lists, although it is true that not all items in an list need to be notable in their own right (i.e. a list isn't like a navbox), so long as they are non-trivial or the list is meant to be exhaustive. It is, however, clear that a list of settlements that a road passes through should be complete, particularly since it is only a finite number of settlements (it's the "potentially infinite lists" which are the headache). The fact a particular road passes through a settlement might be a trivial fact about that settlement, but a non-trivial fact about that road. If you are correct that the main road article will include all of the information currently in this list, then a merge seems in order.
488:
reader to extract information, than having to pull it out of continuous prose. This is why we have, for instance, list-like "Timeline of X" and prose "History of X" articles - all the information in the timeline may lie in the prose article, but the timeline itself isn't redundant because it presents certain key aspects in a more comprehensible way. There is therefore nothing about a "Route outline for Road X" that inherently breaches
Knowledge (XXG)'s policies and guidelines, as it's not necessarily redundant to the main "Road X" article (depending on how the two are written). Of course, it may be consensus that such route outlines are not a good idea! But somebody obviously thought they were, or this article wouldn't exist, and they do have an arguable case. I'm just pointing out that this argument exists, and that you could try to make articles like this distinctive and non-redundant (analagous to the "timeline" articles), but I'll leave that to the "roadier" editors to think about.
432:
is arguably invalid - this is basically a spin-off subarticle. As with the fact that spin off articles don't usually have likely search terms, we also give them leniency in terms of standalone notability: the important thing is whether the page contains useful, organised information that would naturally be part of the main article, but would add excessive length so is better as a subarticle. This does seem exactly the sort of material that it would be natural to include in the main article, but may not wish to do so for length reasons.
423:- most of the delete rationales here are very poor. Merging this content into the main Route 66 article is a possibility, but it might be excessive detail in the route description, in which case this is a valid spin-off - I'll leave that for the raodfans to describe. But the following grounds to delete are complete bunkum: (1) "not a likely search term" - same is true for all sub-articles that are spun off on length grounds. (2) "redundant to category" - no, please read
515:
selective. I think it's appropriate geographic content--whether it should be incorporated into the main article is another matter, but I would suggest not, because it is a very long list.& would overbalance the rest of the article. The key thing this does that a category cannot is present them in geographical order, which is essential context information. (I assume this list does do that--I have not checked).
480:
already been done? As for the title post-merge, what you said about it being an unlikely search term is reasonable. However, leaving redirects for merged pages has the benefit that it doesn't produce dead links on other people's sites or on their bookmarks; I can't see what harm outweights this benefit.
514:
does not discuss this particular type of article. Personally, I find this much clearer than the usual route description--and, in any case, that does not seem to have yet been written in the necessary detail. Sometimes wikiprojects specify more articles than the rest of us want, sometimes they are too
483:
You do seem to mix up "notability" with "non-triviality". In a thesaurus the two are synonymous, but unfortunately they appear to have developed different meanings in
Wikispeak! "Notability" usually refers to whether something deserves an article in its own right. "Triviality" is to do with a fact is
479:
Thanks for a decent reply. I can appreciate that in your opinion all this material should be in the main article, in which case it ought to be merged. I can see a lot of delete !votes - is your opinion that this page should be kept until merger is complete, or do you feel the merger has effectively
446:
Let me reply. 1) No, this isn't a likely search term, which is why the title shouldn't be retained as a redirect if the list is merged. 2) You're right, the list can do things a category can't, but it's still a bit redundant because 3) most of the cities listed aren't notable for being on former US
431:
be used to give a little detail about each town - even something basic like it's population. Categories can't do that. "Redundancy" is an utterly invalid argument, there's nothing wrong with having both a category and a list, as they serve different organizational purposes. (3) "Lack of notability"
451:
deprecated lists of cities in roads articles for the US because a properly written route description will already list the cities through which a road passes. Add to that the inherently subjectivity of determining which are "major" enough to be listed at the exclusion of others, and the side boxes
487:
The only reservation I have about that, is whether the list actually has an advantage as a supplement to the article: a straight list, possibly annotated in some way (e.g. with population size of the settlements, their co-ords, and distances between them along the road) might make it easier for a
410:
Other than the ones mentioned in the famous song ("...St. Louie, Joplin
Missouri, Oklahoma City is mighty pretty, etc.") the communities themselves aren't famous for being on Route 66. This doesn't require a separate page, and the only reason that it takes up so much screen at the moment is the
452:
were killed. This list itself is a spunoff list that would be that "small" infobox on the side of the main article. All of these cities should be included in the by-state subarticless route descriptions, which should already be describing more detail than what this list contains.
533:
156:
509:
I do not think the guidelines of the
Wikiproject are necessarily accepted here--Sometimes wikiprojects specify more articles than the rest of us want, sometimes they are too selective. In any case the essay at
531:
A category would work fine to document towns along US 66. A list of these towns is way too long and is simply listcruft. Should we create lists of towns for other routes, such as US 50? For precedent, we have
150:
411:
dim-witted method of assigning a separate line for each blue link. The page of
Illinois towns could be incorporated into a section of the U.S. 66 article, if need be, in one paragraph.
90:
85:
94:
117:
77:
427:. It's not redundant if it can do something a category can't - and in this case it can, because it can put places in the order they lie on the road. Similarly, this list
317:
per Rschen and
Admrboltz; we can have a large category for this and also have these cities mentioned in the route description of US 66 as well as US 66 in articles. –
386:
511:
171:
138:
556:
526:
497:
474:
441:
415:
401:
376:
357:
325:
307:
290:
267:
242:
213:
59:
132:
17:
465:
263:
204:
128:
549:
350:
235:
81:
178:
366:
334:
73:
65:
573:
36:
144:
572:
Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a
35:
Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a
493:
437:
460:
260:
199:
544:
345:
303:
286:
230:
164:
373:
53:
397:
29:
The following discussion is an archived debate of the proposed deletion of the article below.
448:
489:
433:
319:
424:
455:
257:
194:
539:
412:
340:
299:
282:
225:
522:
370:
278:
188:
50:
393:
534:
Knowledge (XXG):Articles for deletion/List of Towns Along I-95 by County and State
111:
187:
As a stand-alone list, this isn't notable. The majority of entries should be in
517:
191:
or its state-level subarticles. The title is an unlikely search term.
566:
The above discussion is preserved as an archive of the debate.
222:- Do not need a canonical list of every town on US 66.
107:
103:
99:
163:
177:
512:Knowledge (XXG):WikiProject U.S. Roads/Notability
39:). No further edits should be made to this page.
576:). No further edits should be made to this page.
255:- Might be a useful category, but not a list. --
8:
387:list of Lists-related deletion discussions
381:
281:(or appropirate state-specific subpages).
385:: This debate has been included in the
367:Category:Communities on U.S. Route 66
335:Category:Communities on U.S. Route 66
18:Knowledge (XXG):Articles for deletion
7:
74:List of communities on U.S. Route 66
66:List of communities on U.S. Route 66
24:
1:
557:02:19, 18 December 2010 (UTC)
527:22:39, 17 December 2010 (UTC)
498:23:21, 15 December 2010 (UTC)
475:18:31, 14 December 2010 (UTC)
442:17:58, 14 December 2010 (UTC)
416:15:29, 12 December 2010 (UTC)
402:01:58, 12 December 2010 (UTC)
377:03:13, 11 December 2010 (UTC)
358:03:10, 11 December 2010 (UTC)
326:03:10, 11 December 2010 (UTC)
308:03:15, 11 December 2010 (UTC)
291:03:06, 11 December 2010 (UTC)
268:03:06, 11 December 2010 (UTC)
243:03:05, 11 December 2010 (UTC)
214:03:03, 11 December 2010 (UTC)
60:03:42, 19 December 2010 (UTC)
593:
298:redundant to category. --
569:Please do not modify it.
32:Please do not modify it.
536:, which was deleted.
315:Categorify and Merge
333:- We already have
44:The result was
404:
390:
584:
571:
555:
552:
547:
542:
473:
470:
463:
458:
391:
365:as redundant to
356:
353:
348:
343:
324:
322:
277:and redirect to
241:
238:
233:
228:
212:
209:
202:
197:
182:
181:
167:
115:
97:
56:
34:
592:
591:
587:
586:
585:
583:
582:
581:
580:
574:deletion review
567:
550:
545:
540:
537:
469:
466:
461:
456:
453:
351:
346:
341:
338:
320:
318:
236:
231:
226:
223:
208:
205:
200:
195:
192:
124:
88:
72:
69:
54:
37:deletion review
30:
22:
21:
20:
12:
11:
5:
590:
588:
579:
578:
562:
561:
560:
559:
504:
503:
502:
501:
500:
485:
481:
467:
418:
405:
379:
360:
328:
312:
311:
310:
270:
245:
206:
185:
184:
121:
68:
63:
42:
41:
25:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
589:
577:
575:
570:
564:
563:
558:
554:
553:
548:
543:
535:
530:
529:
528:
524:
520:
519:
513:
508:
505:
499:
495:
491:
486:
482:
478:
477:
476:
472:
471:
464:
459:
450:
445:
444:
443:
439:
435:
430:
426:
422:
419:
417:
414:
409:
406:
403:
399:
395:
388:
384:
380:
378:
375:
372:
368:
364:
361:
359:
355:
354:
349:
344:
336:
332:
329:
327:
323:
316:
313:
309:
305:
301:
297:
294:
293:
292:
288:
284:
280:
279:U.S. Route 66
276:
275:
271:
269:
266:
265:
262:
259:
254:
251:
250:
246:
244:
240:
239:
234:
229:
221:
218:
217:
216:
215:
211:
210:
203:
198:
190:
189:U.S. Route 66
180:
176:
173:
170:
166:
162:
158:
155:
152:
149:
146:
143:
140:
137:
134:
130:
127:
126:Find sources:
122:
119:
113:
109:
105:
101:
96:
92:
87:
83:
79:
75:
71:
70:
67:
64:
62:
61:
58:
57:
52:
47:
40:
38:
33:
27:
26:
19:
568:
565:
538:
516:
506:
454:
428:
420:
407:
382:
362:
339:
330:
314:
295:
273:
272:
256:
252:
248:
247:
224:
219:
193:
186:
174:
168:
160:
153:
147:
141:
135:
125:
49:
45:
43:
31:
28:
490:TheGrappler
434:TheGrappler
421:Strong keep
151:free images
249:Categorify
413:Mandsford
394:• Gene93k
300:Admrboltz
283:Admrboltz
371:Fredddie
118:View log
449:WP:USRD
331:Comment
157:WP refs
145:scholar
91:protect
86:history
55:Faraone
457:Imzadi
425:WP:CLT
408:Delete
363:Delete
296:Delete
253:Delete
220:Delete
196:Imzadi
129:Google
95:delete
46:delete
541:Dough
523:talk
429:could
342:Dough
274:Merge
227:Dough
172:JSTOR
133:books
112:views
104:watch
100:links
16:<
507:Keep
494:talk
462:1979
447:66.
438:talk
398:talk
383:Note
304:talk
287:talk
264:7754
261:chen
201:1979
165:FENS
139:news
108:logs
82:talk
78:edit
518:DGG
392:--
369:. –
179:TWL
116:– (
551:72
546:48
525:)
496:)
440:)
400:)
389:.
352:72
347:48
337:.
321:CG
306:)
289:)
258:Rs
237:72
232:48
159:)
110:|
106:|
102:|
98:|
93:|
89:|
84:|
80:|
48:.
521:(
492:(
468:→
436:(
396:(
374:™
302:(
285:(
207:→
183:)
175:·
169:·
161:·
154:·
148:·
142:·
136:·
131:(
123:(
120:)
114:)
76:(
51:L
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.