Don't the schemas ideally need to match the namespace they are in? That sound suggest the following locations:
/blueprint/xmlns/blueprint-ext/v1.0.0 /blueprint/xmlns/blueprint-cm/v1.0.0 on our website. Alasdair On 22 September 2011 14:56, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Dan, > > thanks a lot for reporting this. > > I would have a preference for schemas/blueprint-cm and > schemas/blueprint-ext to be close of xmlns/blueprint-cm and > xmlns/blueprint-ext. > > Regards > JB > > > On 09/22/2011 03:53 PM, Daniel Kulp wrote: > >> >> A couple of us were just having a discussion on the #karaf IRC channel as >> we >> ran into a problem in that the Aries XSD file are not really available on >> the >> web site or anything to allow mapping namespaces -> xsd for use with >> validation in various tools and such. Thus, I'd like to get, at a >> minimum, >> the blueprint schemas onto the site. The question is how "best" to do it. >> >> We could just add a "aries.apache.org/schemas" dir and dump them directly >> in >> there. We could create subdirectories from the (schemas/blueprint, >> schemas/blueprint-cm, etc....), double level (schemas/blueprint/cm, >> schemas/blueprint/ext), etc..... Anyone have a preference? >> >> >> The next step, once they are there, will be to figure out how to use >> mod_redirect or similar with the CMS based site to direct the actual >> namespaces in there to the correct schema. I can work with Joe on that, >> but >> we need the files up there first. >> >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > > Talend - http://www.talend.com > -- Alasdair Nottingham [email protected]
