Referent Tracking System Home

This space is for the collaborative development and improvement of specifications for Referent Tracking (RT).

Hybrid System Hypothesis: If we could always (and inexpensively) query with filtering on the instant of our graphdb relations, could we store the D-tuple collection in a relational database? (The foreign key could be an annotation.) Would that simplify graph representations of RT? RT is all about who's, but the what's and the when's may be functional subsystems anyway. I am probably suggesting that the audit system can be separate from the state (which may seem a bad approach to "integrated" or "native" paradigms), but here, with the caveat that the state can be "natively" reproduced for every addressable instant. Integration can happen in the user interface (with a persistent column that says "Why?" of course). It's the meta-facts that insist on reification.  -Roger

Forms and metadata are suspected of being tabular (dense).  -Roger

We have the following ongoing RT projects:

1. Improvement of metadata templates
2. Graph database representation
3. Develop denotational bonds
4. Realist configurations
5. RT UIs

The following papers are recommended reading:

1. how_to_track_absolutely_everything.pdf
2. Implementation of a Referent Tracking System.pdf
3. Tracking_referents.pdf
4. strategies_for_referent_tracking_in_electronic_health_records.pdf
5. representing_local_identifiers_in_a_referent-tracking_system.pdf
6. representing_the_reality_underlying_demographic_data.pdf