Hello Fabián Mandelbaum,
First of all, IMHO, you do not have to entirely commit to David's model. IMHO,
some of the rules are based on the frontend technology that is displaying the
data (like number 4, beware of same name siblings. When creating frontends
based on repository paths and cache
Hello Ard, Tobías,
first of all, let me thank you for your answers. After reading
Tobías answer to rule #1 and then reading Ard's I realized that I may
have misunderstood the 'data vs. structure' thing, and thank you both
for your clarifications.
OTOH, my file node (extending nt:file)
Tobias Bocanegra wrote:
the nice thing about not having SNS and having a folder
structure for the language is that you can easily access it
via webdav. so you just drop your translated files in the
respective folder again, and your done. having SNS and meta
data just renders this
Ard,
one thing I forgot to ask: is this 'filter' thing available
somewhere? Is it part of JR1.5?
thanks in advance.
Ard Schrijvers escribió:
Hello Fabián Mandelbaum,
First of all, IMHO, you do not have to entirely commit to David's model.
IMHO, some of the rules are based on the
On 9/8/08, Ard Schrijvers [EMAIL PROTECTED] wrote:
Hello Fabián Mandelbaum,
First of all, IMHO, you do not have to entirely commit to David's model.
IMHO, some of the rules are based on the frontend technology that is
displaying the data (like number 4, beware of same name siblings. When
Ard,
one thing I forgot to ask: is this 'filter' thing available
somewhere? Is it part of JR1.5?
No, that is purely theoretical, nothing in Jackrabbit and not planned.
It is part of a virtual layer we build on top of Jackrabbit, but not
part of Jackrabbit indeed
-Ard
But it
OTOH, my file node (extending nt:file) already has the
lang as metadata (a property). I'm doing tests both extending
nt:file (1st
attempt) and nt:resource (as David suggests), I don't really
find any difference, though I know there may be some
difference in performance, or
OK, I'll make sure my XPath queries have the lang attribute somewhere to
limit queries to a given lang.
Thanks!
Ard Schrijvers escribió:
OTOH, my file node (extending nt:file) already has the
lang as metadata (a property). I'm doing tests both extending
nt:file (1st
attempt) and
OK Alex, thanks!
Alexander Klimetschek escribió:
On Mon, Sep 8, 2008 at 2:45 PM, Fabián Mandelbaum [EMAIL PROTECTED] wrote:
Ard,
one thing I forgot to ask: is this 'filter' thing available
somewhere? Is it part of JR1.5?
No, that is purely theoretical, nothing in Jackrabbit
Hello Tobías, thanks for your answer.
Approach #2 is indeed, natural, however the problem I see with
approach #2 is that it seems to break David's rule #1 (data 1st vs.
structure 1st) by imposing a fixed content structure to projects (for
example, /common/ /en/ /fr/ /es/ /it/ etc.).
I'm not
Hello there,
I'm considering David's Model
(http://wiki.apache.org/jackrabbit/DavidsModel) and was wondering how
would David handle translations of documents.
Let's say I have a file, for example: file.xml which is written in
English, and I want to store its translation to, say, Spanish.
hi,
it certainly depends on your intention, but having a folder for each
language is imo the best approach. you might have other resources
later (like images) that are language dependent that you can put in
the folder.
regards, toby
On 9/6/08, Fabián Mandelbaum [EMAIL PROTECTED] wrote:
Hello
12 matches
Mail list logo
