Re: [jakartaee-platform-dev] Batch target namespace

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

    The URI referring to the schema and the XML namespace used by the
    elements in the schema are different things.  You don't need to add
    the qualifier to the URI since the name itself is more than unique
    enough (unless you're worried about two specs defining a schema
    named "jobXML").
    
    The schema namespace controls the scope of the schema element names,
    and is independent of the name of the schema file.  Many of our
    schemas share some common element definitions in (previously)
    javaee_8.xsd.  If you have no need to share any of those common
    definitions, or are worried about defining new elements that might
    conflict with those common definitions, you can define a new
    namespace, and use a different prefix to represent that namespace.
    
    Despite the above, please do think about compatibility from
    one version of your schema to the next.  If someone has a file using
    that schema, what's the minimum they need to change to convert that
    file to use the new version of the schema?  We tried to define our
    schemas in an upwards compatible way, so that all you needed to
    change was the URI and the version attribute.  If you also need to
    change the namespace, and the namespace prefix, and the elements
    names, and ... then it's going to be painful for developers.

Scott Kurz wrote on 3/24/20 9:13 AM:

On the platform call day (minutes:  https://docs.google.com/document/d/1EJ2ilaPhMnQqa3aw6AmwjRbBPGL3_np4uuwklgfqPZI/)

we discussed schema / XML namespace issues including  https://github.com/jakartaee/jakarta.ee/issues/592

 

Though we decided it was a good recommendation to move schemas like batch from namespace   http://xmlns.jcp.org/xml/ns/javaee, to new namespace https://jakarta.ee/xml/ns/jakartaee

 

I think I like https://jakarta.ee/xml/ns/jakartaee/batch (adding an extra qualifier) better.   True, there's no document currently that would pull in elements of batch and another spec sharing this namespace, but what if there were. 

 

Since the publishing process doesn't depend on batch being in this common namespace, I'm going to move it out if no one objects.

 

Thanks,

------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!GqivPVa7Brio!IOLyIW8wniGsHYMw5phLlL91QJLSQJznJKasLbERSnTWtfZ2EsL3vKUyNVGW67TjQA$