Menu

#675 org should allow model.global

GREEN
closed-accepted
None
5(default)
2014-11-19
2014-06-09
No

I'm encoding a community directory which consists of a set of individuals interspersed with organizations (shops, businesses etc.), I'm using <listPerson>, with <person> for the individuals and <org> for the organizations. <person> has model.global in its content model, so page-breaks and column-breaks that occur within a single person's entry can be tagged with no problem, but <org> is not, so milestones are not allowed. I would suggest that these elements are parallel in function and should have similar content models including model.global.

Discussion

  • Fabio Ciotti

    Fabio Ciotti - 2014-06-30
    • assigned_to: Fabio Ciotti
     
  • Fabio Ciotti

    Fabio Ciotti - 2014-11-18

    Seems very reasonable. Only doubt, should not be <listPerson> and <listOrg>a sort of data like container? Is it correct to use them to encode features of the source document?

     
  • James Cummings

    James Cummings - 2014-11-19
    • Group: AMBER --> GREEN
     
  • James Cummings

    James Cummings - 2014-11-19

    F2F at Raleigh 2014-11-19 agrees that you must be allowed milestones in org. Assign to FC to make a reasonable content model.

     
  • Fabio Ciotti

    Fabio Ciotti - 2014-11-19
    • status: open --> closed-accepted