tl;dr: yes: the rendering is left up to the developer.
you’re right, the TEI Stylesheets transformation to HTML does not process any @ref or @key on <persName> (to be turned into clickable links). One issue I see is that the referenced <person> elements do not get processed when they are in the header (where you frequently put these). So, there is frequently nothing to point to in the HTML …
Second, those links might nest: <persName> can self-nest or be within a <ref> or within a <placeName> or …
So, as I learned from my projects, you can’t simply turn every <persName> into an <html:a> because in HTML these elements must not nest.
That said, I totally agree that your request is not at all fancy but common practice – I just do not see how the TEI Stylesheets could take care of the aforementioned issues in a generic way (and with affordable efforts).
> Am 10.12.2017 um 01:49 schrieb Chris Selwyn <[log in to unmask]>:
> I have been struggling with how to handle my personography.
> I understand from the TEI Guidelines Ch. 13 how to construct a personography by making a separate file which contains a <listPerson> of <person> elements. I can also see from Ch. 13 how to refer to those entries using an @ref.
> What I am failing to see is how the TEI XSLT stylesheets render the @ref attributes into a clickable links in HTML.
> Is there something obvious I am missing or is the rendering supposed to be left up to the developer to decide how to do it? Does anyone have a worked example?
> Chris Selwyn