On Monday, January 8, 2018 at 12:14:59 AM UTC-5, James Gatannah wrote:
> FWIW, I think https://leanpub.com/specter looks extremely interesting.
> (Or it may be awful...I haven't had a chance to read it yet, much less work
> through the exercises).
>
Actually, I worked through that ebook last
On Thursday, January 4, 2018 at 5:51:27 PM UTC-6, Ben Kovitz wrote:
>
>
> Well! So far, Specter appears to have taken the "path map" idea that I'd
> been toying with to its ultimate logical conclusion—far better than I could
> ever do it. Nathan Marz even says that needing to manipulate tricky
I replied to Gary Verhaegen:
If you’re shopping around for ideas as to how to define data manipulation
>> API, it may be worth taking some time looking at Specter too.
>>
>
> Thanks for this suggestion, too. I'm now checking it out.
>
Well! So far, Specter appears to have taken the "path map"
Yes; Datomic really is great. There's plenty of wonderful stuff I haven't
even mentioned, like database as a value, persistent history, snapshots at
a timepoint, transaction metadata, smart peer replication etc. It's kind of
the best thing since sliced bread. But if you don't need all that jazz
Unfortunately most of the contexts were fairly specific and a few
years ago, so I don't remember all of the details, and mostly in the
context of private research that I'm not at liberty to share. Some of
the results have been published (though not my specific work) by a
then-colleague of mine;
On Thursday, January 4, 2018 at 4:01:41 AM UTC-5, Gary Verhaegen wrote:
Have you considered encoding your port graph into a normal graph?
That was the first idea I had, and I quickly rejected it as adding
complication. The consideration that led me to port graphs in the first
place was that
On Tuesday, January 2, 2018 at 3:11:45 PM UTC-5, Christopher Small wrote:
> http://docs.datomic.com/entities.html
>
> http://docs.datomic.com/pull.html
>
Thanks—this is really good stuff! Not that I expected anything less, but
it's a happy surprise that it applies so well to graphs. Now
If you’re shopping around for ideas as to how to define data manipulation API,
it may be worth taking some time looking at Specter too.
Have you considered encoding your port graph into a normal graph? That would
require you to define a mapping, but would then allow you to fairly easily
reuse
> ...noticed that the attribute names in the datoms are a lot like the port
labels in port graphs. A port label is essentially an attribute key whose
value is the edges incident to it. And when you chain data patterns in
Datalog queries, that's a lot like navigating through a graph.
That's very
Christopher Small,
Your suggestion to look into Datomic definitely turned up a new idea. I
went through the Datalog tutorial at http://www.learndatalogtoday.org
(which is excellent, by the way), and noticed that the attribute names in
the datoms are a lot like the port labels in port graphs. A
On Monday, January 1, 2018 at 7:57:11 PM UTC-5, Christopher Small wrote:
…you might want to look at Datomic (also authored by Rich Hickey),
> DataScript (an in-memory approximation) or RDF (data language of the
> Semantic Web). They model graphs as `(entity, attribute, value)` triples,
> where
Do you need to be able to attach data to specific edges instances? Or would
it be sufficient to be able to have different types of edges, and be able
to associate data with those abstract edge types?
If the latter, you might want to look at Datomic (also authored by Rich
Hickey), DataScript
€0.02 i like option #3, i think it would be possibly nice for edges to be
named based on the ports they connect.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new
I'm making a little library for myself to represent a kind of graph. I want
to
make it simple, the way Rich Hickey designed much of Clojure. My designs so
far have lacked that kind of plainness and ease of use. I keep wondering,
"What would Rich Hickey do?" Even if you're not Rich Hickey, maybe
14 matches
Mail list logo
