Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartabatch-dev] Fw: Re: [jakartaee-platform-dev] Batch target namespace

Thanks.. it's settled then.

Commented in:
https://github.com/eclipse-ee4j/batch-tck/issues/3
https://github.com/eclipse-ee4j/batch-api/issues/12

Thanks all,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------

Inactive hide details for Cheng Fang ---03/29/2020 03:08:07 PM---+1 for using the common namespace https://urldefense.proofpoinCheng Fang ---03/29/2020 03:08:07 PM---+1 for using the common namespace INVALID URI REMOVED

From: Cheng Fang <cfang@xxxxxxxxxx>
To: jakartabatch developer discussions <jakartabatch-dev@xxxxxxxxxxx>
Date: 03/29/2020 03:08 PM
Subject: [EXTERNAL] Re: [jakartabatch-dev] Fw: Re: [jakartaee-platform-dev] Batch target namespace
Sent by: jakartabatch-dev-bounces@xxxxxxxxxxx




+1 for using the common namespace https://jakarta.ee/xml/ns/jakartaee.

On Thu, Mar 26, 2020 at 11:25 AM Scott Kurz <skurz@xxxxxxxxxx> wrote:
    Cross-posting from the platform-dev ML, I'd floated the idea of carving out a separate namespace for batch.

    Kevin (and Bill, I'd say) leaning towards sticking with the common     https://jakarta.ee/xml/ns/jakartaee., as there's never been an issue with collisions in the past (maybe hard to imagine a document where it would be an issue).

    So if no objections, I'd say we'll go with     https://jakarta.ee/xml/ns/jakartaee.

    Thanks,
    ------------------------------------------------------
    Scott Kurz
    WebSphere Batch and Developer Experience
    skurz@xxxxxxxxxx
    --------------------------------------------------------
    ----- Forwarded by Scott Kurz/Poughkeepsie/IBM on 03/26/2020 11:22 AM -----

    From:     Kevin Sutter/Rochester/IBM
    To:     jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
    Cc:     Scott Kurz <skurz@xxxxxxxxxx>
    Date:     03/25/2020 08:48 AM
    Subject:     Re: [EXTERNAL] Re: [jakartaee-platform-dev] Batch target namespace


    Scott,
    Just to iterate Bill's points... If you are considering adding the "batch" qualifier to the namespace url just out of caution, a potential for future conflicts... Then I would hold off. I would stick with the proposed     https://jakarta.ee/xml/ns/jakartaee. As Bill pointed out on the call, we've been using this common namespace for a long, long time in Java EE and now Jakarta EE. Until it becomes an issue, I wouldn't complicate it. And, if it does become an issue down the line for Batch or any other component that owns a Schema, then changing the namespace is doable. Yes, there would be an impact, but that's only if namespace clashes would start to get introduced.

    ---------------------------------------------------
    Kevin Sutter
    STSM, MicroProfile and Jakarta EE architect @ IBM
    e-mail:     sutter@xxxxxxxxxx Twitter: @kwsutter
    phone: tl-553-3620 (office), 507-253-3620 (office)
    LinkedIn:     https://www.linkedin.com/in/kevinwsutter

    Inactive hide details for Bill Shannon ---03/24/2020 21:57:11---The URI referring to the schema and the XML namespace used by tBill Shannon ---03/24/2020 21:57:11---The URI referring to the schema and the XML namespace used by the elements in the schema are differe

    From:     Bill Shannon <bill.shannon@xxxxxxxxxx>
    To:     jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>, Scott Kurz <skurz@xxxxxxxxxx>
    Date:     03/24/2020 21:57
    Subject:     [EXTERNAL] Re: [jakartaee-platform-dev] Batch target namespace
    Sent by:     jakartaee-platform-dev-bounces@xxxxxxxxxxx



    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: _______________________________________________
    jakartaee-platform-dev mailing list
    jakartaee-platform-dev@xxxxxxxxxxx
    To unsubscribe from this list, visit     https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev




    _______________________________________________
    jakartabatch-dev mailing list
    jakartabatch-dev@xxxxxxxxxxx
    To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartabatch-dev_______________________________________________
    jakartabatch-dev mailing list
    jakartabatch-dev@xxxxxxxxxxx
    To unsubscribe from this list, visit     https://www.eclipse.org/mailman/listinfo/jakartabatch-dev



Back to the top