v2.5.3

• added first version of FoLiA specification in RDF/SKOS #4 (may still be subject to change), with new RDF namespace
• Added EtymologyAnnotation

v2.5.1

• This release fixes an issue in whitespace handling prior to linebreaks. (#101). Whitespace prior to explicit linebreaks is insignificant.

v2.5.0

• The main focus of this release is a reworked and strictly specified whitespace handling. Some changes were already introduced to this end v2.4.1 but these did not solve the problem sufficiently yet. We have now implemented a strict interpretation of whitespace, documented here: https://folia.readthedocs.io/en/latest/text_annotation.html#whitespace . The new rules are applied to older documents as well so this may lead to different perspective on the text in certain cases, but validators will fall back to the old rules and not cause a hard validation failure if the new rules are not met, preserving backward compatibility. (#88)
• Implemented processor tags, a simple tagging mechanism that gives users some handles to convey extra information they want to make available to certain processors. (#93)
• Added a t-lang element (markup counterpart of the lang element)

v2.4.2

• Predefine some subsets for style annotation #90
• Allow features in markup annotation #89
• Allow features in text content
• Added extra documentation for handling leading/trailing whitespace #88
• Allow for multiple foreign metadata nodes in FoLiA, even in 'native' mode #91

v2.4.1

• Ignore all leading/trailing whitespace in text content #88

v2.4.0

• Added modality annotation (#86) this is now preferred also for sentiment annotation (the dedicated sentiment annotation type is deprecated but remains for backward compatibility) as well as other modalities such as negations, truthfulness, doubt.
• Added a simple set definition for geolocation and an example to the documentation (using metric annotation)
• Minor backward-compatibility breaking change: renamed modalityfeature in coreference links to mod so it doesn't conflict with the new modality element, I've never seen anybody use this aspect of coreference linking in FoLiA yet so it's a small risk I'm taking. Let me know if it causes issues for anybody.
• Reintroduced and documented External annotation (#87), allowing you to separate child documents from parent documents whilst maintaining links.

v2.3.0

• Added the possibility of serialising FoLiA to explicit form. Explicit form is a more verbose XML serialisation that makes assumptions that are usually implicit in FoLiA (such as defaults and element categories) explicit in the output. This facilitates the job for parsers who do not implement the full FoLiA logic. This is meant to be used as an alternative serialisation only in cases where it makes sense (to support such 3rd party parsers). #84
• Documentation and README updates:
  • added the new rust library, amended implementation list
• Added new examples and fixed some existing examples
• Some added flexibility in certain nested of structural elements;
  • allow Word directly under Division
  • allow Linebreaks in tables, figures and lists (outside of items, rows/cells), because these are sometimes used to denote pagebreaks in multi-span tables/figures/lists.

v2.2.1

Minor update release:

• added a syntactic movement example from proycon/flat#138
• added FQL documentation on adding relations (proycon/foliapy#11)
• allow AbstractInlineAnnotation in quote

v2.2.0

• The default text delimiter for <part> and <ref> is now space, but this can be overridden with the space="no" attribute. #61
• Revised "AS ALTERNATIVE" directive in FQL
• Various documentation, test and example updates

v2.1.0

• Set definitions can now define constraints on the combination of classes/subsets used. #50
• Added a t-ref element as a text markup counterpart to ref
• Added flexibility for structure elements (more nesting options)