Not. XSD does not provide for this.
You can specify a default value for an item. But as soon as it is absent (when its parent's content model is allowed), any requests to this element return either an empty string or zero (or just an error). A missing element is a nonexistent element!
For attributes, this is possible because attributes are much simpler. All element attributes effectively represent an unordered set of named simple values. There is no attribute tree (with one or another structure) attached to the parent element.
But with elements, things are much more complicated. If something "defaulted" about missing items was allowed, this will cause a lot of ambiguity. For example, some “default content” should be indicated, which would be some sequence of elements called automatically instead of emptiness ... or even the number of possible “default values”, each of which is called when only some elements are explicitly specified, and others should add them implicitly (by default). .... Well, if you think next, everything becomes a stunning complex. Then another language will be created! But for what purpose?
Coldfusion
source share