Hi all, Re this ticket: https://sourceforge.net/p/tei/feature-requests/546/?page=1 I was under the impression from our discussion at the FtF that my job was to present the case for removing defaultVals one by one, and then remove them if Council did not object. However, Syd points out that this should be done through deprecation, so I've now added @validUntil on <defaultVal> on att.fragmentable/@part. We'll see what shows up in the Guidelines build as a result -- I'm not sure whether there's adequate handling in the Stylesheets for it. Meanwhile, I've generated a complete list of atts with defaultVal here: http://wiki.tei-c.org/index.php/DefaultVal_candidates_for_removal since that seems to be what Syd was expecting. He was tasked with removing those which are on required attributes, but there don't seem to be any of those. Cheers, Martin
And it turns out @validUntil is not valid on <defaultVal>. I didn't notice that because the nvdl validation is not working, we think because of an Oxygen problem. So: shall we add <defaultVal> to att.deprecated so I we can put @validUntil on it? Cheers, Martin On 15-06-03 11:38 AM, Martin Holmes wrote:
Hi all,
Re this ticket:
https://sourceforge.net/p/tei/feature-requests/546/?page=1
I was under the impression from our discussion at the FtF that my job was to present the case for removing defaultVals one by one, and then remove them if Council did not object. However, Syd points out that this should be done through deprecation, so I've now added @validUntil on <defaultVal> on att.fragmentable/@part. We'll see what shows up in the Guidelines build as a result -- I'm not sure whether there's adequate handling in the Stylesheets for it.
Meanwhile, I've generated a complete list of atts with defaultVal here:
http://wiki.tei-c.org/index.php/DefaultVal_candidates_for_removal
since that seems to be what Syd was expecting. He was tasked with removing those which are on required attributes, but there don't seem to be any of those.
Cheers, Martin
participants (1)
-
Martin Holmes