Feed on
Posts
Comments

Shift of emphasis

Have been thinking recently: I’m not sure I have the time or the motivation to promote tagtriples as a structured-metadata interchange format (and therefore a competitor to RDF). And I don’t think this is what the world wants anyway - AFAICS, all the buzz at the moment seems to be centred around vertical formats rather than horizontal.

So am wondering - would things be better served by concentrating less on tagtriples-the-format, and more on the aggregation ‘product’?

E.g. The main reason that tagtriples works well at work is the ease of importing data from other sources. This is a pain-in-the-arse in RDF (you need to understand, invent and promote a long-lived URI scheme beside the original data source).
With tagtriples the simple ’symbols and triples’ model has a natural fit with relational data, xml, RSS, LDAP etc.. etc. It ought to be possible to build turn-key import functionality for these services.

So am thinking: maybe I should be positioning the software as a ‘universal data aggregator’?

Viewing 1 Comment

    • ^
    • v
    Have you considered taking the base functionality of tagtriples (tagles?) and integrating it into a Wiki?

    I've often needed the functionality of a Wiki + the functionality of tagles combined. For instance, the on-the-fly DB of tagles (ability to pivot on any node) with the ease of use and text centricitiy of a Wiki.

    Maybe as a plugin for Confluence?

    People work with rows and columns a lot. Just look to how much management uses spreadsheets for text, for instance. To them, it's a super simple database. I see tagles filling that exact role. The advantage is, with tagles, you can click on anything and see everything related to it. Much more useful than a single giant spreadsheet.

    Put it in a wiki, and everyone can edit it.
close Reblog this comment
blog comments powered by Disqus