1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
re colin, |
5 |
|
6 |
On Monday 12 August 2002 18:56, Colin Morey wrote: |
7 |
> (ie every <start> has a |
8 |
> corresponding </start>) |
9 |
|
10 |
actually this would be well-formed xml. valid xml has to be |
11 |
well-formed and must include a dtd in addition. however, for |
12 |
many purposes, well-formed xml is sufficient. |
13 |
|
14 |
> However I'm not sure what you mean by it being astonishing |
15 |
> that it's not valid html.. if you mean that the html generated |
16 |
> by the xsl/xml interaction is not valid, then that's a fair |
17 |
> point, |
18 |
|
19 |
yep. that's what i meant. |
20 |
|
21 |
> (and incidently I believe it is a fault of the xsl not |
22 |
> the xml. |
23 |
|
24 |
that's what i meant again :) just check the xsl stylesheet you |
25 |
use. for example, a valid html page has to declare which dtd it |
26 |
uses at the beginning of each page (see |
27 |
http://www.w3.org/TR/1999/REC-html401-19991224/sgml/dtd.html). |
28 |
this has usually to be done in the xsl stylesheet. |
29 |
|
30 |
> > yep. nevertheless it's wise to choose a powerful, rather |
31 |
> > generic language such as xml/xsl as base language (to easily |
32 |
> > batch-transform content into other formats). |
33 |
> |
34 |
> hmm, that is exactly what we've done.. all of the docuements |
35 |
> are in xml and then get "translated" into html when the site |
36 |
> is built. |
37 |
|
38 |
fine. yep, it's the usual thing to do the transformations on the |
39 |
server-side. |
40 |
|
41 |
regards |
42 |
|
43 |
dan |
44 |
|
45 |
ps. i think i have said what had to be said ;) |
46 |
|
47 |
- -- |
48 |
...::: Daniel Mettler | http://www.numlock.ch :::.... |
49 |
|
50 |
-----BEGIN PGP SIGNATURE----- |
51 |
Version: GnuPG v1.0.7 (GNU/Linux) |
52 |
|
53 |
iD8DBQE9WA4+SLYjgrGjnWQRAl8EAJkB00GX0oMiJZX4nR+5E5XHKgUfdQCgqDvP |
54 |
lDaDqCzQod2A37n2LgSqzuw= |
55 |
=m5Nq |
56 |
-----END PGP SIGNATURE----- |