Feb 052011
 

LG5P98: :

  1. LG5PBC: What is it?

    1. LG5PC9: To organize Having post(s) to explicitly define a WordPress category, this is a “meta”-category where:
      1. LG5Q7U: for each post which defines category(s)
        1. LG5QBS: for each category which a post defines,
          1. LG5QG3: the post is placed in a immediate subcategory (of that that category) named “(definition LG5DEF)  of <parent/> <a universal ID/>”
            1. LG5QL6: Example: If a post defines with the category Meetup.com LFFLFN means, then it is placed in (Meetup.com LFFLFN/(definition LG5DEF) of (Meetup.com LFFLFN) LG6X84)
            2. LG8Q9L: The fact that the definition category is an immediate subcategory of the category it defines: Why (Pros thru cons)
              1. LG8QBN: Big Pro: when the category contents is listed, since subcategories are also listed, this means the category definition(s) will be listed, too (and hopefully 1st).  This is good as they can significantly explain membership of the category and usually definitions take very little space especially compared to the potentially-unlimited members.
              2. LG8QGN: Con: this classification is a violation that a subcategory is a subset of a parent category, as a definition is not a subset of a topic (for instance the definition of human is not itself a human, it’s a definition) unless of course the category being defined is itself a category of “definitions”. Having the exception here bothers me but I don’t see a bad problem with it (at least not yet).
            3. LG7LYO: Renamed subcategory from/to:
              q[(definition LG5DEF) <a universal ID/>]
              q[(definition LG5DEF)  of <parent/> <a universal ID/>]

              1. LG7M4N: As renamed example from/to:
                q[(definition LG5DEF) LG6X84]
                q[(definition LG5DEF) of (Meetup.com LFFLFN) LG6X84]
              2. LG7M6V: Why?
                1. LG7M7E: BIG PRO: some key places the category was displayed it’s parent wasn’t displayed with it, so, without lookup, it was unclear just by the category’s ID what the parent was (so what was being defined)
                  1. LG7MAE: Not in the normal nested categories view but
                  2. LG7MC5: In  http://2.loverules.info/wp-admin/post.php (editor) after categories were selected (selected would be floated to the top so loose their parent)
                  3. LG7MKU: In http://2.loverules.info/wp-admin/edit-tags.php?taxonomy=category (surprisingly the parent column is missing in latest WordPress 3.0.4)
                  4. LG7N4Z: If copying the category (say from the themed category list) in order to reference it, you would then reference the whole thing.
                    1. LG7NNH: Example: instead of having to say (& create/copy) the 2 link (Meetup.com LFFLFN/(definition LG5DEF) LG6X84) we could just put the 1 link (definition LG5DEF) of (Meetup.com LFFLFN) LG6X84.
                2. LG7MPK: Pro: This IS in fact the full name of the category, so one is best to include it.
                3. LG7MR1: Pro: I include the parent 2nd here rather than 1st, specifically “<child/> of <parent/>” instead of “<parent/> <child/>”, as:
                  1. LG7MYZ: Big Pro: for readability in the nested category view (as we know the ” of <parent/>” part there, so have it trailing)
                  2. LG7MZA: Pro: ” of ” is clearer the relationship rather than inferring based on “<1st_expression/> <2nd_expression/>”
                4. LG7N7X: Con: this introduces the maintenance: if the parent renames, then the subcategory will also have to be renamed
                  1. LG7NAF: Example: if Meetup.com LFFLFN renames then (definition LG5DEF) of (Meetup.com LFFLFN) LG6X84 also will need to be renamed.
                  2. LG7NC4: This isn’t too bad because
                    1. LG7NDX: Category renaming doesn’t break internal links but does break external links (the latter should be fixed)
                    2. LG7NEY: Including the <a universal ID/> in the name allows category renaming to be automated.
        2. LG5Q9I: the post is placed in this category definition LG5DEF (ideally, as this could be inferred by the prior).
          1. LG5QNG: Example: If a post is a member of definition LG5DEF) of (Meetup.com LFFLFN) LG6X84 then it is also a definition, so should be placed in definition LG5DEF. And ideally software would automatically place it there.
    2. LG5PPQ: I forged the special universal ID “LG5DEF” since one probably have to remember & type this, yet this still keeps this a universal ID.
    3. LG5QVP: I created a category for this post: q[definition LG5DEF/(definition LG5DEF) of (definition LG5DEF) LG5QVP]
  2. LG8PNS: Consequences are quite flexible structure

    1. LG8POR: One can have a post which defines several categories at once, such as
      1. LG8Q38: a category and all its missing parent categories:
        1. LG8PSP: Example.
      2. LG8Q4T: a glossary, legend, or other definition list.
    2. LG8PTR: One can have a post which does that (defines some category(s)) plus talks on (so is a member of) the category(s) which it defines.
    3. LG8PXW: While it may not always be the best idea, one can have post defines does that (defines some category(s)) and talks of other topics (ideally under which it’s categories) even though none of these are the category(s) it defines.
  3. LG5SBH: Usage

    1. LG5SEF: On 2.LoveRules.Info and ideally elsewhere,
      1. LG5SDS: This replaces category (Category LG5JPD) (~70% complete) (to be continued)