Option to define the hierarchical tag structure once

@danitrusca
I think, one of reasons for introducing nested tags was to allow namespacing.
E.g. to treat #category1/tag2 as different from #category2/tag2, different from #tag2.

Somebody might write you some plugin/script which does:

For each file/block/line/...
	If file/block/line/... contains #tag2, then:
		Remove #tag1
		Replace #tag2 by #tag1/tag2

If you do not want that, you will realy need to do global search and replace in some text editor.

I think, suggested implicit relationships could be declared and analyzed in Neo4j Graph View Plugin which parses file contents independently of Obsidian parser AFAIK. Author @Emile would just need to include tags as recognized relationships. I do not use tags and I think they are not processed now.