Schema in Advance vs Structure in arrears - 0 views

• 
  #1 Kurt Laitner on 01 Feb 10

   

  The predominant model of systems to date has been to analyse your domain, model it, implement it in a rdbms then code access to it (forms on tables). Simplistic but largely true. RDF triplestores among other things allow 'stacking' of data which does not require schema in advance, only equivalency mappings (or standards). We need to decide what we consider foundational to the system (schema in advance) and what will be provided as structure after the fact - architecturally we need to allow both modes - and given extensibility, we must also provide reference structures to provide minimum functionality with a set of "structures after the fact' provided up front (yes I'm aware of the cognitive dissonance there)

   

  <div class="cArrow"> </div><div class="cContentInner">The predominant model of systems to date has been to analyse your domain, model it, implement it in a rdbms then code access to it (forms on tables). Simplistic but largely true. RDF triplestores among other things allow 'stacking' of data which does not require schema in advance, only equivalency mappings (or standards). We need to decide what we consider foundational to the system (schema in advance) and what will be provided as structure after the fact - architecturally we need to allow both modes - and given extensibility, we must also provide reference structures to provide minimum functionality with a set of "structures after the fact' provided up front (yes I'm aware of the cognitive dissonance there)</div>

  ...

  Cancel

To Top