The SVG Repository is an archive that contains all the entities needing a persisted state. Its manifested in an SQL database and interfaced through a Web Service that envelopes it. The end product it generates are dynamic and inter-active SVG documents generated from virtual SVG documents whose composition is compiled at runtime unlike typical SVG files with xml descriptors
SQL Database : containing the Virtual SVG defined through the Linguistic Model which is visualized by means of the Graphic Model
Web Service : distribute the Virtual SVG using algorithms to generate graphic compositions which have dynamic and interactive behaviour
Catalogs that contain the definition of the primary entities of the linguistic model contained in the SQL database
Narrative : Internal catalog that contains topical grouping of specifications for graphic compositions
Symbolism : Internal catalog that contains specifications for graphic compositions to be implemented
Catalogs that contain the definition of the primary entities of the graphic model contained in the SQL database
Context : Internal catalog of storing configuration and augmentation of re-used graphic compositions
Symbology : Internal catalog of re-useable graphic compositions consisting of shapes, symbols and text
Symbols : Internal catalogs that contain both shaped and imported (traced, parsed or sent) symbols
Text : Internal catalog of text (using custom fonts) drawing out paths defining the shapes of characters
There a two mechanisms which publish the graphics specifications and the actual graphics to the SVG repository
Portal Publisher : Publishes the graphics specifications defined in the linguistic model and view the actual graphics. It also contains utilities to perform administrative functions to manage the repository.
Studio Publisher : Publishes the graphics that are defined in the graphic model through several design utilities used to author and process SVG graphics creating compositions contained within repositories.
Secured central access points controlling where the SVG documents are trafficked through ensuring that the server hosting data bundles are only depleted by intended recipients on the internet for economy and security purposes.
Web Channel : interfaced by the websites that have been registered with the specific SVG repository
Mobile Channel : interfaced by the mobile apps that are registered with the specific SVG repository
User tasking definitions and audited publishing activity are stored for security and administrative purposes.
User : Repository user account representing the principal user account on the platform
In-Trays : Work load of tasks to be done in the portal and studio publishing mechanisms
Tasking History : Activity audit of work assigned by the manager to all repository users
Portal History : Activity audit of work on the repository from the portal linguistic designers
Studio History : Activity audit of work on the repository from the studio graphic designers
A demo project containing an extensive collection of examples demonstrating the functionality and structure
of the repositories utilities and processes and how it handles the graphic data. Browse through them to get
practical experience of how it actually works and refer to them as a further aid to the YouTube video tutorials.