Skip to content

0.5.8 Release Notes

Gregory Engel edited this page Apr 14, 2017 · 3 revisions

ANS 0.5.8

New Element Types

Quote

A new quote element has been added to support quotes with multiple elements, nested quotations, and an optional citation. This element supercedes and deprecates (but does not replace) the previous blockquote element.

Example: https://github.com/washingtonpost/ans-schema/blob/master/tests/fixtures/schema/0.5.8/story-fixture-good.json#L311

https://github.com/washingtonpost/ans-schema/issues/89

Corrections

Corrections are now available as a content elements. The top-level .corrections field remains in place and should not be duplicated in the corrections elements. The new correction element should be used for corrections that should appear in-line (e.g., a correction specific to a paragraph.) Top-level corrections should be used for article-wide corrections (e.g., a notice at the top of the a story that it has been found to be fabricated.)

Example: https://github.com/washingtonpost/ans-schema/blob/master/tests/fixtures/schema/0.5.8/story-fixture-good.json#L342

Element Groups

A new element_group element has been added to support indicating arbitrary relationships between content elements (which still must be in sequence.)

Example: https://github.com/washingtonpost/ans-schema/blob/master/tests/fixtures/schema/0.5.8/element-group-fixture-good.json

New Fields / Functionality

Attached Redirect

Put a redirect object in related_content.redirect[0] to indicate that the content has an attached redirect. This content item will be searchable in Arc Content API, will appear in search results and landing pages, but will return a PageBuilder redirect header when requested directly.

Alignment

Content elements can now have an alignment property set. This intended to loosely mirror the functionality of a CSS float, but should not be assumed to be honored in any particular rendering environment.

https://github.com/washingtonpost/ans-schema/issues/85

WebSked

Workflow, Planning, Pitches

https://github.com/washingtonpost/ans-schema/pull/106

Named Entities

Clavis will generate these at a later date.

https://github.com/washingtonpost/ans-schema/pull/125

Current and Future Publishing Status

The current and future publishing status of known published or to-be-published editions of stories can now be represented on non-published copies of content items.

https://github.com/washingtonpost/ans-schema/issues/122

Refined schemas for comments, source, tags and labels

These objects were all present in the schema but largely undefined. They now have explicit schemas reflecting actual usage.

https://github.com/washingtonpost/ans-schema/issues/93

https://github.com/washingtonpost/ans-schema/issues/92

https://github.com/washingtonpost/ans-schema/issues/87

Miscellaneous