RE: Re: Welcome to JSR 311

From: Larry Cable <>
Date: Wed, 11 Apr 2007 16:03:19 -0700

Could we call it*


-----Original Message-----
From: Roy T. Fielding []
Sent: Wednesday, April 11, 2007 3:07 PM
Subject: Re: Welcome to JSR 311

On Apr 11, 2007, at 1:49 PM, Ryan Heaton wrote:

> I would be surprised if there was anybody that is part of this EG that
> is under the illusion that we are trying to create anything more than
> "a new form of application deployment mechanism." Nobody is trying to
> limit whatever REST may be.
> Personally, I don't feel that by putting these classes and interfaces
> in a package called "rest" is implying that they encapsulate the whole
> REST architectural style, nor do I feel it would imply Sun's ownership
> of the style.

Because Sun has aggressively enforced the use and interpretation
of trademarks within the class names of the APIs. So, while you
may have a reasonable opinion in isolation, I have actual text from
Sun lawyers that says that Sun, at least, disagrees with your opinion.
I don't see any reason why I should give Sun something that they
have refused to give anyone else. In any case, as I said, it is
very unlikely that this API will be RESTful, in spite of the name.
I think the API needs to earn its own way, in its own time, and
then people can choose to apply whatever adjectives to it that are
applicable when it is finished.

> I'd just like to see a sensible answer to the question "in what
> package are these classes located?" It makes more sense to use the
> name "rest" in for this, since that's the name of the architectural
> style we refer to in all our discussions and design. Why is "rs" any
> better? Isn't it short for "rest" anyway?

Because it isn't a REST API. Marketing does not make it so.
I don't care what the API is called so long as people call it
something other than REST. And that does include the class names.
"rs" or JAX-RS or Jersey or JARWS or Fred are all names that can
be reasonably distinguished from the architectural style, so I
don't care what they might be short for.

In any case, this matter has been decided. It was a precondition
for starting the JSR that the API be given a name other than REST
or RESTful such that the API can be readily distinguished from the
style and the adjective used to describe it.


To unsubscribe, e-mail:
For additional commands, e-mail:

Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.