Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#321 make listPerson and listOrg member of model.personLike

AMBER
closed-accepted
Lou Burnard
5
2011-11-17
2011-09-21
Laurent Romary
No

Making listPerson and listOrg member of model.personLike would help going to more simplicity in several content models (at the price of generalizing a bit, I confess):
- listPerson: would add listOrg (listPerson is already referred to individually)
- org: would add listPerson and listOrg, but I think I can think of proper use cases
- particDesc: just received a request to get listOrg

Discussion

  • Laurent Romary
    Laurent Romary
    2011-09-21

    • labels: --> TEI: New or Changed Class
     
  • Lou Burnard
    Lou Burnard
    2011-11-01

    Allowing <org> and <listorg> would certainly improve the current content model of <particDesc>, but I am less certain that it's a good idea to blur the distinction between "x" and "listX" in this way.

     
  • Lou Burnard
    Lou Burnard
    2011-11-01

    • milestone: --> AMBER
     
  • Lou Burnard
    Lou Burnard
    2011-11-07

    • assigned_to: nobody --> louburnard
     
  • Lou Burnard
    Lou Burnard
    2011-11-07

    create new class model.orgPart to allow listPerson, listPlace, listOrg within org; allow listOrg within particDesc

     
  • Lou Burnard
    Lou Burnard
    2011-11-17

    New class model.orgPart with members listPerson, listOrg, listPlace added at rev 9768, added reference to it from content model of org. listOrg is already in content model of particDesc.

     
  • Lou Burnard
    Lou Burnard
    2011-11-17

    • status: open --> closed-accepted