Lists of members for classes/macros are confusing

[joeytakeda]

Following the reconfiguring of attribute lists in #592 ("Attribute lists are confusing"), I think model class spec pages should also have a more expanded view to be less confusing:

E.g. The table for model.paraPart is very difficult to parse to figure out how elements are enrolled into the class:

Members: model.gLike [g] model.global [model.global.edit [addSpan app damageSpan delSpan ellipsis gap space witDetail] model.global.meta [alt altGrp certainty fLib fs fvLib index interp interpGrp join joinGrp link linkGrp listTranspose precision respons span spanGrp substJoin timeline] model.global.spoken [incident kinesic pause shift vocal writing] model.milestoneLike [anchor cb fw gb lb milestone pb] model.noteLike [note noteGrp] figure metamark notatedMusic] model.inter [model.attributable [model.quoteLike [cit quote] floatingText said] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.egLike [eg egXML] model.labelLike [desc label] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation listWit table] model.oddDecl [classSpec constraintSpec dataSpec elementSpec macroSpec moduleSpec outputRendition specGrp specGrpRef] model.stageLike [camera caption move sound stage tech view] castList] model.lLike [l] model.phrase [model.graphicLike [binaryObject formula graphic media] model.highlighted [model.emphLike [code distinct emph foreign gloss ident mentioned soCalled term title] model.hiLike [hi q] ] model.lPart [caesura rhyme] model.pPart.data [model.addressLike [address affiliation email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName nameLink persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] climate location population state terrain trait] eventName idno lang objectName rs] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del handShift mod orig redo reg restore retrace secl sic supplied surplus unclear undo] ] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml [att gi tag val] model.ptrLike [listRef ptr ref] model.ptrLike.form [oRef pRef] model.segLike [c cl m pc phr s seg w] model.specDescLike [specDesc specList] ruby] lg

I think it would be much better to have a similar system as the attributes that goes:

• CLASS: ELEMENT ELEMENT
  • CLASS: ELEMENT ELEMENT

For example:

• model.gLike: g
• model.global: figure metamark notatedMusic
  • model.global.edit: addSpan app damageSpan delSpan ellipsis gap space witDetail
  • model.global.meta: alt altGrp certainty fLib fs fvLib index interp interpGrp join joinGrp link linkGrp listTranspose precision respons span spanGrp substJoin timeline
  • model.global.spoken: incident kinesic pause shift vocal writing
  • model.milestoneLike: anchor cb fw gb lb milestone pb
  • model.noteLike: note noteGrp
• model.inter: castList
  • model.attributable: floatingText said
  • model.quoteLike: cit quote
  • model.biblLike: bibl biblFull biblStruct listBibl msDesc
  • model.egLike: eg egXML
  • model.labelLike: desc label
  • model.listLike: list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation listWit table
  • model.oddDecl: classSpec constraintSpec dataSpec elementSpec macroSpec moduleSpec outputRendition specGrp specGrpRef
  • model.stageLike: camera caption move sound stage tech view