Re: Invitation to Co-Shape a 3-D Standard for AI Knowledge — Collaboration Opportunity with K3D

Hi Pete,

Thanks for digging into the Knowledge3D repo and for the thoughtful 
questions.


      Where the nodes live

The current draft schema for a single K3D node is in 
|spec/k3d_node_schema.json|. Every node carries:

  *

    |id|: unique identifier

  *

    |vector|: 3‑D projection

  *

    |embedding|: original high‑dimensional vector

  *

    |metadata|: open object with at least |label| (human‑readable) and
    |type| fields, plus any additional facets you need (technology,
    legislation, ethics, provenance, etc.)

The README’s “Key Concepts” section points to that schema and explains 
how nodes are linked to geometry through a glTF extension

..


      Plain-language examples

You can see plain-language labels in action in the sample datasets—for 
example, |examples/solar_system.k3d| stores each planet’s name in 
|metadata.label|, alongside its embedding and neighbor links


      Status of the vocabulary layer

We don’t yet ship a canonical controlled vocabulary. The |metadata| 
object is deliberately open so you can align nodes with your own or 
community ontologies (SKOS, schema.org, sector‑specific terms, etc.). 
We’re still drafting this part of the standard and would love your 
input—especially given your Graph RAG experience.

If you’d like to join the discussion or contribute proposals, just let 
me know; we’re aiming to converge on a reusable vocabulary layer that 
plugs neatly into graph/ontology tooling while keeping the node format 
lightweight.

Best regards,
Daniel Ramos
daniel@echosystems.ai

On 8/13/25 7:19 PM, Peter Rivett wrote:
> I'm trying to follow up on what you wrote, Daniel:
>
> Rich, reusable vocabularies
>  
> K3D links plain‑language terms to formally typed nodes, making 
> ontologies explorable by humans /and/ machines.
> Facets & provenance
>  
> Each K3D node carries first‑class metadata (technology, legislation, 
> ethics, etc.)—a perfect companion for your “resources & metadata” track.
>
>  
>
>
>  
>
> I'm having problems tracking down the plain-language terms or the K3D 
> nodes in the repo - can you please provide a pointer?
>
> Thanks
> Pete
>
> Pete Rivett (pete.rivett@federatedknowledge.com)