5 votes
Accepted

When to use 'nillable' in XML schemas

nillable is in the spec because the XML Schema WG had a number of members who saw the world in SQL terms and wanted an explicit equivalent to SQL's null values. It's totally unnecessary in my view: ...
Michael Kay's user avatar
  • 3,474
4 votes
Accepted

Storing survey data from csv to xml

Which is the better encoding really depends on what you're trying to store. If you're storing the data gathered by the survey, it'll be much different than if you're storing a record of the user input ...
Morgen's user avatar
  • 1,091
4 votes

Is it good style that calling setters follow the same order as XSD elements?

Whenever I'm doing some tedious task, like making a new X object and setting 20 of its properties I tend to do so in alphabetical order, because that's the order I see things in the IDE's intellisense/...
Caius Jard's user avatar
4 votes
Accepted

Tips and tricks in implementing XML or XML schema

Honestly, my answer would initially be: don't use XML. I've been working with XML for many years and the reality is that it's a terrible format for data exchange. JSON has it's own flaws but it is ...
JimmyJames's user avatar
  • 27.3k
3 votes

When to use 'nillable' in XML schemas

I found a use case! (See https://stackoverflow.com/a/18984458/2886891 for detailed explanation of the bacground.) When there is a mandatory element in the XSD schema, such as <xsd:element name=&...
Honza Zidek's user avatar
3 votes
Accepted

Is it good style that calling setters follow the same order as XSD elements?

The fact that you are using XSD is not important. You are creating Java classes and those don't care the order (well, unless there is some dependency that should be dealt with in the constructor or a ...
Miyamoto Akira's user avatar
2 votes

Is it good style that calling setters follow the same order as XSD elements?

You don't say what the container for your elements is. if you use a <xs:sequence> then the order of the elements is enforced. I had a look and can't see what if any conditions are present if ...
Ewan's user avatar
  • 75.8k
1 vote

Proving two XML schema's are functionally equivalent

Idea 1 is not a formal proof. However, most software are still not formally proven, but released after verification based on an extensive test suite. Many standard compliance verification procedures ...
Christophe's user avatar
  • 77.3k
1 vote
Accepted

C# changing XSD's problem

As I continue my research for days, given that XML and XSD's has been long on enterprise products, my problem has been been experienced by other developers too. If #1 is not a feasible solution, ...
KaeL's user avatar
  • 121
1 vote
Accepted

XSD Namespaces with W3.org

A schema document by definition must have an outermost element whose local name is "schema" and whose namespace URI is "http://www.w3.org/2001/XMLSchema". That can't be achieved unless it has a ...
Michael Kay's user avatar
  • 3,474
1 vote

Tips and tricks in implementing XML or XML schema

1) Name spaces are not required. For a simple project, just keep it as simple a s possible. Use name spaces when your project grows larger, and when you need several xml formats where there is a risk ...
Roland's user avatar
  • 131
1 vote

When to use 'nillable' in XML schemas

Unless xs:nil appears in the element tag, many built-in types do not allow empty values. For example, <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name=&...
dave's user avatar
  • 99

Only top scored, non community-wiki answers of a minimum length are eligible