Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    I would think (but let's wait for an answer by someone who knows definitely) that the best thing to do would be to employ something like Xalan or Xtrans to implement an intermediate XML transformation step, so that your software needs to know only one naming convention. The ability to perform such transformations is one of the major reasons why XML was invented in the first place. Commented Apr 19, 2015 at 7:54
  • @MikeNakis Its a great idea and one I have considered, I was just concerned with memory and processing time with that approach Commented Apr 19, 2015 at 7:58
  • 1
    Processing time will probably suffer, but it should only be by a constant factor, (you should be able to find a tool that works as a filter,) and then it should be noted that if performance is of any concern whatsoever, then XML was probably not the best choice in the first place. Commented Apr 19, 2015 at 8:03
  • 1
    Yes. Essentially you would code one minimal map somewhere, telling the XSLT processor how each of the original files should be transformed. Commented Apr 19, 2015 at 8:43
  • 1
    Since nobody has answered so far, I turned my initial comment into an answer. This will bump this question to the top, so it will be noticed by more people today, Monday. Commented Apr 20, 2015 at 10:01