XML Schema Definition Tutorial
HTML-код
- Опубликовано: 3 окт 2024
- Description and tutorial for XML Schema Definitions (XSD files). In this I show an example XML and how to create a schema that shows how to validate XML against the rules defined by the schema. I show how the commercial oXygen tool can help simplify the process and how to validate using the open-source xmllint tool
I took a semester in information-structuring where we were supposed to learn all this. I am like 25 Minutes in and I am making your videos my god damn xml-bible. It's so clear suddenly. Your explanations are really really nice! Thank you so much!
xml is so verbose and ugly to me. I've tried before to learn more about xml in the past, but it wasn't imperative enough for me to overcome my aversity to xml in order to continue. Now, I have to work with some old soap services at my new job. This is a life saver. I can finally read this stuff. I still think it's weird and hate it though
Thank you. good tutorial
Great content! Thank you so much, it has been very helpful for me
Hi I have bunch of xsd files for validation but my data is in excel format. How would you recommend transforming the excel to xml? Also some of the xsd files have "import namespace" which is unclear to me.
Thank you! Your video helped me to understand and adjust a complex XSD file
What is targetnamespace and why is it used for ?
The TNS is the NS of what you're defining. For example, if you are defining a schema called newstuff, you might bind the TNS to www.example.com/newstuff. But your schema would still be allowed to use definitions from another namespace, like www.example.com/shareddefinitions. You can only have one TNS per schema, but *use* any number of other namespaces.
Wonderful tutorial I learned a great deal. One point that confused me and might need more explanation. Your use of the ex: or xs: prefix before your element was a little unclear. Thank you so much.
Recall that the "xs" and "ex" prefixes are namespaces--a way of distinguishing duplicate names. For example XSD uses the tag "element", but perhaps you wish to use that for your own purpose. So we define "xs:element" to refer to the XSD one and "ex:element" for ours (the EXample). Now these can be anything you'd like and are defined at the top in the XMLNS attribute, so ex and xs aren't hard wired.
@@arbitrarytechnology9354 Thank you. I wrote that comment about 24 minutes in as you were giving definitions. Once the practical example came out, the question resolved itself. Thank you, working my way through your playlist now.
i finally understand how xsd works, thank you!
a life saving content!
Great video and an indruction to XML
Best XSD tutorial I could find, thanks a lot!
First sentence, immediately bragging ;)
Thank you, I was about to give up with XML schemas then I saw this video and finally its is starting to make sense. Great tutorial
Taylor Karen Anderson Christopher Gonzalez David
Thank you Rich!!!! Fantastic tutorial on a topic that has so little coverage.
Very Helpful!
Thank you so much for uploading this tutorial.
This tutorial is hands-down fantastic!! Thanks for getting it out here
Thank you so much - this is a great tutorial with a helpful hands-on example. Much appreciated!
Great tutorial! 😀
Very helpful! Thank you!
Is xml schema a database or its a schema like in database where table structure etc are defined. And we need to follow the table structure??
Tables and databases are but one use for a schema (though RDBMs often call their layout "schema"). In general, a schema is a language definition, such as Backus Naur form of a formal language. A "table" can be viewed as one element definition, but only using XSD "sequence" specifiers...a table's order must always be the same in that child elements must appear in that order. For example, a table with columns "firstname", "lastname", "phone" has only one order. A more general schema might have "firstname", "optional middle name", "lastname", "optional maiden name", "optional home phone", "optional cell phone", "optional business phone", etc. This wouldn't fit well into a table record because so many optional items would waste space, and which is the "phone"? So XSD schemas can be more flexible, but more complicated than table records
Omg..i just needed a very basic and simple definition to understand what schema is. You have completely deviated from what I was looking for!. From what I learnt,xml schema is just like a database schrma but a bit more easier to use than database schema which is why xml is more widely used .. As simple as that! Xml schema is not something which is used only for the purpose of validation,as I have heard from many trainings. Ppl think thay xml schema is for validation.lol! Its not. You have the option of validating ur xml to a schema in xml language. Dats y we do so ,which is not the case in database. Xml schema is needed exactly when u need a table structure,say for example in projects. Else for a a simple xml with 3-4 lines code, its not required. I hve seen ppl generate schema for example xmls also,which is totally unnecessary.
Schema is not a language definition.even in database ,its basically to define rows n columns n tables etc.
@@venig8954 Sorry I wasn't able to answer your question...I thought you were asking about schemas in general. The project that made me create this video was, in fact, part of a formal language definition including a compiler. The XML meta-language ("tags and attributes") was used to remove the need for tokenization, and XSD described the grammar convention (the parser) of that custom language. I'm no longer sure what you were asking, but it seems you've already found the answer you needed elsewhere. Thanks for watching and I hope you enjoyed the video
@@venig8954 You're being an asshole. He took time outta his day to answer you, at least provide well-formed criticism. Seriously have some manners.