- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Thu, 6 Dec 2012 16:54:37 +0000
- To: W3C provenance WG <public-prov-wg@w3.org>
I've added some code example of my proposed solution at http://dvcs.w3.org/hg/prov/file/6113b10ac714/xml/experimental/extensions See description of this folder here: http://www.w3.org/2011/prov/wiki/ProvXMLNamespaces#Experimental_example On Thu, Dec 6, 2012 at 4:20 PM, Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk> wrote: > I've tested and found it to be easy to do several schemas in the same > namespace as long as they just <xsi:include> each-other. > > > So you can have an hierarchy of imports like: > > prov.xsd > -- imports core.xsd > -- imports collection.xsd > ---- imports core.xsd > -- imports links.xsd > ---- imports core.xsd > > and so the top-level prov.xsd simply includes 2-3 <xsd:imports> of the > underlying components. > > > As far as I could figure it out, it means in the extensions the > easiest way to 'fit in' would be to use abstract elements and > substitution groups. > > See http://www.w3.org/2011/prov/wiki/ProvXMLNamespaces for a > discussion of the different alternatives. > > I've also got some test-schemas with this working, but I have not > committed them yet as they are on a different machine. > > > On Fri, Nov 30, 2012 at 3:34 PM, Stian Soiland-Reyes > <soiland-reyes@cs.manchester.ac.uk> wrote: >> Tracker, this is PROV-ISSUE-608 >> >> On Fri, Nov 30, 2012 at 3:29 PM, Stian Soiland-Reyes >> <soiland-reyes@cs.manchester.ac.uk> wrote: >>> They are usually application/xml. >>> >>> On Thu, Nov 29, 2012 at 6:22 PM, Timothy Lebo <lebot@rpi.edu> wrote: >>>> prov-wg, >>>> >>>> Is there a mime type for xml schema? >>>> Or, should we just use "application/xml"? >>>> >>>> I'd like to add it to http://www.w3.org/2011/prov/wiki/ProvNamespaceManagement#Intro >>>> >>>> Thanks, >>>> Tim >>>> >>>> >>>> On Nov 29, 2012, at 12:58 PM, Graham Klyne <GK@ninebynine.org> wrote: >>>> >>>>> Following the teleconference, I did a little digging, and my understanding is that it *is* possible to have a schema for a common target namerspace build from a number of separate schema files: >>>>> >>>>> http://www.w3.org/TR/xmlschema-1/#compound-schema >>>>> >>>>> By my reading, what you *cannot* do is have a single schema composed from multiple "sub-schema" defining terms in different target namespaces. >>>>> >>>>> #g >>>>> -- >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> -- >>> Stian Soiland-Reyes, myGrid team >>> School of Computer Science >>> The University of Manchester >> >> >> >> -- >> Stian Soiland-Reyes, myGrid team >> School of Computer Science >> The University of Manchester > > > > -- > Stian Soiland-Reyes, myGrid team > School of Computer Science > The University of Manchester -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester
Received on Thursday, 6 December 2012 16:55:26 UTC