Issue 6641 - [RFE] Possible to use XML as datasource in Writer (Calc, etc.)
Summary: [RFE] Possible to use XML as datasource in Writer (Calc, etc.)
Status: CONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Windows 2000
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-29 22:51 UTC by erlingd
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description erlingd 2002-07-29 22:51:37 UTC
Please bare with me - Im not good at writing these kind of descriptions.
So basically I'll give an example of why and what I mean !

You have the following:
  "inv1234.xml" One XML file with data (eg. Invoice with customer info, and 
details)
  "inv.dtd" One DTD file for the invoice file.
  "invoice.stw" One OO.o Writer Template file.

You would like to generate a
  "invoice1234.sxw" One OO.o Writer Text Document. (Could be a file containing 
both "inv1234.xml" and "invoice.sxw" so adding more data could be possible ?!?)

It should be possible to generate the "invoice.stw" with only the "inv.dtd".

Step 1. - Create the "invoice.stw"
* Start Writer
* Select Tools|Data Sources|New Data Source
* In "Database type"  choose  "XML-DTD"
* In "Database DTD" specify "DTD:inv.dtd"
* Choose "Apply"
(OO.o Writer process the DTD and generate a tree (?) with possible fields)
(This "tree" should be shown as the Stylist - so drag'n drop of fields is 
possible)
* Author writes the template - and drag's fields into the document.
* Save the file as a Writer Template - named "invoice.stw"

Step 2. - Create the "invoice1234.sxw"
* Start Writer
* Choose File|New Templates and Documents
* Choose the "invoice.stw"
(OO.o Writer examines the template - and prompts for a XML file that is based 
on the "inv.dtd")
* Specify the "Database URL" as "XML:inv1234.xml"
(OO.o Writer now merges the template and the data)
* The user saves the document as "invoice1234.swx"


If I should specify more please send me a mail.

Erling Damsgaard
famdam@tdcadsl.dk
Comment 1 erlingd 2002-08-11 13:25:14 UTC
Should properly be under "database access" !

Comment 2 Frank Schönheit 2002-08-12 07:25:57 UTC
changing type from ENHANCEMENT to FEATURE - this definatively would
require some more work that just enhancing an existent feature.

Additionally, it would need some more extensive design
(The first thing which comes to my mind is that basing a data source
on a DTD only, and not on concrete data, pretty much contradicts the
current data source concept, where a data source refers to the data,
not to the description of the structure of the data.
The second thing is that we would need restrictions for the DTD - we
would have to require a certain structure.)
Comment 3 erlingd 2002-08-12 16:15:59 UTC
But is it impossible ?

Of cause it could be broken into 2. items.
1. Use of XML file as a datasource.
2. Use of DTD file for data-structure and XML for late-binding data.

or just one where you MUST supply DTD and XML at the same time.

---------------------
This, again, results in new questions - eg. a DataBrower for XML and 
Query language for retrieving data.

Pls. respond if I need to clarify anything :-)

Regards
Erling Damsgaard
mailto:famdam@tdcadsl.dk
Comment 4 Frank Schönheit 2002-08-13 14:42:41 UTC
Erling,

/nothing/ is /impossible/ :). I just said it requires more work, and
more design, as it contradicts the current data source concept (where
there is no late data binding) ....

Frank
Comment 5 Frank Schönheit 2002-08-13 14:44:53 UTC
One more thing: I am not really sure how important XML as permanent
backend will become. A purely XML based database format (with one
table = one file) will most probably have horrible performance. Any
more sophisticated solutions are even more complex, and I do not think
that we should start designing JAPS (just another proprietary solution
:) here.

There was a discussion recently in dev@dba, perhaps you want to dig
the archives ....
Comment 6 dirk.grobler 2002-10-08 12:40:38 UTC
Hey Frank,

can you please followup on this.

Thanks,
Dirk
Comment 7 Frank Schönheit 2002-10-08 12:54:23 UTC
I accept this issue. However, this only means I see it as a valid
feature request. Honestly, I do not think that we can give high
priority to this in the short/mid term future.
Comment 8 Frank Schönheit 2002-12-19 14:46:43 UTC
setting target milestone to "not determined"
Comment 9 Frank Schönheit 2003-04-28 16:20:38 UTC
adding "[RFE]" to subject which makes generated reports easier to read ...
Comment 10 hans_werner67 2004-02-02 12:49:18 UTC
change subcomponent to 'none'
Comment 11 Frank Schönheit 2004-07-30 23:06:31 UTC
assigning to user experience team for consideration, according to
http://qa.openoffice.org/issue_handling/handling_RFEs.html

erlingd, OOo w2.0 will implement XML based forms as described in:
http://specs.openoffice.org/appwide/xforms/GUI_spec_part1.sxw
http://specs.openoffice.org/appwide/xforms/GUI_spec_part2.sxw

You may want to have a look at those, and see how well it fits what you're
suggesting here.
Comment 12 bettina.haberer 2010-05-21 14:58:30 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".