๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

cv usk
@cv_usk
AI / Software Research Notes AI Agent, LLMOps, MLOps, Software Architecture ๆŠ•็จฟใฏๅ€‹ไบบใฎๆ„่ฆ‹ใงใ™ใ€‚
๊ฐ€์ž… May 2026
286 ํŒ”๋กœ์ž‰ ์ค‘    469 ํŒฌ
A schema tells you what exists, not what it means. Neo4j has released an open ontology specification as its answer for AI agents ๐Ÿงญ The Neo4j Ontology Graph Specification: A pragmatic, open, AI-first approach It is an open-source specification for describing domain knowledge in a single machine-readable JSON or YAML file. It is Apache 2.0 licensed, with SDKs for JVM, JavaScript, and Go. Highlights ๐Ÿ› ๏ธ Pragmatic Define nodes, relationships, properties, constraints, and indexes in one file. It validates against a published JSON Schema and fits existing development and operations workflows. ๐Ÿ”— Interoperable It builds on W3C standards such as RDFS, OWL, SKOS, and SHACL, and documents how RDFS and SHACL concepts map onto the spec. A reference field on every element can link to external standard terms. ๐Ÿค– AI-first Descriptions and aliases tell an agent whether "Account" means a bank account, what else it is called, and which identifier (such as an IBAN) applies. One ontology can serve as constraints, data derivation, and agent context. The idea is to write the meaning once and use it in both the database and the agents. There is no RDF serialization yet, and the post includes no performance evaluation. #Neo4j# #GraphRAG#
๋” ๋ณด๊ธฐ