RESTful URI design - is multiple URIs for resources user-friendly
===

Suppose I have the following entities: project, company, director.

The following relationships apply:

 - A project has one company
 - A company has one director
 - A director can be a director in several companies
 - A company can be managing several projects

I have imagined a URI design like this:

     GET  /projects
     GET  /projects/{id}
     GET  /projects/{id}/company
     GET  /projects/{id}/company/director
     PUT  /projects/{id}/company           # makes new/overwrite company
     POST /projects/{id}/company           # updates company
     PUT  /projects/{id}/company/director  # makes new/overwrite director
     POST /projects/{id}/company/director  # updates director

Would it be okay/user-friendly to have several URIs for the same resources, e.g.:

     POST /companies                       # makes a new company
     POST /companies/{id}                  # updates company
     GET  /companies/{id}
     POST /directors                       # makes a new director
     POST /directors/{id}                  # updates director
     GET  /directors/{id}

Is this good URI design according to best practices? What are pros and cons of above URI design?