Another approach might be to use SKOS-XL instead of language tags like so:

:A1 a skosxl:Label;
rdfs:label “Ελληνική Δημοκρατία”@gr
skosxl:literalForm “Hellēnikē Dēmokratia”;
bf:romanizationRule <https://www.loc.gov/catdir/cpso/romanization/oriya.pdf>;
.

It’s a little heavy, but a construct like this would tie the key pieces together. A custom language tag on the transliteration can’t tie in the native term.

Jeff

From: Bibliographic Framework Transition Initiative Forum <[log in to unmask]> on behalf of Andrew Cunningham <[log in to unmask]>
Reply-To: Bibliographic Framework Transition Initiative Forum <[log in to unmask]>
Date: Friday, July 1, 2016 at 11:39 AM
To: "[log in to unmask]" <[log in to unmask]>
Subject: Re: [BIBFRAME] Language tags


On 1 Jul 2016 2:19 am, "Joseph Kiegel" <[log in to unmask]> wrote:
>
> The approach of creating variant subtags for specific editions of the ALA-LC romanization tables is outmoded, since the tables are now on the Web. 
>
>  

It is less than ideal, yes, but it was the only one that was proposed as a variant subtag. And no one has proposed a way to tag anything else.

It doesn't help that romanisation tables lacked good versioning information, etc.