Background Pony #7C7A
[@Background Pony \#52BA](/forums/tagging/topics/general-tag-discussion?post_id=5235701#post_5235701)
> Sorry, I don’t understand how that relates to the rest of your post.
With that method, you wouldn't need to tag expected facts, as they would be inferred. You would only tag unexpected tags. E.g. you would tag something like: "rainbow dash (Q1234), depicted as (P456): alicorn (Q7890)". There would be no need to tag "rainbow mane" because it would be inferred unless you indicated otherwise.
> Well, that is why there are both frog and frog (hoof) here.
Yes, but "frog (hoof)" needed to be extracted manually from "frog". And people still use the wrong tag from time to time. There are more tags with multiple meanings (especially for popular OC names) and the decision which meaning remains simple and which gets the parentheses can be a point of contention. Basically, "frog (hoof)" is a workaround, not a true solution.
> OK, but how do they get presented to people - what shows up in the tag field?
When searching/tagging, the label and description show up. But we could show an image too to make the search more useful.
[@UnderwoodART](/forums/tagging/topics/general-tag-discussion?post_id=5235850#post_5235850)
> 99% of people will have no idea what “Q172172” is
Qids like Q1234 are used internally as unique identifiers, but users see labels and descriptions. Try typing, for example, "kiwi" in Wikidathea's search bar. Other implementations could additionally show images or alternative names. They could have other fancy things like tag category colors (as we have now on Derpibooru).
> That’s all fine and dandy, as long as the data exists. It doesn’t help for original characters or locations without some kind of secondary repository for cataloguing characters, creators, and colour details.
Yes, some kind of overlay would be needed if we actually used Wikidata. However, Wikidata was just an example and we could have our own smart tag system. The system could also be shared with other fandoms to share the maintenance burden. Actually, such a shared system would be interesting because you could have one booru for all kinds of art and still only see the things you want to see (MLP content), while hiding things you don't want to see (art from other shows, non-MLP furry stuff and anime, and so on).
> Sorry, I don’t understand how that relates to the rest of your post.
With that method, you wouldn't need to tag expected facts, as they would be inferred. You would only tag unexpected tags. E.g. you would tag something like: "rainbow dash (Q1234), depicted as (P456): alicorn (Q7890)". There would be no need to tag "rainbow mane" because it would be inferred unless you indicated otherwise.
> Well, that is why there are both frog and frog (hoof) here.
Yes, but "frog (hoof)" needed to be extracted manually from "frog". And people still use the wrong tag from time to time. There are more tags with multiple meanings (especially for popular OC names) and the decision which meaning remains simple and which gets the parentheses can be a point of contention. Basically, "frog (hoof)" is a workaround, not a true solution.
> OK, but how do they get presented to people - what shows up in the tag field?
When searching/tagging, the label and description show up. But we could show an image too to make the search more useful.
[@UnderwoodART](/forums/tagging/topics/general-tag-discussion?post_id=5235850#post_5235850)
> 99% of people will have no idea what “Q172172” is
Qids like Q1234 are used internally as unique identifiers, but users see labels and descriptions. Try typing, for example, "kiwi" in Wikidat
> That’s all fine and dandy, as long as the data exists. It doesn’t help for original characters or locations without some kind of secondary repository for cataloguing characters, creators, and colour details.
Yes, some kind of overlay would be needed if we actually used Wikidata. However, Wikidata was just an example and we could have our own smart tag system. The system could also be shared with other fandoms to share the maintenance burden. Actually, such a shared system would be interesting because you could have one booru for all kinds of art and still only see the things you want to see (MLP content), while hiding things you don't want to see (art from other shows, non-MLP furry stuff and anime, and so on).