RE: [Lenyacms-dev] Document xml standardization

Hello Felix,

see my answer below:

> -----Original Message-----
> From: Felix Maeder [mailto:[email protected]]
> Sent: Thursday, April 17, 2003 6:03 PM
> To: Lenya Developers List
> Cc: Wyona Developers List
> Subject: [Lenyacms-dev] Document xml standardization
>=20
>=20
> I think we should also try to standardize the document xml to some=20
> extent. The benefit would be that we could have a generic handling of=20
> metadata and generic solutions for navigation and overview pages. I=20
> suggest three sections: metadata, header and body (although I find it=20
> often difficult to decide if something is "metadata" or=20
> "data" - a title=20
> or an abstract are part of the data but they could also be considered=20
> metadata).
>=20
...

That sound good. I like the part where you use DC for the metadata! I =
think that will make life a lot easier ;-)

>=20
> Problems/open questions:
> - How is the xhtml doctype handled? The idea of the xhtml doctype is=20
> that the user can upload any xhtml document, which is then=20
> inserted into=20
> the "frame" provided by the cms (resp. the body part of the xhtml is=20
> inserted). How do we then provide the standard lenya and dc elements?=20

If you use xhtml there are 2 use cases:
1) the document contains the metadata within a <meta> tag.
2) the document contains no metadata

case 1) then would be "easy" -> xslt to the lenya doc
case 2) standard "to edit"

> Shall we store them in a different file and make the values=20
> (metadata,=20
> navigation title etc.) editable with the bitflux or xopus?

It makes more sense to separate the metadata from the the file! That way =
the author can edit the metadata (and the uploaded file -> which have to =
be in some "standard" format, or not?)

> - How is metadata for multilingual pages handled? If every=20
> language has=20
> its own document, there would also be different metadata for every=20
> language (that have to be entered and maintained). Does this=20
> make sense?=20

No way, Jos=E9 ;-) Ok, let me explain why that does not make much sense:
I have the SAME document in 3 different languages. The information of =
this document are the same in e.g. German, Spanish or English. The only =
thing that will be different is the "caption" of the information! The =
same is true for the metadata.

I developed a reporting tool (different languages for the same document) =
and I want to explain it with a report as example. I have ONE file with =
different languages. Each <report/> is for ONE language. The file =
"report.xml" has 2 languages, but can be extended with n languages =
without touching a pipeline. Here is the example:
<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<reports>
<report lang=3D"de">
<anschreiben>Das Telefonmarketing telefoniert zur Zeit die Telefonaktion =
"WI_int 200302 SAI". Sollte der Kunde Zusatzinformationen w=FCnschen, =
erhalten Sie von uns diesen Ausdruck mit der Bitte, entsprechendes zu =
veranlassen.</anschreiben>
<aktion>
<main>Zusatzinformationen:</main>
<questions>
<question no=3D"1">
<text>Frage: M=F6chten Sie weitere Informationen von Weidm=FCller</text>
<sub>Antwort des Kunden:</sub>
</question>
</questions>
<informationen>Info-Text</informationen>
</aktion>
</report>
<report lang=3D"it">
<anschreiben>Attualmente il telemarketing sta chiamanda per l'azione =
"WI_int 200302 SAI". Se il cliente desidera informazion i supplementari =
riceuerete il  seguente output. Vi preghiamo cortesemente di occuparvi =
delle richieste riportate nel "testo infomatino".</anschreiben>
<aktion>
<main>Informazioni suppplementari:</main>
<questions>
<question no=3D"1">
<text>Domanda: Desiderate altre informazioni dalla Weidmm=FCller</text>
<sub>Risposta del cliente:</sub>
</question>
</questions>
<imformationen>Testo informativo:</imformationen>
</aktion>
</report>
</reports>

> Or should the metadata be stored in different file?

Yes they should.

King regards=20
Thorsten

>=20
>=20
> -Felix
>=20
>=20
>=20
>=20
> --=20
> Felix M=E4der          [email protected]     +41 1 272 9163
>                       Wyona AG, Hardstrasse 219, CH-8005 Z=FCrich
> Open Source CMS      http://www.wyona.org http://www.wyona.com
>=20
>=20
> _______________________________________________
> WyonaCMS-dev mailing list
> [email protected]
> http://wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev
>=20