The Most Legit Use of Namespaces

[gax]

@Ngungu

I guess I won’t be confronted with the issue because I always try to use unique page names. To take the apple example, I would call 1 of the 2 pages Apple-company and the other Apple-fruit, so a search for apple would yield 2 results.

There are a couple of good reasons to use real namespaces instead of unique names

• A namespace tells you what the namespace, and what the name is. Is Apple-fruit in namespace “fruit”, or is “Apple-fruit” some common name? What about “Mary-Jane”?
• you can use search functionality to query namespaces (see also other answers from @Siferiax ), Logseq doesn’t know that “Apple-fruit” is a fruit.
• one might be required to use certain names for compatibility with other users (e.g. courts use naming conventions like “Exhibit A”)
• two people might have picked the same name, and you want to merge the graphs
• print is a name of the function, and it wouldn’t be a good idea to rename it everywhere to print_std)
• if you have a given taxonomy, you wouldn’t want to rename the individual groups to avoid conflicts with your own preexisting tags. E.g. you decide to classify animals. A housecat would be under
  Animalia > Chordata > Mammalia > Carnivora > Feliformia > Felidae> Felinae > Felis > F. catus. (I am using “>” to show that we are not talking about the namespace operator “/” in Logseq.
  But what if you already have a page “Felidae” (for the movie)?. You could rename “Felidae” into “Felidae-animal-kingdom”, but now you are not using the established naming scheme for animals, but your own. This will cause confusion. So instead, you create a page for each group in its own namespace AnimalTaxonomy/Animalia … AnimalTaxonomy/F. catus. Then each page gets a property that tells which parents (one or more) it has.
• If you use namespaces, you get some syntax checking when you enter the names. Otherwise it’s really easy to accidentally end up with lot’s of synonyms, like Apple-company, Apple-business, Apple-corporation, Apple-corp etc.
• You can rename namespaces in bulk (still needs a script, but hopefully will eventually be part of a tag management UI)

@Ngungu

After that I make a page for each chapter or group of chapters that deal with a specific issue. In the page properties I have a property called parent, and I put a link to the parent there.

That’s a good way to do it.

If you want to dig deep, look at these posts: Specify and display relations between pages/tags , Would a rich commitment to hierarchies and classification be an anathema to Logseq culture? , Knowledge Management for Tags / Tag Hierarchies