# @NotNull vs @Nonnull

**URL:** <https://discuss.kotlinlang.org/t/notnull-vs-nonnull/589>\
**Category:** Uncategorized\
**Created:** [April 27, 2014, 10:42pm UTC](https://discuss.kotlinlang.org/t/notnull-vs-nonnull/589 "2014-04-27T22:42:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikehearn](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/mikehearn/32/1424_2.png) [@mikehearn](https://discuss.kotlinlang.org/u/mikehearn)\
**Post date:** [April 27, 2014, 10:42pm UTC](https://discuss.kotlinlang.org/t/notnull-vs-nonnull/589/1 "2014-04-27T22:42:08Z")

</div>

The latter appears to be standard but it seems kotlin only recognises the IntelliJ-specific former form? Is that intentional or a bug?

It would be nice if I could say “assume everything in this namespace is non-null by default except for things marked @Nullable”. I have a codebase where things (mostly return values and parameters) that can be null are marked as such, and everything else isn’t annotated.

---

<div class="post-metadata">

**Author:** ![abreslav](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/abreslav/32/8279_2.png) [@abreslav](https://discuss.kotlinlang.org/u/abreslav)\
**Post date:** [April 28, 2014, 9:22am UTC](https://discuss.kotlinlang.org/t/notnull-vs-nonnull/589/2 "2014-04-28T09:22:43Z")

</div>

We do not support annotations from JSR 305 (which is not a standard, because it never shipped) yet, but we will eventually.

As of having default nullability for whole libraries, this makes total sense indeed, thanks for the suggestion.