@bschussek @simensen

Bernhard -

I have a quick test that should help me see where you are at.

I think maybe Beau gets where both of us are coming from and
might not know how to bridge the gap or thinks the more liberal
approach (mine) is not going to be easily understood by FIG folks
or even work, maybe, I'm not sure.


I have a quick test that should help (at least me):


/path/to/packages/foo-bar/
    src/
        Baz.php
        Qux/
            Quux.php
            Quux2.jpg

What would be the "correct" set of name spaces, from your perspective?

Choice A:

Foo\Bar\Baz
Foo\Bar\Qux\Quux


Choice B:

Foo\Bar\Baz
Foo\Bar\Qux\Quux
Foo\Bar\Qux\Quux2

At this point, I'm guessing you would say A.

What I have been doing is B. (And, yes, I will put back the file extensions.)

So, if I'm right in my guess, then both of us should have a better
perspective of why the other is confusing.

I have been applying "virtual paths" (PHP's namespacing paths) to every single
file and folder.


Let me know if what I guessed about your perspective is correct or wrong. And,
I'm going to issue another PR against your repo - this time for PSR-X - only for
purposes of illustration - not asking you to commit it.

I am going to change the rules of PSR-X so that they reflect the rules
I am operating
under.

Thanks.



On Sat, Jun 22, 2013 at 1:25 PM, Bernhard Schussek <notifications@github.com
> wrote:

> In proposed/resource-location.md:
>
> >  **Namespace**: Given a FQCN `\A\B\C\D`, the namespace of that class is `\A\B\C`.
> >
> >  ### 1.2 Resource URIs
> >
> > +>> Would you agree to calling these Namespace URIs?
>
> Ah ok, I already thought that I was probably misunderstanding you :) Great!
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/bschussek/fig-standards/pull/1/files#r4831519>
> .
>