ICYMI: EntityMap: The Open Standard That Gives AI Systems A Structured View Of Your Business. via @Dixon_Jones: hubs.li/Q04jxS4G0 #business #SEO

EntityMap : le standard ouvert qui donne aux IA une vue structurée de votre entreprise Les IA lisent des pages, pas votre savoir. EntityMap transforme vos contenus en carte d’entités, relations et preuves: moins d’hallus, plus d’EEAT. #SEO #RAG Intrigué ? voir nos actus 👆

.@Dixon_Jones has released a new proposed open standard for delivering knowledge to AI systems called EntityMap.

Today we launched an Open Source protocol for a consultation review, called EntityMap. Spec so you can create your own is at entitymap.org and discussions on the tech side at github.com/entitymap/entitym… - we hope you will use it and share it.

an argument I buy is that good design > bad design with types React generated a lot more value for both devs and end users than "Angular with types" and, also, React internals are typed now framing the debate otherwise misses the point Electric's internals would be better typed, if only there were such a language that could do that while also delivering the other operational characteristics that Clojure delivers that we require another example the fact that Datomic EntityMaps may or may not perform IO when entries are accessed is hugely problematic and has resulted in the entity API being all but deprecated, and this has been privately acknowledged (off the record) by at least one Datomic team member all code written against EntityMap is broken above a certain scale threshold

Excuse me, that one `any` should have been `keyof EntityMap`. Either way, whatever works, works. I'm not sure there's a huge difference between the approaches other that maybe fewer types one way. typescriptlang.org/play?#cod…

EntityPacketRaw<VariantType, EntityMap[VariantType]> as the output type will tie it out - check out typescriptlang.org/play?#cod…

The EntityPacket type is a little overworked. Simplifying it solves the problem: type EntityPacket<VariantType extends keyof EntityMap, T = unknown> = { variant: VariantType; entity: T; } typescriptlang.org/play?#cod…

we also have draftjs types type DraftContentState { entityMap: [DraftEntity] blocks: [DraftBlock] }

maybe, though in my case it's wrapped up in an EntityMap type

Worked through the problem by having an EntityMap / EntityFactory, now the Data/Entities.js 'factory' just holds a reference. #StPaddysDay