Lady, EVOLVED @Lady@cat.family

who is the best pokémon technologist♂

my girlfriend is SO NICE they made me TEA ☕️

i·e·t·f publishes like 200 r·f·c’s a year that’s way more than pokémon

unlike pokémon tho there do exist bad w3 specifications

w3 specofications are KIND OF like pokémon

hm <https://www.w3.org/TR/dx-prof/>

hey you know that part of the specification which is frankly underspecified and generally requires reading between the lines and carrying forward expectations made in different documents in order to even understand what the appropriate behaviour is? well i depend on that

*xsltproc

oh my god reproducing this bug in xslt is so difficult

@gaditb i have come across it, altho i haven’t actually used it yet

some OWL processors attach significance to the namespaces which are declared on the root rdf:RDF element so it is important to ensure that all of the namespaces which appear in the ontology are actually declared there

but XSLT 1.0 has very very limited namespace node support, afaict limited only to copying (and even that is a grey area), so you have to do something like this in an earlier stage to create the namespace nodes so that they are there to copy

<template match="Ontology" priority="2">
<text disable-output-escaping="yes">&lt;owl:Ontology</text>
<for-each select="declare">
<text> xmlns</text>
<if test="normalize-space(prefix)!=''">
<text>:</text>
</if>
<value-of select="normalize-space(prefix)"/>
<text>=&quot;</text>
<value-of select="normalize-space(namespace)"/>
<text>&quot;</text>
</for-each>
<text disable-output-escaping="yes">&gt;</text>
&continue;
<text disable-output-escaping="yes">&lt;/owl:Ontology&gt;</text>
</template>

this is fine

<https://www.w3.org/TR/shacl/> interesting

granted H·O·A·H 1 & 2 were individually shorter but they were longer combined

harmony of a hunter returns is such a long album how did i ever have time for this shit (the previous two albums) as a kid

@thephd in my experience the simplest solution on macos is just to use rbenv always

but yes, macos installs a number of programming languages that they really shouldn't for legacy reasons to keep people's old workflows from unexpectedly breaking on a new OS upgrade

used to also ship with python 2.7, but they finally managed to drop that one after many years of deprecation notices

for you japanese scholars out there, know the old english scholars are just as salty about unicode unification practices

i don’t want the unicode consortium to know about this because they will Not like it but also, hey medievalists, it works