KOSH

Blueprint

Translate
A blueprint is a description and requirements entity. Its purpose is to allow for the creation, transportation and management of entities within a cybersea. Its contents include;
  • Entity Construction document - used by the creation service to build an instance of an entity. This includes many of the parts described in the KOSH object model.
  • Entity Requirements document - used to check the local cybersea for the services and entities required by an instance of the described entity.
  • Entity Interaction document - an description of the public nature of an instance of an entity.
  • Entity Security document - as well as describing suggested and enforceable security directives for both the blueprint and instances of the described entity, this document can also contain licencing and creation directives, pertaining to end user usage agreements.
  • Blueprint Geneology - Where it was created, who created it, revision history, KORE (Kosh Object Repository) ID and weblinks for upgrade, testing, retuning etc.

A blueprint is not a class. A class is specific to a particular language and particular programming paradigm. A class can be used to generate a blueprint, but then so can a COBOL program, or a BASIC program or a C program; as long as there is a KOSH compiler and the the KOSH entity model is followed.

The blueprint is the final stage of the entity design process . It is the entity that is distributed to other cyberseas which hope to make and utilise such objects.

A blueprint must be a citizen of a cybersea before even ONE instance of the entity described in the blueprint can exist in that cybersea. If a entity is found that does not have a blueprint in the blueprint manager, then it will be immediately frozen and quarantined, for later investigation and action.

Due to the virtual nature of the cybersea, the blueprint is in a platform independent distributable format. This allows for a blueprint to be installed into any cybersea, irrespective of the underlying physical hardware.