Lists Home |
Date Index |
Thanks Chris and Alaric, I am much clearer on this, and it is,
thankfully (somewhat) what I thought was the scenario.
My problem with <RecipeML> is, IMO, that it violates
Model-View-Controller (MVC) programming in that it combines data
description and data display in one document.
I have no interest in the CSS or the display criteria of a recipeML
recipe, I just want the data.
I'm willing to acknowledge that there is a use for RecipeML, I just
don't see it as apropos to a XML definition for recipes.
Curious enough, I don't even know what a CSV file is, and Google didn't
really help me to understand it.
I develop in Java for JDBC compliant relational databases, (Frontbase)
is my preferred one; using HTTP as the transport mechanism and HTML
(w/CSS) as the display mechanism.
> ...then you may find it easier to stick to better-established
> standards for such things, like CSV files!
On Nov 21, 2003, at 12:06 PM, Chris Wilper wrote:
> Hi Baiss,
> Exporting to XML is a good step. But you can't
> get interoperability unless you export to a
> more specific, shared format.
> To have interoperability, the programs have to
> be able to import XML, too. If there is a widely
> used recipe XML language (which google tells me
> is the case: http://www.formatdata.com/recipeml/),
> then it would be a good idea to have your program
> allow export to (and import from) that format.
> If another program can read RecipeML, then you're
> all set. If not, but you want to interoperate,
> you could write a XSL stylesheet (or program) to
> transform RecipeML to their format... or you could
> just try to convince them to directly allow imports
> of RecipeML.
> I'm not sure if Quicken imports any form of XML;
> it would be nice, wouldn't it? But just dumping
> any old XML out to a file isn't going to get you
> interoperating with Quicken. If it does support
> any kind of XML import, you have to find out the
> specific form it has to take, and create that as
> output somewhere along the line.
> - Chris
> -----Original Message-----
> From: Baiss Magnusson [mailto:email@example.com]
> Sent: Friday, November 21, 2003 2:41 PM
> To: XML-DEV
> Subject: [xml-dev] Relating to XML
> I have a direct to java client web application which parses a XML file,
> I designed the XML syntax, of recipes into Enterprise Objects (EO's).
> My question is: How does one go about creating interoperability with
> other applications?
> For instance, there is another cookbook application around which has an
> export function and produces an XML type file of similar, but slightly
> different tag syntax than my cookbook program. I would like to import
> it's recipes.
> Is there something about XML services that I am missing?
> I had the same kind of problem with my application
> <www.track-your-finances.com>, where I dumped the transactions into an
> XML file, but then I found no use for those transactions as there was
> no application around which could use the file. I had thought that
> something like Quicken would be able to import the file, but that
> didn't appear to be the case.
Baiss Eric Magnusson