Jamal; I do see what you mean now. The export modules only output the XML and none of the directives. We have marked this as a defect and will fix in an upcoming version of TopBraid Suite.
-- Scott On Jun 21, 1:26 pm, "J.REZZOUK" <[email protected]> wrote: > Scott, > > I don't want to say that "data" are missing but when I import an XML > file starting with an XML declaration like <?xml version="1.0" > encoding="UTF-8"?>, this declaration is missing when I export the XML > file. My understanding was that it was related to this thread. > Jamal > > On 21 juin, 19:10, Scott Henninger <[email protected]> wrote: > > > Jamal; The thread you are posting to is independent of how the > > ImportXMLFile module works. ImportXMLFile will not remove any XML > > data. It reads the entire XML file and creates a DOM tree for further > > processing. > > > In addition Semantic XML can be used to translate XML directly to > > RDF. Again, there is no loss of any XML data. > > > -- Scott > > > On Jun 21, 12:03 pm, "J.REZZOUK" <[email protected]> wrote: > > > > Hello Scott, > > > > Maybe I have missed something but, could you confirm that even in 3.5, XML > > > declarations are removed by ImportXMLFile modules. > > > If I have a simple SPARQLMotion script implementing a simple import/export > > > XML files, I don't like the idea of losing information. > > > I am working in a context where "quality" of data is very important and I > > > have to process data coming from the government : I can not lose > > > information > > > even if in general there is no practical issue. > > > > Thanks > > > Jamal -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
