Should I be using XSLT to transform XML to Multiple EDI formats and vice versa?
-
Hi all, I will be involved in a project where I must translate multiple EDI formats into XML and vice versa? Rather than code all this which I suspect will be impossible as I will be constantly hit with new formats, I was thinking that my app should load an XSLT map with the rules for the translation. I can then create custom XSLT maps on demand. Now my questions before I start: 1. Looking on the web, it seems all articles on XSLT are now quite old so I am wondering if this technology has been superseded in .NET? If so, by what? 2. If I should use XSLT, what would be the best tools to create the maps? I think hand coding will be tough/a bore. By looking the on the web, it seems Stylus Studio is possibly the way to go? I'm not really ridged in my thoughts here so happy if I need to go off in another direction. Many thanks for any advice.
-
Hi all, I will be involved in a project where I must translate multiple EDI formats into XML and vice versa? Rather than code all this which I suspect will be impossible as I will be constantly hit with new formats, I was thinking that my app should load an XSLT map with the rules for the translation. I can then create custom XSLT maps on demand. Now my questions before I start: 1. Looking on the web, it seems all articles on XSLT are now quite old so I am wondering if this technology has been superseded in .NET? If so, by what? 2. If I should use XSLT, what would be the best tools to create the maps? I think hand coding will be tough/a bore. By looking the on the web, it seems Stylus Studio is possibly the way to go? I'm not really ridged in my thoughts here so happy if I need to go off in another direction. Many thanks for any advice.
As long as the EDI is an XML format or can be read into an XMl DOM using a custom XML reader, I'd say it's a splendid idea. Declarative programming - lovely!
tig2810 wrote:
Looking on the web, it seems all articles on XSLT are now quite old so I am wondering if this technology has been superseded in .NET? If so, by what?
Don't think so.
tig2810 wrote:
If I should use XSLT, what would be the best tools to create the maps? I think hand coding will be tough/a bore. By looking the on the web, it seems Stylus Studio is possibly the way to go?
Stylus Studio certainly seems to have strong EDI and XSLT support (looking at their website). Looks good! I've always hand-coded my XSLT, but I've tended to do more involved stuff than mapping data formats, which has required some slightly out of the ordinary XSLT - it's been closer to functional programming thatn data mapping :cool:.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
As long as the EDI is an XML format or can be read into an XMl DOM using a custom XML reader, I'd say it's a splendid idea. Declarative programming - lovely!
tig2810 wrote:
Looking on the web, it seems all articles on XSLT are now quite old so I am wondering if this technology has been superseded in .NET? If so, by what?
Don't think so.
tig2810 wrote:
If I should use XSLT, what would be the best tools to create the maps? I think hand coding will be tough/a bore. By looking the on the web, it seems Stylus Studio is possibly the way to go?
Stylus Studio certainly seems to have strong EDI and XSLT support (looking at their website). Looks good! I've always hand-coded my XSLT, but I've tended to do more involved stuff than mapping data formats, which has required some slightly out of the ordinary XSLT - it's been closer to functional programming thatn data mapping :cool:.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p