# Adopting v1.0.2

**URL:** <https://discourse.citationstyles.org/t/adopting-v1-0-2/1713>\
**Category:** CSL Development\
**Created:** [February 6, 2021, 1:49pm UTC](https://discourse.citationstyles.org/t/adopting-v1-0-2/1713 "2021-02-06T13:49:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![larsgw](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/larsgw/32/187_2.png) [@larsgw](https://discourse.citationstyles.org/u/larsgw)\
**Post date:** [February 6, 2021, 1:49pm UTC](https://discourse.citationstyles.org/t/adopting-v1-0-2/1713/1 "2021-02-06T13:49:54Z")

</div>

Although the `v1.0.2` release is backwards-compatible, I think I cannot adopt it directly. For example, I could now map the BibLaTeX fields `isan`, `ismn`, `isrn` and `iswc` to their respective CSL properties where I previously mapped them to `number`. However, if I map them to CSL’s `ISAN`/`ISMN`/`ISRN`/`ISWC` then output styles might not fall back to those properties. Should I wait to use those fields until styles are updated or will citeproc fall back on those if `number` is unavailable? Or just use both?

Second, I was curious about the deprecation notice of `*-title-short` variables. I assume that only applies to their use in styles, not in the data model?

---

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [February 7, 2021, 5:56pm UTC](https://discourse.citationstyles.org/t/adopting-v1-0-2/1713/2 "2021-02-07T17:56:49Z")

</div>

> [@larsgw](#):
>
> Second, I was curious about the deprecation notice of `*-title-short` variables. I assume that only applies to their use in styles, not in the data model?

The data model will also be moving to treating titles as objects.

> <https://github.com/citation-style-language/schema/pull/323>
>
> \## Description
> 
> As an alternative to title parsing to support independent form…atting of main and subtitles, this converts title strings to objects, with the following properties:
> 
> \- full
> \- main
> \- sub (an array, to support multiple)
> \- ~sub-sub~
> \- ~alternate~
> \- short
> 
> I added embedded examples to the schema, drawn directly from style guides (MLA and Chicago), and \[here's\](https://bdarcus.github.io/schema/csl-data.html#items\_collection-title) example docs generated from the schema.
> 
> addresses #310.
> 
> \## Alternatives
> 
> Alternatives I considered but rejected (though I don't feel strongly against them) using arrays for parts.
> 
> \`\`\` yaml
> \--- 
> title-alt-1: 
> # change main parts to an array (Denis suggested this possibility)
> content: 
> - Main
> - Subtitle
> - "Second Subtitle"
> short: Main
> title-alt-2: 
> # also change alt to an array
> content: 
> - Main
> - Subtitle
> - "Second Subtitle"
> short: Main
> \`\`\`
> 
> But, after subsequent discussion below, \`sub\` is now an array.
> 
> \## See Also
> 
> https://discourse.citationstyles.org/t/design-principles-for-csl-json/1671
> 
> \## Type of change
> 
> \- \[X\] Variable addition (adds a new variable or type string)
> \- \[X\] Breaking change (fix or feature that would cause existing functionality to not work as expected)
> \- \[X\] This change requires a documentation update