#152 multiple origDate elements

[Simona Stoyanova]

Proposition that we recommend using multiple origDate elements for different dating coming from different publications, rather than using certainty and pointing to attributes as some projects have done so far. Example from ISicily where one publication suggests a concrete date and another publication a range, making the use of certainty impractical:

369 CE (Ferrua); 417—22 (Manganaro)

Apart from having different attributes for the dates here, I also need to give two different sources, so I would much rather use two separate origDate elements. Have checked the behavious in EFES and both origDates are displayed fine, we only need to add a line to the XSLT to display a semicolon or something between the two. Plus a paragraph in the guidelines and an example in the training documents.

Thoughts and suggestions welcome!

[BODARD Gabriel]

This needs to be addressed, sooner rather than later, but not for the May 2022 release.

[Elli Mylonas]

Ask for examples on Markup so we can add them to the Guidelines, as well as an example of one template that handles mutliple origDates. Should it be in htm-tpl-struct-sample?