Why does "Tags" vs "tags" property name affect tag color display?

[Wanten]

I noticed that when I use “Tags” (capitalized) as a property name, the tag values display without purple highlighting (screenshot 1). But when I use “tags” (lowercase), all tag values show with proper purple highlighting (screenshot 2).

Is this intentional behavior? Which format is correct? (I assume lowercase “tags” is standard.) Why does Obsidian allow capitalized “Tags” as a property name if it breaks tag highlighting? Also, why does only “tags”/“Tags” trigger this behavior (other words like “eags” or “eggs” don’t work as tag properties)?

[blue_emperor]

According to GPT-4o mini key values in Yaml are case-sensitive so Tags is considered distinct from tags.

Here are reserved properties:

So your list property is formatted as tag format when you use tags and not Tags because Tags is consired distinct from tags in Yaml.

 

https://help.obsidian.md/properties#Property+format

[ariehen]

@blue_emperor

According to GPT-4o mini

Please don’t post chatbot help. Thanks.

The screenshot of the default properties and a test is fine.

[blue_emperor]

You right. If Tags would be considered equivalent to tags then this would be mentioned under Default properties.

[Wanten]

@blue_emperor

GPT-4o mini key values in Yaml are case-sensitive

@ariehen

Please don’t post chatbot help.

I think what @blue_emperor was trying to say might have been misunderstood.
He wasn’t really posting chatbot help, but pointing out that YAML keys are case-sensitive, so Tags and tags would be treated as different properties. He was just speculating that Obsidian might handle them the same way.

So his reply wasn’t chatbot assistance, but rather an explanation based on YAML rules.

[ariehen]

@Wanten

I read and understand what’s happening here, but when you lead with

According to GPT-4o mini

it’s not a good look so mentioned it.

[Wanten]

Got it, thanks for pointing that out.

[digitaldoctors]

case-sensitive YAML is quite enduser unfriendly.
Is there a reason it is case-sensitive ?

Obsidian seems quite thorough in trying to “make sense”. Pluralizing things is an example.

case sensitive YAML seems quite non-Obsidian.

IMO.

[CawlinTeffid]

@digitaldoctors

Is there a reason it is case-sensitive ?

YAML, the language that properties are written in, is case sensitive (or at least the keys are).

The autocomplete suggestions in the properties editor should handle the problem. Outside of the editor (in source mode), Obsidian is more hands off. Unfortunately YAML’s friendly look hides a lot of pitfalls; that’s one of the reasons why the properties editor was built.