Wikipedia talk:Naming conventions (settlements)/Archive 18

From Wikipedia, the free encyclopedia

Archive This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Contents

An international convention is very possible - case in point.

I read above that an international convention is "impossible", but the world-gazetteer website is a complete contradiction to this theory. They disambiguate with "Name (Country, locale)", and it works just fine for everything. Here's a link to their "Mar" list section, but you can find the root of the list here. It's great as a base, but I think it's possible to even do better. Cheers. - THEPROMENADER 07:28, 31 July 2007 (UTC)

This World Gazetteer is seemingly somewhat illogical and seems to think that a country like England for instance is the equivalent of a US state. It has for instance Whitfield, United States of America, Florida) but Whitfield (United Kingdom, England). According to Wikipedia there are five Whitfields in England! It has nothing like the coverage of Wikipedia, and doesn't even include White Lake Township. Dahliarose 11:12, 31 July 2007 (UTC)
I'm not sure why Promenader is holding World Gazetteer up as an example worthy of emulation. It is a poor comparison on several bases. First, and most significantly, they have no need to disambiguate the titles of the articles since they use a database schema in which each object in the database is referenced by a unique id. In such a schema the title does not need to be unique. There could be hundreds of articles with the exact same title. With Wikipedia, the title of necessity must be unique. Second, the actual pages are nearly unintelligible with regards to deciphering where the location is. Consider this entry. It took me a few moments to realize that the location information was contained in the blue shaded box (although why the term "Quiblah" separates it from "Marysville" is a mystery. Sorry, but I don't think the World Gazetteer is something Wikipedia should try to emulate in any manner at all. older ≠ wiser 11:17, 31 July 2007 (UTC)
I didn't explain myself there. I considered the column to the right to be disambiguation - this combined with the placename would make a unique title. If we are obliged to disambiguate here, this is an example of what we could do. Note that the placename with disambiguation indeed make a unique and clearly indicated title. Note also that every entry is disambiguated in exactly the same way: "Placename (Country (, region (, smaller region)))", across the board, for every country. THEPROMENADER 12:46, 31 July 2007 (UTC)
There's still the fundamental question of why an international convention is better. The argument keeps being made that it is possible and that is all fine and good, but as I have stated before, just because something can be done does not mean that it should be done. I have given my reasons why I feel the scheme currently in place for US city articles is the best, and I have yet to hear a compelling argument as to why that should be changed. Again, my experience in dealing with foreign city articles is limited and I do not pretend to know what is best for those articles. That is why I cannot in good faith support imposing the same standard on them if there is any argument to the contrary. ɑʀкʏɑɴ 15:15, 31 July 2007 (UTC)
Thank you for your honesty and honest opinion. Perhaps I am a bit of an exception here, as my birthplace is London, Ontario, yet I've been living in Paris, France for over half my life - this most likely why the difference in "country treatment" is so marked to me. Here, I cannot speak of my hometown in local lingo, as many do not know where Ontario is (and the French seem to be persuaded that Quebec covers more than half of Canada : ), so I am obliged to say "London in Canada" - perhaps adding "near Toronto" as foreigners know the location of major cities in other countries better than they do Provinces. This is also why I think that the some of Wiki's placename naming conventions must seem very backwards from a foreign point of view. THEPROMENADER 16:44, 31 July 2007 (UTC)
Thank you very much for explaining your PoV; that's a great help.
  • This encyclopedia is not written for the French; we expect them to use the fr: WP (which, by the way, uses fr:London (Ontario), so some francophones must manage.)
    • And of course Quebec is more than half the civilization of Canada (and that's what counts, n'est ce pas?) </satire>
  • Ontario is probably enough, usually, to tell them whether they have the right London or not; in the exception, they can either click on it, or look up Ontario directly. English speakers should be in a better position.
  • If you look up London directly, it will take you a click on the dab header to get away from London, England; I think that's an unavoidable cost, given which London most readers will want.
  • We require dab pages to use the actual article titles, to minimize chance of misdabbing. I think it's a good idea; and this is not the place to change.
    • If our non-North American is looking for London, Ontario, there's only one city we have an article on. "Ontario" may reassure him he's going the right place.
    • If he actually wants London, Texas, the state name may remind him that he heard it was in some state beginning with T, and get him to start his search there; in any case, can it hurt? Septentrionalis PMAnderson 17:12, 31 July 2007 (UTC)
(Grin) Consider it an education more than a POV. Your post sounds like it should mean something, but it doesn't: "May do" and "are probably enough" are but hypothoses that do nothing to help this (at least until now) constructive search for concrete wiki-wide solutions, nor does is do anything to validate your very apparent point of view. I never even hinted at eliminating dab pages. Please save the sardonic tone next time you post - there's nothing "wrong" going on here - au contraire. Cheers. THEPROMENADER 17:31, 31 July 2007 (UTC)
I used to be engaged in this debate (on the anti-city, state side) but gave up long time ago, for having more productive things to do; still, I do have this page on my watchlist. I thought I could chime in with a different (fresh?) view on the matter (triggered by Bkonrad "database" remark); just something to think about...
Part of the problem (which is fairly entrenched in our wikipedian minds) is that the article title serves two purposes on Wikipedia: it is a title (in the usual sense of the word) and a locator (in the URL sense of the word) -- it is the page where search facility or an internal link will take you when the string contents are matched. This is something that wikipedia editors take for granted: it is convenient to type [[London]] and inconvenient to type [[AER434FCBDNJ|London]] where "AER434FCBDNJ" is the article's ID in an imaginary database.
An amicable solution to this perennial debate could be perhaps to separate those two things, or possibly separate them optionally. But it would have to be done in MediaWiki software, along the lines of {{DISPLAYTITLE}}, (see Signpost technology report). The feature is now half-baked (and had been broken for a time), as it doesn't affect the text in categories and other "reader" namespaces. As result, the page located on San Francisco, California could have page title "San Francisco" (which would, hopefully, be acceptable even for "city, state" proponents), while physically located in the same place. That would also arguably solve other perennial disambiguation problems, such as whether "The Fall (band)" or "The Fall (novel)" is the "primary use"; they can be located wherever they like (e.g. whatlinkshere link count could be the primary factor), both having the correct title "The Fall". The page locator could be displayed somewhere on the top of the page but on a less prominent location, to ease the use for editors; some other software changes could be done to facilitate navigation and linking for both readers and editors; but the former's convenience is the one which we should strive for.
A further feature could be e.g. the default stripping of bracketed or comma-tized disambiguator (e.g. title of the article John Smith (Welsh politician) would automaticaly be "John Smith", unless explicitly overriden)
Granted, that would also be an opportunity for "page-title vandalism" (because changing the title would not require page moving privileges, which are earned after 4 days of registration anyway).
This was just a sort of (wishful) (incomplete) (brain-storming) thinking; perhaps some push to developers in that direction could be achieved granted a critical mass of editors. Or maybe not. Just my 2c. Duja► 15:34, 31 July 2007 (UTC)
You are of course correct - a large part of the problem does stem from the fact that our article titles serve a dual purpose. I'm not sure who but I do recall someone stating that comparisons to a paper encyclopedia are difficult because a paper encyclopedia is free to use whatever title for an article they like, whereas we are forced to select a unique title for each article. Perhaps, if some of the changes to the software you mentioned were implemented, we would have a little more leeway in terms of article titles, but for the time being - that's not an option :( ɑʀкʏɑɴ 15:59, 31 July 2007 (UTC)
...but, the usual mantra: had we spent half the kilobytes and time discussing a technical solution's features, pros, and cons, as well as persuading the developers to implement it compared to the current eternal debate, we'd likely have it implemented by now. :-). Duja► 16:07, 31 July 2007 (UTC)
(edit conflict) .. and thanks for the fresh input, Duja : )
I think it is the technical aspects of discussing an international convention are the most interesting and conclusive. I am still undecided about the "pre-disambiguation question", but for the method of disambiguation, I am already convinced that parentheses are the only way to treat placenames equally across the board - and that we should totally forget about the "local convention" method that will of course differ from country to country (comma, country, state, parenthesis) with room for miscomprehension between them.
Leaving that oft-mentioned lacking behind, I've also given thought to the "search" aspects of finding articles on Wiki. Being a webmaster, it has always been in my experience that articles that have the search terms in the title always show up on top of the result list. If I was looking for an article for Dieppe in France (and I was not from that country), what do you think my search terms would be? More than likely, exactly those. Speaking from habit, I'd first try just Dieppe, and try both terms if the first search turned up too many results.
(Note: someone moved the above article from its former Dieppe, France to Dieppe, Seine-Maritime: the comma convention is never used like this in France, and there is only one Dieppe in the whole country... there are decidedly more than a few gung-ho "city, staters" out there : )
Interestingly, the person who performed that move appears to be someone quite involved with editing and creating French location articles. Not to insinuate they "know better than you", but one can infer that this person is knowledgable about French locales and nevertheless prefers the comma delimited disambiguation form. This is almost an argument for the City, State method (or a close cousin), as it appears editors not familiar with this discussion and yet familiar with foreign locations nevertheless prefers that method. Again, I would argue that the comma-delimited disambiguation method is not only well understood among Wikipedia users, but expected. ɑʀкʏɑɴ 17:14, 31 July 2007 (UTC)
But a majory part of the argument for the "comma convention" was that is is "common usage" within the U.S.. It is nothing of the kind in France! THEPROMENADER 17:31, 31 July 2007 (UTC)
That may well be - and as stated before, I have no desire to impose a "comma convention" on France, or anywhere else for that matter, if it is nonstandard for the location. My point was to say that from a wiki-wide perspective, the "comma convention" appears to be well understood and sometimes even expected. This helps to defuse the argument that, from a wiki-wide perspective, comma delimited disambiguation is potentially confusing. ɑʀкʏɑɴ 17:39, 31 July 2007 (UTC)
(edit conflict, edited following for the above) No big deal, I'm not a "militant" in any of this. You're right about Olivier: he is one of English Wiki's major French-article contributors (as I am) - I'll ask him about it. THEPROMENADER 17:42, 31 July 2007 (UTC)
It's not the method of disambiguation itself that is confusing, it's the different methods of disambiguation in use within the same category (settlements especially). If all of Wiki used just one method there would be almost no confusion at all, no matter what that method was. My question about the comma is slight and nothing concerning this discussion, so let's not get into that here. Cheers. THEPROMENADER 17:48, 31 July 2007 (UTC)
Both "name-based database" comments above are interesting. Most database entries are assigned "auto-increment" id numbers, and the name is just a spot in the DB array like any other - but we on the "GUI side" can't really do much to work with this - all we have to work with is the article name and content.
I would like to see names remain un-disambiguated if possible, but I am not yet sure if this is possible in this media - or how it will look/be understood in the media as a whole - and in any case, which cities are and aren't disambiguated will of course be a source of constant change, if not confilct. The best solution I have seen thus far was a proposition to have every city occupy a unique "full disambiguation" slot (country included), and have this redirect to a shorter name if later decided. This at least would leave room for later change and later city additions - it would also be an answer to the search criteria I mentioned earlier. THEPROMENADER 16:44, 31 July 2007 (UTC)
Many databases also have a unique index built across one or more user-visible columns that prevents rows with duplicate keys to be entered. The article title is a unique index in Wikipedia. I don't think a technical solution is required here. The solution is already available and used in every other precise class of articles in Wikipedia: only dab when necessary. Why should U.S. cities be any different? --Serge 17:35, 31 July 2007 (UTC)
(scratching head) I'm a web-designer, Serge, but I don't quite see what you mean ("user-visible" - you mean "a selection of data from each entry"?) - nor what that has to do with "only dab when neccessary". We're not talking about details or U.S. cities here, we're talking about an international method. THEPROMENADER 17:55, 31 July 2007 (UTC)
By "user visible" I mean data values that are meaningful and visible to the user, as opposed to a hidden internal sequence number, for example. I know we're talking about an international convention, but the main stumbling block to that is the position that U.S. cities should be treated differently. I'm asking why? --Serge 18:06, 31 July 2007 (UTC)
Understood then, but please stop asking your "why is the U.S. different" question in this thread - it is misplaced. We're trying the technical possibilities of one method for all here. THEPROMENADER 18:33, 31 July 2007 (UTC)
Okay. Well, the Gazeeter example illustrates that one international convention is possible. Whether it's a desirable approach is another matter. Personally, I think how one dabs should depend on the other uses of the name in question, so there is no one particular one-size-fits-all dabbed format for any or all of city names. When you see a dabbed article title in Wikipedia, how it's dabbed should give you a hint about why it's dabbed. Cork (city), for example, tells you that the conflicting uses of Cork are not cities. --Serge 18:49, 31 July 2007 (UTC)
But the reason that dab was chosen is discussed on the talk page. It is in part that Cork, much like Luton, has no larger county of which it is part. Septentrionalis PMAnderson 15:14, 3 August 2007 (UTC)
Is it an "effective" choice would be a proper question - desire is largely a question of taste. Even your isolated Cork example would work if Country was used as a placename locator/disambiguator - as clearly shown in the Gazetteer website. THEPROMENADER 06:50, 15 August 2007 (UTC)

Close to consensus

Just a suggestion, for now can we ignore the arguments to completely get rid of this convention or not? It appears that we are close to reaching a consensus on which cities in the US convention may/should reside at [[City]] and rehashing whether or not this convention should be chucked is getting in the way of that consensus. With that in mind, the only issues that I see remaining are whether or not the wording should say "may" or "should" and whether or not using the AP Stylebook is too US centric.--Bobblehead (rants) 15:54, 15 August 2007 (UTC)

I don't see the point, as long as Serge says he will continue to request, lobby for, and personally move cities to their unqualified name, regardless of what these guidelines say. I'm still against the convention unless the guideline makes it clear that this is an exception to the general rule, and the general rule still applies unless this or some other specific exception applies. — Arthur Rubin | (talk) 16:13, 15 August 2007 (UTC)
Bobblehead - okay. Arthur - that's not what I said. --Serge 16:31, 15 August 2007 (UTC)
For what it is worth, I am all for using the AP list, I find Arthur's caveat acceptable, and I find Serge's use of the word "should" as acceptable. ɑʀкʏɑɴ 16:36, 15 August 2007 (UTC)
Why would it matter if the AP list is too U.S.-centric for a U.S. convention? Skeezix1000 17:51, 15 August 2007 (UTC)
Because we want a convention that makes things easy for all users of this Wiki, including non-Americans? What seems obvious and useful to us Americans may not be so obvious if you're a Minangkabau schoolchild or a Mongolian bureaucrat; but this Wiki is for them too, if they read English.--Orange Mike 18:47, 15 August 2007 (UTC)
Of course, that's obvious. That's not what I was getting at. If the potentially emerging consensus is to have significant U.S. cities at [[City]], then of course any third party list (such as AP) of significant U.S. cities would likely be U.S.-centric. Just as any determination of significant Mongolian cities would likely be Mongolian-centric.Skeezix1000 12:37, 16 August 2007 (UTC)
There is a Tagalog Wikipedia. Septentrionalis PMAnderson 21:37, 15 August 2007 (UTC)

More use of dab page

One of the common issues on settlements being located at the primary topic name is, do they belong there? This is especially true if there are other settlements that also share that name. This comes up rather often on move requests.

The common objections to moving include:

  1. the existing settlement is already at the name so why move it
  2. the existing settlement is the oldest
  3. the existing settlement is the one that all of the others derive their names from
  4. the editors of the existing article don't believe it should be moved
  5. the links to the existing article are mostly for the article currently at this name

What does not get much play is, which article is the primary use. Frequently there may not be one, especially if the primary name has uses other then settlements. Item 4 in the list is the built in bias from the way the requested rename process works. Item 5 is simply an artifact from editors have to clean up links for the other articles that readers and editors expected to find at this name. Item 1 may or may not justify no change. As for items 2 and 3, they may or may not indicate support for a primary topic.

I'd like to see the guideline address this in more detail and give support for using a dab page at the primary name when there are reasonable alternatives for the primary name. I guess I'm thinking that when there are valid points made for moving the current article, locating a dab at the primary name space should be encouraged in the guideline. The US naming convention avoids many of these naming conflicts, but it does not prevent readers from being linked to the wrong article. Vegaswikian 19:04, 17 August 2007 (UTC)

Agreed. I would support any wording that clarified the primacy of primary use in determining which if any of several different uses of a given name should be at the name. Note that this issue is not specific to settlements. --Serge 19:29, 17 August 2007 (UTC)
Serge's point that this issue is in no way limited to settlements is a valid one. At least from my point of view, the reason why I proposed including a link to WP:DAB#Primary topic is because determining the primary use for any given topic is a subject that goes beyond the scope of this specific naming convention. ɑʀкʏɑɴ 20:27, 17 August 2007 (UTC)

Neighborhood/Community distinction?

Sorry if I missed it, but there seems to be an assumption by some that neighborhoods and communities can be clearly distinguished and treated differently. How so? I mean, is La Jolla, a community/neighborhood of San Diego, a neighborhood, or a community? And what about La Jolla Shores, which is a community/neighborhood of La Jolla? I think the distinction is artificial at best. Once again I have to ask: why not use the same tried and true rules for naming neighborhoods and communities that are used to name every other article in Wikipedia? If there are no dab issues, just use the name. If there are, then dab with parenthesis, depending on the situation. --Serge 21:34, 20 August 2007 (UTC)

As you know, not everyone shares your conviction that "Placename, Statename" is a case of disambiguation. So please don't act as if it's generally agreed that it is. AJD 21:55, 20 August 2007 (UTC)
Sorry, but even among the comma convention supporters, most seem to realize that "Placename, Statename" is disambiguation and they openly support this "predisambiguation" for a variety of reasons. Scott Davis is perhaps the most eloquent among them. That there is some minority that stubbornly insists that it is not disambiguation is hardly relevant. Besides, whether Chicago, Illinois, for example, is an alternative name for Chicago is moot - since clearly the most common name used to refer to that city is simply Chicago. --Serge 00:25, 21 August 2007 (UTC)
I don't know how you can say that "most" agree that "city, state" is pre-disambiguation. I don't think you should be accusing other editors of stubbornness either. ·:· Will Beback ·:· 00:42, 21 August 2007 (UTC)
Ok, let me explain this again. For the sake of understanding, we are using the term "neighborhood" to describe the parts of a city that have a special identity (examples: Upper West Side in New York City, West End in London, Universal City in Los Angeles, Dilworth in Charlotte, Financial District in Boston). There is no doubt these places are a part of the city they are found within. Neighborhoods are usually merged into the city articles, but sometimes there is so much info that seperate articles are created. This is different from communities (a word that has many definitions, but for sake of argument is defined as places seperate or partially seperate from another municipality), which are seperate other places entirely. A community can be any spot on the map that is seperate from any other, meaning they can be unincorporated areas, CDPs, boroughs, villages, towns, cities, consolidated-city counties, whatever it may be (examples: Cullowhee, Welcome, Winston-Salem, North Carolina, or even Chicago, Illinois). Since there is a clear distintion between the two, a seperate convention is needed for neighborhoods. Communities are NOT being argued in the lower sections of this talk page with "neigborhood" in the name. The convention for those currently is "City, State" in the US. Hopefully this clears it up for everyone. --Triadian 01:21, 21 August 2007 (UTC)

New proposal

Based on recent discussion, I would propose that the line beginning Cities that have deviated ... in the United States subsection of WP:NC:CITY be replaced by the following:

  • A city listed in the AP Stylebook as not requiring the state modifier (provide a list or link to a list) and is otherwise the primary meaning of its name according to WP:DAB#Primary topic is not required to follow the comma convention and may be titled simply [[City]].

I believe this comes fairly close to addressing the concerns brought up, at the very least for cities in the US. ɑʀкʏɑɴ 21:32, 14 August 2007 (UTC)

I would support that, but would also urge consideration of slightly stronger wording. What many of the comma-convention proponents seem to want to avoid is ambiguity. As such, I suspect they would favor wording that was more clear about whether a given city should be at CityName or Cityname, Statename. Here is wording that addresses that (just changing "may" to "should"):
  • A city listed in the AP Stylebook as not requiring the state modifier (provide a list or link to a list) and is otherwise the primary meaning of its name according to WP:DAB#Primary topic is not required to follow the comma convention and should be titled simply [[City]].
--Serge 21:38, 14 August 2007 (UTC)

Hmm.. I like the use of "may" myself as "should" makes it seem like it is a requirement and not a guideline. I also like the idea of providing examples. How about:

Cities listed in the AP Stylebook as not requiring the state modifier (see this list) may be listed at [[City]] if they are the primary topic for that name (for example Chicago, not Chicago, Illinois, but Phoenix, Arizona not Phoenix).

Just an idea. --Bobblehead (rants) 21:58, 14 August 2007 (UTC)

Again, I'm simply trying to address the concern expressed by others for cut and dried guidelines as opposed to ambivalent ones. Also, FYI, there is plenty of precedent for using "should" in guidelines. This, for example, is from the current U.S. city guideline:
A United States city's article, however, should never be titled simply "city, country" (e.g "Detroit, United States").
Anyway, I would support either the "may" or "should" version. --Serge 22:22, 14 August 2007 (UTC)
I'm okay with this wording, as well. I thought of putting in an example but just wasn't sure if it would cause clutter or not. :) ɑʀкʏɑɴ 22:35, 14 August 2007 (UTC)
I could accept this "should" if it were made clear that cities not listed in the AP Stylebook "should not" be listed without the state name, and that the responsibility for verifying (current) links is that of the person moving it to the unqualified name. — Arthur Rubin | (talk) 22:53, 14 August 2007 (UTC)

Invocation of the AP stylebook seems to reinforce the idea that the English-language Wikipedia is a US-centric project. --Orange Mike 23:40, 14 August 2007 (UTC) (son of a US newsman and a US journalist himself)

Hmmm. Good point, although AP is somewhat international. Does The Times have a stylebook mentioning US cities? — Arthur Rubin | (talk) 23:50, 14 August 2007 (UTC)
There's also the point that this proposal deals only with the naming conventions for US cities and really has no bearing on other worldwide cities. I'm not sure we're going to find a better baseline to use for US cities than the AP list, but if another can be found I'm more than happy to consider it. ɑʀкʏɑɴ 00:21, 15 August 2007 (UTC)
But we Yanks are by no means the only ones interested in US cities; our viewpoint should not rule. I don't think that argument is very strong.
Fair enough. But is using a US-based publication as a baseline source overly US-centric? I guess that's the question at hand. If people feel like doing so puts too much of a US bent on the guideline then we'll reject the proposal. I really would like to see some kind of resolution here, though, so if the AP guideline is unacceptable I really hope someone can find something better. ɑʀкʏɑɴ 00:35, 15 August 2007 (UTC)
Sorry for being the broken record, but if I keep repeating it maybe it will finally sink in. The best baseline to use for US cities is to eliminate this entire project page and simply use the same generic naming conventions for all cities and settlements in the world that are used for all articles in Wikipedia. Second best would be to limit this project page to specify what to do only when dabbing is required (for U.S. cities it would simply say, "When disambiguating is reuired, use Cityname, Statename). Simple. Clean. What's the problem? --Serge 00:40, 15 August 2007 (UTC)
Plenty of reasons that have been brought up before. That proposal is not going to get consensus, so bringing it up is a waste of time. I'm telling you this as someone with mostly the same goals as you have in regards to this page. Λυδαcιτγ 01:13, 15 August 2007 (UTC)
I'd support Arkyan's proposal if it would stop the broken record of proposals to change the naming convention. ·:· Will Beback ·:· 00:46, 15 August 2007 (UTC)
I will stop proposing to change the naming convention if Arkyan's proposal passes (either the "may" or "should" versions, either list). I will not stop if Arthur's caveat (cities not on the list cannot be at Cityname) is included, for I will continue proposing that that caveat be removed for the rest of my life, and will recruit as many other as I can to do the same. --Serge 01:00, 15 August 2007 (UTC)
  • I will support the proposal with or without Arthur's caveat, and I will live with and support the resulting guideline. This guideline should cover all settlement articles, so I think Arthur's caveat is going to have to be included unless we wish to go further towards not predisambiguating. Λυδαcιτγ 01:19, 15 August 2007 (UTC)
  • Why would anyone not want to go further towards not predisambiguating? Seriously, what's the downside (the upside is consistency within Wikipedia, peace and tranquility, etc.). --Serge 01:43, 15 August 2007 (UTC)
  • Downsides include:
    1. as I noticed in Milwaukee, an increase in links pointing to the wrong article
    2. arguments about which city should have the predominant position (my take is that if there is any argument, none should have the predominant position)
    3. move wars,
    4. an increase in the number of moves, as new cities are created, creating new ambiguities
  • If the linking manual of style would suggest that cities be given a fully disambiguated name with a pipe closure in the first reference in an article, such as [[Chicago, Illinois|]], even if the editor believes the city is unique, the first point would be somewhat moot. But I think Serge would oppose that, as well. — Arthur Rubin | (talk) 01:53, 15 August 2007 (UTC)
  • None of these "downsides" are unique to city articles. --Serge 04:06, 15 August 2007 (UTC)
I think we might finally be getting somewhere! I prefer "may" to "should", and consider the AP Styleguide to be a reasonable source of significant US cities, which is what is being discussed. I have no problem with the "Arthur caveat" either. --Scott Davis Talk 05:28, 15 August 2007 (UTC)
I consider Serge's question of "what's the downside" to be disingenuous, and note that while he is right that Arthur's abbreviated list of downsides is not unique to settlements, that does not reduce their validity as downsides. The first two in particular tend to be more significant for settlements than for many other sorts of articles. --Scott Davis Talk 05:28, 15 August 2007 (UTC)
The first two are no more significant for settlements than they are for people. Yet there is no drive to always predab people (with the exception of royalty where the most common name is often unclear, certainly not as clear as Firstname Lastname for most other people), because there is no need for it. For example, the author of Hotel is currently at Arthur Hailey, but if someone else with that name becomes famous, then the appropriate moves and link updates will be done. It's not that big a deal, for crying out loud. Speaking of Hotel (novel), books by default are at [[Book Title]]. But when there is a conflict, they are dabbed. Yet there is no drive to predab all novels at [[Book Title (novel)]]. Why? Because there is no need. Just as there is no need to predab the 22% of U.S. cities that don't require disambiguation. --Serge 05:41, 15 August 2007 (UTC)
You accept that 78% of U.S. cities require disambiguation. Anywhere on this wiki, 78% would be taken as consensus for an action. So, if that large a number of articles required disambiguation then consensus from actual use would say disambiguate them all. Vegaswikian 05:49, 15 August 2007 (UTC)
Are you serious? You are conflating the significance of a given percentage of articles within a given class of articles that require dabbing with the significance of a given percentage of editors sharing an opinion that is sufficient to establish a consensus. This is typical nonsensical "reasoning" used to defend the comma predab convention. I mean, come one. The current consensus is to dab far less than 1% (only 3 cities). One percentage has nothing to do with the other, certainly not in terms of establishing consensus. The current proposal is to move a small number, still probably not even 1%, from Cityname, Statename to Cityname. Yet if that's done, it will be done by consensus. Conflating these percentages is ridiculous. I hope you're joking, except it is not funny. --Serge 06:50, 15 August 2007 (UTC)

There is a clear consensus that some standard be established to allow major world city articles not to predisambiguate. The AP Stylebook has been criticized for being US-centric; however, no better guide has been proposed. I have thus implemented this proposal by replacing "Cities that have deviated from canonical form include New York City, Chicago, and Philadelphia." with the following:

A city in the following list (of cities not required by the AP Stylebook to be suffixed by a state modifier) is not required to follow the comma convention and, when otherwise the primary meaning of its name according to Wikipedia:Disambiguation#Primary topic, may be titled simply [[City]]. The cities are: Atlanta, Baltimore, Boston, Chicago, Cincinnati, Cleveland, Dallas, Denver, Detroit, Honolulu, Houston, Indianapolis, Las Vegas, Los Angeles, Miami, Milwaukee, Minneapolis, New Orleans, New York City, Oklahoma City, Philadelphia, Phoenix, Pittsburgh, St. Louis, Salt Lake City, San Antonio, San Diego, San Francisco, Seattle, Washington.

I also removed the link to this discussion page, as further changes will probably be minor. I used "may" instead of "should" because the first is a lesser change. Perhaps we should wait to see how the change is received by the editors of the various city articles before considering mandating a change to city alone. Λυδαcιτγ 05:27, 17 August 2007 (UTC)

We should probably do a massive move request for the 27 articles with "City" as a redirect. Just so no one gets accused of making a controversial move without discussion. --Bobblehead (rants) 06:14, 17 August 2007 (UTC)
Note that I've gone ahead and removed the example from the guideline. It really serves little purpose if we're already removing cities from the list that do not qualify due to ambiguity issues. ɑʀкʏɑɴ 15:44, 17 August 2007 (UTC)
I also agree that a move request would be prudent. Unilaterally moving these articles could prove contentious. ɑʀкʏɑɴ 15:46, 17 August 2007 (UTC)
If we go this way, should the guideline be written to encourage that all US cites be linked as [[city, state]], even if they are on the list, to avoid surprises for readers? Vegaswikian 18:44, 17 August 2007 (UTC)
I think the logic behind the change was that readers will know the cities without being told the state names, and perhaps be surprised to see the state names included as part of the link. Λυδαcιτγ 00:37, 18 August 2007 (UTC)

Arthur added "No other city should be listed at City."[1]. I don't think there was consensus for that. But if there was, then by the same loose standard there was also consensus to say should instead of may here:

Cities listed in the AP Stylebook as not requiring the state modifier may be listed ...

--Serge 22:25, 17 August 2007 (UTC)

That would change the nature of the guideline. If we want to re-open the proposal to review that variation then I'd suggest we'd need a survey to decide what consensus there is for it. I think we should see how the revision works before weakening it. ·:· Will Beback ·:· 22:34, 17 August 2007 (UTC)
What would change the nature of and/or weaken the guideline? Removing the "No other city should be listed..." line that Arthur just added[2], for which there is no clear consensus, or changing the "may" to "should" for which the clarity for consensus is just as unclear? Both were suggested earlier and there seem to be some agreement with both, though some disagreement (at least from me) regarding the first. --Serge 22:59, 17 August 2007 (UTC)
If it's not clear what the consensus included then we should go back to where we started and hold a survey to clarify it. However since there were subtantial compromises involved the end consensus may not be what we have now. I don't see anyone else complaining, so I think that indicates there's a practical consensus for the currect version. ·:· Will Beback ·:· 00:14, 18 August 2007 (UTC)
Let's do the move request and see whether the moves are all successful. If so, should will be appropriate; otherwise may should remain.
Arthur's change is just a clarification. Without it, the sentence "The canonical form for cities in the United States is City, State (the "comma convention")" and the presence of one defined exemption imply that No other city should be listed at City anyway. Λυδαcιτγ 00:33, 18 August 2007 (UTC)

Prep work for the move request

I put this together for when we're ready to create the move request per the above discussions. This assumes the actual request will be posted on this page under the heading of "Move request".

--Serge 00:02, 18 August 2007 (UTC)

The moves should be decided on city by city, on the city talk pages. ·:· Will Beback ·:· 00:09, 18 August 2007 (UTC)
Actually, if there is formal consensus here and the guideline is changed, then these would be listed as uncontested at WP:RM and they can be moved. If someone wants to contest them they can do so by moving to contested or starting a discussion on the article talk page after moving from uncontested to a full move discussion. Vegaswikian 00:17, 18 August 2007 (UTC)
I'm with Vegaswikian, Bobblehead, Arkyan, etc. What you're suggesting, Will, sounds like a big mess. --Serge 00:19, 18 August 2007 (UTC)
Well, at the very least of the proposed moves should be posted to each city talk page. Naming convenions are just guidelines, as Serge has reminded us so often. ·:· Will Beback ·:· 00:34, 18 August 2007 (UTC)
Absolutely. There is a template for that. I'll help putting them out there. --Serge 02:43, 18 August 2007 (UTC)

No, these should not be uncontested. To say nothing of the regular editors of the articles, who should not be surprised, this discussion is less than a dozen people. There were forty in the last big poll, some of them vehemently opposed to "disambiguate most". If there's consensus for it now, fine; but we have to demonstrate that. Septentrionalis PMAnderson 23:16, 18 August 2007 (UTC)

The proposed moves above will be listed at Wikipedia talk:Naming conventions#Requested moves. A notice directing editors to that centralized discussion will be placed on the talk pages of each of the articles, as well as at Wikipedia:Requested_moves#Other_proposals. Sound OK? Λυδαcιτγ 04:21, 19 August 2007 (UTC)

May I remind everyone there is already some consensus on forming a guideline to go along with these moves. We should not return to discussing the move of these articles without the guideline to go along with it. It already failed many, many times and I am willing to bet it will fail again. Okiefromokla•talk 20:03, 1 September 2007 (UTC)

Neighborhoods in the US

Is there a specific convention in place for these? I did not see it in the guideline. Vegaswikian 23:22, 15 August 2007 (UTC)

I don't think we have a convention in the project page, nor is it clear what consensus is. Neighborhood, City, State and Neighborhood (City, State) seem to predominate with occasional Neighborhood (State) and Neighborhood (City) (if City really does redirect to City, State). There seems to be a mild consensus that Neighborhood, State is unacceptable. — Arthur Rubin | (talk) 23:28, 15 August 2007 (UTC)
Not to mention those of us who believe [[Neighborhood]] is mandated by Wikipedia conventions when there are no known conflicts. --Serge 23:30, 15 August 2007 (UTC)
I wasn't going to mention that because it's clearly not mandated, although some believe it in good faith. — Arthur Rubin | (talk) 23:46, 15 August 2007 (UTC)
So current usage would support Neighborhood, City, State or Neighborhood (City, State) with no identified preference. Vegaswikian 23:59, 15 August 2007 (UTC)
I believe so. It may depend on the state, or whether the neighborhood is a census-recognized community. I don't have a bot to gather the information, though, so I could be wrong. — Arthur Rubin | (talk) 00:04, 16 August 2007 (UTC)
A random sampling through Category:Neighborhoods_in_the_United_States seems to indicate that Neighborhood, City, State is almost the exclusive location for neighborhoods. --Bobblehead (rants) 00:11, 16 August 2007 (UTC)
{edit conflict} And another issue. What happens if this is not in a city? Or if only a portion is in a city? Summerlin, Nevada based on this discussion appears to need moving. Part is in the City of Las Vegas and another part is in a CDP. Is this one of those cases with the common name of Summerlin should be used for clarity (I can see Serge shaking his head). Vegaswikian 00:13, 16 August 2007 (UTC)
Are neighborhoods used by the postal service? How does mail to someone who lives in Summerlin get addressed? In my mind, neighborhoods in the US roughly correspond to suburbs in Australia. Articles about them are named suburbname, state, the same way mail is addressed (but mail uses two lines instead of a comma). The principle of least surprise would suggest using a similar form to postal addressing, if possible. --Scott Davis Talk 11:41, 16 August 2007 (UTC)
In the U.S., as far as I know, a neighborhood that is a subdivision of an incorporated city never has a separate postal place name. In other words, such neighborhoods are not commonly known as "neighborhood, state". --Polaron | Talk 14:30, 16 August 2007 (UTC)
  • Never? Not true. See 92037, 92038 which is La Jolla, a neighborhood of San Diego. The USPS won't even deliver mail to PO Boxes in 92038 that are addressed San Diego, CA instead of La Jolla, CA. --Serge 19:46, 16 August 2007 (UTC)
It's not even common to use neighborhoods for mail for unincorporated areas. From what I've seen, neighborhoods in unincorporated areas just use the name of the nearest city. By and large, the common name for neighborhoods is just the name of the neighborhood and using the comma convention would be a neologism. The only exception to this is when the US Census sets up a CDP, like Skokomish, Washington.--Bobblehead (rants) 14:52, 16 August 2007 (UTC)
"A neighborhood that is a subdivision of an incorporated city never has a separate postal place name"?? My impression was that this actually happens very often. Consider: Long Island City NY 11101; Jamaica NY 11405; Allston MA 02134; Hyde Park MA 02136; Prides Crossing MA 01965; Hyannis MA 02601. These are all neighborhoods within incorporated cities where the preferred postal name is the neighborhood name, not the city name. AJD 16:38, 16 August 2007 (UTC)
Yeah, I was proven wrong just minutes after I made the comment when someone proposed merging Mead, Washington into a neighborhood article I monitor. Go me. ;)--Bobblehead (rants) 16:51, 16 August 2007 (UTC)
Not withstanding former towns/villages that were added into larger municipalities :) My point is these situations are more the exception rather than the rule. I'm sure I can find at least one counter example for every example of such a situation. --Polaron | Talk 16:58, 16 August 2007 (UTC)
Mail is routed through the Summerlin post office which use Las Vegas as the location but the zip codes cover the Summerlin area. Many of the delivery routes are rural routes which I believe means that they are contracted out. Spring Valley is an unincorporated town that gets service from the Rainbow postal facility which also uses Las Vegas as the location. This supports the point someone else made about the postal service using the name of the nearby city. In Clark County, Nevada the assessor tax role shows you the community (neighborhood} name. Vegaswikian 17:50, 16 August 2007 (UTC)

(outdent)Well, even if we acknowledge that some neighborhoods are known as "Neighborhood, State", I think it is safe to say that no neighborhood is commonly referred to as "Neighborhood, City, State". Perhaps we could make it really complicated and go with the USPS convention. If the neighborhood returns as an acceptable option here [3], then "Neighborhood, State" is okay, but if you get nothing or "[Neighborhood] is not acceptable, use [City]" then "Neighborhood (City, State)" or "Neighborhood (City)" is the article name?--Bobblehead (rants) 17:20, 16 August 2007 (UTC)

If anyone wants to see how confusing this can be, look at Sun City a dab page. This is a mix of cities and communities. I believe that most are dabbed as if they are US cities, and I have no idea why Frisco Lakes and Hill Country Retreat are listed. Vegaswikian 19:46, 16 August 2007 (UTC)
I have a feeling you meant Sun City :) ɑʀкʏɑɴ 19:51, 16 August 2007 (UTC)
Bobblehead's suggestion is probably a good way to go about this issue. That at least gets rid of the double-comma convention :) --Polaron | Talk 19:59, 16 August 2007 (UTC)
Sounds fine to me so long as it is understood this only applies to neighborhoods within an incorporated city - there are a number of unincorporated towns that return "unacceptable" on the USPS site as mail is routed through a post office in a nearby town. ɑʀкʏɑɴ 20:22, 16 August 2007 (UTC)
And there are parts of the US where every municipality is incorporated. Last I followed these matters, the post office preferred municipalities as post office names, but used their own boundaries for them. Septentrionalis PMAnderson 20:50, 16 August 2007 (UTC)
As far as I know, the term "municipality" is synonymous with "incorporated city/town". I was more referring to cases where one rural town might have its mail routed through a neighboring rural town, but remains a seperate town and not a neighborhood. ɑʀкʏɑɴ 21:12, 16 August 2007 (UTC)
Then make that "Every square foot of land belongs to an incorporated town."Septentrionalis PMAnderson 21:20, 16 August 2007 (UTC)
Ahh, like in New England! That's quite true then. I suppose in cases like that it becomes nigh impossible to lay out the guideline and have to leave it up to the discretion of the editors involved to determine whether the place they're writing about is to be considered a neighborhood of the incorporated town or otherwise .. ɑʀкʏɑɴ 21:26, 16 August 2007 (UTC)
The guidelines really vary by state. Maybe the simple answer is if the state has defined the type of community, be it township, village, incorporated, unincorporated or it is a CDP the article gets named as a city. Don't know how this would affect a military base. I think most of them are CDPs and may even have a unique post office address.

Ok, I think we've gone off on a tangent here. I believe the intent of this discussion was for neighborhoods of cities, not for communities incorporated or unincorporated or CDPs... all of those I believe use the Postal comma disambig if needed at all. Now, given, if there's no need to disambiguate, I don't think we should. But when we need to, it seems we have four main ways to disambig across the United States. The most popular is the double comma method (i.e. "Neighborhood, City, State" ). This can lead to long titles, but it pinpoints the location of the neighborhood in the title, heavily disgtinguishes from another neighborhood of the same name, and the Pipe Trick works with it. The second most popular method seems to be the city state in parentheses method (i.e. "Neighborhood (City, State)" ) where the city and state are in parentheses, seperated by a comma. This is basically the same as the last method, only using parentheses instead of another comma. Another method is just having the city name in parentheses, which I'll call the city in parentheses method (i.e. "Neighborhood (City)" ). This uses less disambiguation, but honestly, what are the odds of two neighborhoods of the same name found in two cities (of any consequence to even have neighborhood articles) of the same name to prevent this method from working? It's shorter and easier to type, but is not as widely used right now. The fourth method just disambiguates by what the type of place: the the word neighborhood in parentheses method (i.e. "Westside (neighborhood)" ). If there's ever a conflict with two neighborhoods of the same name, the city name is added in the parentheses with no comma: (i.e. "Westside (Boston neighborhood)" ). The pipe trick works for them all. These seem to be our choices. Shall we work on a concensus here for uniformity and organization sake? --Triadian 06:33, 17 August 2007 (UTC)

The problem is phrasing. We are using city in the Californian sense of "incorporated municipality"; therefore, if we say "neighborhood in a city" we include neighborhoods within small rural towns in Connecticut or townships in New Jersey. I don't think this is what Triadan means; I presume he is thinking of large cities like New York and Newark, New Jersey, both of which have West Sides, differently disambiguated. Septentrionalis PMAnderson 14:27, 17 August 2007 (UTC)
In such states, we in fact use "Neighborhood, State", like Lincroft, New Jersey; because Lincroft is a CDP; so this is a fifth possibility. Septentrionalis PMAnderson 14:30, 17 August 2007 (UTC)
Ok, I think phrasing is apparently a problem here. When I say neighborhood, I'm referring to a section of a city (or town if the case may be). If it's outside of a city, or partially outside of a city, then it is in my terms a community (and in North Carolina, an unicorporated community) and thus uses the "Community, State" method (or has in any case in my state). For example, Steele Creek, North Carolina, was partially annexed by the city of Charlotte, so since it is not entirely a "neighborhood" yet, we at WP:CLT decided to treat it as another unincorporated community (or town or city or village or township for that matter). Where I think we need a concensus is with neighborhoods like Elizabeth (neighborhood) and Little Italy, Baltimore and Monta Vista, Cupertino, California and Gateway (neighborhood), Washington, D.C.. --Triadian 19:54, 17 August 2007 (UTC)
Lincroft is a (reasonably well defined) section of suburbia within a largely suburban incorporated municipality. It is called a neighborhood; what else does one call it? (It also happens to be a CDP, which is why we have an article on it). Let's have a proposal on neighborhoods in urban areas. Septentrionalis PMAnderson 16:20, 18 August 2007 (UTC)

Communities are named as cities

I think that the consensus seems to be saying that communities are not to be considered neighborhoods for naming purposes and that they will be named as if they were a city. Communities are loosely defined as areas that have a commonly used name and are not located solely within a city or a CDP. City is defined to include formal definitions for municipalities as defined by each state or a CDP. We may need to refine this definition. Vegaswikian 00:35, 18 August 2007 (UTC)

  • It does need a little refinement anyway - there are some very large CDPs in some states that are geographically capable of containing what the locals may well consider separate, unincorporated towns and not a neighborhood of the containing CDP. I don't have any examples on me, so I may be making a mountain out of a molehill - but that was the reason I stated previously that what is considered a "neighborhood" should probably be wholly contained within an incorporated city to be considered "neighborhood" and not "town". ɑʀкʏɑɴ 00:47, 18 August 2007 (UTC)
I'm in 100% agreement with Vegaswikian on that. As for communities within CDP's... if such a thing exists, they should be rare and if they have their own identity, then the Census Bureau has failed them. Such places should be included in the CDP article unless its big enough for them to declare independence and form their own "Community, State" article. An example of a CDP that may have neighborhoods within could be Arlington, Virginia, with the Pentagon City, Virginia neighborhood. This is an odd case though and should be dealt with as such. --Triadian 01:38, 18 August 2007 (UTC)
This is a bit of a misunderstanding of CDPs -- they are, almost by definition, artificial entities created to present a statistical data summary for an area that would otherwise not have any summary. Most CDPs are individual communities. However, there are quite a lot of exceptions. Some CDPs are an amalgamation of two or more nearby communities. Sometimes a CDP represents the rump or remainder of a community left behind after a portion has either incorporated or been annexed. Sometimes a CDP corresponds to an entire minor civil division (which in the Census Bureau's way of looking at things are not incorporated municipalities, even though the may actually be so according to state law). So, basically, I wouldn't try to formulate a naming convention for communities based around CDPs -- they pretty much need to be handled on a case by case basis.
But that aside, back to the original topic of this section, I'd much prefer to see neighborhoods within cities use a parenthetical disambiguation -- whether that includes the city only or city and state doesn't matter too much to me. Communities that have an identity apart from any larger administrative subdivision can have a place, state name. older ≠ wiser 02:21, 18 August 2007 (UTC)
Ok, that's good, so that would throw out the double comma method, which I'm not too fond of myself. Other thoughts? --Triadian 04:29, 18 August 2007 (UTC)

What are people from other countries going to make of your rather localised method? THEPROMENADER 06:02, 18 August 2007 (UTC)

I expect they might read the article and come to learn something, which is more the actual point of an encyclopedia (as opposed to arguing about naming every article with an artificial consistency). older ≠ wiser 11:20, 18 August 2007 (UTC)
They have to find the article before they read it - the above is problematic in that respect. "Articficial consistency" is a phrase that sounds negative but doesn't really mean a thing. References should be consistant - as a matter of course. THEPROMENADER 14:21, 18 August 2007 (UTC)
I am profoundly unconvinced by any argument that minor variations in the title pose any serious impediment to anyone finding an article. Yes, I intended "artificial consistency" to sound negative. Arguing about hypothetical impediments posed by what some perceive to be inconsistencies in the names of articles does not, in my opinion, contribute significantly to improving the quality of the encyclopedia. Variations in article titles can and should be covered by redirects to assist people with finding articles. older ≠ wiser 17:46, 18 August 2007 (UTC)
But there is nothing negative about consistency. Although the term "artificial consistency" paints consistency in a negative light, it neglects to clearly define what that negative aspect is... "artificial"? "Natural" is only natural to those already used to the method - yourselves. Adding redirects is an unneccessary step that would not be needed were the article title clear. What many of you are doing here is imposing the comfort of your own local linguistic habits as a standard for the places you yourselves live in, but this is both narrow-minded and backwards. The fact that you need to "correct" your method's deviation from the rest of the wikipedia standard (parenthesis) through extra "corrections", and trying to justify the same through "interpretations" of normally non-sequitur Wiki policies, does not denote a line of reasoning with Wikipedia in mind - you are placing the method first, Wikipedia second. THEPROMENADER 18:14, 18 August 2007 (UTC)
But having articles at titles that are not common names, simply for the sake of some simplistic desire for consistency is bad. Redirects are not an unnecessary step, but rather are precisely how such matters should be handled. What you might see as a "clear" article title, might be confusing to others. Despite your repeated and false proclamations to the contrary, there is nothing whatsoever deviant about the comma convention nor is the parentheses the only accepted standard method of disambiguation. I'm not sure what the rest of your point was -- I don't see any such thing as what you describe. What I see is people (the ones who contribute to and edit Wikipedia articles) using conventions familiar to them as appropriate for the article subject. That is Wikipedia first -- not arguing about the perceived lack of an consistency in names. older ≠ wiser 18:27, 18 August 2007 (UTC)
You see, this is exactly what I mean. (This interpretation of) "Common name" (little to do with the "city, state" common method that we speak of here) is only "common" to the person either from that area or familiar with that jargon. Wikipedians contributing using conventions familiar to themselves is not what one can call putting the reader first. THEPROMENADER 19:30, 18 August 2007 (UTC)
And please do tell what "others" would find "confusing" about City (Country, stateifneeded). THEPROMENADER 22:23, 18 August 2007 (UTC)
First, why do you distinguish between reader and editor? On Wikipedia, anyone can be either. Second, if a reader who is unfamiliar with a local convention happens to learn something about the local convention, is that such a bad thing? I'm serious -- a huge part of what makes Wikipedia so popular is the element of discovery. I'm constantly surprised by the extraordinary variety of knowledge available here. older ≠ wiser 20:56, 18 August 2007 (UTC)
Was that a serious question? Contributors write for readers - not for themselves - and one writing an article knows exactly where it is. Is Wikipedia not a reference - for readers?
So you want to "educate" those visitors to your local customs? What you're doing rather is obliging readers to adopt them as a tool for finding/understanding Wikipida placename articles - but not all of them - after of course they go through the extra steps (combing search results for (cityname) because they don't know/didn't use "state"; reading disambig pages) to find what they are looking for.
Little, if not nothing, in your replies really answered any of my points; substanceless expressions of doubt and misgivings can in no way disqualify these. Also, searching for "positive" reasons to justify an already-chosen method (whose existence has more to do with comfort than utility) is not an answer to the same! THEPROMENADER 22:23, 18 August 2007 (UTC)
I seem to recall Promenader also declaring that his chosen method would be "educational". I agree, as it happens, that we should not surprise our readers to educate them; but that's why we should use Lincroft, New Jersey: the local dialect of English does (and when we must choose between dialects, we do and should choose the local one). Septentrionalis PMAnderson 23:21, 18 August 2007 (UTC)
More misinterpretation of "common name", and I never meant "educational" in the sense of anything in the exchange above - "clear", "complete", "recognisable" and "findable" are all I'm aiming for with the the method that so far passes the most tests. A bit of objectivity, please. THEPROMENADER 23:35, 18 August 2007 (UTC)
To ThePromenader, yes that was a serious question. What hypothetical readers do you write for? Of course contributors should write for readers. Your proposition would in effect force everyone to use an artificial unconventional convention. To me, that is counter-productive in the extreme. Your hypothetical reader that is unable to find an article is nothing more than a chimera of your rhetoric. The reason nothing in my replies answer any of your points is that in my opinion you have no valid points. older ≠ wiser 01:40, 19 August 2007 (UTC)
International readers - those unfamiliar with the provinces/states/regions of other countries. Again, the only readers who would find a low-level-geography-with-comma disambiguation "conventional" are those already familiar with the local geography of the country they are searching in, and using a local manner of speech for an article naming method asks that the reader also be familiar with the same - there is nothing at all "invalid" in this very simple point. It is in fact the contributors imposing this "local method" they are most comfortable with who are "forcing" others unfamiliar with it to learn and adapt to it. If I (living in France) were to look for the U.S. Lake Placid without knowing what state it is in, my keywords would not be "city" and "state": in what way is this point "hypothetical" or "invalid"? THEPROMENADER 07:23, 19 August 2007 (UTC)
Yes, and the supposed impediment to finding articles that you see is precisely the function of redirects. There should be no necessity for a reader to know local conventions to be able find an article and to my knowledge, there has not been any credible evidence that there is any actual impediment. Why should we force everyone to use an unconventional convention? Well, if your hypothetically clueless reader looking for "Lake Placid" happened to type exactly that into the search box and clicks Go -- they would get to a disambiguation page. If they are so clueless as to be unable to parse a disambiguation page -- then I don't think any naming schema alone would be sufficient to help them find their way. older ≠ wiser 11:50, 19 August 2007 (UTC)

There is nothing hypothetical in anything I wrote. Especially where reference works are concerned, one cannot assume a reader's foreknowledge of the subject he is looking for (which in itself is an idea that is a contradiction in itself) - that, if anything, is hypothetical. Assuming that the same reader will use "go" instead of searching adds yet another variable and a layer of hypothesis and ignores even the option (and argument thereof above) that one will use the search function. Again, "city, state" is only conventional to those who know what/where "state" is and already accustomed to that method.

I can't see how one can imagine that I am "imposing" anything on anyone - the guidelines are there for contributors, and these change only through reason (in most cases) and consensus. If I read the history of the "city, state" convention correctly, it would seem that it was a decision made by a narrow consensus of only a few and applied to thousands of articles through the help of a bot - this is "imposing" if anything. Reading (settlement) convention page, I can't but note the vehemence in the line "A United States city's article, however, should never be titled simply "city, country"": if this practice were not an already often used method for this publication, there would be no need to adopt this sort of tone.

What you have done here is create a convention comfortable for contributors themselves - yourselves - not readers. You have taken your own way of talking familiar to those familiar to you and imposed it here, in spite of the fact that this goes against every Wikipedia policy concerning article names and disambiguation created before it (nary a mention of "comma" in the WP:NAME policy page - parenthesis only). We are not talking about a method of disambiguation that is different from anything existing - we are talking about one that has been in use locally in the U.S. since decades already, and this fact speaks loads for itself - and this fact, in fact, is the method's only solid defence in argument. Unfortunately, that same line of reasoning shows a disregard for readers from other English-speaking countries; you don't have to think about these readers, but denying that it is even possible to do so, or refusing to even consider the question, is quite another matter.

What exactly is wrong with the parenthetical disambiguation in use for the rest of Wikipedia? What is there not to understand in "City (Country, stateifneeded)"? None are even willing to consider a practice that would not only make a placename instantly identifiable for all, but would be a method already in use for all other Wiki subjects? On that note: Wikipedia was more consistent before the "city, state" method was introduced here. THEPROMENADER 13:07, 19 August 2007 (UTC)

Honestly, just about everything that I've seen you write here has been purely hypothetical. Further, at this point I'm unable to follow your convoluted reasoning to even understand what points you might be trying to make. From what I can tell, your proposition will exchange a completely artificial convention that is common to no one for a convention that corresponds (to a large degree at least) to actual usage. I do not see any benefit whatsoever. older ≠ wiser 14:18, 19 August 2007 (UTC)
I'm not sure what you are referring to with regards to "Wikipedia was more consistent before the "city, state" method was introduced here." Either you are being disingenuous or you are simply uninformed -- the comma convention has been in use in Wikipedia since the earliest days. It may not have been articulated as a formally stated convention, but there is abundant evidence that articles were named city, state from very early on. older ≠ wiser 14:35, 19 August 2007 (UTC)
Convoluted? Not understanding would be convenient in this sort of situation, I suppose, but if you're confused, just read each sentence individually; each is a point in itself. Searchability, international recognition, consistency - these are not opinions or bias (as you would seem to suggest): they are points indispensable for any serious online reference. THEPROMENADER 15:22, 19 August 2007 (UTC)
You seem to be laboring under the illusion that the comma convention actually poses a significant problem for users finding articles -- I disagree and have yet to see anything other than the hypothetical chimeras of your rhetoric as evidence to the contrary. Lacking an actual problem, your solution is impractical and fundamentally misguided. older ≠ wiser 15:30, 19 August 2007 (UTC)
Your declaring something to be something does not make it so. Especially when you refuse categorically to even consider that something. Searchability, recognition (locale) and consistency are anything but "hypothetical chimeras" as far as references are concerned, so hold the defamatory adjectives please. You have yet to show how City (Country, stateifneeded) would be "confusing" or "misguided". THEPROMENADER 15:45, 19 August 2007 (UTC)
By the very same token, your declaring that that something is something does not make it so. Your repeated declarations regarding searchability, recognition, and consistency, without presenting any evidence other than your hypothetical chimeras does not mean that your declarations are valid. You have yet to show how a massive change to naming conventions would produce any tangible benefits. older ≠ wiser 15:54, 19 August 2007 (UTC)
To try to turn my critique of your (lack of) argument back on my own is a rather non sequitur thing to do - the fact that "city, state" exists as a local custom is the very reason for its existence here needs no 'declaration' for it to be true - it is a simple fact that speaks for itself. Since you declare them to be "hypothetical chimeras" (and that repeated only seemingly intelligent but baseless name-calling is getting quite annoying, by the way), you would say that searchability, topic recognition and consistency are not useful to a reference? THEPROMENADER 16:04, 19 August 2007 (UTC)
While it might seem to you that your statements are self-evident, I assure you that that is not in fact the case. My understanding of your argument, such as it is, is that you are fundamentally mistaken. older ≠ wiser 16:44, 19 August 2007 (UTC)
LOL - you repeatedly insist that I am "mistaken", but to date have never been able to begin to suggest how. In what way are consistency, indentifiability and searchability bad things, and how is "City (Country, Stateifneeded)" "confusing"? THEPROMENADER 19:02, 19 August 2007 (UTC)
I have never claimed that consistency, indentifiability and searchability are bad things -- only that you have not clearly shown that your proposition would produce any demonstrable benefits in these regards. older ≠ wiser 19:17, 19 August 2007 (UTC)
Well, those three things are embodied in my proposition, and if even you cannot show that they "bad" things, and I can clearly demostrate how they can be implemented, and for a real and practicable end to boot, then they are a demonstrable improvement over the existing local "me the contributor" system. If you don't want to think outside of your little box, then be pleased that those of your ilk are most militant in present discussion and will most likely always be the majority there. Cheers. THEPROMENADER 21:47, 19 August 2007 (UTC)
Well, see, that's just it -- you have already convinced yourself of the supposed self-evident merits of your proposal. I don't see any merit in substituting your brand new artificially constructed "little box" for the expansive, flexible, and adaptive existing system that at least comes closer to approximating actual usage. I mean, I don't even understand why you are talking about the goodness or badness of "consistency, indentifiability and searchability" -- as far as I'm concerned you have not clearly demonstrated that your proposition is superior to the existing system with regards to these items. older ≠ wiser 21:57, 19 August 2007 (UTC)
You haven't even considered the question. Insofar all you've done is question the credibility of he who is presenting a proposition without even touching on the issue of the presentation itself - vague unfounded negative assertations aside. "Actual usage" - for who, yourself? You've built your own little box, not mine. THEPROMENADER 22:03, 19 August 2007 (UTC)
What makes you so sure that I haven't considered the question and rejected it? Who's actual usage? How about the actual usage in countless English language documents? And yes, I do prefer the expansiveness, flexibility and adaptability of the current system to the artificiality your brand new little box. older ≠ wiser 22:11, 19 August 2007 (UTC)
I've asked the same question several times over, to no answer: In what way are consistency, indentifiability and searchability bad things, and how is "City (Country, Stateifneeded)" "confusing"? A few of you have imposed your own method of comfort on your own little corner of Wikipedia: in defense of this method, please save the disservice of pretending to reason for its service to all, because reason is not at all the reason for its presence here. Cheers. THEPROMENADER 22:32, 19 August 2007 (UTC)

It has been proposed that this argument be moved to User talk:ThePromenader and User talk:Bkonrad, because there is no productive discussion on the topic at hand.
When any useful opinions have been formulated, return to this section for evaluation by other editors. --Triadian 22:17, 19 August 2007 (UTC)

<----Side discussions aside, I think there is a consensus that communities, however defined, are to follow the same naming convention as cities. If this is correct, then this point is clarified. That leaves the naming convention for neighborhoods still under discussion. Vegaswikian 20:35, 19 August 2007 (UTC)

Proposal on Neighborhoods

Again, I think we've gotten off the subject and I think it's time I stated my opinion. I was waiting on others to chime in, but the discussion needs to be directed. Keep in mind the purpose for all of this is to establish a guideline, not a mandatory prison sentence for articles. For neighborhoods (defined as areas within a city with a seperate identity) I propose we use the convention "Neighborhoodname" if no disambiguation is needed. This would make the Plaza-Midwood article stay at its current name, as would Harlem. This is using the 'common name' guideline. If disambigutaion is needed, I propose we use the convention "Neighborhoodname (Cityname)", and only if further dab is needed the convention "Neighborhoodname (Cityname, Statename)", where Statename can be subsituted for Countryname if needed. For areas that have partial identity outside the city's jurisdictional boundaries, those articles should be treated as if they were seperate communities and the details can be discussed in the article proper. As such, articles like that shall use the common "Communityname, StateOrCountryname" convention. I believe this proposal encompasses the gist of what's been argued here and I believe offers a worldwide approach to the situation. Agree? Disagree? Comments? --Triadian 21:24, 19 August 2007 (UTC)

I'm OK with this. I've never liked the three-level comma format ("Neighborhood, City, State"). Unlike "Community, State", such a three-level format is not common. I wouldn't object to leaving some discretion for preemptively naming relatively unnotable neighborhoods in minor cities as "Neighborhood (City)" -- at the least, the guideline could suggest making redirects from the disambiguated forms. older ≠ wiser 21:45, 19 August 2007 (UTC)
I agree with that. If in doubt, dab it anyway. As for redirects, it's almost a given that make them for colloquial terms (if possible) so I'm in agreement with that as well. --Triadian 21:51, 19 August 2007 (UTC)
Agree that state should not be required unless needed to disambiguate. I agree in leaving some discretion rather than imposing an absolute format for all neighborhoods-- where a common name is sufficent with no confusion, that should be prefered to some Wikipedia created construct not in common use. I lean against the parenthesis as probably unnecessary in many cases, especially where there is existing use of the construct "Neighborhood, City" rather than requiring "Neighborhood (City)" --again, what people actually write should be prefered to an artificial form with no significant history outside of Wikipedia. -- Infrogmation 00:56, 20 August 2007 (UTC)
But how common a form is "Neighborhood, City"? It strikes me as being an odd formulation. I mean, it is not like that is even a postal code as it is with Place, State. And it seems to me that in writing, if context was needed, it would be more natural to spell it out along the lines of "Placename" is a neighborhood in the city of "Cityname". Or John Doe lives in the "Placename" area of "Cityname". older ≠ wiser 02:00, 20 August 2007 (UTC)
I find it odd as well. It seems to be a neologism to me, taking a play out of the playbook of "City, State", a method that was based on the postal system. I know of no extraInternet source where "Neighborhood, City" is used. Given, it is a method already in place for some cities, but as are the others. FYI, I've placed some rename suggestion tags on many US city neighborhood talk pages to hopefully get a broader range fo views. --Triadian 02:12, 20 August 2007 (UTC)

I suggest that if we need to change the prevailing "two comma" system [neighborhood, city, state] that we go with [neighborhood, state] except where the placename needs further disambiguation, in which case we could either fall back on [neighborhood, city, state] or use [neighborhood (city, state)]. Using [neighborhood] alone would contradict the city naming convention that we just agreed upon. [Neighborhood, city] is unconventional and may not be adequate. ·:· Will Beback ·:· 02:49, 20 August 2007 (UTC)

The problem with "neighborhood, state" is that it is not a common name unless it is a valid postal location (which is the more the exception rather than the rule). --Polaron | Talk 03:00, 20 August 2007 (UTC)
I would support using "Neighborhood, State" only for the cases where the neighborhood is a CDP or a postal location (like Allston, Massachusetts or Hyannis, Massachusetts), and either "Neighborhood" or "Neighborhood (City)" depending on whether disambiguation is necessary. My main aim here is breaking out of the (as I see it) tyranny of Census-Bureau terminology that was imposed just because the city-and-town data we have was based on Census-Bureau data. There's no reason for Allston and Hyannis to be treated differently just because one's a CDP and the other isn't. AJD 03:11, 20 August 2007 (UTC)
This convention seems to have comma'd itself into a corner here. I remember the "great debate" over La Jolla, San Diego, California and the move from La Jolla, California that finally closed the debate: much of the issue there was maintaining the reasoning that "city, State" was "common English" (although only in that neck of the world), and La Jolla, California would seem to be "common usage" to an even smaller population - those living in or very near the community of La Jolla itself (I am aware that the U.S. post office lists the same community under La Jolla, California, but this in my opinion is just a source selected to justify giving the community the same treatment as a city). I'm not really sure what use Postal bureau methods are here, as Wikepedia has not at all the same use, method, organisation nor function. I think the reasoning behind the final decision to adopt a three-level comma convention for communities (that one in particular, anyhow) was to provide a distinct method showing that the community was, in fact, not a city, but part of one, all in maintaining clarity for the "city" identity of "city, state" articles. THEPROMENADER 13:59, 20 August 2007 (UTC)
But by that token, there's no reason for us to give CDPs privileges that we don't give postal addresses; the Census Bureau's methods don't necessarily match our goals, and they are in some cases actively misleading. Should Hyannis, Massachusetts then be moved to Hyannis, Barnstable, Massachusetts (or something)? Personally, I'm in favor of the maximal expansion of the comma convention: using Placename, State for anyplace that there's strong evidence that that format is regularly used (for instance, by the Postal Service); but I'm not totally committed to that if we can come up with another more-or-less consistent system. I just don't think a system that treats Hyannis and Allston so differently, on the basis of the Census Bureau's arbitrary classifications, is anything like consistent enough. AJD 15:03, 20 August 2007 (UTC)
If the comma method has still consensus here, I'd go for the "full disambiguation" route as well: if it doesn't consider foreign readers, at least it's consistent. I've tried my hand at devising another method: I've found that, for placenames, the "full disambiguation) parenthesis method (Place (Country, stateifneeded) is much clearer, for readers from all countries, across the board (English Wikipedia readers do not only come from the U.S). If you're interested, please find it here. Cheers. THEPROMENADER 16:38, 20 August 2007 (UTC)
The reason I support the comma convention is because I don't believe it is "disambiguation" per se but rather just correct naming. The article Amesbury, Massachusetts is so named not to disambiguate it from any other towns or entities that might be called Amesbury, but merely because "City, State" is the correct standard way to refer to a U.S. city. You may call this a "local convention", but that's just the same as to say that people not from the U.S. don't know the correct way to refer to U.S. locations.
Anyhow, I've gotten sidetracked. My point here isn't to defend the comma convention—it's just to say that we shouldn't treat two neighborhoods differently in terms of article naming just because one happens to be a CDP and the other isn't. CDPs are artificial. AJD 16:55, 20 August 2007 (UTC)
I didn't at all mean that - "City, State" is perfectly adapted to U.S. use, although only through inventive definition can one really call it a "name", and even then, only there. The thing is, Wikipedia readers are not all familiar with U.S. customs and geography, so I don't think the method very adapted to here. My own country of origin uses the comma disambiguation method, and I still think the same. THEPROMENADER 17:24, 20 August 2007 (UTC)
Agreed; USPS designations, however, tend to influence usage, because Americans do in fact know their own address. Septentrionalis PMAnderson 17:11, 20 August 2007 (UTC)
Indeed. It is worth noting, however, that Wikipedia largely ignores USPS designations. My parents for instance, live, according to the USPS, in Kensington, Maryland. According to Wikipedia (and the Census Bureau), however, they live in North Bethesda, Maryland, while Kensington, Maryland merely refers to the incorporated town, not the much larger postal area. Just because wikipedia city articles look like USPS designations does not mean they are the same as them. john k 13:45, 21 August 2007 (UTC)
Regardless, I believe the city name in which the neighborhood is found must be included in the title. Otherwise, we are defeating the entire purpose of creating these articles, which are essentially offshoots of the city article. If this is done with "Neighborhoodname (Cityname)", "Neighborhoodname (Cityname, Statename)", "Neighborhoodname, Cityname", "Neighborhoodname, Cityname, Statename" doesn't matter all that much to me. I just prefer parentheses because the comma method can hardly be found anywhere else but Wikipedia as far as neighborhoods go. --Triadian 01:37, 21 August 2007 (UTC)
Ok, I was not aware CDP's could be within entire cities. Most of them that I have seen are seperate areas. If there are these special cases though, I think the area's position as a neighborhood of a municipality trumps its CDP status, as that is only for statistical purposes. As such, it should probably go with the neighborhood disambig style and not community. It really just depends on how the CDP is set up. --Triadian 01:30, 21 August 2007 (UTC)
CDPs are not "within entire cities". I'm not sure what prompted that. The situation in New England states and a few others are a little unusual in that the Census Bureau regards a New England Town as a minor civil division, while by state law they are incorporated municipalities. Some of these towns have dispersed settlement patterns with urbanized areas separated by less populated regions. In such cases these urbanized areas might be treated as CDPs by the Census Bureau (which works with local authorities to define such places so as to produce meaningful statistical data). In some cases, the entire New England Town might be a densely populated urban area. In these cases, the entire town may be treated as a CDP so as to be included in the same listing as incorporated places. In no cases that I am aware of is a CDP defined within a city (or, to be more precise, within what the Census considers as an incorporated place). Of course all of this irks New Englanders to no end and poses challenges for classifying settlements there. older ≠ wiser 02:07, 21 August 2007 (UTC)
Being a New Englander, I'm irked to no end, of course. But it's telling that you say "a city (or, to be more precise, within what the Census considers as an incorporated place)"; these obviously aren't equivalent, and the latter isn't "more precise" than the former. They're just two different things. What I'm most familiar with is Massachusetts, so I'll use examples from that. I hope we can agree that the Census Bureau's decision to regard MA communities that call themselves "cities" as incorporated places and communities that call themselves "towns" as minor civil divisions is totally arbitrary? Consider the cities of Beverly, Massachusetts and Barnstable, Massachusetts. Both are cities by state law. Both "have dispersed settlement patterns with urbanized areas separated by less populated regions," as you put it. But because Beverly calls itself a "city" and Barnstable calls itself a town, Barnstable is an "MCD" and Beverly is an "incorporated place". And so, for instance, West Barnstable, Massachusetts is a CDP but Beverly Farms isn't—and we reflect that arbitrary distinction, based on nothing but the Census Bureau's misclassification, in the titles of the articles, one of which uses the comma convention while the other doesn't. So, Barnstable is indeed a city that contains CDPs, and I don't see why we should treat West Barnstable on the one hand and Beverly Farms and Allston on the other hand as different types of entities. AJD 14:41, 21 August 2007 (UTC)
Those are rare special cases, and that's why we're setting up a guideline here, not a mandatory decree. So basically we're not "treat"ing Beverly Farms or West Barnstable like anything. For the sake of argument, let's leave strange Massachusetts circumstances out of this. --Triadian 19:16, 21 August 2007 (UTC)
Yes, everyone is in agreement that Census classification of New England places is problematic -- even the Census Bureau. But I might note that West Barnstable, Massachusetts is not a CDP. I've yet to see a CDP defined within a place that is incorporated as a city -- even in New England. older ≠ wiser 23:35, 21 August 2007 (UTC)

Back to the US cities

New section because nothing's been discussed on this for two days.

I strongly oppose removing the state name for one simple reason: in the United States, all cities are parts of the states wherein they are located. Forgive me if this has already been stated, but to me it seems like the defining issue. This is the result of being in the United States: because the states are more than administrative subdivisions, location by state is important. Would we say "Chicago is a city in Cook County, United States"? This is different from where the location is given as disambiguation, such as Oakwood, Ohio, since Oakwood can be a municipality in Cuyahoga, Montgomery, or Paulding Counties.

Moreover, it helps to have consistency: it really seems unusual to have just a few big cities in one format, while 99.99% of municipalities nationwide are on a different format. Nyttend 22:26, 20 August 2007 (UTC)

I agree entirely. However there are some editors who have strong feelings about this and so we're trying to accommodate both views. so that we can stop wasting time discussing this. ·:· Will Beback ·:· 22:40, 20 August 2007 (UTC)
Exactly. This is part of a reasonable compromise, in the hopes that most people can be mostly satisfied on this issue :) ɑʀкʏɑɴ 22:48, 20 August 2007 (UTC)

Move requests

I've gone ahead and filed a move request for US cities based on the discussions had previously. If you haven't already please voice your opinion of the matter over at Wikipedia talk:Naming conventions#Requested moves. ɑʀкʏɑɴ 22:48, 20 August 2007 (UTC)

UK counties

I've made some amendments to the UK section of this page. It reflects consensus, naturally, but it makes clearer some of the finer aspects of the Counties of the United Kingdom which are much more complex and contentious than was previously covered in the naming convention... Jza84 00:16, 24 August 2007 (UTC)

Mexico

Ok, since they reverted my changes, I'll open this discussion, there is really nothing much to say besides that Mexico (like most countries) uses the "City, State" format, but for some reason whoever wrote the Mexico paragraph didn't put it that way, so I tried to fix it but it seems like they wanted me to propose it here first, I could find so many sources stating how that format is the standart in Mexico but I'll wait what they say. Supaman89 23:14, 9 November 2007 (UTC)

I reverted your change because prior to your mass moving the Mexico city pages to the pre-disambiguated "city,state" format, all the city articles did follow the convention as written prior to your edit. It would be beneficial if you proposed your change to the naming style of Mexican cities first before you massed move them and then claim that because most city articles now use the "city,state" style, the guideline should be changed. Is there a wide spread name duplication issue within Mexico that would require pre-disambiguation? --Polaron | Talk 23:23, 9 November 2007 (UTC)

Ok, I understand you, I didn't even know that this page existed until I was advised so I thought I'd be logical to add the state if it didn't have it, because that's the way it's used in Mexico, that's why I did it, so are we alright with the correction made to the Mexico section? Supaman89 00:10, 10 November 2007 (UTC)

I don't see a problem with using the "City, State" format for Mexico. It has the same federal system as the U.S., and every city or town is located in one and only one state. ·:· Will Beback ·:· 00:34, 10 November 2007 (UTC)
I've no strong opinion either way. I like the principle of least surprise at finding Acapulco at Acapulco, which accords with the instruction to "use common names" (how many of those drunk foreing tourists even know what state they're in?), but it is incongruous to look at Category:Cities in Coahuila (or any of the others) and see that half the towns have the comma and state and half don't. And it does seem logical to place "Pachuca" at "Pachuca, Hidalgo", if you've just looked up (for example) Denver and found it at Denver, Colorado: for a perfect illustration of this, check the first edit summary on the history of Irapuato, Guanajuato. I've seen the several Mexican town articles created at "city, state" by casual editors, even when "city" alone is a red link: I suppose it's just what comes naturally. I don't care either way, but if it's going to happen I would ask: (a) make sure all the redirects are place (variant names, with and without accents, etc); (b) use the state names with accents (I reverted a string of towns moved to "name, Nuevo Leon" the other day); (c) Mexico City should not be moved. Aille 01:58, 10 November 2007 (UTC)
I agree that consistency is beneficial. Regarding your last point, isn't Mexico City a federal district, the rough equivalent of a state? Kind of like Washington D.C., not contained within any state. ·:· Will Beback ·:· 02:20, 10 November 2007 (UTC)

Yes, the Distrito Federal (DF) is like a small state but is not, it contains Mexico City within but at the same time it could be a synonym to refer to the city itself, like when you say “I’m going to D.C.” it is like the Mexican version of Washington D.C. actually in Spanish it is "México D.F." Supaman89 02:42, 10 November 2007 (UTC)

I'd prefer to keep the cities at City, when unambiguous or when there's an obvious choice, in accordance with WP:NC(CN). Spacepotato 07:56, 10 November 2007 (UTC)

That's not the way is it used in Mexico, it always follows the "City, State" format whether they need it or not (like in the USA), and like they said it is always nice to have some consistency. Supaman89 19:09, 10 November 2007 (UTC)

Cities are not always referred to as City, State, even in the USA. They are sometimes referred to in this way (the comma convention), and this has been used as a disambiguating convention here on Wikipedia. The problem is that its universal use in any region is in conflict with naming principles for other parts of the world, as well as general naming principles—it's comparable to moving Turin to Turin, TO, Lille to Lille, Nord, etc. Spacepotato 21:24, 11 November 2007 (UTC)
The convention addresses individual countries individually. There's no requirement that the standard be the same for Mexico as for France. Having consistent naming within Mexico would be beneficial for both readers and writers. ·:· Will Beback ·:· 21:48, 11 November 2007 (UTC)

Spacepotato, I see that you reverted my edit, It seems like you're the only who wants to leave it as simply [[City]] (I don't know why) even though as I mentioned it is the way it is used in Mexico, and other users have agreed with me that it is better to have consistency, it doesn't look good when some cities follow the [[City, State]] format and some don't. Supaman89 18:18, 12 November 2007 (UTC)

It conflicts with what's done in other regions, and with the general principle of placing subjects at their names. In a case like Acapulco, for example, the state name is clearly superfluous. Spacepotato 19:08, 12 November 2007 (UTC)

If they type the word Acapulco, they'll learn that it is located in the State of Guerrero, what is wrong with that? it's just like when people type Los Angeles and then they see that the city is located in the State of California. Supaman89 19:56, 12 November 2007 (UTC)

Article names are not to inform the reader, but to identify the article. Many of our article names are wholly opaque to the uninitiated (e.g., Ab initio multiple spawning, NGC 2915.) Although there are other Acapulcos, the one in the Mexican state of Guerrero is by far the best known, so that it can be identified to the reader simply as Acapulco. Spacepotato 23:17, 12 November 2007 (UTC)
"Acapulco" is not the name of the city. Its name is "Acapulco de Juárez", yet we choose to put it somewhere else. The practice in the large region closes to Mexico, the United States, is to put places at "City, State". That's worked out well and only a few exceptions have been needed. ·:· Will Beback ·:· 22:57, 12 November 2007 (UTC)
Acapulco is the common name of Acapulco de Juárez, and so the article is placed there, in accordance with the principle to use common names. In the case of the U.S., the universal use of the comma has been a source of arguments for years (as a glance up top will show you), and I'm eager to avoid the same problem for Mexico. Spacepotato 23:17, 12 November 2007 (UTC)

Thank you for your unpretentious concern, but as I said before it is the way it is used in Mexico whether they need it or not (just like in Italy they follow the "City (XX State)" format) whoever wrote the paragraph in the first place obviously didn't know that, therefore I'm just trying to fix it.

BTW, what about the L.A. example, should we name the article simply "Los Angeles" instead of "Los Angeles, California" because it is by far the most famous one? Or should we follow the "City" format for all the U.S. cities unless they need disambiguation? Supaman89 00:37, 13 November 2007 (UTC)

I do think that Los Angeles, California should be moved to Los Angeles. It seems clear that Los Angeles, California is the primary topic for Los Angeles, which redirects there now. In general, if a city has a unique name or is the primary meaning of its name, and it is sufficiently notable to be known outside its region, I would prefer to avoid the comma. As for the U.S. guideline, I would prefer wording similar to the Canadian guidelines (i.e., if a city has a unique name or is unquestionably the most significant place with its name, it is permissible to place it at City, if desired; otherwise, it should go at City, State.) Spacepotato 02:25, 13 November 2007 (UTC)
It's the U.S. that's the exception to the WP:NC(CN) ("What word would the average user of the Wikipedia put into the search engine?"), right? For instance, looking at the Canada guidelines, it appears that Toronto, Winnipeg, et al. are at those locations. Asking that "What word..." question, Mazatlán would beat Mazatlán, Sinaloa, hands down, and probably be given a good run for it's money by (grimace) Mazatlan, Mexico. I can see the rationale for both sides of this argument, and I don't think there have been enough voices heard yet to embark on a massive comma-stating of the Mexican articles. Aille 01:39, 13 November 2007 (UTC) (but if you are going to, Supaman, take the time to fix the odd double redirect here and there, please?)

Just noting again that prior to this discussion, all Mexican city articles were primarily at "city" except for ones needing disambiguation. Supaman89 then started mass moving these articles to the forced comma convention without discussion. Then, he changed the listed naming guideline for Mexico to his style claiming that since this is how the Mexican city articles are titled, the convention should follow that. All these changes should be undone pending the outcome of this discussion. If there is consensus to change to the forced comma convention, then we can proceed with renaming. If there is no consensus, status quo prevails as per the standard at Wikipedia. --Polaron | Talk 01:51, 13 November 2007 (UTC)

Ok, it seems like we are not understanding each other, according to the example above "Los Angeles" would easily beat down "Los Angeles, California" as well as "New York City” would beat "New York, New York" still every single City-Article in the U.S. has the State despites of its necessity or not, simply because that's the way it is used in the United States and that's the way it is used in Mexico as well, so why would the U.S. cities make reference to the State but the Mexican ones don't? Even though both countries follow the same format? as simple as that, the only argument until now is "If they don't need it, don't put it" so using that same principal if the U.S. (or any other country that uses that format) don't need disambiguation then don't put the state, how contradictory is that? Supaman89 02:28, 13 November 2007 (UTC)
Oy, don't go there. If you really want to know, there are several hundred kilobytes of discussion on this. Bottom line is, pre-disambiguation is not the usual Wikipedia naming style but it has been claimed that the U.S. is a special case that deserves to be exempt. --Polaron | Talk 02:36, 13 November 2007 (UTC)
Well, that's the problem—our guidelines for different places don't match each other, nor do they match general principles, and this makes editors unhappy. But it's not true that all U.S. city articles are at [[City, State]]. New York City, Chicago, and Philadelphia aren't, and the guidelines presently allow for 24 other U.S. cities to drop their commas, should the moves be proposed and accepted. Spacepotato 02:40, 13 November 2007 (UTC)
(EC) That's not quite right. Numerous fields have special naming conventions, even for places. The U.S. convention works well, and if it would work well for articles on places in Mexico it should be made the standard there too. We can debate the proposal on its merits, for how it would work in this topic. ·:· Will Beback ·:· 02:42, 13 November 2007 (UTC)
Do Mexican city names warrant pre-disambiguation? Is the repeat use of names so widespread that pre-disambiguation makes sense? --Polaron | Talk 02:47, 13 November 2007 (UTC)

I don't mean to be rude about this but, what makes the U.S. so special that all their cities are allowed to have the State even if they don't need it?, but the Mexican cities that do use the same format can not? for example Mentor-on-the-Lake I'm sure there is not another city in the whole world that has that name so there's no problem with people choosing the wrong one, still it mentions the state Mentor-on-the-Lake, Ohio that's just one of PLENTY examples, so again that's a bit of hypocrisy right there.

BTW, what about Argentina, Brazil, Canada, etc. that also use the “City, State/Province” format and no one says anything? Supaman89 03:56, 13 November 2007 (UTC)

Reply to Supaman: as I read the guidelines on this project page, Argentina, Brasil and Canada only use "city, state" when disambiguation is needed: see Manaus, Belém, Salta and Toronto. That, as Polaron points out, is the general rule. The US (and Australia) is the excpetion: we might want to become part of that exception, but let's try first and reach a consensus.
Reply to Polaron: Is the use of names repeated? Yes and no is the easy answer to that. "Yes" because if you look at Municipalities of Oaxaca, you'll see 15 or 20 municipalities and their head-towns called "San Francisco". "No" because each one of them is "San Francisco Something": San Francisco del Mar, San Francisco Ixhuatán, San Francisco Solá, etc. San Francisco, Oaxaca, would have to be a disambig page. Most of the country's San Franciscos (and San Juans and San Josés and Santa Marías) come with a 'surname' for disambiguation purposes; however, the gazeeter of my Guía Roji road atlas lists at least 30 as plain San Francisco. And I bet every state has its Emiliano Zapata and its Benito Juárez. Couple of places called Minatitlán, four or five Tuxpans, sprinklings of Tenangos and Tenancingos. So "yes". Having said that, I don't know how many of those are no more than two streets, a cantina and a stop sign. Wikipedia aims to be comprehensive: does that include villages of 200 people in the Sierra Gorda? Do we need to pre-disambiguate to cover that level of detail? (The question's not retorical.)
Back to Supaman: On a related point, there are two municipalities called San Andrés in Veracruz (although one doesn't have an article yet), which is why I reverted the move of San Andrés Tuxtla to San Andrés, Veracruz. And I see San Francisco Coacalco has been moved to San Francisco, State of Mexico, ditto San Francisco Tetlanohcan to San Francisco, Tlaxcala. Besides being a breach of 'use common names' (in this case, San Andrés Tuxtla or, if you insist, San Andrés Tuxtla, Veracruz), that will create a nightmarish when someone gets round to writing about San Andrés Tenejapan, the "other" San Andrés in Veracruz. I don't know if there are other San Franciscos in EdoMex or Tlaxcala, or other San Josés in Ags. besides San José de Gracia, but moving them to the comma-state format without taking the 'surname' with them is asking for trouble. Please reconsider; as I've said, I'm not convinced that city, state, isn't the right choice for Mexico, but do it properly if you're going to do it. Aille 04:50, 13 November 2007 (UTC)

Yes, I understand and as you mentioned A LOT of cities have repetitive names, so for precision they need to include the state (even if they didn't, again that's the standard form in Mexico just like the U.S.) and as Will Beback and yourself said, it is always nice to have some consistency it just looks wrong when half the cities have the state and half don't, and finally I don't even know how this became such a big deal, people are going to keep typing "Acapulco" but the title name will be "Acapulco, Guerrero" just like people type "Miami" (another popular name) and it sends them to "Miami, Florida". Supaman89 05:19, 13 November 2007 (UTC)

Include the state if you will, but why move Santa María del Tule to Santa María, Oaxaca, and not to Santa María del Tule, Oaxaca? Take a look at just how many Santa Marias there are in Municipalities of Oaxaca. And that's a problem you already came across in the EdoMex, isn't it, when you moved Santiago Teyahualco to Santiago, State of Mexico, and then came across Santiago Tianguistenco and had to move it to Tianguistenco, State of Mexico, because the "Santiago" location was taken. San Juan de los Lagos is San Juan de los Lagos, or San Juan de los Lagos, Jalisco, if you insist, but not San Juan, Jalisco; ditto, San Cristóbal de las Casas, and long etc. Aille 05:42, 13 November 2007 (UTC)

Oh yes, I remember, I think I did it because the names were too long but I kept the oficial form bolded right in the introduction, anyways thank you for your understanding but I'm affraid I can't edit the paragraph myself because someone may revert it (by the third time). Supaman89 15:42, 13 November 2007 (UTC)

As Aille mentioned, Mexico already has its own system of disambiguation by adding a "surname" to city names. Wouldn't that system work for most cases? Please don't confuse postal addresses with city names. The state name is not part of the city name. Don't justify changing the convention using the US system as the use of that system is also contested. --Polaron | Talk 16:26, 13 November 2007 (UTC)

Those "surnames" are not "Mexico's own system of disambiguation" as I said plenty of times before in Mexico they always have to follow the "City, State" format whether they need it or not, and the United States should not be a special case, when the U.S. finally change (if they do) their naming criteria then we'll talk about this issue again, until then I don't really see how someone could argue not to do something, when they're doing it themselves. Supaman89 01:17, 14 November 2007 (UTC)

What do you mean "they always have to follow the city,state format whether they need it or not"? Who is it that is dictating this? I'll say it again: The state name is not part of the city name. Don't justify changing the convention using the US system as the use of that system is also contested. Most of the rest of the world don't follow the US city naming style. --Polaron | Talk 02:05, 14 November 2007 (UTC)

I don't know if the whole world follows the same naming system as the USA or not, but Mexico does use the same system, therefore if all the U.S. cities have the ",state" (Denver, Colorado) it's just logical that the Mexican ones do it too (Hermosillo, Sonora), until the U.S. changes its articles to simply "City" (Little Rock, Arkansas → Little Rock) I just don't see how people could argue someone else not to do it.

Your basis for proposing this change is "this is how US cities are named so this is how Mexican cities should be named too"? You won't convince too many people of the need to change the existing guideline if that is your main argument. I don't think there was ever any debates as to what to name Mexican city articles so the status quo (prior to your mass moves) did not pose any problems whatsoever. --Polaron | Talk 03:28, 14 November 2007 (UTC)
The towns' names were too long -- so he gave them new names. Compare: 39 hits on Google for san-juan-jalisco vs. 234,000 for san-juan-de-los-lagos. Of course, this is same editor who made up his own set of state abbreviations because the ones used by the government, post office and 110 million Mexicans were too long. Words fail me; I think I'll unwatch this page. Aille 19:57, 14 November 2007 (UTC)
Postscript. Anyway, is the location of the article so important? Linking to Hermosillo, Sonora, in a paragraph of another article will take you to the same utltimate destination. (And yes, a lot of times the structure and flow of an article requires that you do include the state.) The matter hardly warrants the amount of bytes we've already spent on it. Aille —Preceding comment was added at 20:14, 14 November 2007 (UTC)

Polaron seriously, I've got pretty much any argument to why it should be changed, and I think I’ve repeated them plenty of times already, the U.S. was just an example not my basis, but if you keep bringing the same things that I’ve already answered then we'll never going end this thing, you know I'm right just accept it, there is not one logical reason why if both countries that use the same format one of them is allowed to use it but the other one don’t as simple as that, would it bother you so much that it’s changed to “City, State” (which is how it should’ve been in the first place), I would just find it pretty difficult to tell someone not to do something, when I’m doing it myself. Supaman89 20:08, 14 November 2007 (UTC)

I gave it a week to see if anyone else responded, I'll proceed to fix the paragraph. Supaman89 (talk) 19:28, 19 November 2007 (UTC)
A lack of continued argument does not give you license to enact the changes you see fit. There clearly exists no consensus for doing this and I will revert the change. Until you can achieve consensus for a change to the guideline, the status quo (as flawed as it may be) remains the guideline. ɑʀкʏɑɴ 19:54, 19 November 2007 (UTC)

While I prefer to use the default Wikipedia-wide guideline of using common names, using the comma convention as a default is acceptable if it is not applied too rigidly. Before you change the convention, let's work on a proposed wording that specifically allows for major cities to to stand alone (see Australia and Canada for examples of how to define which can be exceptions). At a minimum, a proposed move request should be able to go through if it can be shown that the city name by itself is sufficiently known globally. My worry is people will start opposing such move requests by saying it is against the naming style, which itself was imposed artificially. --Polaron | Talk 23:01, 19 November 2007 (UTC)

Ok, let me create a proposal section to put the paragraph that's being reverted, so adjustments can be made. Supaman89 (talk) 01:17, 20 November 2007 (UTC)

Proposal

Mexican geographical articles go under the [[City, State]] format, ex. Nogales, Sonora always separated by the "comma convention". The same format applies to cities that share names with the state, ex. Oaxaca, Oaxaca leaving the single name Oaxaca as reference to the state.

International known places might be left as [[Placename]] only, ex. Mexico City, Acapulco and Cancun.

Adjustments and corrections are welcome. Supaman89 (talk) 01:17, 20 November 2007 (UTC)

You may wish to leave a note on Wikipedia talk:Naming conventions to make people more aware of this proposal and try to get some broader input. ɑʀкʏɑɴ 15:24, 21 November 2007 (UTC)
  • Oppose. All in all, the "City, State" notation suggests that the name is not unique; i.e., if we have an article on, for example, Empalme, Sonora, it automatically suggests that there is a place in Mexico called "Empalme" elsewhere outside Sonora and that Empalme proper is a disambiguation page. As far as I know, only the naming convention for the U.S. settlements uses this scheme, and it is constantly disputed anyway. On a different note, what are "international(ly) known places"? By what criteria are they selected? How would you decide if any given place in Mexico is "internationally known"? Why should that even affect the naming conventions? You say that they "might" be left under an undisambiguated title. What affects the decision whether they "might" or "might not" be renamed/left alone? What is the benefit of this approach to readers and to Wikipedia as a whole? What is the ultimate benefit of mass-renaming the city articles? Are there flaws with the existing naming scheme that can only be fixed by mass-renaming? If so, have you considered a different solution?—Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky) • (yo?); 16:09, 21 November 2007 (UTC)
  • Suport. Logical and consistent. ·:· Will Beback ·:· 20:33, 21 November 2007 (UTC)
  • unpersuaded. The United States convention rests on three grounds: Most American placenames need disambiguation; American English normally does this as City, State; and even places which are unambiguous are idiomatically so called (Lincroft, New Jersey, for example). Are any of these true of Mexico? Septentrionalis PMAnderson 20:49, 21 November 2007 (UTC)
    There is like 30 paragraphs above explaining and debating the use of the "city, state" format for Mexico, if anyone has any questions you may check it, this proposal is merely to make any modifications, corrections, etc. before changing it, suggestions about the paragraph are welcome. Supaman89 (talk) 03:17, 23 November 2007 (UTC)
    That largely says: WP:IWANTIT; the most obvious supporting reasoning (that City, State is some sort of privilege for the United States) is invalid. If there is evidence in that long discussion which addresses any of the three points I asked about, please cut and paste it nere. Septentrionalis PMAnderson 06:04, 23 November 2007 (UTC)
Ok let's see:
  • Most American placenames need disambiguation - Not really but ok let's leave that as a may, anyhow Mexican cities need desambiguation probably more than the American ones.
  • American English normally does this as City, State - Yes, you're right, Mexico also uses that same format (as I've repeated plenty of times) just need to look at any Mexican publication to verify that.
  • even places which are unambiguous are idiomatically so called - Yes that would be pretty much the same case for Mexico, adios. Supaman89 (talk) 03:41, 24 November 2007 (UTC)
Again this is not an approval or not section, it is merely to modify or adjust the paragraph presented, the discussion is above this section, and after repeating plenty of times why the paragraph should be change no one presented a logical reason to refuse the arguments above, thank you. Supaman89 (talk) 01:46, 29 November 2007 (UTC)

No one has replied those points above, but yet some people just won't let me fix the paragraph, I strongly ask you to answer those points or just let me fix the paragraph, cuz right now I can't do anything. Supaman89 (talk) 04:09, 11 December 2007 (UTC)

The name of an article should, if possible, be the most common name used to refer to the subject of the article. In the case of an article about a city, the name of the article should be the name of the city, if possible. Adding the state is fine, if required for the purpose of disambiguating. If it's the only city in the world with that name, adding the state does not enhance precision. Same thing if it is not the only city in the world with that name, but clearly the best known one. The fact that some countries do not follow this fundamental Wikipedia naming convention is unfortunate, but not an excuse to perpetuate the error. If there are any points left unaddressed by this, please let us know what they are. --Serge (talk) 05:27, 12 December 2007 (UTC)
It would be incorrect to call the U.S. naming convention an "error". It's a legitimate decision agreed to by a majority of involved users. ·:· Will Beback ·:· 05:40, 12 December 2007 (UTC)
Might makes right, Will? Is that what you really want to argue? The majority is just as able to make an error as is any minority. Even if a decision is agreed to by a majority of involved users does not mean it's not an error. The result is that hundreds of U.S. city articles have names that do not reflect the most common name used to refer to the subject of that article, even though there is no other significant usage of that name that warrants using clarifying information (the state) for disambiguation or precision. IMHO, that is a huge error. --Serge (talk) 17:07, 12 December 2007 (UTC)
I don't want to argue over this same matter further. I just was pointing out that it's just an opinion that the U.S. naming convention is an error, and that the consensus of users agree that it's a good, working convention. ·:· Will Beback ·:· 17:20, 12 December 2007 (UTC)

New York City, United States

I have seen people add United States behind New York City in articles, where there is unlikely to be any confusion. Is this policy? Or even needed? Don't we assume our reader have a base level of geographic knowledge? I'm sure that this has been discussed before... --Knulclunk (talk) 02:57, 20 November 2007 (UTC)

Given that New York City is one of those world cities that we don't require a state or province on, we surely don't need a country. --Orange Mike 03:03, 20 November 2007 (UTC)
Some folks add "USA" or the equivalent to the text of many settlement articles, on the presumption that this is a global encyclopedia and we shouldn't assume that reader will know which country "California" is in. That's reasonable. We've never made it a practice to add country names to settlements names, unless absolutely required. ·:· Will Beback ·:· 04:47, 20 November 2007 (UTC)
I'm not sure what you mean by "settlement" here, Will. --Orange Mike 04:59, 20 November 2007 (UTC)
"Settlement" is the broad term encompassing cities, towns, villages, settlements, CDPs, etc. For an example of what I'm talking about, see Maywood, California or Compton, California. ·:· Will Beback ·:· 05:23, 20 November 2007 (UTC)
What about lists of cities, then ? Say you have a list like :
Paris, France
Berlin, Germany
etc.
what is the preferred style for a US city ? My opinion is that the list should aim at being consistent, hence a Chicago, USA in the list, but what if the city is Springfield instead of Chicago ? Anne Aunîme (talk) 20:15, 22 November 2007 (UTC)
This convention concerns how articles are titled, not how the place names are used in articles. That said, if the list is put together like that then write "New York City, USA", or "Springfield, Illinois, USA". ·:· Will Beback ·:· 20:32, 22 November 2007 (UTC)

Talk:Southampton#Naming_of_articles_about_city_suburbs

There's a discussion at the above location suggesting that this convention should be ignored in the case of Southampton, for no reason I can ascertain! Additional input there would be appreciated. Waggers (talk) 10:43, 21 November 2007 (UTC)

As I made clear on the Southampton talk page, I fail to understand why areas in the city are now being described as Location, Hampshire ahead of Location, Southampton. Why is real world use being overwritten in favour of a Wiki convention? These places are known parts of the city ahead of the county, so why the change? This change means the level of geography by which most of these places are referred to is being ignored. Surely how people refer them in reality carries more weight than internet conventions? Dan K (talk) 22:25, 26 November 2007 (UTC)
The truth is that most of the areas are referred to as both Southampton and Hampshire. West End, for example, is outside of the Southampton administrative area but often referred to as being part of Southampton - yet it is separated from the city both administratively and physically. Many areas within the city boundary have a strong local identity, separate to that of the city as a whole. But the most important thing is that we are consistent across the project, and therefore it's important that we have a convention and that we follow it. If you're proposing a change, exactly what are you proposing? Would the change apply to areas within unitary authorities, or suburbs of any larger settlement regardless of administration, or what? If it's the latter, how do you distinguish between a suburb and a settlement in its own right? Unless you're willing and able to answer questions like these and justify your answers, there really is no point in continuously moaning. Please try to be constructive. Waggers (talk) 09:26, 27 November 2007 (UTC)

You asked me to move the discussion here, so I don't really see why you are now complaining about me doing so. Areas across the city do have their own identity, but that identity is more affiliated to the city than it is the county. The most obvious level is surely that of administration. Taking West End for example (one I know quite well seeing as I live there) despite it usually being referred to as Southampton I see no problem with it being Hampshire (ignoring the fact there is a West End in Fareham) as it is not within the city authority's boundaries. Areas of the city should be referred to as such - to further the point North End, Portsmouth should be described as such - not North End, Hampshire. For commonplace names using a large brush simply confuses matters. There are two West Ends in Hants, so they can't be two West End, Hampshire articles. So further disambiguation is needed, leading to a piecemeal arrangement which shows up the flaws of trying to shoe horn in too broad a rule. It should be far more flexible to accurately reflect real life, because geography (especially in the UK) is not a uniform subject, so trying to pretend that it is will throw all kinds of problems. Most importantly, the level of description I'm proposing be reinstated is more accurate. Hampshire is a far bigger geographical area than the unitary authorities of Southampton or Portsmouth. By describing the areas of these cities as such, you are providing a far more accurate description of where they are. And to play devil's advocate, if a convention is not uniformly implemented across the project can it really be called a convention? Dan K (talk) 13:27, 27 November 2007 (UTC)

So what exactly are you proposing? Should suburbs of Winchester (not a unitary authority) be disambiguated to Place, Winchester instead of Place, Hampshire? After all, they may well identify more with the city than the county, just as you claim areas of Southampton do. If that's the case, how do we distinguish between a suburb of the city and any other settlement within the City of Winchester district? If you're suggesting a change in the convention, we need to know what it is you're proposing and how to implement it across the project, not just in Southampton. Waggers (talk) 13:41, 27 November 2007 (UTC)

At the moment, we have a clear, simple convention, which can be easily applied and is appropriate for virtually all articles on places in England (as Dan K points out, in the rare cases where there are two places with the same name in the same county, we have to do something slightly different). I can't see an alternative proposal based around suburbs matching this. The question of what constitutes a suburb is complex; often residents of areas around a city do not regard themselves as living in suburbs of it, but rather as being in distinct towns or villages. Those who live further out may often regard all the outer areas of the conurbation as being suburbs. We're not in a position to easily adjudicate on this, and any policy which tries to set the definition of a suburb will inevitably lead to many, many arguments on its application. It is likely to lead to confusion as to the most appropriate title for an article, leading to broken links or multiple articles on the same place. If you have a concrete proposal which addresses these concerns, please put it forward; otherwise, while I understand the reasons for opening a discussion on this, I can't see it leading to an improved convention. Warofdreams talk 00:56, 28 November 2007 (UTC)

The Winchester example is a red herring, as Hampshire is still the authority - the joys of a two tier system - which doesn't apply to unitary authorities hence their name. You keep going on about suburbs and distinguishing them, but as I have said, why not use the authority? Boundaries are te obvious cut off line. Once you get into metropolitan counties where there is only a single tier of government the convention is the same as it is now. The change here only applies to places such as Hampshire, Dorset, East Sussex and a handful of others where part of the county is two tier government (as is the case for Winchester and Hampshire) and part is single tier (Southampton, Portsmouth, Brighton & Hove etc). You are now using all county level descriptions (Metropolitan, Shire and UA), rather than just two. You'd simply giving more credence to the notability of unitary authorities, and giving more accurate geographic descriptions of where places are. Dan K (talk) 17:36, 28 November 2007 (UTC)
OK, that's a decent, solid proposal. The current policy is to use ceremonial counties, and you would like to change it to use administrative counties and unitary authorities. Have I got that right? I'm not opposed to this idea in principle, but I'm not too keen on some of the long disambiguators which would result - Bath, Bath and North East Somerset, and also note that some disambiguators would repeat the place name, giving little useful information (apparently only Reading, Reading at the moment, but the trend seems to be towards more large towns in Britain being at disambiguated titles). Finally, I think that the county/UA split may easily be misunderstood, and that we will see many more articles created in [place, shire district] or [suburb, town] format than are at present. Warofdreams talk 02:06, 29 November 2007 (UTC)

Well as I said earlier, I don't really believe that there is any one-size-fits-all solution, so there would have to be flexibility in any system used. BANES is a worst case scenario, but at the same time is only one word longer than say East Riding of Yorkshire, but I agree it is unwieldy. If further disambiguation is needed, the ceremonial county could be used (if not already covered) or a further subdivision such as metropolitan district or district council. As for the final point, I think that's hard to gauge really, but would say that Wiki must be fast approaching some sort of plateau for the number of articles being created in relation to English geography, surely? Dan K (talk) 08:23, 29 November 2007 (UTC)

There are quite a few villages that don't have articles yet, so I think there's some more to do. Whilst I appreciate that you've now come up with a more defined proposal, I still don't think it meets your criteria of reflecting real-world usage. The Winchester example is not a red herring - there are areas that are suburbs of Winchester, just as there are areas that are suburbs of Southampton; those areas of Winchester may well identify more with the city than the county of Hampshire. If the justification for a change is to better reflect real-world usage, surely we should make sure any proposal does exactly that? Otherwise, it's a change for the sake of change. Waggers (talk) 10:54, 29 November 2007 (UTC)
The only way to get universal real-world usage is to do everything ad-hoc. While this is not something I have a problem with, I have a strong feeling I'd be in the minority. I'm not saying my proposal is perfect, but it does address problems of areas of cities like Southampton, Portsmouth etc, which the current convention does not. As I've said before, there is no way any one-size-fits-all rule will address all the problems of all the articles, so I think the best thing to do is to get one that addresses as many issues as possible. For places like Winchester's areas and the Metropolitan counties, everything in is nigh on identical to the status quo, if the Winchester issue is something that is against my proposal, it must be against the current convention too. Dan K (talk) 12:02, 29 November 2007 (UTC)
It just seems a little odd that an area with strong ties to a city without unitary authority status would be disambiguated to the county, while an area that happens to be within a unitary authority area but has a strong, independent identity (or more ties to the county than the city) would be disambiguated to a nearby city. But I'm happy to live with that, it's not a dealbreaker. Waggers (talk) 12:30, 29 November 2007 (UTC)

So where do we go from here? Dan K 23:42, 3 December 2007 (UTC)

It looks like you've got (slightly reluctant) agreement, so I'd suggest drafting your change to the convention here and, providing there are no objections, we can go ahead and make the change, renaming the appropriate articles. Warofdreams talk 23:14, 9 December 2007 (UTC)
I should make clear that I still disagree with Dan K's proposal, as the time and effort required to rename all the articles and clean up all the backlinks, together with the confusion and inconsistency that would be caused, are in no way justified by the almost negligible benefit of making the change. Waggers (talk) 10:46, 10 December 2007 (UTC)
Apologies, I misunderstood your last comment. In terms of dealing with backlinks, that shouldn't be a deciding issue; there probably won't be too many, and we are likely to be able to get someone to write a bot to do it efficiently if the task seems overwhelming. In that case, while there wouldn't be any harm in drafting the proposed change, the objections Waggers raises are those which need to be discussed. Warofdreams talk 12:18, 10 December 2007 (UTC)

Proposed addition to "United States" section

I propose the following addition to the "United States" section, in order to better reflect current practice and consensus. Though I'm sure it's not too controversial, I figured I'd start a discussion on talk just in case there are any objections. Note that this is not a proposed policy change, nor is it an argument for or against the "comma convention". This would go after the AP Stylebook passage.

Currently, only three article about U.S. cities do not use the "comma convention"—Chicago, New York City and Philadelphia. If you think any of the other articles listed above should be moved to [[City]] instead of [[City, State]], please start a discussion on the article's talk page. Note that such moves have been proposed before, and have not gained consensus in the past.

Thoughts? szyslak 23:53, 22 January 2008 (UTC)

That seems to accurately reflect current practice. ·:· Will Beback ·:· 00:02, 23 January 2008 (UTC)
As of January 2008, please. Otherwise we have to keep fixing it. Septentrionalis PMAnderson 00:06, 23 January 2008 (UTC)

Perhaps instead of directing users to simply "start a discussion on the article's talk page", we could direct them to WP:RQM. Thus, the new passage would read as follows (with a couple of minor changes/fixes):

As of January 2008, only three articles about U.S. cities do not use the "comma convention"—Chicago, New York City and Philadelphia. If you think any of the other articles listed above should be moved to [[City]] instead of [[City, State]], please start a discussion via Wikipedia:Requested moves. Note that such moves have been proposed before, and generally have not gained consensus in the past.

szyslak 02:23, 23 January 2008 (UTC)

Though I'm not sure what problem this would be solving, I'm okay with the proposed addition/change, as long as the last sentence, "Note that such moves have been proposed before, and have not gained consensus in the past.", is not included. It's generally true, but biased and irrelevant. I'm okay with the suggested "as of January 2008" part:

As of January 2008, only three articles about U.S. cities do not use the "comma convention"—Chicago, New York City and Philadelphia. If you think any of the other articles listed above should be moved to [[City]] instead of [[City, State]], please start a discussion via Wikipedia:Requested moves.

--Serge (talk) 05:40, 23 January 2008 (UTC)

I wouldn't say there's a "problem" to solve, but I think the statement about permissible [[City]]-format names needs some qualification, especially regarding the fact that consensus needs to be determined before such a move is made.
Anyway, I'll go ahead and add the proposed passage without the "such moves ... have not gained consensus" part, which isn't particularly necessary. szyslak 02:04, 31 January 2008 (UTC)

Scotland guidelines

More than a month ago User:Jza84 unilaterally added this guidelines for Scotland pages. I don't think anyone was aware this had happened, until he brought his own edit there up as an argument on the Talk:Perth, Scotland. As usual new guidelines only come to wipespread attention when a guideline hobbyist tries to impose something absurd with only the guidelines as an argument.

AS you can see from the page Talk:Perth, Scotland (there has been an attempted move here), it is a complete nonsense to pretend as User:Warofdreams did that its had consensus for several years. Guideline pages are not places to subvert de facto wikipedia standards and undermine wikipedia's health by inventing "consensus" for ideas that virtually no-one supports. Deacon of Pndapetzim (Talk) 11:07, 27 January 2008 (UTC)

No consensus? See Wikipedia_talk:Naming_conventions_(settlements)/Archive_6#Standard_for_United_Kingdom.3F and Wikipedia_talk:Naming_conventions_(settlements)/Archive_7#UK_placenames. Pretty clear, and while there has been discussion on whether to disambiguate by ceremonial county, historic county, administrative county or other similar divisions for various nations, there has been no dissent here as to the general policy of disambiguating at a sub-national level. The location, discussion and page history of the vast majority of places requiring disambiguators supports this. Of course, consensus can change, and it may do as a result of this discussion, but please do not claim that consensus never existed simply because you did not participate in the discussion.

Incidentally, as this discussion is now ongoing, I will happily leave the pages you have moved, but for future reference, you may like to look at the Wikipedia:BOLD, revert, discuss cycle. Warofdreams talk 20:38, 27 January 2008 (UTC)

  • Actually, all the pages I moved were actually just moved back. Those convos you cited are ancient and contain nothing relevant; there is virtually nothing mentioned about Scottish placenames, and there's no indication any decision was reached. The guy who added the guidelines, Jza, didn't even participate in those discussions anyways. The "Consensus" (really!) does not exist, and there is nothing on this talk page to support the additions made a month and a half ago. Subverting community dialogue by inventing consensus for ideas that haven't been discussed is really, really bad play. Rather than behaving like this, wouldn't you prefer instead to join in the discussion here? That'd be really good, as you must have some thoughts on the issue. Regards, Deacon of Pndapetzim (Talk) 21:09, 27 January 2008 (UTC)
That is a non-existent "consensus" you deliver. One Discussion from 4.5 years ago (involving 4 editors) that is not consistent with the guideline you claim we had consensus on (where coincidentally your comment there states exactly the opposite of what you are now doing) and a discussion from 3 years ago that is a textbook example of no consensus if I ever saw one. Thanks for the tip on the cycle, but I have been about here for three years and am very well aware of it. What is crystal clear is that no consensus exists (either now or in the past) for the guideline as was. SFC9394 (talk) 21:21, 27 January 2008 (UTC)

Guidelines Deacon added - descending disambiugation

Where possible, articles on places in Scotland should go under [[placename]]. Thus Glasgow, not Glasgow, Scotland. Where disambiguation is needed, articles should go under [[placename, Scotland]]. Thus Perth, Scotland, not Perth, Perth and Kinross. Where disambiguation is still needed, articles should go under [[placename, Council Area x]]. Thus Abernethy, Highland and Abernethy, Perth and Kinross. If even then it is still needed, then another form of natural and recognisable disambiguation should be sought, such as traditional regions, committee areas, etc, as in Kinnaird, Gowrie and Kinnaird, Atholl, both in Scotland and in Perth and Kinross.

  • Support. Entirely common sense proposal, very succinctly constructed and should be adopted word for word. Bill Reid | Talk 19:40, 27 January 2008 (UTC)
  • Support (assuming this is really necessary at all), and with the added suggestion of using X, Island as an alternative as suggested below. There are also island disambiguation issues to contend with e.g. Sanday, Orkney but let's not waste more time on that. Ben MacDuiTalk/Walk 20:08, 1 February 2008 (UTC)
  • Strong Oppose The previous "council area" disambigation was more than adequate. Plus this leaves open debate with UK vs. Scotland. -- Jza84 · (talk) 22:46, 1 February 2008 (UTC)
Given that I've never seen anyone create an article on a Scottish settlement with the name "Placename, UK", I think this is not a debate we are likely to see. Of course, there could be people seeking to prove a point, but I doubt there are many people who think that "Placename, UK" would be a natural name for a settlement. Lurker (said · done) 14:47, 2 February 2008 (UTC)
  • Support Not that I pay much attention to these kind of guideline pages anymore, since the stealth policymaking where one or a few editors alter the guidelines then expect everyone to follow suit really irritates me. But, an attempt at a common sense guideline is worth a try. The above proposal is the most common sense and, contrary to the section below entitled "existing practice" is pretty much the way most of us who prefer actual editing to endless policy debates have been doing things before now. Lurker (said · done) 12:51, 2 February 2008 (UTC)
  • Lurker, please Assume good faith. At the time I wrote the "existing practice" paragraph, I inspected about half a dozen categories (perhaps a few more), and saw exactly one "placename, Scotland" article, and about 2 dozen "placename, <something smaller than Scotland>" articles. I checked the history of some of those, to ensure there hadn't just been a mass rename, but didn't check them closely. None of the ones I checked had been moved as their last edit, only one that I recall had moves in recent history. If I was wrong, it's OK to point that out with a broader set of statistics, not with sarcasm and an assumption I was pushing my own barrow. --Scott Davis Talk 22:25, 2 February 2008 (UTC)
  • Support A vote for common sense - using widely-known terms to uniquely identify. There are likely to be exceptions to any "rule" Finavon (talk) 19:57, 2 February 2008 (UTC)
  • Commenting I would like to point out that several major atlases, including those by the OS and AA, disambiguate to council area for places in Scotland. I think this is worth noting. -- Jza84 · (talk) 01:00, 3 February 2008 (UTC)
Those are internal to the UK - wikipedia is a worldwide document. When Pan Am 103 happened it was referred to around the world as "Lockerbie, Scotland" - not "Lockerbie, Dumfires and Galloway" - frankly it was reported as "Lockerbie Scotland" for the 6pm UK news because internal to the UK the vast majority of people in England wouldn't have a clue about Scottish council areas. Are we trying to help or hinder the reader? There is only one solution here - and all the other voices say the same thing. SFC9394 (talk) 01:15, 3 February 2008 (UTC)
That's a totally fair point, but I felt that it was a bite of info worth noting here. Of course there have been suggestions to further disambiguate to former counties, or worse, "traditional" regions (like the non-statutory Highlands). I would hope that should this new system be adopted, we are supporting that the second tier of disambiguation is to council area??? -- Jza84 · (talk) 01:27, 3 February 2008 (UTC)
Oh, and the Gazetteer of Scotland uses council areas as the subdivisions of Scotland. Also worth noting for my point against other forms of subdivision for Scotland. -- Jza84 · (talk) 01:31, 3 February 2008 (UTC)
  • Support Sensible solution to a problem that simply need not have ever exsisted. Hierarchical naming makes sense - pointing a reader to some obscure council name is only going to confuse. SFC9394 (talk) 01:15, 3 February 2008 (UTC)
  • Support - see my comments on "Highland" on this page, which talk about how misleading it is. Only in cases where there are several places with the same name in Scotland, e.g. Kincardine, Letham, Newburgh etc is it worth differentiating. --MacRusgail (talk) 18:07, 5 February 2008 (UTC)
  • Support - I have changed my mind on this one, after reading the Perth Talk and here. I was actually the prat that moved a lot of these articles to the daft "council area" dabs in the first place (I stopped doing it quite a long time ago now). I repent. --Mais oui! (talk) 04:36, 29 February 2008 (UTC)

Guidelines User:Jza84 added - council always formula

In Scotland, disambiguated place names should go under [[placename, council area]]. Thus Fort William, Highland, and Clarkston, East Renfrewshire not Fort William, Scotland (which is a redirect page) or Clarkston, Renfrewshire.

(from discussion at Talk:Perth, Scotland):

The reason for providing a second part to a name is to clearly differentiate the place from other(s) with the same name. The second part of the name should be better known than the first. Beyond this, to me, it matters little what is used, "county" (old or new), region, unitary authority, or nation, so long as it makes it clear where the article is about and differentiates it from other places with the same name. For old "county towns" adding the county or region does little for clarity (as Lincoln, Lincolnshire). Perth, Perth and Kinross repeats infomation, whereas Perth, Scotland adds clarity (provided there is no other Perth, Scotland of similar prominence). Finavon (talk) 13:31, 27 January 2008 (UTC)
Absolutely no guideline is needed for UK articles. On occasions where there are multiple instances of the name the best workaround can be found amongst the editors of those articles to find a suitable solution. To suggest that all placenames of settlements have to go under "placename, council" is ridiculous. I have commented on this before, and this seems to be a worryingly increasing trend of content decisions affecting thousands of articles being decided unilaterally by a small group of editors who want everything to fit in neat and tidy boxes and come up with "guidelines" which everyone should follow. I will link to the essay Wikipedia:Avoid instruction creep - I think this needs to be clearly accepted in the context of UK place/settlement articles - I am fed up being hemmed in by an unnecessary and useless bureaucracy decided on by a tiny number of editors. SFC9394 (talk) 14:17, 27 January 2008 (UTC)

This is wrong anyway, it should be "Fort William, Highland Region" - the Highlands are a completely different entity to Highland region, and the current idea misleads some people into thinking that some areas are in the Highlands, which are not, and some which are in the Highlands are not. I still think this is Americanisation of wikipedia. --MacRusgail (talk) 16:55, 27 January 2008 (UTC)

Some examples

  • Fort William - Highlands, & Highland region
  • Campbelltown - Highlands, but not Highland region - Argyll
  • Pitlochry - Highlands, but not Highland region - Perthshire (Perth and Kinross?)
  • Thurso - Not in Highlands (Lowland Caithness), but in Highland region
  • Edinburgh - Clearly neither in Highlands nor Highland Region
  • Orkney - Not in the Highlands (nor arguably truly Scottish), but lumped with them for certain purposes)
  • Western Isles - Highlands, but not Highland region. Properly this term refers to ALL of the Hebrides, not just the outer ones!

This is why this is a particularly horrible and misleading usage. Banff is a traditional county town, and none of its people consider themselves "Aberdeenshire" - it's anathema to them, but since there's only one Banff of any note in Scotland, "Banff, Scotland" makes perfect sense. Apart from the fact that London based penpushers have made a dog's dinner of Scottish geography, there have been several changes during the 20th century, which will lead to great confusion. --MacRusgail (talk) 17:03, 27 January 2008 (UTC)

The comments by SFC and MacRusgail are very well put. Not an iota of thought was put into Jza84's attempted guidelines. SFC's suggestion for no guidelines is probably the nearest we can get to the best possible situation, ironic as that seems. Per comments of SFC, the more I find out about the guidelines process the more disturbed I become. Many such guidelines are written by a tiny number of people on obscure pages who push their little coups through with usually no discussion and thereafter attempt to subvert community dialogue by forwarding them as a fait accompli. Thats how we've got most of those monarch names we have, and why so many Scottish places were moved. Little attempted coups like that. Jza84 even had the temerity to cite the text he himself had written a month before as an excuse to move the long established Perth, Scotland to the absurb Perth, Perth and Kinross, writing It is convention to use the style "PLACENAME, COUNCIL AREA" for Scottish places, but the guidelines do permit the excercise of commonsense and rare exceptions., while User:Warofdreams wrote when moving the page in line with guidelines. If you disagree with the guidelines, please discuss them; do not change them unilaterally ... irony, eh? Did we all become idiots overnight that we're expected to buy that kind of thing? I apologize, I'm now sounding rather abrasive, and I must WP:AGF. Deacon of Pndapetzim (Talk) 17:16, 27 January 2008 (UTC)
Have to say I didn't realise the extent of what was going on here. The current vast amount of moves by User:Warofdreams is completely OTT. No discussion, no consensus - just "moves per...." - this is a guideline (with virtually no discussion and inserted into the page 2 months ago) not a policy - you really can't be doing that. Don't bother doing the mass moves on any of the articles I work on or they will get moved straight back. Totally ridiculous. SFC9394 (talk) 20:00, 27 January 2008 (UTC)
And he just reinstated it too. Quite unbelievable. I don't think actual consensus matters. Why bother forming it when you can just pretend it exists? Deacon of Pndapetzim (Talk) 20:11, 27 January 2008 (UTC)
Right. Please do not remove guidelines which have had consensus simply because you disagree with them. There is a discussion under way; there are no grounds to cover up the existing consensus. A link to the ongoing discussion is the ideal compromise. Please assume good faith and avoid personal attacks. Warofdreams talk 20:41, 27 January 2008 (UTC)
Warofdreams ... this is nonsense. What evidence do you have that this is an "existing consensus"? Deacon of Pndapetzim (Talk) 20:46, 27 January 2008 (UTC)
"the existing consensus". There is no discussion on this page - this has received *NO* discussion amongst a wide body of editors (and unless tucked away on someone's private talk page I can't even find *any* discussion at all). What is going on here is, quite frankly, breathtaking. SFC9394 (talk) 20:50, 27 January 2008 (UTC)
Indeedie. Warofdreams ... you can presume that no-one here is psychic nor has access to the relevant IRC logs ... so given that absolutely no-one has even bothered defending that ... lol ... "consensus" ... or otherwise provided any evidence of its existence, you might actually be obliged to provide some. It'd certainly help. Regards, Deacon of Pndapetzim (Talk) 20:57, 27 January 2008 (UTC)
I am sorry to see that you are continuing to make accusations of bad faith with no evidence. I am interested in a discussion aimed at building consensus. Truth be told, I am unconcerned as to the merits of this proposal, but I have been shocked at the way you have attempted to bulldozer your ideas through, by pretending that there has never been any consensus, trying to cover up evidence of it, and making personal attacks. Why not simply put forward your proposal, with the arguments in favour, and invite discussion? Warofdreams talk 21:24, 27 January 2008 (UTC)
Chatise me for bad faith, fair enough. But don't do that and then say you have attempted to bulldozer your ideas through, by pretending that there has never been any consensus, trying to cover up evidence of it, and making personal attacks, as that is much worse faith, and is simply untrue in any case. I don't need to pretend it doesn't exist. It doesn't, as you should know. And I am not the one "bulldozing" ... my edits to the main page settled at "Under discussion", whereas yours are an attempt at imposing a guideline that has yet to be defended, and is opposed by many people. And "personal attacks"? Where? Utter nonsense. Please participate in the discussion rather than continuing with this stuff. Deacon of Pndapetzim (Talk) 21:30, 27 January 2008 (UTC)
I am not interested in replying to your baseless accusations. I will participate in the discussion below. Warofdreams talk 00:02, 29 January 2008 (UTC)
"by pretending that there has never been any consensus". There hasn't - as I have demonstratively shown above (including the fact that your comments in one of those pieces of "consensus" is the diametrical opposite of the page moves you have been making!). AGF claims work both ways - as your comments above prove - since "attempted to bulldozer your ideas through", "by pretending", "trying to cover up evidence", are all complete failures of AGF. SFC9394 (talk) 21:37, 27 January 2008 (UTC)
I'd like to just say (during a period where I'm struggling for editting time) that I didn't add new guidelines as such, I merely elaborated on them. The guidelines stated they were for the United Kingdom but only tackled England. I made this clear in the edit summary and based this on the disambiguation I've seen already established for Scottish settlements inline with WP:BOLD. I don't have a problem with them being revisted and scruntenised, but do have a problem with nasty targetted messages implying I acted in bad faith. I had the articles best interests at heart and don't believe my elaboration was at all bad faith. I stand-by it. It would have been nice to have been invited here to explain my edits. -- Jza84 · (talk) 22:45, 1 February 2008 (UTC)

Existing practice

I have had a look at the titles of articles in some of the subcategories of Category:Towns in Scotland and Category:Villages in Scotland. It looks like the existing practice (which is likely to represent the current consensus) has been to name articles with the simple town/village name where possible, and to add ", <council area>" where disambiguation is needed. The three choices are therefore:

  1. do nothing (and risk this situation arising again)
  2. codify the existing practice (and probably fix the few current exceptions)
  3. establish a new guideline and move articles that don't conform.

Any new conventions would likely involve either changing the word(s) after the comma, changing from comma to parentheses, and/or mandating that all article titles should have a qualifying word(s) (usually called pre-disambiguation by detractors). Any of these changes would have lively debate in this forum, based on prior experiences here. --Scott Davis Talk 05:44, 28 January 2008 (UTC)

The majority of placenames in Scotland have no dab. I'm off on wikibreak now. I hope no-one tries to reinstate those guidelines again, it's really bad to do that. All I can add to the debate just now is to say that use of the Council X looks more absurd the more famous the place is. I hope neutrals read the concerns posted here and on Talk:Perth, Scotland. I think they need to be taken seriously. 5 different people have expressed the same opinion regarding use of these, and we're not all nutters. Regards, Deacon of Pndapetzim (Talk) 08:51, 28 January 2008 (UTC)
X, Scotland seems quite sensible bearing in mind the smaller number of settlements viz-a-viz England. However, we need to consider what to do with the Isles as often they are more logically attached to the island names as opposed to Scotland. How about this in sequence:
  1. X,Scotland / Isle Name
  2. X,Council Area where there is more than one in Scotland
And add in a appropriate disambiguation page where option 2 is required. Regan123 (talk) 19:24, 28 January 2008 (UTC)
Excellent, a constructive discussion. Either approach has some advantages:
  1. Using "Scotland" as the first choice disambiguator: it is a better known location than the council areas, it means that Perth doesn't have a disambiguator which repeats the placename, and it in no way precludes using council areas where there is more than one place of the same name in Scotland.
  2. Using the council areas as the first choice disambiguator: results in fewer cases where a second choice disambiguator is required, is the existing practice (and yes, there has been a consensus for disambiguating below national level), is more similar to the practice in Wales, England and Ireland, and allows for three major island groups to be first choice disambiguators without having to create exceptions.
I'm not really too bothered either way, although I can see the merits of changing to using Scotland. The isle proposal is entirely new, and again has some appeal - perhaps we should get some more input from WP:WPSI? Warofdreams talk 00:25, 29 January 2008 (UTC)

I've commented above and will add a note on the WPSI talk page. Having been involved in a few MOS-related discussions of late it seems to me incredible that important guidelines like 'Naming conventions' can simply be altered without any necessity either to request input from or inform those affected. The whole system is in need of a complete overhaul in my view. Ben MacDuiTalk/Walk 20:08, 1 February 2008 (UTC)

The title of this section is misleading. Many places in Scotland have the form "Placename, Scotland". This is the practice in the most commonly-edited articles. Articles with the form "Placename, Region" are often little-edited articles which were moved unilaterally without discussion. Where a commonly-edited article, like Perth, Scotland, is moved, there are usually objections. Lurker (said · done) 14:44, 2 February 2008 (UTC)