# Schema 5.5 now available: adding CRediT, new record types for blogs and posters, and more - Crossref

**URL:** <https://community.crossref.org/t/schema-5-5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more-crossref/16080>\
**Category:** Content Registration\
**Tags:** metadata, schema, blog, infrastructure, research-nexus\
**Created:** [9 July 2026 13:46 UTC](https://community.crossref.org/t/schema-5-5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more-crossref/16080 "2026-07-09T13:46:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Crossref](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/crossref/32/31_2.png) [@Crossref](https://community.crossref.org/u/Crossref)\
**Post date:** [9 July 2026 13:46 UTC](https://community.crossref.org/t/schema-5-5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more-crossref/16080/1 "2026-07-09T13:46:47Z")

</div>

Research is rarely limited to a single contributor performing a single role. Behind every research output are people contributing in various ways: software development, data analyses, methodology design, and much more. Often, the same person contributes in several of these ways. Until now, Crossref metadata could only capture part of that picture, and this is changing now.

* * *
This is a companion discussion topic for the original entry at [https://www.crossref.org/blog/schema-5.5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more/](https://www.crossref.org/blog/schema-5.5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more/)

---

<div class="post-metadata">

**Author:** ![rclark](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/rclark/32/19_2.png) [@rclark](https://community.crossref.org/u/rclark)\
**Post date:** [9 July 2026 14:57 UTC](https://community.crossref.org/t/schema-5-5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more-crossref/16080/2 "2026-07-09T14:57:23Z")

</div>

Listed on 9 July 2026 14:57 UTC



---

<div class="post-metadata">

**Author:** ![RCUB](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@RCUB](https://community.crossref.org/u/RCUB)\
**Post date:** [27 July 2026 12:26 UTC](https://community.crossref.org/t/schema-5-5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more-crossref/16080/3 "2026-07-27T12:26:44Z")

</div>

Is this schema 5.5 already implemented in Metadata Quality Check/Parse XML against Crossref Schema?

> **[crossref.org : metadata quality check](https://www.crossref.org/XSDParse)**

I have tried to parse an XML file in schema 5.5 and it says it has errors, but then I tried to activate it in the Crossref website for activate DOIs ([https://doi.crossref.org/servlet/home](https://doi.crossref.org/servlet/home)) and then it worked well, and the DOI has been activated.

The errors mentioned are

1. [Error]: s4s-elt-invalid-content.1: The content of ‘#AnonType\_role’ is invalid. Element ‘assert’ is invalid, misplaced, or occurs too often.
2. [Error]: s4s-elt-invalid-content.1: The content of ‘#AnonType\_person\_name’ is invalid. Element ‘assert’ is invalid, misplaced, or occurs too often.

But I alredy checked and the XML file it is written following the same examples of the contributors webpage

> **[Contributors - Crossref](https://www.crossref.org/documentation/schema-library/markup-guide-metadata-segments/contributors/)**
>
> This guide gives markup examples of contributor metadata for members registering content by direct deposit of XML. A contributor is a person or organisation that is considered the author of a work. A contributor may be a person or a group author...

and the best examples in XML in Gitlab

[https://gitlab.com/crossref/schema/-/blob/master/best-practice-examples/5.5.0-article-2-roles.xml?ref\_type=heads](https://gitlab.com/crossref/schema/-/blob/master/best-practice-examples/5.5.0-article-2-roles.xml?ref_type=heads)

Thank you very much for your attention, and I apologise if I did not sent the message in the right place.

---

<div class="post-metadata">

**Author:** ![priddle](https://avatars.discourse-cdn.com/v4/letter/p/f17d59/32.png) [@priddle](https://community.crossref.org/u/priddle)\
**Post date:** [28 September 2026 11:50 UTC](https://community.crossref.org/t/schema-5-5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more-crossref/16080/4 "2026-09-28T11:50:52Z")

</div>

Hello!

My apologies your message from 27 July was missed.

Yes, you are correct about the XML Parser giving errors regarding CRediT roles even if the XML is formatted correctly. This is an issue our team is aware of and they are working on a solution. As of today (Monday 28, September), I don’t have an estimate of when that will be completed, but as soon as I learn more, I’ll post an update here.

If you have any XML that you want us to double check or if you encounter errors during deposit, please feel free to send them to me via [support@crossref.org](mailto:support@crossref.org).

Warm regards,

Poppy

---

<div class="post-metadata">

**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\
**Post date:** [8 October 2026 15:19 UTC](https://community.crossref.org/t/schema-5-5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more-crossref/16080/5 "2026-10-08T15:19:41Z")

</div>

Hello @RCUB ,

Our Metadata Quality Check [XML Parser](https://www.crossref.org/02publishers/parser.html) now supports schema version 5.5. Thanks again for bringing this to our attention!

-Isaac

---

<div class="post-metadata">

**Author:** ![RCUB](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@RCUB](https://community.crossref.org/u/RCUB)\
**Post date:** [9 October 2026 10:44 UTC](https://community.crossref.org/t/schema-5-5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more-crossref/16080/6 "2026-10-09T10:44:25Z")

</div>

Thank you very much for fixing this issue.
