Skip to content

schema-dts & schema-dts-gen v0.6.0
Compare
Choose a tag to compare
@Eyas Eyas released this 18 May 17:16
v0.6.0
37c81d7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changelog

Changes in schema-dts

  • Support for "Reference-only types" (i.e. {"@id": "..."} objects) to previously-established objects. This allows users to define circular references in a "@graph". (see #107)
  • Defines intermediate SchemaValue<T> for property values (see #104)
  • Skips empty Base types under certain conditions. This shaves 500+ lines of output. (see #104)
  • Make enums much more permissive (see #107)
    • allow relative Enum names when applicable
    • allow https://schema.org/ and http://schema.org/ IRIs for enum values
  • Give Boolean similar characteristics as above.
  • DataType now inherits up-to-date documentation from Schema.org definitions (See #107)
  • Clean up how nested DataTypes are rendered, and support for types like PronounceableText which are data types that have values. (See #109)

Changes in schema-dts-gen

  • Breaking Changes:
    • Property parsing is stricter on custom schema where rangeIncludes references a non-existent type.
    • Only types defined in ontology will be included in our class map and output. This means that a reference to e.g. 'Text' or 'DataType' would previously succeed, but now fails.
  • Support for "Reference-only types" (i.e. {"@id": "..."} objects) to previously-established objects. This allows users to define circular references in a "@graph". (see #107)
  • Defines intermediate SchemaValue<T> for property values (see #104)
  • Skips empty Base types under certain conditions. This shaves 500+ lines of output. (see #104)
  • Prunes DataType objects not referenced in ontology. (see #107)
  • Make enums much more permissive (see #107)
    • allow relative Enum names when applicable
    • allow HTTP and HTTPS protocols when the enum IRI is HTTP (when IRI is HTTPS don't allow HTTP).
  • Implement Boolean as a regular enum (with above characteristics) (See #107)
  • DataType now inherits live documentation from Schema.org rather than saved "well-known" documentations. (See #107)
  • Clean up how nested DataTypes are rendered, and support for types like PronounceableText which are data types that have values. (See #109)

Generated Schema Diff: https://www.diffchecker.com/sxFsWqKU

Assets 2
Loading