The thing is - all these interfaces represent a "feature" and can be split into two categories' get and set. And each feature can correspond to an admin extension. So they all seem to be of a kind irrespective of if the deal with objects or scalars.

David Buchmann <notifications@github.com> wrote:
>> @@ -0,0 +1,33 @@
>> +<?php
>> +
>> +namespace Symfony\Cmf\Component\Routing;
>> +
>> +use Knp\Menu\NodeInterface;
>> +
>> +/**
>> + * Interface to be implemented by content that exposes editable menu
>referrers.
>> + * This is used with the Sonata MenuAwareExtension.
>> + */
>> +interface MenuAwareEditInterface
>
>ups, indeed while "aware" just means something knows about something
>else, symfony is using this when something wants to be told about those
>things, hence the setters.
>
>for publish workflow i think its fine, as this is not about some other
>entity but about metadata fields. i don't think `Access` is more
>telling than `Edit`. but indeed for what i try to introduce here, its
>not a nice name. there is no MenuAwareInterface as we don't need that,
>but just the RouteAwareInterface. we could try to find better names for
>those. i have unfortunately no great idea right now.
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/symfony-cmf/MenuBundle/pull/103/files#r5437724

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.