Peter I think we are agreeing (?) on the issue of proprietary : in essence, any code that you do not write yourself is 'proprietary' in some way - it "belongs" to someone. I agree that OS can "whither" and you may have a system on hand that is not being developed or maintained.... but at least you still have the code. I have purchased commercial products before without code (the compnay wanted to save money!) and have ended up rewriting some apps because of a lack of continued support.... As for the XSP thing - you have said yourself that someone is who not a Java expert/guru would not be able to write 'complex' Cocoon applications without the use of XSP - for the rest of us XSP fills a perfectly valid need in a way that allows us to focus on XML and XSLT; ideally, of course, there would be a team effort for such apps and each person could get focus on what he/she is best at in order to develop a "perfect" app. Unfortunately, in my "little world" I do not have such and must do the best I can with what I can learn...
>>> [EMAIL PROTECTED] 30/01/2003 05:12:45 >>> > Thanks for the comments; I am still not sure I > understand or agree with the "proprietary" code part; > my definition (based around ownership) seemingly disagrees > with yours - we will then obviously disagree about the > implications... For purposes of evaluating information technologies I consider a technology proprietary if it is only available from a single source (or perhaps a closed consortium). Eg. an AS/400 is proprietary a PC is not, MS Excel is proprietary, spreadsheets, in general, are not. When a technology happens to be an Open Source project your concerns are probably less than if the source was an obscure vendor with minimal revenues. None-the-less many Open Source initiatives have withered on the vine in the past. As I've also implied, it's not just an issue of long term support; portability can be an issue. The other issue is the cost of acquisition: when something is available from multiple sources it there is competition to drive down prices (not a concern with Open Source) and competition to include features (including good documentation :-)... However, all this is just incidental to the reason for my original response: the fact remains that you don't need XSP to write a major Cocoon application... -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. "The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy." --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
