given this example

```
class foo
{
   /** @PHPCRODM\Id /*
   public $id

   /** @PHPCRODM\Node /*
   public $foo

   /** @PHPCRODM\ParentDocument /*
   public $bar

}
```

it will lead to configuring PHPCR ODM to set the id on the ``id`` property, the underlying PHPCR Node (the closest equivalent in the ORM world would be the underlying "row" in a table) to the ``foo`` property and the instance of the parent document (remember PHPCR is a tree database) in the ``bar`` property.

based on this information the goal is to ignore the ``foo`` and ``bar`` properties. however as explained i do not know how to access the PHPCR ODM ClassMetadata inside an exclusion strategy so I am doing this hack based on the property name (``parent`` in this case but of course users could name the property with a parent mapping whatever they want so this doesn't really work in all cases) and on the interface. but like i said .. it should actually be based on the information in PHPCR ODM ClassMetada for the given object being considered.