Re: Multiple XML schema files for a common target namespace (PROV-ISSUE-608)

Hi Stian,

On 02/05/2013 01:55 PM, Stian Soiland-Reyes wrote:
> On Tue, Feb 5, 2013 at 9:14 AM, Luc Moreau <> wrote:
>> The schema uses some xml constructs such as abstract elements and
>> substitution groups, just because we want to split the schema
>> in several files.
> No, also to give a defined place for third-party extensions to put
> their thing. If I am doing stianprov.xsd - how should I do it
> otherwise? Copy-paste everything from prov.xsd and redefine it?

We had a xsd:any that catered for that.
> Do the abstract elements and substitution group cause say the JAXB
> generated classes to look horrible, or have lots of getAny()
> properties requiring casting etc? Perhaps we should have a go using it
> with the leading frameworks for Java (JaxB) and .NET (?) before we
> dismiss it.
> The XSD spec is after all 9 years old.. is this still something 'new'
> and 'dangerous'?
>> but define documentElements in the root file, defining the union over all
>> elements in all the files.
>> Same structure, but without abstract elements and substitution groups.
> This would be a bigger maintenance problem (more chance of getting it
> wrong somewhere), and would not work for third-party extensions.
What do you mean? The prov namespace will be frozen at the end of
the working group activity.  xsd:any allows for third party extensions.


Professor Luc Moreau
Electronics and Computer Science   tel:   +44 23 8059 4487
University of Southampton          fax:   +44 23 8059 2865
Southampton SO17 1BJ               email:
United Kingdom           

Received on Tuesday, 5 February 2013 14:18:59 UTC