TEI P5 permits <schemaSpec> as a repeatable child of a variety of elements (<front>, <body>, <back>, <encodingDesc>, <div>, or any numbered division element). But roma only processes the first <schemaSpec> found (in document order), unless the user specifies which <schemaSpec> should be processed (by specifying its @ident as the $selectedSchema parameter).
The p5odds schema makes no changes to this permissiveness.
The tei_customization schema issues an error message unless there is one and only one <schemaSpec> in the customization ODD.
(And note that ATOP has no intention of doing anything intelligent if a customization ODD has more than one <schemaSpec>.)
We (@sydb & @martindholmes) think the constraint used in tei_customization should be brought forth into P5 proper.
TEI P5 permits
<schemaSpec>as a repeatable child of a variety of elements (<front>,<body>,<back>,<encodingDesc>,<div>, or any numbered division element). But roma only processes the first<schemaSpec>found (in document order), unless the user specifies which<schemaSpec>should be processed (by specifying its@identas the $selectedSchema parameter).The p5odds schema makes no changes to this permissiveness.
The tei_customization schema issues an error message unless there is one and only one
<schemaSpec>in the customization ODD.(And note that ATOP has no intention of doing anything intelligent if a customization ODD has more than one
<schemaSpec>.)We (@sydb & @martindholmes) think the constraint used in tei_customization should be brought forth into P5 proper.