Tags and Terms for Types of Workflow?

Question

SDL Tridion 2013 has Bundle (multi-item) workflow. How should we 1) tag and 2) refer to the editing workflow in previous versions (in question and answer text)?

I've heard a few phrases such as:

• Legacy workflow (it's the same engine, only VBScript would be "legacy")
• Classic workflow
• Single-item (editing) workflow

Preferences on how to distinguish between the two types? Should we wait for the documentation?

Update (thanks, David)--the docs have:

• Bundle workflow
• Task workflow
• Programmatic workflow
• Classic editing workflow

I don't think we need separate tags and accepted Bart's answer.

Answer 1

Do we require a specific tag and name, what is wrong with just tagging questions with 2011 workflow or 2013 workflow, that indicates nicely what version and the question can indicate whether it is related to a editing workflow or bundle workflow?

Then if people start to create tags like editing-workflow or bundle-workflow we can always consider to give them a proper wiki description or suggest them as a synonym.

Since we cannot create a taxonomy structure in our tags, I would think it makes most sense to try and keep the amount of tags as low as possible (using synonyms to force alternative namings to be automatically replaced by its parent).

Answer 2

I, for one, hate that "Legacy workflow" term. As far as I know, the only legacy thing in 2013's implementation of workflow is VBScript automatic activities. All processes are running under the same workflow engine.

If you wanted a definitive list for the different types of workflow there's a pretty good page in the documentation.