Frontend DogmaWhy “NaN !== NaN” in JavaScript (and the IEEE 754 Story Behind It), by (not on Mastodon or Bluesky):
San Diego Music Events BotHonoring Our Veterans Concert
Tuesday, Nov. 4, 2025, 2pm @ Point Loma Community Presbyterian Church
#classical #standards #sandiegolivemusic #sandiego #livemusic
https://www.sandiegoreader.com/events/2025/nov/04/honoring-our-veterans-concert/
NFDI4Culture✒️ Falls ihr zum Thema Retrodigitalisierung regelmäßig Infos erhalten wollt, könnt ihr euch in die Mailingliste eintragen: https://www.listserv.dfn.de/sympa/subscribe/retrodigitalisierung?previous_action=info
#NFDIrocks #Kulturerbe #Digitalisierung #Retrodigitalisierung #Standards #WSRD
^ap (ks)
3/3
WenStandards - who needs them, certainly not palimentarians?
BBC bias again. But I suspect it will fit right in with the BEEB and Brice and they will stick to their guns
James NashNow that the @designtokens format specification has reached its first, *stable* version, I decided to have a look back at my own journey of getting involved in the DTCG and contributing to that spec...
https://cirrus.twiddles.com/blog/2025/10/31/my-dtcg-journey/
NISOInfoNISO voting members have approved a new working group! This one will develop a recommended practice for optimizing open interoperability around integrated library systems. To learn more & for info on joining the new group: www.niso.org/press-releas...
#libraries #standards
#libraries #standards
Jamie ClarkNew from the OASIS Coalition for Secure #AI (CoSAI): the #AI Incident Response Framework v1.0: https://www.coalitionforsecureai.org/defending-ai-systems-a-new-framework-for-incident-response-in-the-age-of-intelligent-technology/ (Announcement, 29 Oct.)
It's organized around the NIST #incidentresponse lifecycle, but adapted specifically for AI systems that traditional IR tactics weren’t designed to handle.
This guidance isn't platitudes: it comes with actionable playbooks, written in the (OASIS standard) #CACAO structured playbook format, friendly to policy exchange and automation.
Playbooks: https://github.com/cosai-oasis/ws2-defenders/blob/main/incident-response/AI%20Incident%20Response.md
CACAO: https://docs.oasis-open.org/cacao/security-playbooks/v2.0/cs01/security-playbooks-v2.0-cs01.html
#Standards #OASISopen #OpenForTheWin
It's organized around the NIST #incidentresponse lifecycle, but adapted specifically for AI systems that traditional IR tactics weren’t designed to handle.
This guidance isn't platitudes: it comes with actionable playbooks, written in the (OASIS standard) #CACAO structured playbook format, friendly to policy exchange and automation.
Playbooks: https://github.com/cosai-oasis/ws2-defenders/blob/main/incident-response/AI%20Incident%20Response.md
CACAO: https://docs.oasis-open.org/cacao/security-playbooks/v2.0/cs01/security-playbooks-v2.0-cs01.html
#Standards #OASISopen #OpenForTheWin
Defending AI Systems: A New Framework for Incident Response in the Age of Intelligent Technology
The Coalition for Secure AI (CoSAI) has released the AI Incident Response Framework, Version 1.0, which provides security teams with the tools, knowledge, and structured approaches they need to protect AI systems from emerging threats.
ThibAbsolute banger of a post by @mariafarrell, shared by @tarakiyee on another network. Every other paragraph is quote-worthy.
"That impulse to scour away the messiness that makes life resilient is what many conservation biologists call the pathology of command and control. Today, the same drive to centralize, control and extract has driven the internet to the same fate as the ravaged forests."
AFOC#ResearchTopic of the day: #VerifiablePresentations of #VerifiableCredentials.
I'm quite fond of these types of credentials & have been following their development for several years now. #CryptographicallySecure digital credentials are the future of privacy-preserving forms of trustworthy proof.
There are so many use cases for them - I'd love to see just about every company & organization start issuing them for any number of things. I want to start my VC collection!