Menu

#267 profileDesc: one or more catRef

AMBER
closed-fixed
5
2011-12-08
2011-04-02
No

The content model for profileDesc allows many catRef elements, but section 2.4.3 (#HD43) implies that you should only have one catRef but indicate multiple categories in the value of @target. Seems the content model of profileDesc should be restricted to allow a maximum of one catRef or section 2.4.3 should discuss under what circumstances you might have more than one catRef.

Discussion

  • Lou Burnard

    Lou Burnard - 2011-11-02

    I think this is another example of the Guidelines offering more than one way to do it. Almost any text will need more than one catRef/@target value: you can choose either to supply them all as the value of one @target attribute, or to supply them all as separate <catref> elements. Or indeed both. I'm not certain when to apply which strategy: I suppose the latter is more appropriate if you add some new classification methods to an existing text, or if the number of such classifications is really large, but neither seems like a strong argument. If we plump for either option as the only one recommended we will break some existing documents.

     
  • Lou Burnard

    Lou Burnard - 2011-11-02
    • milestone: --> AMBER
     
  • Kevin Hawkins

    Kevin Hawkins - 2011-11-03

    Oops. Now that I revisit this, I see that I misread section 2.4.3. For clarity, though, I propose revising "fall into more than one category" to say "fall into more than one category in a taxonomy". That is, you should have as many catRefs as there are taxonomies used. (When you use more than one category in a given taxonomy, you either use @target or you somehow manage to point to all of the categories using @target.)

     
  • Lou Burnard

    Lou Burnard - 2011-11-09
    • assigned_to: nobody --> kshawkin
     
  • Lou Burnard

    Lou Burnard - 2011-11-09

    After discussion, we agree that putting all targets on a single catref is not what we would recommend. Multiple catrefs with single targets also seems a bit extreme. So need to draft recommendation about stylistic preference.

     
  • Kevin Hawkins

    Kevin Hawkins - 2011-11-09
    • status: open --> pending
     
  • Kevin Hawkins

    Kevin Hawkins - 2011-12-08

    Impelemented at revision 9915.

     
  • Kevin Hawkins

    Kevin Hawkins - 2011-12-08
    • status: pending --> closed-fixed