Re: Link Livesites: http://www.ctg.albany.edu
Joerg I was browsing the white paper referred to; in http://www.ctg.albany.edu/publications/reports/xml?chapter=9 it mentions that XML files are connected to XSL files by placing links to the stylesheets at the top of the XML files. It then goes on to say: This significantly simplifies content management because it enables you to make changes to only one content file and make no changes to the stylesheets because the content is totally separated from the presentation. Figure 8 illustrates how these XML/XSL transformations occur within the Cocoon publishing framework. This is a little misleading and underplays the true value added by Cocoon in completely separating content from presentation - the connections happen in the sitemap; there is no need to specify stylesheets in your XML files; as soon as you do this you are implicitly mixing content and presentation. If you are able, I think some changes would help clarify the situation. Regards Derek [EMAIL PROTECTED] 30/06/2003 10:03:04 We had it already on the list last week, here is the official announcement. I have added the link in the CVS. Joerg Original Message Subject: RE: Contact Us Form Date: Mon, 30 Jun 2003 09:41:18 -0400 From: Jim Costello [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Yes, We would be glad to be listed on your powered by Cocoon page. Our base url is http://www.ctg.albany.edu. The entire site is done in Cocoon 2, using standard XML/XSL with a docbook schema for our XML documents. The site currently has close to 4000 pages produced by approximately 300 xml/xsl files. We expect to be producing about 10,000 pages by the end of the year with no increase in the number of xml/xsl files. The main content of our site are the reports, guides and studies that our Center produces. We needed a sensible way to manage these documents, control the source file and produce a variety of formats HTML, PDFs, multiple locations on the site. XML and Cocoon has been the answer. The site has only been live for about 1 month, but we've already seen a doubling of our traffic and it's much easier to maintain and find our information on the site now. It's all Cocoon and XML/XSL; no database involvement. We also have a white paper on the site at http://www.ctg.albany.edu/publications/reports/xml that explains our rationale and approach to using xml and cocoon. One other component of the site at http://www2.ctg.albany.edu/egovfirststop/ uses Cocoon 1 and mySQL database to power an information repository application. We will be upgrading this application to Cocoon 2. Jim Costello Web Application Developer Center for Technology in Govenment www.ctg.albany.edu [EMAIL PROTECTED] (518) 442-3812 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Mailscanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Link Livesites: http://www.ctg.albany.edu
Hello Derek, yes, that's obviously misleading. But I'm not related to this page. After the mention on this list last week I only asked them to be listed on Cocoon's Livesites page and Jim Costello sent me this mail below. I added the link in the CVS and forwarded this mail, especially because of the impressive figures. Now the report: It's the typical Cocoon 1.x handling using processing instructions. But I don't know if they wrote their own component handling processing instructions or if the report is outdated or simlpy wrong. The X-Cocoon header clearly states that they use Cocoon 2.0.4, but he also wrote (in the mail below) that they still have Cocoon 1.x in use for a part of their homepage. I'm cc-ing Jim Costello, so he can read and clarify your objections. Regards, Joerg Derek Hohls wrote: Joerg I was browsing the white paper referred to; in http://www.ctg.albany.edu/publications/reports/xml?chapter=9 it mentions that XML files are connected to XSL files by placing links to the stylesheets at the top of the XML files. It then goes on to say: This significantly simplifies content management because it enables you to make changes to only one content file and make no changes to the stylesheets because the content is totally separated from the presentation. Figure 8 illustrates how these XML/XSL transformations occur within the Cocoon publishing framework. This is a little misleading and underplays the true value added by Cocoon in completely separating content from presentation - the connections happen in the sitemap; there is no need to specify stylesheets in your XML files; as soon as you do this you are implicitly mixing content and presentation. If you are able, I think some changes would help clarify the situation. Regards Derek [EMAIL PROTECTED] 30/06/2003 10:03:04 We had it already on the list last week, here is the official announcement. I have added the link in the CVS. Joerg Original Message Subject: RE: Contact Us Form Date: Mon, 30 Jun 2003 09:41:18 -0400 From: Jim Costello [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Yes, We would be glad to be listed on your powered by Cocoon page. Our base url is http://www.ctg.albany.edu. The entire site is done in Cocoon 2, using standard XML/XSL with a docbook schema for our XML documents. The site currently has close to 4000 pages produced by approximately 300 xml/xsl files. We expect to be producing about 10,000 pages by the end of the year with no increase in the number of xml/xsl files. The main content of our site are the reports, guides and studies that our Center produces. We needed a sensible way to manage these documents, control the source file and produce a variety of formats HTML, PDFs, multiple locations on the site. XML and Cocoon has been the answer. The site has only been live for about 1 month, but we've already seen a doubling of our traffic and it's much easier to maintain and find our information on the site now. It's all Cocoon and XML/XSL; no database involvement. We also have a white paper on the site at http://www.ctg.albany.edu/publications/reports/xml that explains our rationale and approach to using xml and cocoon. One other component of the site at http://www2.ctg.albany.edu/egovfirststop/ uses Cocoon 1 and mySQL database to power an information repository application. We will be upgrading this application to Cocoon 2. Jim Costello Web Application Developer Center for Technology in Govenment www.ctg.albany.edu [EMAIL PROTECTED] (518) 442-3812 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Fwd: RE: Link Livesites: http://www.ctg.albany.edu]
FYI Joerg Original Message Subject: RE: Link Livesites: http://www.ctg.albany.edu Date: Tue, 1 Jul 2003 09:03:26 -0400 From: Jim Costello [EMAIL PROTECTED] To: 'Joerg Heinicke' [EMAIL PROTECTED] Joerg and Derek, The white paper (which is nearly a year old) on our Web site does refer to XML applications we had developed using Cocoon 1, so that's why there is no mention of the sitemap of Cocoon2. In fact, that paper is directed to a general web site audience who may be wondering about the advantages/drawbacks of moving from an HTML-based website to an XML-based website. So while we do mention Cocoon since we use it, we primarily focused on general use of XML/XSL. The Web site itself uses Cocoon 2 - with the sitemap performing the functions as noted below of associating stylesheets with XML files - but we didn't start using Cocoon 2 until after we had written the paper. However, in Cocoon 1 the separation of content/style/logic was still achieved when properly implemented within the Cocoon 1 framework. So I don't think the point is incorrect, although I see where it may be a bit misleading or confusing to someone who is familiar with Cocoon. We can look to clarify this in the paper by stating that our references are to Cocoon 1 and that Cocoon 2 handles these things differently and more effectively through its use of the sitemap. But again, the paper is primarily directed to a general audience (not Cocoon specific) and not surprisingly, one of the main questions we'd hear when developing the paper was from Web developers who were familiar with HTML and JavaScript etc., but not too familiar with XML, and asked how you connected your XML files with your XSL stylesheets. That basic separation of content from style is still a big mystery to many HTML users. So that's why we explicitly mention the connection using processing instructions in the paper. Thanks for the comments. We'll try to clear up some of its misleading elements. Jim Costello Web Application Developer Center for Technology in Govenment www.ctg.albany.edu [EMAIL PROTECTED] (518) 442-3812 -Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 2:37 AM To: [EMAIL PROTECTED] Cc: Jim Costello Subject: Re: Link Livesites: http://www.ctg.albany.edu Hello Derek, yes, that's obviously misleading. But I'm not related to this page. After the mention on this list last week I only asked them to be listed on Cocoon's Livesites page and Jim Costello sent me this mail below. I added the link in the CVS and forwarded this mail, especially because of the impressive figures. Now the report: It's the typical Cocoon 1.x handling using processing instructions. But I don't know if they wrote their own component handling processing instructions or if the report is outdated or simlpy wrong. The X-Cocoon header clearly states that they use Cocoon 2.0.4, but he also wrote (in the mail below) that they still have Cocoon 1.x in use for a part of their homepage. I'm cc-ing Jim Costello, so he can read and clarify your objections. Regards, Joerg Derek Hohls wrote: Joerg I was browsing the white paper referred to; in http://www.ctg.albany.edu/publications/reports/xml?chapter=9 it mentions that XML files are connected to XSL files by placing links to the stylesheets at the top of the XML files. It then goes on to say: This significantly simplifies content management because it enables you to make changes to only one content file and make no changes to the stylesheets because the content is totally separated from the presentation. Figure 8 illustrates how these XML/XSL transformations occur within the Cocoon publishing framework. This is a little misleading and underplays the true value added by Cocoon in completely separating content from presentation - the connections happen in the sitemap; there is no need to specify stylesheets in your XML files; as soon as you do this you are implicitly mixing content and presentation. If you are able, I think some changes would help clarify the situation. Regards Derek -- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
