Title: Message
I would try to shy away from the word "instance" which had
already caused us weeks of frustration... :-)
My two cents,
Eilon
-----Original Message-----
From: Thomas Schaeck
[mailto:]
Sent: Wednesday, December 11, 2002 7:42
AM
To: Gil Tayar
Cc:
Subject: RE: [wsrp-wsia] [I#154]
Proposed Resolution: Rename "entity" to " portlet"
Importance:
Low
Hi Gil,
you may have misinterpreted my last mail - I agreed that both
can be named
the same, my proposal was to name both
something like "portlet instances"
or better "portlet
entities" rather than just "portlet".
That would resolve my concern and still use consistent naming
for CCEs and
POEs.
Best regards,
Thomas
Gil Tayar <> on 12/11/2002
05:54:06 AM
To:
cc:
Subject: RE:
[wsrp-wsia] [I#154] Proposed Resolution: Rename "entity" to
"
portlet"
Spec-wise, using the term "portlet" for both CCEs _and_ POEs
is exactly
right, because they are nearly identical.
Using a _different_ term,
spec-wise, may be the
confusing thing - confusing the reader that there is
an inherent difference between the two (where, spec-wise, there
isn't).
I agree with you that application-wise, there _will_ be a
difference
between
CCEs and
POEs (POEs are the "types" and CCEs are the instances). But we are
concerned with the spec, and the spec MUST be adamant - there
is little
difference between the two - they are both
"portlets".
Gil
-----Original Message-----
From:
Thomas Schaeck [mailto:]
Sent: Tue, December 10, 2002 21:28
To: Gil Tayar
Cc:
Subject: RE:
[wsrp-wsia] [I#154] Proposed Resolution: Rename "entity" to
" portlet"
My concern primarily was that using the term "portlet" for
consumer
configured entities would be confusing.
(Since in various portals POEs will
be selectable as
"portlets" from some kind of toolbar or customizer I was
not equally concerned about producer offered entities to be
named
portlets.)
Since it is true that POEs technically are not different from
CCEs, we
might name both "portlet instances" or better
"portlet entities".
Best regards,
Thomas
Gil Tayar <> on 12/10/2002
06:47:56 AM
To:
cc:
Subject: RE:
[wsrp-wsia] [I#154] Proposed Resolution: Rename "entity" to
"
portlet"
Exactly. Also, the differentiation between POEs and CCEs is
artificial, and
the doesn't differentiate between the
two except for the fact that a
Consumer can delete
only CCEs, and that POE descriptions are returned in
getServiceDescription.
One could argue that a POE is a "portlet type" - a prototype
for CCEs. The
problem is that the spec doesn't say
anything about this. Can't I have two
"stock quotes"
POEs, which both map to the same "portlet type", but
pre-configured _by the Producer_? Of course. What is the difference
between
those two and a Consumer-configured entity
which takes one of the two above
POEs and configures
it? None.
Meaning POEs and CCEs are both "portlets" (POPs and
CCPs).
And Rich, maybe it is time to start talking about "portlet
instances" as
those transient things (ouch!) that
become unique at runtime (I like that
phrase!).
Gil
-----Original Message-----
From: Rich
Thompson [mailto:]
Sent: Mon, December 09, 2002 20:30
To:
Subject: Re:
[wsrp-wsia] [I#154] Proposed Resolution: Rename "entity" to
"portlet"
Subbu is right, you can have multiple instances of an entity
on a page
regardless of whether it is Producer Offered
or Consumer Configured. Those
instances become unique
in a transient manner at runtime, but start from
the
same persistent configuration each time.
Rich Thompson
Interaction Middleware
and Standards for Portal Server
IBM T.J. Watson
Research Center
Yorktown Heights, NY
(914) 945-3225
Thomas
Schaeck@IBMDE
To: Subbu Allamaraju
<>
cc: Rich
Thompson/Watson/IBM@IBMUS,
12/09/2002 01:06
PM
From: Thomas
Schaeck/Germany/IBM@IBMDE
Subject: Re: [wsrp-wsia]
[I#154] Proposed Resolution:
Rename
"entity" to
"portlet"(Document link: Rich
Thompson)
In many portals, "portlet" is used for what you can select in
the
customizer (this corresponds to "producer offered
entity") and someting
like "portlet instance",
"portlet occurrance" or "portlet entity" (JSR 168)
is
used for the instances of such portlets on pages (this corresponds to
"consumer configured entity").
Best regards,
Thomas
Subbu Allamaraju <> on 12/09/2002 07:00:05
PM
To: Thomas Schaeck/Germany/IBM@IBMDE
cc: Rich Thompson/Watson/IBM@IBMUS,
Subject: Re: [wsrp-wsia] [I#154] Proposed Resolution:
Rename "entity" to
"portlet"
Thomas Schaeck wrote:
> We have to
be very careful here since we have two different kinds of
> entities - it would make sense to rename "producer offered
entities" to
> "portlets", but I don't think it
would make sense to use the term
"portlet"
> for "consumer configures entity".
But since a consumer configured entity is similar to a
producer offered
entity outside the entity management
interface, why does the same term
not apply to such
entities? Am I missing something?
Regards,
Subbu
>
> Best regards,
>
> Thomas
>
>
>
> Rich Thompson/Watson/IBM@IBMUS on 12/09/2002 06:33:29
PM
>
>
To:
> cc:
> Subject: Re:
[wsrp-wsia] [I#154] Proposed Resolution: Rename "entity"
to
> "portlet"
>
>
>
>
>
>
>
>
> This was a question we said at the
Nov F2F that we would allow to sit for
a
> few weeks. Seeing as there have been no replies to this
issue, I propose
> that we resolve it by renaming
entities to portlets throughout the spec.
> This
aligns with the name of the spec and thereby will help guide the
> spec's readers.
>
> Rich Thompson
>
>
>
>
>
Gil Tayar
>
<Gil.Tayar@webcol To:
>
>
lage.com>
cc:
>
Subject: [wsrp-wsia]
>
[I#154] Rename "entity" to "portlet" or
>
11/24/2002 06:50
"portlet type"
>
AM
>
>
>
>
>
> Issue: 154
> Status:
Active
> Topic: general
> Class: Technical
> Raised by: Eilon
Reshef
> Title: Rename "entity" to "portlet" or
"portlet type"
> Date Added: 7-Nov-2002
> Document Section:
>
Description:
> As the word "entity" is too general,
and because we have finally given a
> name to the
thing that we are "showing", why not rename entity to
"portlet"
> or "portlet type"
>
>
>
>
----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the
subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
>
>
>
>
----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the
subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
