XML / XSL

Maybe a little late but check these sites out http://www.motive.co.nz/glossary/markup.php[^] Wikipedia: XML[^] W3Schools: Introduction to XML[^] Seems to be a close call between structural and semantic.

what is your exact question?

Hi, you need to excape the xml string, refer below links it should help. system.security.securityelement.escape[^] http://www.bensonthomaslive.net/1/post/2009/08/escape-xml-string-characters-in-c.html[^]

Thats a big Xml!!! and it looks like a Scalar Vector Graphic image. What do you want us to change in it? For the record, if you dont know how to see this image then you can save it in a file and change the file extension to .svg and then open it in IE.. you will see "NS-IT" written in it. However, What is your question?!!

Thank you, Richard so much ;) Last few days i was struggle with it section[@thankyou='thank you']

Hey, Moderator, I now think this would be more appropriate for the XML forum. Do you agree?

You'll probably get better results if you use the MSXML components[^] to generate your XML document. Apart from anything else, it will take care of properly encoding your string values. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

You can also Click on http://techgurulab.com/course/xml-study-material/[^] to get a complete requirements

You don't mention if there can be one or more example nodes within each catalog node. This code works if there are many catalog's with one example node. <?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" exclude-result-prefixes="msxsl" <xsl:output method="text" indent="no"/> <xsl:template match="catalog"> <xsl:value-of select="example"/> </xsl:template> </xsl:stylesheet> And this code works if there are many catalog nodes and many example nodes. <?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" exclude-result-prefixes="msxsl" <xsl:output method="text" indent="no"/> <xsl:template match="catalog"> <xsl:apply-templates select="example" /> </xsl:template> <xsl:template match="example"> <xsl:value-of select="node()"/> </xsl:template> </xsl:stylesheet> XSLT is recursive by nature, so no need for the loop. If you want text output, I don't understand the HTML tags in your example code.

I think you do not understand the question. The problem is that the tool (XSD.EXE) generates code that uses arrays. Arrays are limiting since it is difficult to add to or remove items from them. I was looking for another tool (that used a more appropriate collection) or an easy workaround. Perhaps I could have phrased my question better. The limitation I mentioned was intended to mean that the tool generated arrays, not that of arrays themselves. Even at this late stage, I appreciate your answer. However, I believe you misread the question.

I feel for this poster.... The issue is most likely poor XML and XSLT design. Too many people refuse to take the time to understand their data and XML and in the rush to 'get something working' they create a schema that is bloated, incomplete and that requires a lot of resources to even attempt to use. Six days for 100MB? Yes - I can say that the schema does not represent the data well and the XSL is probably even worse because it must translate this rickety XML into something that might be even more poorly designed and implemented and it is apparent that the XSL has been where all of the changes and fixes have been applied. For starters -- do not avoid using attributes simply because elements seem 'easier' -- they are not. Things that describe a thing -- are attributes. Things that own things -- are usually elements. I post here because -- when you try to engineer a system and write the entire application at the same time -- all the while saying -- just get it running, we'll fill in the details later -- and also you take alot of shortcuts ('it will be easier if we do ....')....all you are doing is moving the work further down the line and making it more difficult.... There is a definite amount of work that must be done -- never assume that you can avoid it and do as much up front as you can.

If there is no root, you do not have a valid document. I think you are confusing the XML declaration with the root -- the root is the first element that is NOT the XML declaration...what you have posted -- is an XML schema fragment.

XML is the data container; XSLT is the document that transforms the XML into some other data container -- its purpose is to do what you are asking. XSD is the schema -- it defines the format of the XML so that consumers can correctly instantiate objects that are contained in the XML document. People are not seeming to understand the difference or the purpose of XML/XSD/XSLT -- and that is somewhat tragic because it is the best way to do things and maintain validity of data through disparate systems.

This is not the document you want for figuring out CRUD. You need the XSD to do that properly. You could guess and as long as the database column names matched you *might* be able to guess correctly, but...I would not be helping you if I recommended that you do that. If you can write your own query to select a row and if you also had access to ADO.NET -- you could have the table tell you its schema and then the query could be written properly. This method that you are using -- is not a great idea -- you can have some success in doing it, but not for long and it is very likely that you will manage to put a row in the database that will be junk data because you do not know the schema -- you are just making blind CRUD operations. A better choice might be stored procedures because you can just provide the parameters from the client side. At any rate, the less you count on being smart on the client side, the better off you will be.

It is valid -- but, the creator of the XSD did not indicate that it was required -- and you have assumed that it is required. If your code cannot tolerate that -- then modify the XSD to make it required and have whoever produces the XML give it a default value.... However, this is simply pushing it off to the side. This is an issue that does not relate to XML per se -- it relates to best practices about defining and validating data. The XSD defines the structure and rules of XML -- so the designer of the schema must describe the data perfectly and consumers must not make assumptions that are not supported by the XSD.

No, it's already in QA.

Hi Bernhard, Bernhard Hiller wrote: Did you add the [XmlInclude(typeof(CTrModules.MDataSaveXML))] attribute to the base class I don't really want to go with that option, because then I have to remember to add such an include for any class I derive from the base class. But I tried it just for test purposes: I get the same problem. The option I chose to use is this one: Bernhard Hiller wrote: or pass an array of types to the constructor of the serializer? I wrote a method to gather all types in an array and I pass this array to the serializer. I set a breakpoint at the call of the serializer and inspected this array: - Overrides {System.Xml.Serialization.XmlAttributeOverrides} System.Xml.Serialization.XmlAttributeOverrides Non-Public members types Count = 5 System.Collections.Hashtable \[{CTrModules.MDataSaveXML}\] {System.Collections.Hashtable} Key {Name = "MDataSaveXML" FullName = "CTrModules.MDataSaveXML"} object {System.RuntimeType} Value Count = 1 object {System.Collections.Hashtable} \["Instance"\] {System.Xml.Serialization.XmlAttributes} Raw View \[{CTrModules.QSM\_Var\_Dict}\] {System.Collections.Hashtable} Key {Name = "QSM\_Var\_Dict" FullName = "CTrModules.QSM\_Var\_Dict"} object {System.RuntimeType} Value Count = 1 object {System.Collections.Hashtable} \["Instance"\] {System.Xml.Serialization.XmlAttributes} Raw View \[{System.String}\] {System.Collections.Hashtable} Key {Name = "String" FullName = "System.String"} object {System.RuntimeType} Value Count = 1 object {System.Collections.Hashtable} \["Instance"\] {System.Xml.Serialization.XmlAttributes} Raw View \[{CTrModules.MHandleException}\] {System.Collections.Hashtable} Key {Name = "MHandleException" FullName = "CTrModules.MHandleException"} object {System.RuntimeType} Value Count = 1 object {System.Collections.Hashtable} \["Instance"\] {System.Xml.Serialization.XmlAttributes} Raw View \[{FFV\_Cockpit.InternalExcHandler}\] {System.Collections.Hashtable} Key {Name = "InternalExcHandler" FullName = "FFV\_Cockpit.InternalExcHandler&q

You asked the right question: I was trying to select the setpoint nodes, so i must remove the @Name.