Hi,
The problem with Option 2 is that in read-only mode it works, however, when
you start manipulating regular document as if they were ND (e.g. add a
child document or go to the document Administration), you need to convert
the simple document into a ND (e.g. move X.Page to X.Page.WebHome) and the
result would most certainly impact applications. Not sure if this is a
problem that impacts only the transition period, but IMO it`s worth keeping
in mind.
A second (maybe not vital but still valid) issue with Option 2 is URLs. I
understand we plan to resolve /bin/view/X/Y to X.Y if it exists, then try
X.Y.WebHome and ultimately fallback to the page not found error. The issue
I see is that if at point A in time X.Y.WebHome exists and at a later point
B in time the document X.Y is also created, then any existing
"/bin/view/X/Y" URLs that previously existed will no longer point at
X.Y.WebHome, but will now point at X.Y instead, effectively hijacking it.
The only way of accessing X.Y.WebHome after point B in time would be to use
/bin/view/X/Y/WebHome and our objective was to remove "WebHome" from the UI
or URLs.
Even with the above in mind, I still favor Option 2, since option 1 sounds
unrealistic in terms of work to be done an ensuring consistency across
implementations.
Thanks,
Eduard