I've only just started to look at Scriblio but was wondering if
there's any mileage in some/all of the ideas I write about here:
Is anyone experimenting with Scriblio in this way?
> Scriblio seems like it would be pretty easy to replace MARCish with
> ntriples (or RDF/JSON, or some internal representation), but I'm not
> entirely sure how you would really make it act much differently than
> it currently does... Conneg for different representations?
The behavior that I have mapped out is to resolve any data linkages as
the record is saved, store the link in the postmeta record, index the
textual representation in the facets, and do something fancy at
display time in the body of the record. That's not perfect, but it's a
start. Some additional logic could be added to update the indexing of
linked data other than at the time records are saved.
> In my mind, the current way that Scriblio stores it's data is /very/
> document-centric (and pretty static -- it being a big blob of text,
> not very atomic), so this might need to be rethought in order to make
> this work well.
You're not entirely wrong. Previous versions did indeed store records
as a big blob of text (structured html I exclaim), but the current
version stores the data as an array that can be easily manipulated at
display time. One application of linked data that it employs now is in
connecting to parent/child/other records (though only within the
current instance at the moment).