XML, XSLT, XSD & Web Service getting started Book Recommendation
-
I have been doing .NET (ASP.NET, winForms, C#) and MS SQL Server development (including SSIS & SSRS) for quite some time now. I have now changed jobs and in addition to my prior .NET experience, my new role requires strong knowledge in Extensible Markup Language (XML), Extensible Stylesheet Language Transformations (XSLT), XML Schema Definition Language (XSD) and Web Service use and development. I am therefore asking the Lounge community for a book recommendation to get me up and running with a strong solid foundation with the technologies mentioned.:thumbsup:
"Coming soon"
Here is one good book but only if you have time to spend on xslt. For not complex need w3schools is pretty useful Clickety And don't forget if you ever have problems, questions or something else, ask in the appropriate forum / place here in CP :)
Microsoft ... the only place where VARIANT_TRUE != true
-
This is pretty simple stuff. The w3c schools[^] may be a good way to start.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
-
Here is one good book but only if you have time to spend on xslt. For not complex need w3schools is pretty useful Clickety And don't forget if you ever have problems, questions or something else, ask in the appropriate forum / place here in CP :)
Microsoft ... the only place where VARIANT_TRUE != true
w3schools is not a good place![^]
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
I have been doing .NET (ASP.NET, winForms, C#) and MS SQL Server development (including SSIS & SSRS) for quite some time now. I have now changed jobs and in addition to my prior .NET experience, my new role requires strong knowledge in Extensible Markup Language (XML), Extensible Stylesheet Language Transformations (XSLT), XML Schema Definition Language (XSD) and Web Service use and development. I am therefore asking the Lounge community for a book recommendation to get me up and running with a strong solid foundation with the technologies mentioned.:thumbsup:
"Coming soon"
-
I have been doing .NET (ASP.NET, winForms, C#) and MS SQL Server development (including SSIS & SSRS) for quite some time now. I have now changed jobs and in addition to my prior .NET experience, my new role requires strong knowledge in Extensible Markup Language (XML), Extensible Stylesheet Language Transformations (XSLT), XML Schema Definition Language (XSD) and Web Service use and development. I am therefore asking the Lounge community for a book recommendation to get me up and running with a strong solid foundation with the technologies mentioned.:thumbsup:
"Coming soon"
If you managed to learn C# and T-SQL, the most is done. - XML is only about taking care on how to write properly an XML document and knowing little bunch of terms (namespace, entity, processing instruction, element, attribute, CDATA). Best reference (you will probably never need it more than once) is http://www.w3.org/TR/2008/REC-xml-20081126/[^] - XSLT (and XPath) is more challenging. It's a bit like learning T-SQL: both are functional languages, both have little grammar and both take a lot of practice to master. Here again, IMHO the best reference is still MSDN : http://msdn.microsoft.com/en-us/library/ms256069(v=vs.110).aspx[^] - XSD is about learning a standard for schema definition (not much more than knowing your web.config elements). A quick glance at http://msdn.microsoft.com/en-us/library/ms256235(v=vs.110).aspx[^] will give an idea. Here again, Visual Studio is capable of doing the hard work for you, translating an entire dataset to his respective Xsd Schema. Schema used for XML document validation purposes require usually a little fine tuning. - Web services are little more than a web page that returns a standardized XML instead of an HTML, and a corresponding client to interpret it. Visual Studio will handle most of the Object to XML serialization and deserialization for you and part of the dirty work (wsdl, interfaces). Real troubles start when mixing WebServices from different frameworks (.Net vs Java, for example). I hope I didn't offend anyone with this simplification, but very often, big sounding words don't necessarily hide very complex concepts.
Object reference not set to an instance of an object
-
If you managed to learn C# and T-SQL, the most is done. - XML is only about taking care on how to write properly an XML document and knowing little bunch of terms (namespace, entity, processing instruction, element, attribute, CDATA). Best reference (you will probably never need it more than once) is http://www.w3.org/TR/2008/REC-xml-20081126/[^] - XSLT (and XPath) is more challenging. It's a bit like learning T-SQL: both are functional languages, both have little grammar and both take a lot of practice to master. Here again, IMHO the best reference is still MSDN : http://msdn.microsoft.com/en-us/library/ms256069(v=vs.110).aspx[^] - XSD is about learning a standard for schema definition (not much more than knowing your web.config elements). A quick glance at http://msdn.microsoft.com/en-us/library/ms256235(v=vs.110).aspx[^] will give an idea. Here again, Visual Studio is capable of doing the hard work for you, translating an entire dataset to his respective Xsd Schema. Schema used for XML document validation purposes require usually a little fine tuning. - Web services are little more than a web page that returns a standardized XML instead of an HTML, and a corresponding client to interpret it. Visual Studio will handle most of the Object to XML serialization and deserialization for you and part of the dirty work (wsdl, interfaces). Real troubles start when mixing WebServices from different frameworks (.Net vs Java, for example). I hope I didn't offend anyone with this simplification, but very often, big sounding words don't necessarily hide very complex concepts.
Object reference not set to an instance of an object
thanks :thumbsup:
"Coming soon"
-
If you managed to learn C# and T-SQL, the most is done. - XML is only about taking care on how to write properly an XML document and knowing little bunch of terms (namespace, entity, processing instruction, element, attribute, CDATA). Best reference (you will probably never need it more than once) is http://www.w3.org/TR/2008/REC-xml-20081126/[^] - XSLT (and XPath) is more challenging. It's a bit like learning T-SQL: both are functional languages, both have little grammar and both take a lot of practice to master. Here again, IMHO the best reference is still MSDN : http://msdn.microsoft.com/en-us/library/ms256069(v=vs.110).aspx[^] - XSD is about learning a standard for schema definition (not much more than knowing your web.config elements). A quick glance at http://msdn.microsoft.com/en-us/library/ms256235(v=vs.110).aspx[^] will give an idea. Here again, Visual Studio is capable of doing the hard work for you, translating an entire dataset to his respective Xsd Schema. Schema used for XML document validation purposes require usually a little fine tuning. - Web services are little more than a web page that returns a standardized XML instead of an HTML, and a corresponding client to interpret it. Visual Studio will handle most of the Object to XML serialization and deserialization for you and part of the dirty work (wsdl, interfaces). Real troubles start when mixing WebServices from different frameworks (.Net vs Java, for example). I hope I didn't offend anyone with this simplification, but very often, big sounding words don't necessarily hide very complex concepts.
Object reference not set to an instance of an object
I second the recommendation to read the XML spec, but would also add that you need to read the Namespaces spec as well because it is an addition to the core standard that you almost always need, and while conceptually very simple, most people struggle to really understand how it works. If you want a good book, XML in a Nutshell, Third Edition[^] from O'Reilly is pretty good. XML Schema looks relatively simple, but the data model and semantics behind it are horrendously complex. In fact the technical lead of the group that developed the XML spec, as well as authored most of the XSLT/XPath 1.0 spec James Clark[^]) left the W3C over his objections to the complexity of XML Schema and how that complexity infected all the subsequent XML related specs. Fortunately, you usually don't really need to understand it because the tools take care of it for you. I think the XML in a Nutshell book covers this topic as well as you would need. When I have to author a schema by hand I usually use RELAX NG[^] Compact Syntax instead and use a tool to convert it to XSD. If you only need XSLT/XPath 1.0, I would also recommend reading the specs - they are short and extremely well written. 2.0 is a completely different story - horrendously complex, primarily because it has to support XML Schema. Adoption of 2.0 is still pretty low so you may not need to know it, but if you do, I'd recommend XSLT 2.0 and XPath 2.0 Programmer's Reference [^] by Michael Kay who was one of primary editors of those specs.
-
I have been doing .NET (ASP.NET, winForms, C#) and MS SQL Server development (including SSIS & SSRS) for quite some time now. I have now changed jobs and in addition to my prior .NET experience, my new role requires strong knowledge in Extensible Markup Language (XML), Extensible Stylesheet Language Transformations (XSLT), XML Schema Definition Language (XSD) and Web Service use and development. I am therefore asking the Lounge community for a book recommendation to get me up and running with a strong solid foundation with the technologies mentioned.:thumbsup:
"Coming soon"
the best i have seen is XML: Visual QuickStart Guide, 2nd Edition from Peachpit - Check here
-
If you managed to learn C# and T-SQL, the most is done. - XML is only about taking care on how to write properly an XML document and knowing little bunch of terms (namespace, entity, processing instruction, element, attribute, CDATA). Best reference (you will probably never need it more than once) is http://www.w3.org/TR/2008/REC-xml-20081126/[^] - XSLT (and XPath) is more challenging. It's a bit like learning T-SQL: both are functional languages, both have little grammar and both take a lot of practice to master. Here again, IMHO the best reference is still MSDN : http://msdn.microsoft.com/en-us/library/ms256069(v=vs.110).aspx[^] - XSD is about learning a standard for schema definition (not much more than knowing your web.config elements). A quick glance at http://msdn.microsoft.com/en-us/library/ms256235(v=vs.110).aspx[^] will give an idea. Here again, Visual Studio is capable of doing the hard work for you, translating an entire dataset to his respective Xsd Schema. Schema used for XML document validation purposes require usually a little fine tuning. - Web services are little more than a web page that returns a standardized XML instead of an HTML, and a corresponding client to interpret it. Visual Studio will handle most of the Object to XML serialization and deserialization for you and part of the dirty work (wsdl, interfaces). Real troubles start when mixing WebServices from different frameworks (.Net vs Java, for example). I hope I didn't offend anyone with this simplification, but very often, big sounding words don't necessarily hide very complex concepts.
Object reference not set to an instance of an object
ssineriz wrote:
If you managed to learn C# and T-SQL, the most is done.
I wouldn't say that. XML is relatively easy if you need do nothing more than populate business data AND you have an existing model to work from. However designing an new XML schema from scratch and getting it right is not trivial. And although trivial XSDs are simple if you run into any that are even a bit more than trivial and it is going to require real work to figure it out. And again designing one from scratch is not trivial and even more so than creating an XML schema since you must get both correct. XSLT is substantially harder than both of the above since you not only basically need to know both of the above but you will also need to figure out how to invoke a XSLT interpreter and often will need to figure out how it interacts with outside entities. Web Services as long as you keep it trivial and can find examples are not that hard to do, especially in C# but ONLY as long as you get lucky and understand the requirements of the API. If you need to interface with an existing web service or others outside vendors expect to interact with your new API then getting it right can be difficult.
-
I have been doing .NET (ASP.NET, winForms, C#) and MS SQL Server development (including SSIS & SSRS) for quite some time now. I have now changed jobs and in addition to my prior .NET experience, my new role requires strong knowledge in Extensible Markup Language (XML), Extensible Stylesheet Language Transformations (XSLT), XML Schema Definition Language (XSD) and Web Service use and development. I am therefore asking the Lounge community for a book recommendation to get me up and running with a strong solid foundation with the technologies mentioned.:thumbsup:
"Coming soon"
XSLT for dummies is an excellent introduction and will give you a solid grounding in the subject. Search engines will teach you everything else you need to know! :-)
Follow my mission to create a business application in LightSwitch at: http://therearefourlightswitches.blogspot.com