|
|
|
| The following comment has been added to this issue: |
[ Permlink ] |
|
Author: Anahide Tchertchian
Date: 07/06/07 18:37
Comment:
For lists it would be good to use right away the XPath / JCR syntax,
if possible, which is
n:names[3]
for the third element (warning, first element in XPath is 1, not 0).
Also I'd like to use a path-based syntax, like in XPath, for
subelements:
n:names[3]/n:firstName
that way, there's a minimum number of things to learn for the
framework users and known concepts are reused and we're close to
existing standards.
Of course all this is not URL- and EL-compatible...
Florent
|
|
Only the dublincore schema declares the "dc" prefix, all schemas should declare one.
One way to use the prefix when retrieving a property value would be:
getProperty("dc:title")
or getProperty("dublincore:title") for compatibility (?)
When using complex properties:
"n:name.n:firstName" or "namespace.name.firstName for compartibility (?)
When using lists:
"n:names#3.n:firstName" or "namespace.name#3.firstName for compatibility (?)
This has to be consistent with restful urls generated (see NXP-1106) and jsf document resolver (that currently uses #{document.schemaName.fieldName}) even if some characters may be forbidden there.
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
