kentsmith9 wrote:The actual structure is more about association so when you are on a page you can see the parent pages like [[Places/Areas/Parking Lot]]. That tells you this parking lot information is bound under Areas under Places.
Ah, I think I get it, since the reader can see the parent pages there is less need for an exhaustively descriptive title.
(Nomenclature quandary...the field into which we put "Parking Lot", "Shopping Center", "Swimming Pool" etc. is called out in WME as "Type". However the initial Places wiki calls it "Category" and uses the word "Type" for whether it's an Area or Point. I'll bring this up in the Places wiki thread. Meanwhile in the following I use "Type" according to the WME, not the wiki.)
It seems like we are headed towards most Place Types being either Area or Point, with very few being eligible for both. That would seem to suggest structuring the Places wiki along the lines of Places/<Type> rather than Places/Area/<Type> and Places/Point/<Type>.
For the Parking Lot wiki, we are starting with just Area but I and others have seen a number of opportunities for Point so I wrote in a a stub for that at the end of the wiki. It seems to work; the wiki discusses the primary application of Parking Lot (Area) but can then have a subheading, or perhaps a subsection, treating the secondary application (Point).
I've retitled my draft as simply "Parking Lot", with the first subsection being "Primary Application (Area or Point)" in which it's declared that Area is the primary application of the Parking Lot type. Just a strawman for now.