Josias Thöny wrote:
[...]
- change site managers to return UUIDs for URLs
- implement link resolving component
- update "Insert Link" editor functionality
- update DocumentManagerImpl not to move sources when content is moved
- check which other parts of the code will be affected
(document ID string magic)
What did I forget?
Perhaps a migration tool?
Yes, that's an important point.
One thing which hasn't been discussed yet is how internal links would
look like in the xml. Can we still use the xhtml:a element?
<xhtml:a href="550e8400-e29b-11d4-a716-446655440000_en">foo</xhtml:a>
Or with a special scheme:
<xhtml:a
href="lenyalink://550e8400-e29b-11d4-a716-446655440000_en">foo</xhtml:a>
I'd prefer this option, maybe even
lenyalink://550e8400-e29b-11d4-a716-446655440000/en
to clearly separate UUID and language.
Or do we need a new element, like e.g.
<lenya:link uuid="550e8400-e29b-11d4-a716-446655440000"
lang="en">foo<lenya:link>
I'm not quite sure - the first option has the advantage that the XML
schema is not affected, but the second makes it clearer what is to
be treated as an (internal) link.
Maybe the first option in connection with
ResourceType.getLinkAttributeXPaths() is sufficient.
On the other hand, the <lenya:link> concept seems cleaner than the
link attribute XPath solution ...
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
