On Thu, 21 Mar 2002, Steve Bang wrote:
> OK, I guess I slipped on the intuitiveness of HTML tags -- I don't know
> where my mind was at that moment. Regardless, I prefer consistency and
> clarity whenever possible. I know you do too. Your clarified the issues
> and I am somewhat comfortable wi
, March 21, 2002 4:10 PM
> To: Tag Libraries Users List
> Subject: RE: JSTL tag prefix naming conventions?
>
>
> So, sorry I didn't respond earlier; for some reason, the mailing list
> didn't send me these messages until hours later. Thanks for all your
> comments; I ca
On Thu, 21 Mar 2002, Shawn Bayern wrote:
> So, sorry I didn't respond earlier; for some reason, the mailing list
> didn't send me these messages until hours later. Thanks for all your
> comments; I can't speak authoritatively for the entire expert group, but
> here are my own personal opinions
So, sorry I didn't respond earlier; for some reason, the mailing list
didn't send me these messages until hours later. Thanks for all your
comments; I can't speak authoritatively for the entire expert group, but
here are my own personal opinions.
On Thu, 21 Mar 2002, Steve Bang wrote:
> While J
ght about discussing?
Steve
> -Original Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 21, 2002 12:01 PM
> To: Tag Libraries Users List
> Subject: RE: JSTL tag prefix naming conventions?
>
>
> However, they will become a de-f
However, they will become a de-facto standard.
So it's the usual abbreviation cuz it's easy to type versus full word
because it's meaningful argument. Java philosophy supports the latter, so
I will too.
How about is JSTL peeps? Can we have more meaningful default namespaces?
On Thu, 21 Mar 2002
11:53 AM
> To: 'Tag Libraries Users List'
> Subject: RE: JSTL tag prefix naming conventions?
>
>
> Aren't prefixes defined by the developer of the application
> using the the
> JSTL tags?
>
> The prefixes in the documentation are merely suggestions, you
Aren't prefixes defined by the developer of the application using the the
JSTL tags?
The prefixes in the documentation are merely suggestions, you don't HAVE to
follow that.
> How were the names for the JSTL tag library prefixes chosen?
> I think that
> the naming could be more consistent and/
How were the names for the JSTL tag library prefixes chosen? I think that
the naming could be more consistent and/or meaningful. For example, instead
of the current ones, how about these alternatives:
c --> core
x --> xml
fmt --> format
sql --> sql
But, even this isn't clear that the libraries
