Check this out:

    $ cat a.php
    <?php
    trait Foo { static $b = 'foo'; }
    class Bar { static $b = 'bar'; }
    class Baz { use Foo; static $b = 'buh'; }
    class Qux { use Foo; static $b = 'azdg'; }
    echo Foo::$b;
    echo Bar::$b;
    echo Baz::$b;
    echo Qux::$b;
    ?>

    $ php a.php
    Sep 25 00:29:05 dev-robert php: PHP Stack trace:
    Sep 25 00:29:05 dev-robert php: PHP   1. {main}() /home/robert/a.php:0
    Sep 25 00:29:09 dev-robert php: PHP Fatal error:  Baz and Foo define the same property 
    ($b) in the composition of Baz. However, the definition differs and is considered incompatible. 
    Class was composed in /home/robert/a.php on line 4

It's okay to define this value in a trait, but if it gets used with a different value in a class implementing the trait, then you get a fatal error. Any time I run into a situation where I have to provide a name like this, I try to ask myself if there's a better way. 

@nmonterroso: What's the motivation for including this name value? How do you expect implementing classes will use this value?