Subject: FW: [dita] FW: Question to DITA TC: @keyref missing for <filepath> and <userinput> in DITA 1.3? (described in spec, but not in DTD)
I was going back through my emails and found this email from last year that I donât know whether this has been captured anywhere to fix in DITA 2.0. Is there someplace this is tracked â itâs not a needed proposal (I donât think) just a correction to the grammar files.
I can confirm that filepath and userinput do not allow @keyref in the 1.3 RNG, which is definitely an oversight.
However, this was the case in DITA 1.2 as well.
So it looks like the oversight dates back to the original addition of keyrefâthe software domain was never updated to allow keyref on elements specialized from elements to which keyref was added.
Since this has been this way since DITA 1.2 I donât think we can treat it as an errata (and in any case weâre not planning an errata 3 for DITA 1.3 at this point).
One workaround would be to use the generalized form of the elements, meaning <ph class=â+ topic/ph sw-d/filepath â keyref=âsomekeyâ/>.
This would be semantically correct and grammar valid and should result in the intended processing result.
Pretty ugly but it should work.
I hope you are doing fine.
I am writing to you as a member of the DITA TC regarding a question related to the DITA spec:
We have noticed that the @keyref attribute (which we would like to use to reference text variables) is not supported for the <filepath> and <userinput> elements, although DITA 1.3 spec says that it should.
Either the DTD or the documentation are wrong. Are you already aware of this issue?
What can I tell our tools team, who have checked that it is not on our end that we have removed the attribute from those two elements, but that it really doesn't exist in the 'plain' DITA DTDs?
Thanks and regards,