[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp-wsia] [change request #188] Conformance -> Semantics (# 1)
Yes, we thought about that as well. Just to focus on the first case you
suggest, how would one do a conformance test for:
"the Consumer MAY supply no values, indicating that all transitions
are valid."?
The best we could do would be to report whether or not a Consumer
invocation ever exercised this option. I'm not sure there is any value in
that report and therefore we suggested just conveying the semantics by:
"If the Consumer does not supply a value for validNewModes, the
Portlet can assume that all transitions are valid.".
As a semantic statement it conveys useful guidance to Producer/Portlet
implementers without being a burden upon a conformance test suite.
Rich Thompson
Eilon Reshef <Eilon.Reshef@webcollage.com>
02/28/2003 07:51 PM
To: wsrp-wsia@lists.oasis-open.org
cc:
Subject: RE: [wsrp-wsia] [change request #188] Conformance
-> Semantics (# 1)
Rich,
In some of those cases it seems that the reason why these are not
conformance statements is because they enforce a certain constraint from
one
end of the communication. It seems that in some cases they can be left as
conformance statements if the actor is replaced - for example:
1.
Old text: If no values are supplied, the Portlet MAY assume that all
transitions are valid.
New text: the Consumer MAY supply no values, indicating that all
transitions
are valid.
2.
Old text: The Producer MUST expect the getMarkup() operation to be invoked
for the minimized state just as for all other window states.
New text: The Consumer MUST/SHOULD/MAY call the getMarkup operation in a
minimized state.
Etc.
My two cents,
Eilon
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Thursday, February 27, 2003 00:34
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [change request #188] Conformance -> Semantics (#1)
Document: Spec
Requested by: Rich Thompson
Reasoning: Julie MacNaught & I have been walking through the Conformance
statements from a testing perspective. We would suggest that the following
are important semantic statements, but are not testable conformance
statements. Rather than a large number of change requests, here are the
first 26 rewordings that remove the conformance language while keeping the
semantics. I have included IDs on each for easy referencing.
ID: A
Section: 3.5
Page/Line: 11/43-45
Old text: If the Producer exposes the PortletMangement portType, then the
Consumer MAY clone the Producer Offered Portlets and uniquely configure
them for its own use. The Consumer MAY also choose to directly use the
Producer Offered Portlets.
New text: If the Producer exposes the PortletMangement portType, then the
Consumer can clone the Producer Offered Portlets and uniquely configure
them for its own use. The Consumer can also choose to directly use the
Producer Offered Portlets.
ID: B
Section: 3.12
Page/Line: 14/15-16
Old text: In order to permit load balancing to function, regardless of the
transport binding in use, the Consumer MUST manage transport level issues
itself
New text: In order to permit load balancing to function, regardless of the
transport binding in use, the Consumer needs to manage transport level
issues itself
ID: C
Section: 5.15
Page/Line: 17/19-20
Old text: This LocalizedString structure describes both the value for a
particular locale and the resource name that MAY be used to extract the
value for other locales from a ResourceList
New text: This LocalizedString structure describes both the value for a
particular locale and the resource name that can be used to extract the
value for other locales from a ResourceList
ID: D
Section: 5.1.11
Page/Line: 19/40-41
Old text: The handle by which Consumers MAY refer to this Producer Offered
Portlet
New text: The handle by which Consumers can refer to this Producer Offered
Portlet
ID: E
Section: 5.1.11
Page/Line: 20/40-42
Old text: Setting this flag to "true" suggests to the Consumer that it MAY
want to clone the Portlet when placing it on an aggregated page rather
than waiting for the processing described in section 6.3.3
New text: Setting this flag to "true" suggests to the Consumer cloning the
Portlet when placing it on an aggregated page rather than waiting for the
processing described in section 6.3.3
ID: F
Section: 5.1.18
Page/Line: 23/21-23
Old text: This array MUST include an entry for any user category the
Producer is willing to have the Consumer assert for an End-User, including
the user category names defined in section B.2 of this specification New
text: This array includes entries for every user category the Producer
is willing to have the Consumer assert for an End-User, including the user
category names defined in section B.2 of this specification
ID: G
Section: 5.1.21
Page/Line: 24/32-34
Old text: When the sendAllLocales boolean flag is set to "true", the
Producer's response SHOULD contain values for all returned localized
strings in all locales where they are available
New text: When the Consumer sets the sendAllLocales boolean flag to
"true", it is requesting the Producer's response include values for all
localized strings in all locales where they are available
ID: H
Section: 5.2
Page/Line: 25/14-16
Old text: While it is possible a ServiceDescription will change with time
(e.g. Producer deploys additional Portlets), Producers SHOULD return as
complete a ServiceDescription as possible.
New text: While it is possible a ServiceDescription will change with time
(e.g. Producer deploys additional Portlets), Producers are encouraged to
return as complete a ServiceDescription as possible.
ID: I
Section: 6.1.2
Page/Line: 26/38-40
Old text: This field provides a string the Portlet MAY use to prefix
tokens that need to be unique on the aggregated page
New text: This field provides a useful string for Portlet's prefixing of
tokens that need to be unique on the aggregated page
ID: J
Section: 6.1.9
Page/Line: 30/4-5
Old text: The Consumer MAY supply this information based on the setting
the End-User has requested.
New text: The Consumer can supply this locale based on the settings the
End-User has requested.
ID: K
Section: 6.1.9
Page/Line: 30/14-16
Old text: The Consumer SHOULD inspect the Portlet's metadata to determine
which of these modes the Portlet supports in addition to any
Producer-defined modes.
New text: In addition, the Portlet's metadata indicates which of these
modes the Portlet supports in addition to any Producer-defined modes.
ID: L
Section: 6.1.9
Page/Line: 31/6-8
Old text: If no values are supplied, the Portlet MAY assume that all
transitions are valid.
New text: If the Consumer does not supply a value for validNewModes, the
Portlet can assume that all transitions are valid.
ID: M
Section: 6.1.9
Page/Line: 31/8-9
Old text: Consumers wishing to prohibit all transitions SHOULD supply just
the current mode in this array.
New text: Consumers can prohibit all transitions by supplying just the
current mode in this array.
ID: N
Section: 6.1.9
Page/Line: 31/6-8
Old text: If no values are supplied, the Portlet MAY assume that all
transitions are valid.
New text: If the Consumer does not supply a value for validNewWindowStates
,
the Portlet can assume that all transitions are valid.
ID: O
Section: 6.1.9
Page/Line: 31/8-9
Old text: Consumers wishing to prohibit all transitions SHOULD supply just
the current windowState in this array.
New text: Consumers can prohibit all transitions by supplying just the
current windowState in this array.
ID: P
Section: 6.1.10
Page/Line: 32/6-8
Old text: When a SOAP binding is used, the character set of the markup
returned by the Producer MUST match the character set of the response
message's document.
New text: When a SOAP binding is used, the XML specification requires the
character set of the markup match the character set of the response
message.
ID: Q
Section: 6.1.10
Page/Line: 32/27-28
Old text: The locale and markup type, if any, of the preferred title MUST
be identical to that of the markup
New text: The locale and any markup type, textual markup types only, of
the preferred title has to be identical to that of the markup
ID: R
Section: 6.1.13
Page/Line: 33/43-45
Old text: The Consumer is not required to persist the navigationalState
for longer than this set of interactions, but MAY provide such a
persistence if desired.
New text: The Consumer is not required to persist the navigationalState
for longer than this set of interactions, but can provide such a
persistence if desired.
ID: S
Section: 6.6
Page/Line: 42/11-12
Old text: Consumers SHOULD be careful about the support supplied by the
web stack with regards to multiple bindings that will be offered by many
Producers.
New text: Consumers need to be careful about the support supplied by the
web stack with regards to multiple bindings that will be offered by many
Producers.
ID: T
Section: 6.7.1
Page/Line: 42/29-31
Old text: Note: Invocations of performBlockingInteraction() MAY happen in
this scenario if the Portlet impacts some backend system as a result of
the invocation as this impact could change the markup some other Portlet
will generate.
New text: Note: Invocations of performBlockingInteraction() can happen in
this scenario if the Portlet impacts some back-end system as a result of
the invocation as this impact could change the markup some other Portlet
will generate.
ID: U
Section: 6.7.3
Page/Line: 44/4-6
Old text: These Portlets MAY also push navigational state to the Consumer
such that an End-User may bookmark some portion of the state for use in
later conversations.
New text: These Portlets can also push navigational state to the Consumer
such that an End-User may bookmark some portion of the state for use in
later conversations.
ID: V
Section: 6.8.5
Page/Line: 45/31-33
Old text: The Portlet SHOULD be prepared to receive a mode it does not
currently support as it may have existed in a previous PortletDescription.
New text: The Portlet could receive a mode it does not currently support
as it may have existed in a previous PortletDescription.
ID: W
Section: 6.9.2
Page/Line: 46/9-11
Old text: The Producer MUST expect the getMarkup() operation to be invoked
for the minimized state just as for all other window states. New text: The
getMarkup() operation can be invoked for the minimized state
just as for all other window states.
ID: X
Section: 6.9.5
Page/Line: 46/24-26
Old text: The Portlet SHOULD be prepared to receive a window state it does
not currently support as it may have existed in a previous
PortletDescription.
New text: The Portlet could receive a window state it does not currently
support as it may have existed in a previous PortletDescription.
ID: Y
Section: 7
Page/Line: 47/24-25
Old text: Regardless of whether or not the registration portType is
exposed, Producers MAY offer out-of-band processes to register a Consumer.
New text: Regardless of whether or not the registration portType is
exposed, Producers can offer out-of-band processes to register a Consumer.
ID: Z
Section: 7.1.1
Page/Line: 48/7-9
Old text: This string MAY then contain any additional characters/words the
product or Consumer wish to supply.
New text: This string can then contain any additional characters/words the
product or Consumer wish to supply.
----------------------------------------------------------------
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>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]