Re: proplib and the jet age

[Izaac <izaac%setec.org@localhost>]

On Mon, Dec 31, 2012 at 08:16:31PM +0000, David Holland wrote:
> where that's not enough nowadays we have sqlite. Ergo, what we want
> from proplib is data transfer, and any plans for the future should
> take this into account.

[...]

> The chief question, therefore, is what data model the new stuff should
> support. There are at least seven obvious candidates I can think of:
> 
> (a) What we have in proplib (arrays and string-keyed dictionaries)
> only, with the explicit understanding that only tree structures are
> supported and not graphs; that is, no dictionary or array can appear
> more than once.
> 
> (b) Same as (a) but extend dictionaries to be keyable with arbitrary
> atom types.
> 
> (c) A more general semistructured model, like (b) but that explicitly
> allows graph structure without being fully graph-oriented.
> 
> (d) RDF, or more likely a tasteful subset of RDF with data types
> instead of using URIs for everying. (http://www.w3.org/RDF/)
> 
> (e) Property graphs.
> (https://github.com/tinkerpop/blueprints/wiki/Property-Graph-Model)
> 
> (f) Property graphs where property values can be tuples rather than
> only atoms.
> 
> (g) Relations (tables of rows with named fields).

Now, I'm a slow bear.  Can someone explain to me why good ole XDR isn't
good enough?

-- 
. ___ ___  .   .  ___
.  \    /  |\  |\ \
.  _\_ /__ |-\ |-\ \__