What limitations should there be on contentDirectory?

[zimeon]

As currently defined there are no restrictions on what contentDirectory might be. Perhaps:

• It should be a single path element not a complex path (ie. no /) ?
• It should have the same small number of limitations that are placed on logical paths (cf. Logical Paths: Allowed Characters and Path Separators #411) ?

Seems like an edge case so this could be left until after 1.0.

[pwinckles]

The spec does forbid / here.

The contentDirectory value MUST NOT contain the forward slash (/) path separator.

[zimeon]

Thanks @pwinckles , that certainly answers my first bullet. I wonder whether there should be any other restrictions? For example, a contentDirectory of .. or . would not seem good

[pwinckles]

Yes, I agree. I am not allowing them in my client.