RE: Hello and question
Here's the context: We have several hundred thousand time series, but they will, for the foreseeable future, remain in their present repository (the Fame time series database application.) However, there are a few hundred series which our staff use regularly, and which they need to query, graph, plug into reports, save as PDFs, import into spreadsheets, etc. By and large, the Cocoon framework seems like a promising way of providing these multiple views of the data. At this early stage in our planning, we're considering a mechanism whereby these few hundred series are dumped from Fame into XML, one file per time series. We explicitly don't want to dump the data into some intermediate format (e.g, Oracle or whatever), because Fame will remain the core database. I suppose that you can't hit Fame (whatever that might be) directly? Or that you are afraid of the load that hitting Fame directly would put on the system? I don't really see why dumping the data into Oracle or whatever is any different from creating an intermediate XML file? They are both data stores... You need to determine what the functional requirements are in terms of performance and querying and let that determine the technical architecture and not just pick operating system managed XML files arbitrarily. However, either way Cocoon still may be a good fit; it can handle output from an relational database (with JDBC) almost as easily as handling an XML file directly and if you have to create the XML from scratch it probably makes more sense to do that with Cocoon instead of using some other external tool to do the job. - 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]
Hello and question
Hello, A word of introduction... I belonged to the list a year or so back, but got sidetracked from Cocoon for awhile. Now I'm back tinkering with 2.04, and have no shortage of questions. Here's one (a rather broad and newbie-ish one.) In my project I have a large number of XML files that correspond to time series. Each is the same format: timeSeries seriesNameP12345/seriesName observation date2001-03-12/date value1.25/value date2001-03-13/date value1.28/value /observation /timeSeries ... etc. Now: using the various mechanisms available through Cocoon, how best would I query a given file (directly, as opposed to through a database) via an HTML form, e.g., to extract and display only selected dates/values? I have a vague grasp of various ways I could do this if my data were to reside in an intermediate DBMS of some sort, but the objective here is to store each time series as an XML source file only, while still being able to query it. Does this make any sense? :) - Brent Eades, Almonte, Ontario http://www.almonte.com http://www.bankofcanada.ca - 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]
RE: Hello and question
Brent, you may try inserting them into Xindice (an XML DBMS [1]) or, much simpler, search them by the use of XSLT. Though, I must say, time series data beg to live in a Relational model. Regards, [1] http://xml.apache.org/xindice/ - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - -Original Message- From: Brent Eades [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 10:48 PM To: [EMAIL PROTECTED] Subject: Hello and question Hello, A word of introduction... I belonged to the list a year or so back, but got sidetracked from Cocoon for awhile. Now I'm back tinkering with 2.04, and have no shortage of questions. Here's one (a rather broad and newbie-ish one.) In my project I have a large number of XML files that correspond to time series. Each is the same format: timeSeries seriesNameP12345/seriesName observation date2001-03-12/date value1.25/value date2001-03-13/date value1.28/value /observation /timeSeries ... etc. Now: using the various mechanisms available through Cocoon, how best would I query a given file (directly, as opposed to through a database) via an HTML form, e.g., to extract and display only selected dates/values? I have a vague grasp of various ways I could do this if my data were to reside in an intermediate DBMS of some sort, but the objective here is to store each time series as an XML source file only, while still being able to query it. Does this make any sense? :) - Brent Eades, Almonte, Ontario http://www.almonte.com http://www.bankofcanada.ca - 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] - 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]
Re: Hello and question
You can use XPath in XSL. Something like xsl:for-each select=timeSeries/seriesName/observation[ date='2001-03-13']/* xsl:... /xsl:for-each In cocoon, there are ways to loop through a directory, so you can query every file timeSeries seriesNameP12345/seriesName observation date2001-03-12/date value1.25/value date2001-03-13/date value1.28/value /observation /timeSeries ... etc. Now: using the various mechanisms available through Cocoon, how best would I query a given file (directly, as opposed to through a database) via an HTML form, e.g., to extract and display only selected dates/values? - 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]
Re: Hello and question
As always, ... it depends ... You haven't said how many different time-series files you will be using and you haven't said how often these will be updated and/or queried. Your proposed solution may be appropriate and quite simple to implement or it may be a disaster in the making. Outsiders can't help you without much more information. On Tue, 2003-01-21 at 16:47, Brent Eades wrote: Hello, A word of introduction... I belonged to the list a year or so back, but got sidetracked from Cocoon for awhile. Now I'm back tinkering with 2.04, and have no shortage of questions. Here's one (a rather broad and newbie-ish one.) In my project I have a large number of XML files that correspond to time series. Each is the same format: timeSeries seriesNameP12345/seriesName observation date2001-03-12/date value1.25/value date2001-03-13/date value1.28/value /observation /timeSeries ... etc. Now: using the various mechanisms available through Cocoon, how best would I query a given file (directly, as opposed to through a database) via an HTML form, e.g., to extract and display only selected dates/values? I have a vague grasp of various ways I could do this if my data were to reside in an intermediate DBMS of some sort, but the objective here is to store each time series as an XML source file only, while still being able to query it. Does this make any sense? :) - Brent Eades, Almonte, Ontario http://www.almonte.com http://www.bankofcanada.ca - 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] -- John Austin [EMAIL PROTECTED] - 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]
Re: Hello and question
On 21 Jan 2003 at 18:29, John Austin wrote: As always, ... it depends ... You haven't said how many different time-series files you will be using and you haven't said how often these will be updated and/or queried. Your proposed solution may be appropriate and quite simple to implement or it may be a disaster in the making. Outsiders can't help you without much more information. Yes, I know it was a broad (and not especially Cocoon-specific) question. Here's the context: We have several hundred thousand time series, but they will, for the foreseeable future, remain in their present repository (the Fame time series database application.) However, there are a few hundred series which our staff use regularly, and which they need to query, graph, plug into reports, save as PDFs, import into spreadsheets, etc. By and large, the Cocoon framework seems like a promising way of providing these multiple views of the data. At this early stage in our planning, we're considering a mechanism whereby these few hundred series are dumped from Fame into XML, one file per time series. We explicitly don't want to dump the data into some intermediate format (e.g, Oracle or whatever), because Fame will remain the core database. So I suppose I was just trying to get a handle on what the preferred methods would be of using web forms to do simple queries on these XML files... other folks mentioned XSLT, which I realize would be one route... but I still don't know enough about JSP, XSP, etc, to know what other mechanisms might be available. - Brent Eades, Almonte, Ontario http://www.almonte.com http://www.bankofcanada.ca - 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]
Re: hello example question
There is a really good article on www.ibm/developerworks/ called introduction to cocoon 2. It explains the whole sitemap concept in detail. John Moylan - 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]