Work on 567

[sydb]

This change implements 567 by changing the content models of the following elements as per the description on the ticket. This fix has a non-backward compatible change: a member of model.milestoneLike is no longer allowed as the only child of <listBibl>. I consider the fact that such was allowed a corrigible error. (For supporting evidence I note that there are no examples of it in the Guidelines, nor am I aware of any prose discussing what the BLEEP it would mean.)

I did not remove <listRelation> from model.biblPart, per my comment on the ticket of 2017-11-20, to wit that:

• the (only) effect would be to remove <listRelation> as a possible child of <bibl>;
• that would obviously break backward compatibility;
• <bibl>s can clearly have relations to at least other bibliographic items (n.b. <relatedItem>), if not people, places, and things.

Thus I think if we want to remove <listRelation> from model.biblPart, that would require another ticket and a separate discussion.

I did not change any examples that had <relation> as a direct child of <listSomething>, because there were none.

Elements changed:

• <listBibl>
• <listEvent>
• <listNym>
• <listObject>
• <listOrg>
• <listPerson>
• <listPlace>
• <listRelation>

[lb42]

A bibl containing only milestone like elements and text is entirely possible. You might want to indicate formatting only. Please think again.

[sydb]

Sorry, @lb42, that was my fault … the comment should have said “listBibl”, not “bibl”. While you are obviously correct that <bibl> should be allowed to have text & milestones (one wonders why not text & model.global, though), I think you will agree that a <listBibl> should have at least one bibl-like-thing in it.
I will see if I can edit the comment above …
Yup. Comment edited, which means future readers will, at first blush, think we are being bizzarre.

[peterstadler]

changes look appropriate and my local build of the schemas was successful – thanks @sydb