Misplaced Pages

Revision as of 21:32, 24 August 2006

Part 1

Here, we are voting on principle. That is the generic pattern for all the states.

Here is how it works: Arguments go under the Principle header. Discussion/rebuttals go under the Discussion header.

Voting takes place in the section below. Arguments and discussion only.

Discussion starts below:

Principle 1: X

This format is already used by a number of WikiProjects, including (but not limited to) New York, Pennsylvania, Vermont and Maryland. The reason that "New York State" is used for the state name in NY is to disambiguate between New York State and New York City. --TMF 17:03, 10 August 2006 (UTC)

That's not true; we use "New York State Route X" because NYSDOT uses it. --SPUI (T - C) 17:46, 10 August 2006 (UTC)

The fact that NYSDOT uses the term is true as well; however, my explanation was necessary to appease others who would likely attempt to move articles to "New York Route X" if this principle is selected. --TMF 17:48, 10 August 2006 (UTC)

That's also used by NYSDOT, but not as much. They use "NY Route X" and "NYS Route X" about equally. There's no reason we can't decide to use "New York Route X". --SPUI (T - C) 17:51, 10 August 2006 (UTC)

The main issue I would have with using "New York Route X" would be the hassle of moving 500 or so pages based on a single word in the title. --TMF 17:54, 10 August 2006 (UTC)

I agree with TMF on this point. New York State calls itself "New York State" on any official documents, names, etc. (driver's licenses, um, excuse me, "Driver Licenses" for example) to disambiguate itself from "New York City." There are, as far as I know, no New York City Routes, but that's not the point. I believe, also, that the NYSDOT official names are actually "New York State Touring Route ###(L)" and "New York State Reference Route 9R#L," but if someone's willing to point me to a reference showing otherwise, I'll stand corrected. NYS calls itself, officially, "NYS," and so I'm pretty sure that a Misplaced Pages User referring to Route 347 would look up "New York State Route 347." --Tckma 19:25, 10 August 2006 (UTC)

Hassles should not come in the way of a popular concensus. --TinMan 19:58, 10 August 2006 (UTC)

In any event, this isn't the place to discuss this; the conventions by state won't come until part 2. --TMF 20:59, 10 August 2006 (UTC)

(I've switched the parentheses with brackets in Principle 1 to prevent confusion with Principle 2.)' This format is the most likely version a visitor to Misplaced Pages would type in to find the correct article. It distinguishes from all other routes by placing the state name first. This format should also satisfy fans of the pipe trick, since ] could be redirected to this format: State Name Road Term x. Therefore, an editor could type ] and it would redirect to the correct article. --TinMan 19:58, 10 August 2006 (UTC)

No, it wouldn't. To wit, Route 15 ( that's ] ) certainly does NOT redirect to Illinois Route 15. --Tckma 20:33, 10 August 2006 (UTC)

That's because in Illinois the routes are "Illinois Route X". That redirect isn't a bad idea though - I'm going to make it. --SPUI (T - C) 05:49, 11 August 2006 (UTC)

An editor could, but most won't know, and we'll end up with articles that use the state name when they shouldn't. --SPUI (T - C) 05:49, 11 August 2006 (UTC)

What's so bad about them not using the pipe trick if all roads lead to the same place? --TinMan 19:56, 11 August 2006 (UTC)

One potential problem is that new editors tend to use the article title when making links. Also, many editors tend to fix redirects that aren't broken, preferring the direct link. If the article title is incorrect, that propagates the use of the incorrect name. --Polaron | Talk 20:01, 11 August 2006 (UTC)

From an inter-state perspective, this is the best way to name highways, as someone said in a past conversation that a resident from one state usually refers to a route from another by their state name first. It also sounds better when spoken out loud. --LBMixPro 03:48, 18 August 2006 (UTC)

Discussion

As far as I know, this convention is what most people, including me, have wanted. ςפקιДИτς ☺ ☻ 17:29, 10 August 2006 (UTC)

That's also not necessarily true. --SPUI (T - C) 17:46, 10 August 2006 (UTC)

I agree. --Rschen7754 (talk - contribs) 00:09, 14 August 2006 (UTC)

As do I. JohnnyBGood t c VIVA! 22:45, 15 August 2006 (UTC)

Ditto on that. Seicer (talk) (contribs) 04:14, 24 August 2006 (UTC)

While reasonable people may disagree, this is likely what your average Misplaced Pages user would type in to search for an article on a specific state highway. S/he is likely to realize that there can potentially be 52 different Route X's in the U.S. alone, and thus would probably type the state name first, unless, as has been said on the discussion page, there was some sort of crazy listcruft desires. Any regional language differences ("Route," "Highway," etc.) can be taken care of with redirects to the commonly used local name of the road. --Tckma 19:07, 10 August 2006 (UTC)

This is the method I agree with. As I noted in the suggestion for the second principle, being from Michigan I know the highways are M-1, M-50, etc, but anyone from the other 49 states probably don't know that and would be more likely to search for state highway XX Stratosphere (talk - Contrib) 04:05, 11 August 2006 (UTC)

Ditto Stratosphere. M is an obvious abbreviation for Michigan, but it could also be Minnesota if you were'nt familiar with the style. Abbreviations should be spelled out. By the way, its possible the main reason they are called "M-x" is because there is an "M" on most Michigan route shields. North Carolina used to have "NC" on their shields. --TinMan 19:58, 12 August 2006 (UTC)

See my note below about Kansas and Michigan. —Scott5114↗ 06:16, 13 August 2006 (UTC)

Will this discussion cover State Highway v state highway, or state route, when it comes to the category names? Vegaswikian 07:48, 17 August 2006 (UTC)

Now you're getting into generic terms, which is a whole other animal with some people supporting capitalizing them and others not. I think we're better off saving that debate for another time.-Jeff 01:30, 20 August 2006 (UTC)

I voted for this, since I've been pushing for a commonly used disambiguation technique for highways, I noticed that that is commonly done by putting the state name first. Again, we don't disambiguate towns using Town (State), but rater Town, State. If people usually disambiguate state highways by putting the state name first then this seems to be the best option.-Jeff 03:48, 19 August 2006 (UTC)

I couldn't have said it better myself. If I, as a New Yorker, was a first-time Misplaced Pages visitor and I wanted to look up, say, Michigan Highway 40 (just as an example), I would literally type in "Michigan Highway 40". I expect that this is true in most cases, as to me, it simply makes sense to refer to an out-of-state route by placing the state name first, then the road type and finally the number. After all, I wouldn't refer to California State Route 20 as "State Route 20" while I'm standing in downtown Rochester. I would explicitly say "California State Route 20". --TMF 03:55, 19 August 2006 (UTC)

What people might search for should not be the determining factor in titling an article. The actual name of the thing should determine the title. Searching should definitely be taken care of by redirects in any case. Also the town, state naming convention used mainly by US cities is improper because it gives the impression that the state name is part of the town/city name. --Polaron | Talk 04:03, 19 August 2006 (UTC)

If I've said it once, I've said it a thousand times. Misplaced Pages:Use Common Names says:

When choosing a name for a page ask yourself: What word would the average user of the Misplaced Pages put into the search engine?

--Tckma 19:34, 21 August 2006 (UTC)

The only debate now is: What is the actual name of the thing? Some say this, some say that, and both sides have compelling evidence supporting their position. And WP:NAME also says this:

Generally, article naming should give priority to what the majority of English speakers would most easily recognize, with a reasonable minimum of ambiguity, while at the same time making linking to those articles easy and second nature.

The only problem is the ambiguity and the semantics of the wording of both the policy and the "actual thing," and the unseen difficulty of fulfilling this requirement. --physicq210 04:18, 19 August 2006 (UTC)

If it were Misplaced Pages's policy to only use official names, I would agree with Polaron's comment above, but as we all know, this is not the case. Wilmington is a common name, but ambiguous, Wilmington, Delaware is also a common name, as that is how people usually disambiguate the city in Delaware known as Wilmington. In Misplaced Pages, we can disambiguate using parens, but if people are more used to seeing something disambiguated another way we should use that way, since we are allowed to use the more complete names option.-Jeff 04:23, 19 August 2006 (UTC)

Non-standard disambiguation should only be used if the resulting name+disambiguation term combination is actually in significant use. There are many states that do not use the state name in what they call their roads and articles for roads in those states should not be forced to use an incorrect name. If the state name in front style is in significant use in a particular state, only then should the state name in front method of disambiguation be considered. --Polaron | Talk 04:43, 19 August 2006 (UTC)

I agree on Tckma's comment. People are going to say and refer to a highway as either "Kentucky State Highway 33" or "Kentucky State Route 33" (the official term is Kentucky State Highway FYI). But then you look at Ohio, and how one user wanted ti jump to his own conclusion. So instead of something reasonable to Misplaced Pages's naming convention, you have State Route 55 (Ohio) instead of something more plausable, such as Ohio State Route 55 or Ohio State Highway 55. No one is going to refer to it as "State Route 55 Ohio" in real life... Seicer (talk) (contribs) 04:18, 24 August 2006 (UTC)

Principle 2: Commonly-Used-Name X (State Name)

For each state, choose a common or commonly-used official name. For instance:

• Florida: State Road X
• Louisiana: Louisiana Highway X
• Massachusetts: Route X
• Michigan: M-X

Then, if necessary, apply standard disambiguation conventions by adding a qualifier in parentheses:

• State Road X (Florida)
• Louisiana Highway X
  • Other states that commonly use the state name in front are: IL, MD, MS, MT, NE, NH, NY, NC, ND, PA, VT. These will not need disambiguation info under this Principle.
• Route X (Massachusetts)
• M-X (Michigan highway)

--SPUI (T - C) 17:46, 10 August 2006 (UTC)

Discussion

This is standard practice on Misplaced Pages, in part because it makes it easier to write articles. If you don't understand this, please read Misplaced Pages:pipe trick. One can type ] rather than ]. Note that redirects should always be made using a completion list. The routes should also be included on disambiguation pages, which also have a completion list for coordinating redirects. This ensures that a reader is likely to find the article. --SPUI (T - C) 17:46, 10 August 2006 (UTC)

SPUI, until you showed the link to pipe trick (and I used the trick here also!) I did not understand the purpose behind what you were doing. Perhaps this is certainly why people do not understand and we end up edit-warring - could it be because they don't know how to use Misplaced Pages? --master_son 22:08, 10 August 2006 (UTC)

Actually we do understand how to use the Pipe trick, thank you very much. But we should not redo the whole system just so we can use the pipe trick. --Rschen7754 (talk - contribs) 23:06, 10 August 2006 (UTC)

ok. Then we shouldn't with already existing ones. but new ones? Wisconsin was a possible example. very few articles written (about 10-15?) so it probably made some sense to convert the existing there, but where do we draw the line? --master_son 23:10, 10 August 2006 (UTC)

Also, the typical user will most likely type in Wisconsin Highway x rather than type in Highway x, realizing that there is more than one highway by that name. Besids, who, being a newcomer to Misplaced Pages, would realize taht the article was at the odd "Highway x (Wisconsin)? --Rschen7754 (talk - contribs) 23:36, 10 August 2006 (UTC)

Who would realize the article is at John Smith (English statesman)? Or Atlas (mythology)? We should strive to be correct. --SPUI (T - C) 05:53, 11 August 2006 (UTC)

Ditto. We should be making these articles easy to locate for the average Misplaced Pages user, not those who are "roadgeeks" or who need to be very strict in terms of naming conventions. Let's make this easy for them people, and keep it with a name that is reasonable and something that phonetically sounds good. Seicer (talk) (contribs) 04:20, 24 August 2006 (UTC)

As far as I know, the piipe trick was added AFTER Misplaced Pages started using parenthetical disambiguation. --SPUI (T - C) 05:53, 11 August 2006 (UTC)

While I respect the idea that the names should come from the official source (i.e. the state's particluar Dept of Transportation) I feel that in many situations, the average wikipedia user would have no idea of the local official name. For example, being from Michigan I am aware that the state highways are referred to as M-1, or M-50. But, if you were to ask someone from the other 49 states (maybe wisconsin, indiana, ohio excluded) they would have no clue that was the fact, unless they were a roadgeek. Stratosphere (talk - Contrib) 03:57, 11 August 2006 (UTC)

While I think we should definitely select a commonly used name, I don't think we should use this method of disambiguation. Yes, naming articles in this manner does make it easier on editors for typing because of the pipe trick mentioned above. However, we need to make Misplaced Pages search user-friendly, which may not necessarily be editor-friendly. As I've said before (on this project's talk page), I've been using this principle only because it appeared to be a standard precedent on the states I've been working. (As a side note, I believe that fact demonstrates that I'm willing to abide by whatever standards come out of this poll.) --Tckma 19:11, 10 August 2006 (UTC)

Why not? what's not user-friendly about that method? I think its both editor-friendly and user friendly in this sense. if one guesses based on experience, this will help them get to the correct location. I would think WIS 15, so I type it - but if we did not have a disambiguation or redirect, I'd get the edit page. with what we have now (there's a completion list on WP:WIH as well.) if I typed in or clicked on a WIS 15 link, it would take me to Highway 15 (Wisconsin).--master_son 22:14, 10 August 2006 (UTC)

It's only user-friendly if you throw in a bunch of redirects. If I'm looking for state highway, well, I'm fairly intelligent and I realize many states can have the same number highway. So I'll type "New Hampshire Route 101" rather than "Route 101" or "Route 101 (New Hampshire)." My point is this: In common speech the state's name comes first. Locally, the road is referred to as just "Route one-oh-one," or even just "one-oh-one." Sure, we need disambiguation -- If you're giving someone directions to Hampton Beach, you probably aren't going to talk about U.S. Highway 101 -- unless the person is really lost! One could conceivably imagine giving directions involving both Route 101 (New Hampshire) and Route 101 (Massachusetts), but they aren't the same road (neither crosses the state line). So in that case you would say "New Hampshire Route 101" and "Massachusetts Route 101" -- the state name always comes first. Ask yourself: What would Joe Average Wikipedian type in to get to an article? --Tckma 17:20, 14 August 2006 (UTC)

By putting something like "Route 4" as the first words of an article will just open a can of worms. What's next? "Highway 52 (United States)"? "Route 95 (Interstate)"? I've never seen a road sign with parentheses on it... and I believe that road signs should be the #1 thing we consider since that's what people read when they travel, that's where common names usually come from, and that's how resident's addresses usually read. I might live on Virginia Highway 8, but not Highway 8 (Virginia). Who would ever type "Highway 8 (Virginia)" in a search unless they are familiar with Misplaced Pages? I understand that no matter what a person types in a search, we can redirect to it. Yet, I feel the articles should have titles that a user can relate to. All the editor tricks and strange formats editors want to use can be redirects to a format that reads like a road sign or an address, like I suggested in Principle 1. EDITOR < USER. --TinMan 19:54, 11 August 2006 (UTC)

The parenthetical term is a disambiguation. It is not part of the article name. As long as expected search queries are redirected to the correct article, then it shouldn't be a problems. Some people just seem to dislike this disambiguation method (for whatever reason) even though it is used by many encyclopedias (print and online). --Polaron | Talk 20:17, 11 August 2006 (UTC)

One more thing I think I should add: This format assumes that the routes are known (using the term "highway" as an example) as "Highway x" in their respective states, wherein the each state's articles would need to be diambiguated to differentiate between the multiple "Highway x"'s in the county. However, in my state, and I dare say in most states, the road is never known as "Highway x", except in informal speech, but instead (using North Carolina as an example), "N.C. Highway x", "North Carolina Highway x", "NC x", or some variant of that. The state name or state abbreviation is never left out in any formal or semi-formal format. Michigan I assume is the same way with its "M-x". The "M" is still there, therefore a parentheses disambiguation shouldn't be used here... the abbreviation may have to be spelled out. Now, in places like Massachusetts, the routes may just be commonly known as "Route x" with no reference to the state. In those cases, I believe this Principle 2 is best suited. If that is the case, we're going to have a big uniformity problem. I don't know for sure if that is true though. I've noticed SPUI argue that "Route x" is the true name of the road someplace, but I can't remember where. --TinMan 05:43, 12 August 2006 (UTC)

Kansas and Michigan have special dab problems -- in Kansas at least, both the common and official name is "K-X" (as in K-32). However there's a lot of other things that are K-X (I'm sure you can imagine the problems with K-9 meaning either or a canine). Same for Michigan - there are even problems with other highways named M-X, as the motorway system in Great Britain also uses that convention. So these two states need special attention. Principal 2 definitely works better for these highways than Principal 1, as Principal 1 would require the names to be at "Kansas State Highway 32" (which is neither correct nor commonly used, at least from my experience) or "Kansas K-32" or something else clumsy like that.—Scott5114↗ 07:05, 12 August 2006 (UTC)

If the official state name was "Boring Route x" would you use that for the article name? --Rschen7754 (talk - contribs) 06:19, 13 August 2006 (UTC)

If Boring is the state, yes. If Boring is a class, I'd use Boring Route X (State). --SPUI (T - C) 11:02, 13 August 2006 (UTC)

Just because it is the official name does not mean we have to use it. For example, Jimmy Carter and Bill Clinton. --Rschen7754 (talk - contribs) 19:51, 13 August 2006 (UTC)

In either case the state abbreviaiton would have to be spelled out. That's a given. It's just a question of whehter you want the state name in the front or the back of the title...or have the state stated twice for some strange reason. In the copy (details) of the article, I assume you can call it "K-x" all you want; same with "M-x". K obviously stands for Kansas and M obvoiously stands for Michigan in those states. Also, even in abbreviated form, the state name or a state abbreviation is always existent and in the front. --TinMan 20:50, 13 August 2006 (UTC)

Let's worry about getting the disambiguation for the other 48 states first and then we can come back to Kansas and Michigan when it's time to decide schemes for individual states. (Not sure, but does Nebraska use N-X?) —Scott5114↗ 21:40, 13 August 2006 (UTC)

I support using common names, but as long as we are using common names, we should also be using a common disambiguation techniques as well. For example, Wilmington is an ambiguous name for an article. So how do we disambiguate? There is the parentheses option (Wilmington (Delaware), Wilmington (North Carolina) etc.), but that's not the technique commonly used to disambiguate town names, thus we have the article titles: Wilmington, Delaware and Wilmington, North Carolina. So before we decide that we should be disambiguating with parentheses, we should back up and see if there is another way to go about doing it for that state. In Maryland, we call our state routes simply "Route X", but when we want to disambiguate from other states' state routes we say "Maryland Route X". So to someone from Maryland at least, the title Maryland Route 2 makes more sense than Route 2 (Maryland) since the former uses a more familiar style of disambiguation. I'm not nessesarily saying that we should put the state name first, if people in Lalaland, for example, call thier routes "State Highway X" and disambiguate by saying "State Highway X of Lalaland" then we should go with that convention.-Jeff 04:06, 15 August 2006 (UTC)

A note to those who say "This is how we do disambiguation on Misplaced Pages" -- that's not really an accurate statement when made absolutely. There are, in fact, multiple methods of disambiguation on Misplaced Pages, and parentheticals is only one. It may be the most common, by virtue of the fact that it is the most adaptable, but it seems incorrect to me to just say "This is how it's done". Powers 14:42, 22 August 2006 (UTC)

I agree, and was just about to mention this myself. Let me just add that according to Misplaced Pages:Naming conventions (common names), we should "use the most common name of a person or thing that does not conflict with the names of other people or things", so "Route 2" indeed conflicts with other things named Route 2, but "Maryland Route 2" does not, so therefore the aforementioned statement would favor the second convention.-Jeff 16:42, 22 August 2006 (UTC)

But we should not use a disambiguation method that creates names that are almost never used. There are some states that almost never use the state name in front such as Massachusetts. With the parenthetical method, it is clear that the term in parentheses is not part of the name. With the state name in front, it would give the impression that the state name is part of the road name. --Polaron | Talk 17:47, 22 August 2006 (UTC)

It's my impression that putting the state name first is the most common way to disambiguate route names. If it can be argued that neither the general public nor media, etc. of a certain state uses this method, then that can be argued in that state's debate in the individual state polls, and that state can be an exception to the "use statename first" principle.-Jeff 18:14, 22 August 2006 (UTC)

Principle III: State by State

Principle III, decide on a state by state basis. Neither naming convention is 100% correct for all 50 states as a whole, neither is it 100% correct for each state individually as has been evidenced in discussions engaged in long before I lost interest in this whole mess. This should be discussed at a centralized spot for each state (ie: a wikiproject or if none exists the list of routes/highways for that state) and a consensus should be reached for each state on their own. Gateman1997 02:40, 24 August 2006 (UTC)

Discussion

I don't want to throw cold water on this, but this was a tried and failed proposition. Good idea though, although I'm not supporting this for realistic reasons. Call it Realpolitik. --physicq210 02:43, 24 August 2006 (UTC)

I know it's not realistic to assume that anyone involved with this disaster would want to engage in a discussion and follow wikipedia policy at this point... but then the world can be a very sad place indeed. I'm off to write some articles about non state highways and lighthouses, but keep me appraised if anyone wants to be mature and discuss this matter rather then vote to a non binding stalemate. Gateman1997 02:47, 24 August 2006 (UTC)

Well, all I can say right now is: welcome to the (hopefully temporarily) polarized world. --physicq210 02:51, 24 August 2006 (UTC)

This principle is pretty much the current status quo. A valid choice that should probably have been included from the beginning. --Polaron | Talk 02:47, 24 August 2006 (UTC)

I would disagree. The current status quo, at least back in April when I last was involved (and correct me if I'm wrong) is that one side insists that all states should be named (State) State Route X and the other says all routes should be State Route X (State)? Is that where it stands today? Because if that's the status quo that's not what I'm suggesting. I'm suggesting that a consensus on what each state's highways should be named be made individually at each state and then applied. This hasn't been done to my knowledge beyond some RFM's which are hardly consensus building discussions. Gateman1997 02:52, 24 August 2006 (UTC)

State by state is pretty much what is happening right now with each WikiProject deciding the naming convention for their state. WA and CA, where the most debate has been are probably the only ones that haven't come to consensus (yet). --Polaron | Talk 02:55, 24 August 2006 (UTC)

If that's the case (and that's where I remember it standing), why are we now voting on a non binding poll that supposes it speaks for all states? Why not discuss this at the two states that need discussion and come to a consensus. Gateman1997 03:28, 24 August 2006 (UTC)

I'd agree with you if those projects exhibited the capability to resolve this issue themselves. Time has proven that they lack the ability to do so, resulting in this. --TMF 03:31, 24 August 2006 (UTC)

Then bring those two states to the community as a whole in an RFC or two. That's what it's there for. If the rest are running smoothly then so be it, why should we attempt to preempt consensus? Gateman1997

Principle 0: The basics

Let's back up a bit, perhaps? Rather than jumping right into the center of the debate? I have a few general principles (since that's what this part is supposed to be about, right?) that I'm wondering if we can all agree on:

1. Highway articles almost all need to be disambiguated somehow. "Route 90" could be anything from an Interstate to a county route.
2. There are multiple ways of peforming disambiguation.
3. Misplaced Pages guidelines do not have a preference for one method of disambiguation over another.

If we can all agree on these three, I have some more that might be more controversial but would help us form a foundation for later principles. Powers 19:41, 11 August 2006 (UTC)

Sure. --Rschen7754 (talk - contribs) 22:23, 11 August 2006 (UTC)

Agreed. howcheng {chat} 22:49, 11 August 2006 (UTC)

Why not? --physicq210 00:05, 12 August 2006 (UTC)

I agree... to an extent. You could stretch these to fit both of the principles, so the statements as they are written I agree with. --TinMan 05:26, 12 August 2006 (UTC)

w00t. —Rob (talk) 14:42, 12 August 2006 (UTC)

Disagree. Misplaced Pages:Naming conventions says that "Generally, article naming should give priority to what the majority of English speakers would most easily recognize, with a reasonable minimum of ambiguity, while at the same time making linking to those articles easy and second nature." Linking to articles is easier with parenthetical disambiguation. --SPUI (T - C) 11:07, 13 August 2006 (UTC)

Misplaced Pages:Naming conventions also says "Names of Misplaced Pages articles should be optimized for readers over editors; and for a general audience over specialists." I don't think "making linking to those articles easy and second nature" necessarily means parenthetical disambiguation is preferred. In fact, Misplaced Pages:Disambiguation#Specific topic specifically says "If there is a choice between using a short phrase and word with context, there is no hard rule about which is preferred," and, in reference to using adjectives for disambiguation, "but it's usually better to rephrase the title to avoid parentheses." Powers 14:46, 13 August 2006 (UTC)

Any "disambiguating" portion of a state highway article's title (meaning a portion which does not commonly appear in documents published by the maintaining agency in the context of referring to a specific road, which exists only to help readers understand the context, or which simply disambiguates it from other roads with the same proper name) should be confined within parentheses. Period. If a certain state's DoT is inconsistant, then we can discuss it, write to them for clarification, whatever we need to do. These steps should not be necessary in the majority of cases. —freak(talk) 14:16, Aug. 13, 2006 (UTC)

Um, why? Since when is disambiguation only allowed via parentheticals? Powers 14:46, 13 August 2006 (UTC)

Principle 8 in the ArbCom case --Rschen7754 (talk - contribs) 18:09, 13 August 2006 (UTC)

"...but their use is not a required method." (ibid.) --Tckma 17:25, 14 August 2006 (UTC)

• Okay, I don't know where to jump into the debate here, so I'm just gonna start here. I think the articles should be named like the interstate and federal routes. For example, instead of Pennsylvania State Route 39, how about just PA-39? --myselfalso 19:11, 13 August 2006 (UTC)
  • Well, the problem with that is that it's confusing. It might work for some states, but definitely not all of them. In fact, the articles about Interstate and US highways are not named I-XX and US-XX. ςפקιДИτς ☺ ☻ 19:17, 13 August 2006 (UTC)
  • True, I did forget that I-XX and US-XX are redirects to Interstate-XX and US Route-XX. Ultimately, I like it the way it is. The current name for the PA-39 article is Pennsylvania Route 39. I think we should stick with that. --myselfalso 19:47, 13 August 2006 (UTC)
    • Well, I also think you should stick with that, unless the word "Highway" or "State Road" is more common in PA. I've been there a number of times, but I can't say for sure. Those decisons are later on though. Right now, we're trying to decide whether "State Term x" or "Term x (State)" is better for the majority of the country. Each side has great points, but in the end, this matters very little. No matter what the decision is, redirects can be made for almost anything. Yet, it has to be done to stop this nationwide mayhem, which by the way, seems to have died down since this debate started. --TinMan 21:04, 13 August 2006 (UTC)
    • I think it's easier to do it "State Term X" rather than "Term X (State)". I just like the formatting better. "Pennsylvania Route 39" makes more sense to me rather than "Route 39 (Pennsylvania)". I should think that there would be a disambiguation page for Route 39 (for each state route 39 and federal and interstate route 39) reguardless of the name of the page, but I would think that more people searching up PA-39 would search under "Pennsylvania Route 39" before "Route 39 (Pennsylvania)". I think the article should be named for what is simpler for the person looking up the article. And while "Route 39 (Pennsylvania)" looks cleaner than "Pennsylvania Route 39", I think the latter is easier to find faster. --myselfalso 23:01, 13 August 2006 (UTC)
      • What people are likely to search for should not be the main concern. That's what redirects are for. The title should be a common name that is used by the state DOT. For the specific case of Pennsylvania, PennDOT does use "Pennsylvania Route" but some other states do not include the state name in what the state DOT calls its state highways. --Polaron | Talk 23:14, 13 August 2006 (UTC)
        • Well stated, Polaron, I agree completely. Names should be based on official usage. → JARED   00:03, 14 August 2006 (UTC)
          • I don't think anyone's arguing that. The question is whether to disambiguate via the state-name-as-adjective prior to the route designation, or via a parenthetical state name. Powers 00:57, 14 August 2006 (UTC)
            • I completely disagree. The state DOT's half the time don't know what they're own routes are called. Many just call them many names. We had a big discussion on this for I think Minnesota highways, which are called Trunk highways. I say that road signs and mailing addresses trump the state DOT's. For example, in North Carolina, legislation dictates that Interstate 95 is called "Interstate Route 95", something I think the article shouldn't be called. Plus, Misplaced Pages encourages common names, as long as its not too informal. Official names should be used, but not when nobody calls them that. An article about the BB&T bank should be named BB&T, not Branch Banking and Trust that probably nobody has heard of. Now if a state DOT or some other official body uses language that anyone can identify with, by all means, apply it, just as long as the rest of the country doesn't suffer with silly abbreviations. The talk page of this naming convention has already covered a lot of this. I encouage that everyone at least skim over that before rambling away. --TinMan 02:27, 14 August 2006 (UTC)
              • I agree, the title of an article should reflect what the general public calls the route, not what only the government calls it. Here, the SHA calls each route MD X, but that convention isn't used by the general public. The general public is more likely to call each route "Maryland Route X", which is the naming convention we use at WP:MDRD. However if the general public uses what the government uses in a certain state, by all means, use that convention. -Jeff 03:17, 14 August 2006 (UTC)
              • That was what I was saying — choose a common name that the state DOT also uses (even if it is not the full legal/official name). But if the state does not append the state's name to what it calls its state highways, then the title should reflect that. --Polaron | Talk 03:28, 14 August 2006 (UTC)
                • Wait, whoa. We still have to disambiguate it somehow, and the pipe trick is the only reason anyone's come up with for using parenthetical disambiguation. I personally don't find that particularly compelling. Much better to have parallelism, IMO. Powers 11:35, 14 August 2006 (UTC)
              • Um, with what part of my statement do you disagree, TinMan? Powers 11:35, 14 August 2006 (UTC)
                • When you stated, "common name that is used by the state DOT" I thought you wanted the DOT's to decide everything, something I oppose (the bold threw me off). My point is that DOT's rarely know themselves. In Virginia's case, when someone sent an email to the state DOT, they just looked at what the minutes of DOT meetings said and gave out popular references. Your further statements clarify your true intentions though. I'm in a agreement now that I know what you're saying. --TinMan 18:41, 14 August 2006 (UTC)
                  • I didn't say that. Maybe you meant to reply (and disagree with) Polaron? Powers 22:58, 14 August 2006 (UTC)
                  • right. --TinMan 02:41, 15 August 2006 (UTC)

Agree with all numbered "Principle 0" items given above. --Tckma 17:23, 14 August 2006 (UTC)

I also agree with this. Both ways work - what's the problem? We can always use redirects. --master_son 23:17, 15 August 2006 (UTC)

Disagreement

OK, so we're all agreed on points one and two, then. Point three has broad support, but SPUI and FreakofNurture disagree. SPUI has a good point that parenthetical disambiguation allows the pipe trick to work, but I think it's important to note that the pipe trick will still work as long as we have the proper redirects in place. In fact, I daresay almost all of the linking issues on both sides of the argument go away if we have the proper redirects in place. Even the search issue pretty much goes away if we have the proper redirects in place. Perhaps, then, the only remaining issue is what should the user see at the top of the page? That is, the title -- but the title without respect to how easy it is to search for or how easy it is to link to it, since all that is taken care of by redirects; rather, the title with respect to how it is read by the user on the actual article. Thoughts? Powers 15:09, 15 August 2006 (UTC)

I agree that redirects make alot of points moot in this debate, so what it comes down to is what title simply looks right. People from "Some State" might say "Route X" but disambiguate from other states by saying "Some State Route X" and people from "Another State" might say "Highway X" and disambiguate by saying "Highway X in Another State". In this case I think the article titles should match how people disambiguate rather then use parentheses. Like I said before we don't disambiguate town names with parentheses because people are more familiar with using "TownName, StateName", I don't see why that principle should be any different here.-Jeff 15:44, 15 August 2006 (UTC)

That's not the only issue - Rschen7754 was changing the bolded titles of articles from "State Route X" to "California State Route X" until he was blocked for it. He only did it on pages that were located at "California State Route X" (California has some at each).

There's also the issue of only those of us "in the know" using the redirects. If someone is writing an article on Foo, California, and wants to say that State Route X runs through it, they'll probably look up State Route X, find the disambiguation page, click through to California, and use the title of the page. So the article will read "California State Route X runs through Foo". --SPUI (T - C) 20:07, 15 August 2006 (UTC)

I don't think someone would do that. I think they would search for "California State Route x" (or some other term)... the point is, I think they would obviously put the state name in the search, realizing that each state has routes and there are U.S. routes, and Interstate routes, county routes, so on and so on. Furthermore, what's wrong with saying "California State Route X runs through Foo"? I don't see anything wrong with that. --TinMan 18:46, 16 August 2006 (UTC)

You are objecting to one of my assumptions that doesn't affect the argument. No matter what someone types, if they find the page, they are likely to link to it using the title. And saying "California State Route X runs through Foo" is bad writing, because it is redundant, just as we don't say "California State Route X runs from Foo, California to Bar, California via Baz, California and Bam County, California". People don't generally call it that. --SPUI (T - C) 20:37, 16 August 2006 (UTC)

So you're saying that people are smart enough to not repeat "California" all the time. Is there some reason that they wouldn't use ] runs from ] to ] via ] and ]? We already expect them to do that for the city and county links. Isn't it reasonable to think they'll do it for the road link too? howcheng {chat} 21:55, 16 August 2006 (UTC)

Yes, I am saying that. See for instance and . It's worse here than with cities because some states do put the state name first. --SPUI (T - C) 22:48, 16 August 2006 (UTC)

Good point SPUI. I can see where this would get quite redundant on articles dealing specifically with California or another state. However, saying "State Route 1 is a state highway in the U.S. state of California" is an incorrect statement. That's why I suggest we treat route articles like we do for city articles. After the state name has been claified once, we can drop it for the rest of the article, similar to how pronouns replace nouns. For example: you could say: "Washington State Route 7 is a state highway in the U.S. state of Washington. It is 372 miles (83 SPUI UNITS) long. State Route 7 travels east-west in the northwest corner of the state." Yes, Washington would be clarified twice in that instance, but I don't think we have a choice if we want to be accurate. In North Carolina, the first bolded letters have been replaced by a common nickname, so an article might read: "NC 87 is a state highway in central North Carolina, United States." (I just put SPUI units for kicks.) Now, let's say I'm writing an article on Clingmans Dome and I wanted to describe the road that takes visitors to the park. I would have to say "North Carolina State Highway 37 provides access to the park", not "State Highway 37 provides access to the park" since the mountain is right on the NC/TN state line. (That's not a true statement, it's just for example). --TinMan 01:41, 17 August 2006 (UTC)

'However, saying "State Route 1 is a state highway in the U.S. state of California" is an incorrect statement.' Uh - what? That's perfectly correct, just like "Santa Barbara is a city in California, United States." Santa Barbara is a disambiguation. There are multiple cities named that. This one is a city in California - and this SR 1 is a state highway in California.

Wait, how is saying anything "State Route 1234 is a state highway in the U.S. state of Utopia" an incorrect statement? Even if it's also a state highway in Dystopia, the former's still correct. --Tckma 19:49, 17 August 2006 (UTC)

Look below. --TinMan 02:08, 18 August 2006 (UTC)

As for your Clingman's Dome example, it depends. You could say "State Highway 37 provides access to the park from Fooville, North Carolina" without any ambiguity. --SPUI (T - C) 13:50, 17 August 2006 (UTC)

I guess you could wiggle around it like that. I stand corrected...d'oh! I'm just not a fan of leaving the state name off on non-route articles. You could say "Billy Joe lived on State Route 8 in California" or "Billy Joe lived in California on State Route 8" or "Billy Joe lived on California State Route 8". Each has its benefits and down-sides. --TinMan 18:07, 17 August 2006 (UTC)

Something that hasn't yet been mentioned here either is that the correct name for the route is simply state route 8, not california state route 8. Caltrans calls all their routes state routes, not california state routes. It would be more correct, then, if you really want to put the state name before the route, to put "Billy Joe lived on California's State Route 8," just as you would say "Billy Joe lived on San Francisco's Market Street," not "Billy Joe lived on San Francisco Market Street." atanamir 17:29, 22 August 2006 (UTC)

TinMan's Final Analysis: So I guess all we're voting on tomorrow is which design do you like better. Both principles have pros and cons and I could go either way. The best thing to do is weigh each side and come do a decision, selecting the lesser of two evils. --TinMan 18:07, 17 August 2006 (UTC) By the way, check out . Four years ago. It's all Brion's fault. --SPUI (T - C) 22:48, 16 August 2006 (UTC)

Okay, so the issues are the title as it appears to the reader, without regard to how easy it is to link to it, but with regard to how it influences editors referring to it. Is that fairly accurate? Powers 14:35, 17 August 2006 (UTC)

It's also easier to link to a parenthetically-disambiguated title. The naming convention apparently takes into account these nuances. --SPUI (T - C) 14:46, 17 August 2006 (UTC)

I'm not clear on what you mean by the latter statement; which naming convention, and which nuances? I think your first statement is obviated by the use of redirects. ] works regardless of whether the link in question is a redirect or the main article. Powers 14:56, 17 August 2006 (UTC)

The only possible reason I can see for that is to avoid the user seeing "California State Route 1234... redirected from State Route 1234 (California)" in the article title. And really, who cares, as long as you get to the actual article? --Tckma 19:43, 17 August 2006 (UTC)

The only impact I see is in the parent category display order. They will appear odd in appearance and look like some are misnamed if the dab form is used. I'm not saying wrong, just odd. Having the state name first for these articles unifies the look in those categories and makes it clearer that each state names their roads differently. Vegaswikian 06:21, 19 August 2006 (UTC)

Flaw in point 3

Coming to this late, and have no great stakes in the debate, but there is a flaw in point three, that Misplaced Pages guidelines do not have a preference for one method of disambiguation over another. Misplaced Pages:Disambiguation does offer the following: it's usually better to rephrase the title to avoid parentheses when discussing specific topics. Steve block Talk 10:47, 24 August 2006 (UTC)

Voting

So we're going ahead with voting despite the fact that we can't even agree on the principles involved? This has the makings of a sham. Powers 20:44, 19 August 2006 (UTC)

Wow, right now it's a dead heat. --TinMan 01:52, 20 August 2006 (UTC)

Going back to my initial thoughts about this poll when I first heard about it two weeks ago, I believed that this had all the signs of a sham. Consider the two proposals: the first one would establish a nationwide standard. Would this set a standardized naming convention? Yes, to an extent. Would it please everyone involved? Absolutely not. Would it be an appropriate NC for every state? Equally not so. Then you go to proposal two, which advocates the use of a "common name". From the way the proposal is presented and the comments of others, this proposal seems to be nothing more than advocating status quo. Anyone can argue what a common name is, meaning that the heated debates (WP:WASH and WP:CASH come to mind) over naming conventions that this poll was intended to end, will continue to rage on. The end result: regardless of what proposal is chosen, someone won't be happy at the end of the day. --TMF 02:29, 20 August 2006 (UTC)

Well, it's inevitable, isn't it? --physicq210 04:24, 20 August 2006 (UTC)

Pretty much. =) --TMF 04:42, 20 August 2006 (UTC)

I'll be laughing out loud if the vote ends in a tie, but I'll be crying on the inside. Stratosphere 02:50, 20 August 2006 (UTC)

as an added note, I used to be in agreement with the argument of those who have signed principle 1, but given the examples that would be applied to Michigan (which I think are stupid), I opted for principle two which would keep the status quo at the Michigan WP. I haven't been around in the Roads department nearly as long as many of you, but I see why it had to come down to this, it's unfortunate. Stratosphere 02:09, 21 August 2006 (UTC)

I have to agree that the Michigan example in Principle I is stupid and redundant. However, one of the reasons I chose Principle I was simplicity. If we were to follow Principle II, we would have 51 naming standards/conventions for state highways, one for each state and the District of Columbia. --physicq210 02:21, 21 August 2006 (UTC)

I agree. If the Michigan example in P1 had been Michigan State Highway XX, I would have voted for P1. Nobody calls a route a trunkline, the DOT hardly uses the term, and Michigan M-XX is just stupid. Oh, well, in the end it all doesn't matter. As SPUI says, everything can be fixed with redirects. Stratosphere 02:43, 21 August 2006 (UTC)

The trunk highway name was chosen for Michigan because no one was sure what the specific term was for Michigan. There's no reason why "Michigan State Highway XX" can't be used for Principle I, as it still fits the basis of the principle. --TMF 02:51, 21 August 2006 (UTC)

From what I understand, per the previous discussions, P1 uses the official term, which is trunk line. That's how it's defined in law and it make me cry on the inside. Stratosphere 03:20, 21 August 2006 (UTC)

When I proposed principle I, I was under the impression that I was merely proposing a principle and that the road term would be determined by discussion and not necessarily by official name. If I'm wrong, someone correct me. --TMF 03:23, 21 August 2006 (UTC)

If that is the case, (I've been wrong before), then once the voting is over for this part we vote for styles per state on an individual basis that follow the principle passed? Stratosphere 03:28, 21 August 2006 (UTC)

Exactly. From the project timeline: Part II: Individual state conventions - By 23:59 UTC on September 4: Preliminary list of conventions vote begins (one section for each state, that is where voting will occur. Transclusions onto state highway WP talk pages are acceptable as well). Here we are voting on "Highway" versus "Route" versus "State Route" etc. for each state individually. --TMF 03:37, 21 August 2006 (UTC)

Ah, pfft, reading is for suckers :P I guess I was under the impression that this first part was going to set a hard definition and that part 2 would be voting on minor variations of the one that is selected. Good to know. Stratosphere 03:45, 21 August 2006 (UTC)

The issue now is what they will redirect to. --physicq210 02:49, 21 August 2006 (UTC)

I'm guessing that if its close to a tie, each state just gets to pick one and move on to the next step of the process. By the way, bets anyone? :) --TinMan 04:23, 20 August 2006 (UTC)

TinMan, you're probably pretty accurate with that assumption. Honestly, I see "status quo" in the future of this poll. --TMF 04:42, 20 August 2006 (UTC)

What is the status quo? --physicq210 04:43, 20 August 2006 (UTC)

Individual naming conventions by state determined by the individual state WikiProjects. --TMF 04:45, 20 August 2006 (UTC)

<sarcasm> I thought it was confusion and flaring tempers. </sarcasm> --physicq210 03:57, 21 August 2006 (UTC)

That too :P. It seems like no matter how this debate turns out, the individual naming conventions are going to be the real debate here. Thus we will end up where we were at the start of this part of the debate, only with the states now being forced to pick NCs.-Jeff 18:31, 21 August 2006 (UTC)

Wait, now. Isn't Principle 1 XX? Or is it XX? --Tckma 19:28, 21 August 2006 (UTC)

It depends. That's why it was decided to leave out the descriptive (and hence limiting) adjective altogether. --physicq210 19:30, 21 August 2006 (UTC)

It's whatever the individual state poll come up with. It could be Trunk Highway, State Road, State Route, Highway, Autoroute, Fluffy Bunny Route, Primary Route, SR, etc. However, the guideline says it should be a common name and one that's somewhat official as well. --TinMan 17:05, 22 August 2006 (UTC)

Seems to me the best idea on here is uniformity. Even though Principal 2 seems slightly more confusing to me, it's a lot less confusing than both principles being used at once. I expect to adhere to the majority vote, be it the result I supported or not, but I don't expect others necessarily to adhere to it. Nyttend 01:38, 23 August 2006 (UTC)

This poll seems to have stirred up lots of controversy in the Misplaced Pages:WikiProject Virginia Highways. We had already agreed on a standard, Virginia State Highway XX, and another user, User:NE2, comes along and wants to change what we already have to State Route XX (Virginia). The same debate that goes on here has spread to our project. It is almost like he is dictating it to us. I think that no matter what happens nobody will be happy. This is a never ending battle, and I think it is a losing one on all sides. --Willy No1lakersfan (Talk - Contribs) 02:33, 24 August 2006 (UTC)

Termini problem

Ok, I was just thinking, which is scary! For Principle 2, what would you say for roads that terminate at the state line. For instance, if State Highway 37 (Delaware) ended at State Highway 92 (Virginia), how would you phrase it so someone could understand "State Highway 37 ends where State Highway 92 begins at the Virginia state line." Would you put parentheses there too to show which state highway goes to which state? --TinMan 23:44, 23 August 2006 (UTC)

There are several ways to disambiguate in article text. State Route 37 in Delaware, Delaware's State Route 37, or Delaware State Route 37, I prefer the last, especially if that's what the articles end up being called. When referring to out-of-state towns we don't say Maryland's Annapolis, for example, we say Annapolis, Maryland. Similarly we should apply the standard disambiguation method here whenever it is called for.-Jeff 00:59, 24 August 2006 (UTC)

Piped links older ≠ wiser 01:45, 24 August 2006 (UTC)

So in other words you would either say "State Highway in " or revert back to Principle 1? Exactly what I was expecting. --TinMan 02:08, 24 August 2006 (UTC)

No, Regardless of which option were in force, I'd be using piped links for just about every reference to a road. No one uses any of the suggestions under Option 1 for "Michigan M-XX or Michigan Trunk Highway XX or Michigan State Highway XX". I don't know about any of the other states. The current naming convention for Michigan roads is pretty good AFAIC. M-XX (Michigan highway) is unambiguous, and with the pipe trick, it is simple to create links that display the name most commonly used for the roads, M-XX. With the names suggested for Option 1, it wouldn't be quite as convenient. older ≠ wiser 02:26, 24 August 2006 (UTC)

Right, a number of states don't use the title name for the rest of the article. They may abbreviate the state name like M for Michigan or VA for Virginia or NC for North Carolina and use that form for the rest of the article. Michigan is a special case in where the abbreviated version "M-XX" is part of the title. Most states, as of now, do not use their abbreviated version in the actual title. It's either "State Route XX (State Name)" or "State Name State Route XX", not "SN-XX (State Name highway)" for most states. So if everyone keeps debating "well, State Route XX is the common name, not Mystate State Route XX " and they're not even going to use that common name in the article, why bother? In the abbreviated form, the state names are in front, so why not for the title? Why not use a format that you you're going to use in the article, even if it is just abbreviated? --TinMan 02:37, 24 August 2006 (UTC)

I don't follow what you are saying here: In the abbreviated form, the state names are in front, so why not for the title? Why not use a format that you you're going to use in the article, even if it is just abbreviated? What do you mean by the "abbreviated form"? I mean, I really don't give much of a hoot about what how articles for roads in other state name their articles. I will be pretty POed if someone once again renames all the Michigan road articles. The articles had originally been at "Michigan State Highway XX" and after some discussion in which everyone except Rschen7754 agreed that the name "Michigan State Highway XX" was not only incorrect but bad, a number of editors undertook to rename the articles. IMO, the current naming setup there is much preferable. The most common way to refer to the routes, M-XX, is first and has the greatest emphasis in the title. The parenthetical portion provides clear disambiguation (and facilitates using the pipe trick). older ≠ wiser 12:58, 24 August 2006 (UTC)

For termini, I usually put either "State Highway 152, Texas state line" or simply "TX-152".

Now as for the Michigan/Kansas debate: I've never been to Michigan, so I'm not sure about the officialness of the names there. But I'll say this about Kansas: the only source I've ever seen not use "K-" was The Kansas City Star, and it's based on the Missouri side. K- is used by KDOT as well as common usage. Then, we have problems with K-9 and K-12 and other non-highway articles conflicting. So we add a parenthetical term, which is the same thing that is normally done when article names conflict. "Kansas State Highway 10", "Kansas 10", and "Kansas K-10" are neither official nor commonly used. But, again, this is more relevant to part 2 of the poll.—Scott5114↗ 14:53, 24 August 2006 (UTC)

Part I Voting

Directions

• Add your name and YOUR NAME ONLY using the format #~~~ below the principle in which you endorse. You cannot vote more than once.
• DO NOT change and/or otherwise edit votes that are not yours (except for those of confirmed abusive sockpuppets, to be nullified only by one of the six judging admins, and those who have not reached the 100-edit threshold, in which case anyone may strike out).
• Do not discuss principles or otherwise leave comments here. Please discuss in the relevant sections above.

Reminder

• Voting ends 23:59, Thursday, August 31 2006 (UTC).
• The current time is 19:30, Monday, December 23, 2024 (UTC).

Principle I: XX

Examples

• Florida State Road XX
• Louisiana Highway XX
• Massachusetts Route XX
• Michigan M-XX or Michigan Trunk Highway XX or Michigan State Highway XX
• New York State Route XX

Votes in support of Principle I

1. TMF
2. howcheng {chat}
3. Rschen7754 (talk - contribs)
4. -Jeff
5. physicq210
6. TinMan
7. Homefryes
8. Station Attendant
9. GeeJo ⁄_(c) • 07:04, 20 August 2006 (UTC)
10. Nyttend
11. Athryn
12. JB82
13. Seattlenow
14. Stratosphere
15. WAS 4.250 04:46, 21 August 2006 (UTC)
16. Calton
17. *drew
18. FLWfan
19. Exodio — Preceding unsigned comment added by 216.146.80.34 (talk • contribs) Note: This vote is valid; see . --physicq210 03:26, 22 August 2006 (UTC)
20. tckma 19:24, 21 August 2006 (UTC)
21. -- tariqabjotu 20:31, 21 August 2006 (UTC)
22. --EngineerScotty 23:09, 21 August 2006 (UTC). But barely.
23. --Gherald
24. Kether83 04:40, 22 August 2006 (UTC)
25. Thumbelina 17:31, 22 August 2006 (UTC)
26. JohnnyBGood t c VIVA! 22:48, 22 August 2006 (UTC)
27. Willy No1lakersfan (Talk - Contribs)
28. --myselfalso 19:15, 23 August 2006 (UTC)
29. Bubba ditto

    FairHair Vote struck, as editor did not meet 100-edit threshold; see vote count for evidence. --physicq210 02:56, 24 August 2006 (UTC)

30. Seicer (talk) (contribs)
31. Zsinj
32. Deh 21:29, 24 August 2006 (UTC)

Birgitte§β ʈ Talk

--SPUI (T - C)

—Scott5114↗

master_son

Polaron | Talk

older ≠ wiser Bunchofgrapes (talk) 00:24, 20 August 2006 (UTC)

Lincher 13:12, 20 August 2006 (UTC)

W.marsh 04:41, 21 August 2006 (UTC)

Cyde Weys 05:04, 21 August 2006 (UTC)

FCYTravis 05:34, 21 August 2006 (UTC)

Kusma (討論)

Avenue 14:45, 21 August 2006 (UTC)

Nnnnnnnhytr 16:03, 21 August 2006 (UTC) (Very new user, probably trollish sock (contribs) - Fut.Perf. ☼ 16:43, 21 August 2006 (UTC))

FrankB 21:14, 21 August 2006 (UTC)

—freak(talk) 21:55, Aug. 21, 2006 (UTC)

--SB | T 22:05, 21 August 2006 (UTC)

atanamir 22:54, 21 August 2006 (UTC)

Rory096 23:22, 21 August 2006 (UTC)

Ral315 (talk) 02:03, 22 August 2006 (UTC)

Dakota 07:50, 22 August 2006 (UTC)

InkSplotch 17:37, 22 August 2006 (UTC)

—Rob (talk) 17:48, 22 August 2006 (UTC)

M 00:27, 23 August 2006 (UTC)

→ JARED   14:39, 24 August 2006 (UTC)

Bastique▼ _voir 15:10, 24 August 2006 (UTC)

Principle III: State by State

Decide on a state by state basis either at the state's wikiproject or if none exists on the list of routes for that state.

Votes in support of Principle III

1. Gateman1997 02:36, 24 August 2006 (UTC)