Version Schema - Experimental.1 {VSchemaInDev.1}. Copyright and license: http://versionschema.org/LICENSE. Specification: http://versionschema.org/ Applied quality assurance practices. Applies to the product on any change in the version representation (i.e., a version bump of any kind). There can be as many of these as actually apply to your product release gates. Used when no other assurances are proffered. Used when reviews are performed by experts, other than the changers, for all changes in each published release. Used when output from a static analyzer is reviewed and acted on for each published release. Used when a third party autdior or standards entity revews all changes for each published release. Used when some testing has been performed for each published release. Used when tests cover the changed features for each published release. Used when 50% or more of product (code paths) is tested for each published release. Used when 75% or more of product (code paths) is tested for each published release. Used when 100% or more of product (code paths) is tested for each published release. Used when an independent auditor or standards entity runs compliance tests for each published release. Rules that specify why a version field is incremented or changed. The field is changed/increment for all changes of any kind. The field is changed/incremented randomly or at the whim of bipedal wetware. The field is changed/incremented only for backwards compatible changes. Can be used as a modifier, for instance documentation_new_section may or may not be backwards compatible. Applying back_compat to the same field refines the rule set. Cannot be combined with any other rule that implies a breaking change. The field is a constant, relative to the rest of the fields. It cannot be changed independantly, but it can change if any other field in the version changes. TBD: Whether and how to tie allowance of change to other named fields? Changes that fix bugs, refactoring, clarifying documentation, etc., without introducing new features or API changes. The field is changed/incremented only for addition of new features (modification of an API) without breaking backwards compatibility. Any simple change. Can be combined with any rule that does not imply high complexity. Any complex change. Can be combined with any rule that does not imply low complexity. New section(s) added to documentation. New paragraph(s) added to documentation. Refinements to documentation. The field is changed/incremented only for none backwards compatible changes. Used as a modifier, for instance documentation_new_section may or may not be backwards compatible. Applying not_back_compat to the same field refines the rule set. Cannot be combined with back_compat or any other rule that implies a non-breaking change. The field is changed/incremented for changes to images (icons, pictographs, etc) or the visual layout of the content. Defines the data format. (string, XML/JSON/YAML). Only string is supported at this time. List of delimiter characters. Indicates whether the schema is a draft, living document, final or deprecated version. The schema document is subject to revision. The schema document is a "living document", subject to change foreever. The state tag can never be changed. Except for this state tag, the document is no longer subject to revision. The docuement cannot be changed, except to modify the state to deprecated. The schema is deprecated. The document is no longer subject to revision of any kind. New dependencies should not be taken on this document. The document may be removed from public feeds. The type of the field being defined. The field type is pure alpha characters. The field type is mixed alpha and numeric characters. The field type defines enumerations. The field type is pure numeric. Lists the kinds of transitions that field value can pass through. TBD: Syntax/semantic definition. When false, transitions represent a single track through the defined state machine. When true (default), work may commense in or more phases simultaneously. All of the child elements, must be present in the version string or record, in any order. Declare ancestor schemas and transition rules. Allows seperate prerelease and release schemas to be related to each other by some simple rules. A URI pointing to the ancestor. Any of the child elements, can be present in the version string or record, in any order. There must be at least one. A place holder for any quantity of any kind of whitepspace, including new-line characters. Maximum number of new-lines allowed in a whitespace block. Default is 1. Maximum number of non-newline type characters allowed in a whitespace block. Default 65535 (max). Designates a section of the version string or record that represents a named/referencable field. Fields contain a type attribute and any of the elements in the vs:baseelementsGroup, vs:controlGroup and vs:ruleelementsGroup. The field name. Must be unique among its siblings in its parent element. When true, rules are inherited from the first outer node they can be found in. No rules applied if not found in the chain of containing outer elements. Defines the presense of a string literal within the vesion string or record. One and only one of the child elements may be present in the version string or record. Declares an optional segment of the version string or record. Declares an ordered list of elements. Defines a transition type for signed integer numeric fields. Useful for count to zero from +/- starting point or anything else that needs a signed integer transition. You must provide a value for this type, no default is provided. Defines allowed transition states. Optional name. Names the state transition target state. Names the state transition source state. Use to define types (essentially macros) to reference. Required for recursive definitions and also saves some space and typing. Use to reference a defined type. The type name refered to. The name to use at the element scope in which type is referenced. Defines a transition type for unsigned integer numeric fields. Defines that a VersionMeta tag appears at the specified location in the vesion string or record. Defines default prefix used for all VersionMeta tags that do not begin with "https://" or "http://". A fully qualified URL referencing human readable documentation for the containing element. A URN that, when appended to the VersionSchema's canonicalReference content, yields the human readable documentation for the containing element. Top-level container for everything in a version schema definition file. There MUST be exactly one VersionSchema element per schema file.