btremIn `h-card`, is is appropriate to use `p-name` for a neighborhood? I'm inclined to think not, but I'm not sure. Trying to decide on whether to include neighborhood in photo posts, and if so, how.
[KevinMarks]name is the default thing that's shown from an h-card, so it could make sense. The structured parts are based on vcard which have an old school postal address bias
btremLooking through old photo posts, it appears that I have somewhat inconsistently used name for neighborhood. Honestly, the bigger question is not what property name to give it, but rather how might I want to search for photos in the future? By name? By neighborhood? So I suppose this isn't much of a #microformats question.
gRegorp-locality is probably the closest since it's "city/town/village". If the neighborhood name is all you're going to display, probably makes sense to add p-name to it as well.
[dave]It’s hard to tell but I’d agree with gRegor and use p-locality. The parsed JSON output from the example of a parsed h-adr seems to imply you can have multiple of them, so if you needed to you could put e.g. “Southside” and “Fort Worth” as localities for somewhere in Southside.
gRegorIf you needed to parse and match a neighborhood name exactly, I might use multiple p-locality. Otherwise I'd probably be inclined to just put it in one, even if I combine with the city. E.g. I might use "North Park, San Diego" for the North Park neighborhood
btremThose are all useful to think about. I'll never have a neighborhood without a locality. So it'll be "South Lake Union" in "Seattle". Or "North End", "Boston". I've always thought of locality as specifically for a city or town, i.e., something incorporated in some sense. Thanks for the ideas.