markjspivey

Abstract Agent Type System with Context Graphs, DIDs/VCs, Causality, and Provenance

A comprehensive framework for defining agent behavioral contracts (Abstract Agent Types) and managing their runtime interactions through Context Graphs, with full support for decentralized identity, verifiable credentials, causal reasoning, and provenance tracking.

electrons don’t, electricity does .

with property graphs, as compared to RDF, wouldnt the internals of nodes (properties) not be considered actually a part of the graph itself (or atleast not first class)?

why being downvoted?

Parallels to Restful API, Hypermedia as the Engine of Application State ...

im asking because of the medieval warm period and subsequent little ice age which occurred prior to the more recent big uptrend

Yes one of the graphs is from back then, so then I’ll ask again since 650 is not 1354 …

what do you mean by a similar graph if the original post only goes back to 1950 but japans goes back to 600?

I'm confused by your use of "fractal", could you expand a little bit on how your using that word in context here?

How does the article and the HN comments not mention Stephen Wolfram and his Physics Project … ?

this doesn't make any sense though, your write up starts with an assumption that multiple records in the dataset are "obviously" the same entity ... so we wouldn't even need entity resolution then ...

"entity resolution" as a process should moreso imply how to determine whether two records that aren't obviously the same entity are actually the same entity ... and how you would go about discovering and proving and declaring that ...

what you describe is still an actual supply chain issue though, you are merely elaborating on a possible cause for particular supply chain issues .

we can’t conflate nor confuse the interrogatives (who for what for when for where for why for how) ...

things being talked about are merely distinct, and certainly not interchangeable either / ors .