Lady, EVOLVED @Lady@cat.family

i don’t feel this way about everything being written in C tho because C is actually a meritous language

oh, i feel about everything being written in Rust the same way i do about everything being written in Java

@gaditb in some ways, the prediction is true

« JPEG XL is a genuine "one true format", and i'll be switching all assets across all of my sites to it the moment support is turned on in Firefox and Chrome. I won't even wait for Webkit to play catchup. » this comment aged poorly

@monorail oh hey me too

@aschmitz (also, for things like books, you can’t identify the directionality of a book from the directionality of its first characters. but you also probably shouldn’t be conveying books as plain strings.)

@aschmitz i think the main advantage to doing it in metadata is it’s easier to bestpractice it, in the same way that language tags are bestpractice, whereas doing it with unicode characters leads to situations where a lot of people don’t bother because it works for them in their languages on their machines

@aschmitz (as an aside, this definition of string means R·D·F strings cannot contain U+0000, U+FFFE, or U+FFFF, despite those being perfectly usable Unicode characters in other contexts)

@aschmitz “string” in this context means <https://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/#string>, « the set of finite-length sequences of zero or more characters (as defined in [XML]) that match the Char production from [XML]. »

as far as your actual question, i’ll point you to <https://www.w3.org/TR/string-meta/> which discusses strengths and drawbacks of various approaches in depth

Json·L·D supports two different R·D·F 1.1 equivalences for strings with both language and direction, but unfortunately both are basically unusable in Owl (as one is a custom datatype, which cannot be reasoned about, and the other is a blank node, which cannot be the value of a data property)

(actually it¦s probably best to keep direction as a separate property unless and until they update all of the downstream specifications to support R·D·F 1.2, since 1.1 only supports language, but shhhhh)

YES it is more processing work to explicitly handle all those possibilities but it is BETTER i tell you!!

programmers!! stop defining Json‐L·D syntaxes which encode text as plain strings with separate properties for language, direction, and media type!! Json‐L·D explicitly supports tagging direction AND language directly on the string itself!! and rdf:XMLLiteral exists for data which is serializable to X·M·L!

(i was saying “we¦re ALMOST done i just need to add Web Annotations” up until yesterday, and then i realized i hated how Web Annotations do TextualBody¦s so now we need AWOL as well)

anyway we¦re ALMOST done i just need to add AWOL

anyway i don¦t really care; i¦m not expecting anyone to actually use this Full Ontology for anything, it¦s supposed to be subsetted, but i do need to like, do a basic sanity check to make sure it isn¦t inconsistent, at least

one of the big bottlenecks apparently is the fact that i have multiple classes with

“rdf:value exactly 1
rdf:value only xsd:string”

i have no idea why THIS is the thing making everything slow, but when i remove it the speed increases are Quite Substantial