search

DigitalLatin / guidelines

A repository for the LDLT Guidelines
GNU Affero General Public License v3.0
0 stars 3 forks source link

Require xml:id on <app>? #38

Open sjhuskey opened 6 years ago

sjhuskey commented 6 years ago

It might be helpful for those wishing to work with the data on their own to require @xml:id on every <app>.

adunning commented 6 years ago

I feel as if I am missing something here, but it may be worth remarking that, if enforced by the schema, this would make manual encoding much more difficult. Right now, I can use a fill-in snippet in TextExpander (or indeed Oxygen) to produce valid XML and only have to type the variants, but having to come up with an ID for every use of <app> would prevent this.

sjhuskey commented 6 years ago

It's definitely a trade-off. The concern is whether or not we want the individual app elements to be citable in a CTS or CTS-like scheme. In that case, it's essential for them to have ids.

hcayless commented 6 years ago

I've thought for a while that we might need both a work-in-progress schema and a final product schema. IDs are trivial to add with a script/XSLT/XQuery pass, but possibly too much burden on human editors. At the same time, there are scenarios where IDs are crucial, because the logic of the document demands linking between elements.