Releases: GfSE/SpecIF
SpecIF Schema v0.11.1
This is the master branch with SpecIF-Level-3; it corresponds to v0.10.3. The differences between SpecIF-Level-1 and -3 are:
- Properties with dataType 'string' and 'xhtml' may have multiple languages.
- A SpecIF data set (file) may have types, resources, statements and hierarchies with multiple revisions. Whereas in SpecIF-Level-1 all identifiers must be unique, in SpecIF-Level-3 there may be multiple revisions of an element. However any 'key' consisting of identifier and revision must be unique.
- As a consequence, any reference may point to a specific revision of the element. Of course the referenced element must be present in the SpecIF data set (file).
- A reference to an element may specify "revision": 0, which means the last revision being present.
- All SpecIF data sets (files) conforming with Level-1 schema (v0.10.3+) will also correspond to Level-3 schema (v.0.11.1+).
Many thanks to https://github.com/oalt for the discussions towards the support of multiple languages and multiple revisions.
SpecIF Schema v0.10.3
Some smaller changes:
- In the schema, there is no more constraint (regex) on the icon any more, any string will do.
- now, not only the string data-type, but also the xhtml data-type has a maximum length.
- The constraint check is now specific for the individual data-types.
SpecIF Schema v0.10.2
The dataTypes are now specifically defined for each base type ('boolean', 'integer', ....) using a 'oneOf' json-schema construct. While all correct specif data-sets (files) will pass as before, the schema checking is now more strict with respect to the use of properties per dataType.
SpecIF Schema v0.10.1
Making the branch v0.10.x consistent. In this branch, entity identifiers must be unique, so a given SpecIF data set can only hold a single revision per entity (SpecIF Level-1: "No revisions"). As any statement subject or object reference can point to the single supplied entity revision anyways, specifying a revision is redundant. Therefore, the schema and the constraint checks have been changed so that all references including statement subjects and objects are made without revision.
Note that beginning with SpecIF 0.11.1, entities with identical ids, but differing revisions can be supplied in a SpecIF data-set (file). References can be made to a specific (supplied) entity revision. This allows SpecIF Level-2: "Instances with revisions" and SpecIF Level-3: "Types and Instances with revision".
The release consists of a JSON schema and a JavaScript function checking the most important constraints.
SpecIF Schema v0.10.0
Following Dublin Core, the objects have been renamed to "Resources", the relations to "Statements" and the attributes to "Properties". Similary, the sources have been renamed to "Subjects" and the targets to "Objects". A statement is a triple "Subject Predicate Object" according to first order predicate logic.
The release consists of a JSON schema and a JavaScript function checking the most important constraints.