close

help: tag implications »

Already familiar with tag implications? See the quick reference guide for a list of concise guidelines.

Tag Implications

Suppose you tag a post with miniskirt. Miniskirts are simply a type of skirt, so ideally you would like for people who search for skirt to see your miniskirt post. You could tag your post with both skirt and miniskirt, but this starts to get tedious after awhile.

Tag implications can be used to describe is-a relationships, like this one. A miniskirt is a type of skirt. When a miniskirt → skirt implication is created, Sankaku Channel listens for the miniskirt tag. Then, whenever a user adds miniskirt to a post, the server automatically tags that post with skirt. (For the technically minded, the tag is normalized before it is saved to the database.)

Tag implications are comprised of two tags: a predicate and a consequent. The predicate is the tag for which Sankaku Channel listens. In the previous example, the predicate is miniskirt. The consequent is the tag which the server adds as a response. In the example, the consequent is skirt.

You can have multiple implications for the same predicate; Sankaku Channel will add all of the matching consequent tags. If we were to also create a miniskirt → female_clothes implication, for example, the addition of 'miniskirt' would expand to 'miniskirt skirt female_clothes'.

Implications can also be chained together to form a hierarchy. Instead of implicating miniskirt → female_clothes, like above, we could create a skirt → female_clothes implication. Combined with the existing miniskirt → skirt implication (essentially yielding miniskirt → skirt → female_clothes), the end result would be the same as above.

The implication process occurs AFTER the alias process.

It's easy to go overboard with implications and important not to create them for frivolous things. For instance, we could theoretically implicate everything to an 'object' tag, but this is pointless and only adds bloat to the database. So, when considering implications, look for tags which users are likely to employ in their searches. For cases where the predicate and the consequent are synonymous, aliases are a much better idea as they have lower overhead.

While you can suggest new implications, only an administrator can approve them.

Was your implication request rejected? Stay tuned for an article that outlines the most common reasons, coming soon.