<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (earth2marsh)</title>
    <link>https://pinboard.in/u:earth2marsh/public/</link>
    <description>recent bookmarks from earth2marsh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://unstats.un.org/unsd/geoinfo/ungegn/wgGuidelines.html"/>
	<rdf:li rdf:resource="https://community.openstreetmap.org/t/gulf-of-america-gulf-of-mexico/124571/49"/>
	<rdf:li rdf:resource="https://phagesdb.org/namerules/"/>
	<rdf:li rdf:resource="https://www.digdeeproots.com/articles/naming-as-a-process/"/>
	<rdf:li rdf:resource="http://hopperanddropper.com/syllables-scrabble-letters-and-picking-brand-names/"/>
	<rdf:li rdf:resource="https://cloudplatform.googleblog.com/2017/10/API-design-choosing-between-names-and-identifiers-in-URLs.html"/>
	<rdf:li rdf:resource="https://medium.com/startup-grind/google-home-vs-alexa-56e26f69ac77#.cykdt9fvw"/>
	<rdf:li rdf:resource="http://www.kristaseiden.com/events-best-practices-for-hierarchies-and-naming-conventions/"/>
	<rdf:li rdf:resource="http://www.businessinsider.com/where-did-slack-get-its-name-2016-9"/>
	<rdf:li rdf:resource="http://arlobelshee.com/good-naming-is-a-process-not-a-single-step/"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Hungarian_notation"/>
	<rdf:li rdf:resource="https://groups.google.com/forum/#!msg/swagger-swaggersocket/ATKYZrTH9Eg/zwPzf1MwLQAJ"/>
	<rdf:li rdf:resource="http://sfstreets.noahveltman.com/#17710"/>
	<rdf:li rdf:resource="http://www.washingtonpost.com/blogs/govbeat/wp/2015/03/06/these-are-the-most-popular-street-names-in-every-state/"/>
	<rdf:li rdf:resource="http://en.wikipedia.org/wiki/Reification_(fallacy)"/>
	<rdf:li rdf:resource="http://www.tbray.org/ongoing/When/200x/2006/01/09/On-XML-Language-Design"/>
	<rdf:li rdf:resource="http://martinfowler.com/bliki/TwoHardThings.html"/>
	<rdf:li rdf:resource="http://www.tbray.org/ongoing/When/200x/2005/12/23/UPI"/>
	<rdf:li rdf:resource="http://scienceblogs.com/notrocketscience/2009/05/baby_names_suggest_that_cultural_trends_are_abandoned_more_r.php"/>
	<rdf:li rdf:resource="http://kk.org/ct2/2008/07/googleunique-names.php"/>
	<rdf:li rdf:resource="http://www.psychicwhois.com/"/>
	<rdf:li rdf:resource="http://entrepreneurs.about.com/cs/gettingstarted/ht/business_name.htm"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://unstats.un.org/unsd/geoinfo/ungegn/wgGuidelines.html">
    <title>UNGEGN - United Nations Group of Experts on Geographical Names</title>
    <dc:date>2025-01-28T23:27:06+00:00</dc:date>
    <link>https://unstats.un.org/unsd/geoinfo/ungegn/wgGuidelines.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Guidelines for guidelines!
<blockquote>At the Third United Nations Conference on the Standardization of Geographical Names held in Athens in 1977, the gathering and dissemination of toponymic information were discussed. The great variation in approaches from country to country, led Josef Breu, elected as UNGEGN Chair in 1977, to initiate the compilation of Toponymic Guidelines, with a sample from Austria submitted to the Eighth Session of UNGEGN in 1979 (W.P. 5).

Recommendations have been made, and updated, concerning the content of Toponymic Guidelines, and the subject is retained as an UNGEGN and Conference agenda item. Guidelines have been presented as technical documents, published in World Cartography, published by individual countries, or made available on websites. 40 countries have now issued Toponymic Guidelines, with a number of countries having developed several editions since 1979. Other countries are encouraged to make their material available for editors worldwide.</blockquote>]]></description>
<dc:subject>geography mapping names naming standards guidelines</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:bcf6a1347104/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:geography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mapping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:guidelines"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://community.openstreetmap.org/t/gulf-of-america-gulf-of-mexico/124571/49">
    <title>Gulf of America - Gulf of Mexico - General talk - OpenStreetMap Community Forum</title>
    <dc:date>2025-01-28T23:23:40+00:00</dc:date>
    <link>https://community.openstreetmap.org/t/gulf-of-america-gulf-of-mexico/124571/49</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>name=* is defined as the primary name of the feature. For a feature in the natural environment, the primary name generally comes from either common or official usage (as opposed to a small placard someone found somewhere). The more well-known and widely known a natural feature, the more credence we typically give to common usage in case of conflict with official usage.

According to the multilingual name tagging scheme 1, name:*=* subkeys conform to the IETF’s BCP 47 standard, so name:en=* is defined as the primary name in the English language. We’re inconsistent about whether this is the name in the local dialect of English or according to a consensus of English dialects. For example, name:en=United States 1 follows common American English, not the official name or the customary name in British English. On the other hand, name:en=Salt Lake City 1 differs from the local dialect, which calls the city simply “Salt Lake”. But in these cases, neither name is particularly controversial, and user comprehension doesn’t suffer greatly from the use of one or the other.

BCP 47 also allows us to pair a language code with an ISO country code as shorthand for a “dialect”, so name:en-US=* would indicate the primary commonplace name in American English. Some languages like Chinese 2 and Portuguese 1 use country-qualified codes fairly frequently to accommodate different dialects. English doesn’t normally have so many naming differences that fall neatly along national dialectal lines. Usually our differences are about more practical matters, like what to call association football. In fact, American English is an umbrella term for the multitude of dialects of English spoken in the United States 2.

Unfortunately, this dialect tagging scheme clashes with the Data Working Group’s officially documented approach for indicating a geopolitical naming dispute 1. For example, the Vietnamese government takes the position that the South China Sea should be called the “East Vietnamese Sea” in English, contrary to what the Chinese and Philippine governments would prefer. Conversely, the U.S. federal government accepts the Vietnamese government’s name for Ho Chi Minh City 2, but ordinary Vietnamese speakers in the U.S. refuse to call the city by this name 14 or let anyone else do so domestically. Few linguists recognize a “Vietnamese English” dialect or “American Vietnamese” dialect, but name:en-VN=* and name:vi-US=* can be understood as the names that would be commonplace in Vietnam when using English and in the U.S. when using Vietnamese, whatever the reason.

These country-qualified names discourage edit wars and politically motivated vandalism that contradicts the project’s consensus about the on-the-ground rule. So far, since I’ve added name:vi-US=* to Ho Chi Minh City, no one has unilaterally changed name:vi=* to Sài Gòn. This seems to work better than just adding alt_name=* or old_name=*, because name:vi-US=* appears right below the name that some people find objectionable in an alphabetically sorted list of tags. It might help that some data consumers can show the usual name to Vietnamese speakers except to those in the U.S. 3, or that search engines that index one key will likely index the other with very similar behavior.</blockquote>]]></description>
<dc:subject>geography naming gulf politics controversy openstreetmap mapping</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0f189f0f59ab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:geography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gulf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:controversy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openstreetmap"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mapping"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://phagesdb.org/namerules/">
    <title>The Actinobacteriophage Database | Naming Rules</title>
    <dc:date>2024-01-10T04:48:23+00:00</dc:date>
    <link>https://phagesdb.org/namerules/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Below are some of the hard-and-fast rules of phage naming, so please pay careful attention to them. But there may also be times when a proposed name technically satisfies all the rules below yet still may not be a good choice. Because of this, we review all phage names when you submit them, and may need to “veto” a particular name and ask you to modify or change it. The more you stick to the rules and guidelines below, the less likely it is your name will need to be modified before entering the scientific record.

Rules

Do not name your phage after Nicolas Cage.
Must be a new name. Duplicate names will be rejected.</blockquote>]]></description>
<dc:subject>humor hilarity research biology naming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:839c5a12857a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:humor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hilarity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:biology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.digdeeproots.com/articles/naming-as-a-process/">
    <title>Deep Roots - Naming as a Process (Article 1)</title>
    <dc:date>2021-06-23T01:51:50+00:00</dc:date>
    <link>https://www.digdeeproots.com/articles/naming-as-a-process/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["The source of all technical waste
Wasteful code is any code that is hard to scan. Technical waste is anything that increases the difficulty of reading code.

Me.
My focus on code reading may seem odd to many of you. After all, we’re programmers. We’re good at reading complex code, and our job is to update code. Shouldn’t the definition of technical waste be something about the cost and risk of changing code?

This is.

It turns out that the largest single thing developers spend time doing is reading code.

More than design.
More than writing code.
More than scanning.
And yes. Even more than meetings (well, probably)."]]></description>
<dc:subject>naming culture code design development practices apis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:365345d27f9a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hopperanddropper.com/syllables-scrabble-letters-and-picking-brand-names/">
    <title>Syllables, Scrabble Letters, and Picking Brand Names - Rich Barton | HopperandDropper.com</title>
    <dc:date>2020-11-28T20:03:54+00:00</dc:date>
    <link>http://hopperanddropper.com/syllables-scrabble-letters-and-picking-brand-names/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Use high-point Scrabble letters.  My wife and I love to play Scrabble (a great brand name, btw).  The highest point letters (least often used in English) are Z, Q, X, J, K.  These are memorable letters for people because they are so seldom used.  Use them in your brands.  Xerox, Kodak, Coke…]]></description>
<dc:subject>branding naming marketing names</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e5c0a2e76554/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:branding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:marketing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cloudplatform.googleblog.com/2017/10/API-design-choosing-between-names-and-identifiers-in-URLs.html">
    <title>Google Cloud Platform Blog: API design: Choosing between names and identifiers in URLs</title>
    <dc:date>2018-02-21T18:00:17+00:00</dc:date>
    <link>https://cloudplatform.googleblog.com/2017/10/API-design-choosing-between-names-and-identifiers-in-URLs.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[nicely written post by Martin Nally]]></description>
<dc:subject>apis design identifiers names resources naming url</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7cf3c099fa5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:resources"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:url"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/startup-grind/google-home-vs-alexa-56e26f69ac77#.cykdt9fvw">
    <title>Google Home vs Alexa – Startup Grind – Medium</title>
    <dc:date>2017-01-10T16:35:07+00:00</dc:date>
    <link>https://medium.com/startup-grind/google-home-vs-alexa-56e26f69ac77#.cykdt9fvw</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>design microcopy ux gender naming Alexa home Google</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f0fa311298f7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:microcopy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gender"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Alexa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Google"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.kristaseiden.com/events-best-practices-for-hierarchies-and-naming-conventions/">
    <title>Digital Debrief – Events: Best Practices for Hierarchies and Naming Conventions</title>
    <dc:date>2016-11-10T18:25:06+00:00</dc:date>
    <link>http://www.kristaseiden.com/events-best-practices-for-hierarchies-and-naming-conventions/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>google:analytics events naming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:04c1b016f441/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:google:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:events"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.businessinsider.com/where-did-slack-get-its-name-2016-9">
    <title>Slack: Where did it get its name?</title>
    <dc:date>2016-09-28T04:20:40+00:00</dc:date>
    <link>http://www.businessinsider.com/where-did-slack-get-its-name-2016-9</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>slack history name naming</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0c058cdb55d5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:slack"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:name"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arlobelshee.com/good-naming-is-a-process-not-a-single-step/">
    <title>Naming is a process, not a single step | Arlo Being Bloody Stupid</title>
    <dc:date>2016-08-16T05:42:16+00:00</dc:date>
    <link>http://arlobelshee.com/good-naming-is-a-process-not-a-single-step/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>naming programming Design refactoring development culture names</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:54be60e1ae28/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:refactoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Hungarian_notation">
    <title>Hungarian notation - Wikipedia, the free encyclopedia</title>
    <dc:date>2016-05-18T16:24:16+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Hungarian_notation</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[1. Don’t use two fields to describe the same data when one will do. (Resist the redundant boolean)
2. Just say no to Hungarian Notation.

Linus says:
> Encoding the type of a function into the name (so-called Hungarian notation) is brain damaged—the compiler knows the types anyway and can check those, and it only confuses the programmer.

Re: https://www.hl7.org/fhir/patient.html]]></description>
<dc:subject>naming variables api apis design bestpractices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0e71c5450109/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:variables"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:bestpractices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://groups.google.com/forum/#!msg/swagger-swaggersocket/ATKYZrTH9Eg/zwPzf1MwLQAJ">
    <title>Confused about where to start / Swagger vs OpenAPI naming - Google Groups</title>
    <dc:date>2016-04-13T14:50:58+00:00</dc:date>
    <link>https://groups.google.com/forum/#!msg/swagger-swaggersocket/ATKYZrTH9Eg/zwPzf1MwLQAJ</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["
I'm tasked with taking a client's new SMS (as in mobile text messaging) REST API from its current beta state to general availability. One of the tasks is a review of the documentation and any changes required to the published API and its associated docs before going GA. Having found Swagger, I'm looking into whether we should convert our existing documentation to a Swagger spec before launching the API, so that we can use Swagger tools for generating client libraries for our customers to use, web-based documentation, etc.

Something that has thrown me off a bit is the transition from Swagger to its new name (as Wikipedia puts it) of the OpenAPI Specification.  This initially left me with the assumption that most material still referring to "Swagger" would be older, even perhaps outdated or deprecated.

But after a day or so of browsing, it appears that I should pretty much ignore this rename, and just look for Swagger material. The OpenAPI site doesn't even seem to reference specific tools and frameworks, quite unlike the Swagger site. I think it has a bit of a vapourware feel, which appears to be a total injustice to the real state of things in Swagger-land. But perhaps I'm reading too much into Wikipedia's phrasing of Swagger having been _renamed_ to the OpenAPI Specification.

Could anyone set me straight, please?"]]></description>
<dc:subject>swagger openapi naming confusion examples</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:622f58f417b2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:swagger"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:confusion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:examples"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sfstreets.noahveltman.com/#17710">
    <title>History of San Francisco Place Names</title>
    <dc:date>2015-05-11T04:34:36+00:00</dc:date>
    <link>http://sfstreets.noahveltman.com/#17710</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>sanfrancisco history streets maps mapping names naming</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:02dc96af2908/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sanfrancisco"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:streets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mapping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.washingtonpost.com/blogs/govbeat/wp/2015/03/06/these-are-the-most-popular-street-names-in-every-state/">
    <title>We counted literally every road in America. Here’s what we learned. - The Washington Post</title>
    <dc:date>2015-03-07T15:43:55+00:00</dc:date>
    <link>http://www.washingtonpost.com/blogs/govbeat/wp/2015/03/06/these-are-the-most-popular-street-names-in-every-state/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>maps roads culture naming America nytimes</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:9e316091e683/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:roads"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:America"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:nytimes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://en.wikipedia.org/wiki/Reification_(fallacy)">
    <title>Reification (fallacy) - Wikipedia, the free encyclopedia</title>
    <dc:date>2014-02-13T00:16:25+00:00</dc:date>
    <link>http://en.wikipedia.org/wiki/Reification_(fallacy)</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["From Latin res thing + facere to make, reification can be loosely translated as thing-making; the turning of something abstract into a concrete thing or object"]]></description>
<dc:subject>fallacy logic naming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:bc7005652cc7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:fallacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:logic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tbray.org/ongoing/When/200x/2006/01/09/On-XML-Language-Design">
    <title>ongoing by Tim Bray · On XML Language Design</title>
    <dc:date>2012-02-12T17:37:29+00:00</dc:date>
    <link>http://www.tbray.org/ongoing/When/200x/2006/01/09/On-XML-Language-Design</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>design language software xml naming vocabulary tim_bray</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6bf4be523d5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tim_bray"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://martinfowler.com/bliki/TwoHardThings.html">
    <title>TwoHardThings</title>
    <dc:date>2011-12-01T20:24:42+00:00</dc:date>
    <link>http://martinfowler.com/bliki/TwoHardThings.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[There are only two hard things in Computer Science: cache invalidation and naming things.

-- Phil Karlton

Long a favorite saying of mine, one for which I couldn't find a satisfactory URL.

There is also a variation on this that says there are two hard things in computer science: cache invalidation, naming things, and off-by-one errors.

EDIT: see https://www.karlton.org/2017/12/naming-things-hard/]]></description>
<dc:subject>quote quotes cache philosophy naming programming caching invalidation computerscience</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cd2583e5cffe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quote"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:caching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:invalidation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:computerscience"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tbray.org/ongoing/When/200x/2005/12/23/UPI">
    <title>ongoing by Tim Bray · UCI</title>
    <dc:date>2011-06-28T17:05:03+00:00</dc:date>
    <link>http://www.tbray.org/ongoing/When/200x/2005/12/23/UPI</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["There are only two hard things in Com­puter Sci­ence: cache in­val­i­da­tion and nam­ing things." Phil Karlton

EDIT: see https://www.karlton.org/2017/12/naming-things-hard/]]></description>
<dc:subject>quotes computer science caching naming</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a272a89bbcca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:computer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:caching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://scienceblogs.com/notrocketscience/2009/05/baby_names_suggest_that_cultural_trends_are_abandoned_more_r.php">
    <title>Baby names suggest that cultural trends are abandoned more readily the quicker they catch on : Not Exactly Rocket Science</title>
    <dc:date>2009-05-06T18:38:43+00:00</dc:date>
    <link>http://scienceblogs.com/notrocketscience/2009/05/baby_names_suggest_that_cultural_trends_are_abandoned_more_r.php</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[" female names were jettisoned from popular use more quickly than male ones, although the reasons behind this faster turnover are unclear […] To find out why, Berger and Le Mens gauged the reactions of 661 expecting parents to a list of 30 names. They found that the parents were less likely to give their children names that had seen the sharpest recent rises in popularity, regardless of how popular the names were overall. This was mostly because they viewed these names as short-lived fads; when the duo adjusted their results for this perception, a name's rise in popularity no longer affected its attractiveness .  These results highlight the capricious nature of fame and popularity. Public concern that something's popularity is fleeting can make it seem less attractive, and ensure that its popularity actually is fleeting! It's a self-fulfilling effect - a meteoric rise to stardom can generate the very conditions that cause an equally swift downfall."]]></description>
<dc:subject>culture names naming trends baby</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:fe3f63837dd0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:trends"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:baby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kk.org/ct2/2008/07/googleunique-names.php">
    <title>Conceptual Trends and Current Topics</title>
    <dc:date>2008-07-30T14:40:09+00:00</dc:date>
    <link>http://kk.org/ct2/2008/07/googleunique-names.php</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Some adults may object to naming a kid like you were searching for a domain name, (or a brand), but our kids are delighted about this uniqueness and international sensibility.]]></description>
<dc:subject>naming names name identity children parenting google search unique</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0af155a977d4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:name"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:identity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:children"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:parenting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:unique"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.psychicwhois.com/">
    <title>Psychic Whois</title>
    <dc:date>2008-07-02T20:00:19+00:00</dc:date>
    <link>http://www.psychicwhois.com/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Nice ajax-y domain name suggester/availability tool.]]></description>
<dc:subject>ajax suggestion service branding domain name names naming search</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e9e4aec81757/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:suggestion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:service"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:branding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:domain"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:name"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:search"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://entrepreneurs.about.com/cs/gettingstarted/ht/business_name.htm">
    <title>Create a Great Business Name</title>
    <dc:date>2007-07-27T20:13:43+00:00</dc:date>
    <link>http://entrepreneurs.about.com/cs/gettingstarted/ht/business_name.htm</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[A great name is the beginning of a great brand. It should be memorable and create a certain feeling when heard. Here's a quick how-to on creating one and making sure it's not already used.]]></description>
<dc:subject>branding names business entrepreneurship startup company naming</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e21a38e35043/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:branding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:entrepreneurship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:startup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:company"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:naming"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>