Merge pull request #423 from CapsicoHealth/ldhasson-patch-2

Update README.md

README.md

@@ -1,10 +1,10 @@
 <P align="center"><IMG src="Tilda.jpg"></P>
 <H1>Intro</H1>
-Tilda (Transparent Integrated Light Data Architecture) is not an ORM, but an integrated data platform that takes a base-level view from the database schema level, and projects it out to various programming environments. It provides a JSON-based configuration language to define basic tables/objects, and higher level patterns such as Exporters, History, Datamarts, Pivots, Datamats, Formulas etc... It generates code so can focus on your business logic. It automates migration, deployments (in single-database or multi-tenant fashion), documentation, and increases team velocity working with complex data models from design to deployment.<BR>
+Tilda (Transparent Iterative Light Data Architecture) is not an ORM but a data-oriented platform that takes a model-driven approach at the database schema level and projects it out to various programming environments. It provides a JSON-based configuration language to define tables and higher level patterns such as complex views, exporters, history/versioning support, datamarts, pivots, formulas etc... It generates code so can focus on your business logic. It automates migration, deployments (in single-database or multi-tenant fashion), documentation, and increases team velocity by supporting iterative development cycles working with complex data models from design to deployment.<BR>
 <BR>
-This work is based on ideas and experience gathered building large data systems and complex applications, from CORBA runtimes and EJB containers, to Hibernate-based or myBatis systems, and more recently, a full-fledged real-time clinical analytics platform. Tilda aims to be as transparent and simple as possible for the modern data engineer, providing a fairly flat view of your data in plain SQL and/or code artifacts and projecting across multiple tiers of your application. It's transparency is critical in helping use Tilda simply as a model management tool with minimal adoption risk, or as a full fledge ETL and data application building block (the all-in approach). All assets generated are human-readable from the get go and is easy to walk through and understand if need be. But you don't have to. Tilda takes a decidely data-centric view of the world: we believe you cannot build a complex large-scale performing data application without thinking about it full-stack, and it all starts at the data model level. <B>we believe that no framework can hide your database, so why try</B>? This is Data to the metal, and all the way up full stack.<BR>
+This work is based on ideas and experience building complex data systems and applications using at times EJBs, Hibernate, myBatis or even plain JDBC. Those systems have included real-time predictive modeling, standard 3-tier transactional web applications, and classical data warehousing. Tilda aims to be as transparent and simple as possible for the modern data engineer. Its transparency is critical in helping use Tilda simply as a model management tool with minimal adoption risk, or as a full fledge data application building block (the all-in approach). All assets generated are human-readable from the get go and are easy to walk through and understand if need be (but you don't have to). Tilda takes a decidely model- and data-centric view of the world: we believe you cannot build a complex data application without thinking about your data model. <B>We believe that no framework can hide your database, so why try</B>? This is Data to the metal, all the way up full stack.<BR>
 <BR>
-At this time, Tilda only supports Java 1.8+ as a target language, and Postgres 9.5+ as a target Database. However, the framework was built to support other languages (such as JavaSCript or .Net for example), and other data stores (MS SQL Server, mySQL, and also non-relational backends such as Cassandra,  MongoDB or Hadoop). Ultimately, we are aiming for an extensible data architecture that would enable integration with different formats, such as CSV, or HL7 (a standard healthcare data exchange format), and the ability to extend the patterns supported (feeding data to predictive models for example). Tilda ultimately strives at identifying core patterns used in a complex data-driver application, and capture them as reusable declarative bits so you can assemble them to match your needs.<BR>
+At this time, Tilda only supports Java 1.8+ as a target language, and Postgres 9.5+ as a target Database (while exploiting features from V10, V11 and V12 if available). However, it may not be too hard to implement other target languages in the future  (such as JavaSCript or .Net for example), and other data stores (MS SQL Server, mySQL, and also non-relational backends such as Cassandra,  MongoDB or Hadoop). Ultimately, we are aiming for an extensible data architecture that would enable integration with different formats, such as CSV, or HL7 (a standard healthcare data exchange format), and the ability to extend the patterns supported (feeding data to predictive models for example). Tilda ultimately strives at identifying core patterns used in a complex data-driven application, and capture them as reusable declarative bits so you can assemble them to match your needs.<BR>
 
 <H1>Docs</H1>
 We are making progress on the <A href="https://github.com/CapsicoHealth/Tilda/wiki">Wiki</A> and started publishing the <A href="https://capsicohealth.github.io/Tilda/overview-summary.html">JavaDocs</A> for the project.