Input: [#] CS035 [Section] 4.2 [Statement text]

Output: When generating the ServiceDescription response the Producer SHOULD use the desiredLocales (an array of strings) to control what locales are returned for localized strings.


Input: [#] CS185 [Section] 4.2 [Statement text]

Output: When the Consumer does not supply this parameter, the Producer MUST return a portletDescription for each of the "Producer Offered Portlets" the Consumer has access to through the supplied registrationContext.


Input: [#] CS036 [Section] 5.1.1 [Statement text]

Output: The maximum length of a sessionID is 4096 characters, though Producers SHOULD keep it as short as possible as this can have a significant impact on Consumer performance.


Input: [#] CS037 [Section] 5.1.1 [Statement text]

Output: Producers SHOULD also keep the sessionID as stable as possible since changes in value can also have a significant impact on Consumer performance.


Input: [#] CS038 [Section] 5.1.1 [Statement text]

Output: If the Producer returns an InvalidSession fault message after returning a sessionID, the Consumer MUST NOT resupply that sessionID on a subsequent invocation and SHOULD reinvoke the operation that caused the fault message without any sessionID and supply any data that may have been stored in the session.


Input: [#] CS039 [Section] 5.1.2 [Statement text]

Output: portletInstanceKey: An opaque string, unique within the RegistrationContext, which the Consumer MUST supply as a reference to its use of the Portlet.


Input: [#] CS040 [Section] 5.1.2 [Statement text]

Output: Consumer SHOULD keep their portletInstanceKey values as short as possible.


Input: [#] CS041 [Section] 5.1.2 [Statement text]

Output: If the PortletDescription also has templatesStoredInSession set to "true", then the Consumer MAY elect to only send these once for a sessionID.


Input: [#] CS186 [Section] 5.1.3 [Statement text]

Output: The value which the Consumer supplies in the portletInstanceKey field MUST remain constant for any one particular use of the Portlet.


Input: [#] CS227 [Section] 5.1.3 [Statement text]

Output: In order to support items that could become part of a URL activation, this token MUST remain constant for the lifetime of the portletInstanceKey and be the value used for both Consumer and Producer namespacing (see [Section 9.3]).


Input: [#] CS042 [Section] 5.1.4 [Statement text]

Output: If the portletState field has a value, the Consumer MUST return this value on subsequent calls using the same portletHandle. Note that such uses can span multiple starting and stopping cycles of the Consumer and therefore this state MUST be persisted by the Consumer until successfully invoking destroyPortlets with the related portletHandle.


Input: [#] CS192 [Section] 5.1.4 [Statement text]

Output: When this field [PortletContext.scheduledDestruction] is missing, scheduled destruction is not in use and the explicit destruction operations MUST be used instead.


Input: [#] CS043 [Section] 5.1.5 [Statement text]

Output: UserScope is an open set of values where the Producer SHOULD restrict the values supplied to those specified in this specification or custom values the Consumer has indicated it supports.


Input: [#] CS044 [Section] 5.1.5 [Statement text]

Output: "wsrp:perUser": The markup is specific to the userContext for which it was generated. Changes to the data of the UserContext MUST invalidate the cached markup.


Input: [#] CS045 [Section] 5.1.6 [Statement text]

Output: Note that any key used by the caching system to locate this markup MUST include the MarkupParams structure that was current when the content was originally cached.


Input: [#] CS046 [Section] 5.1.6 [Statement text]

Output: validateTag: A string the Consumer MAY use to attempt to revalidate markup once the expires duration elapses.


Input: [#] CS047 [Section] 5.1.6 [Statement text]

Output: If the Consumer does not know how to process the specified userScope, it MUST NOT cache the markup.


Input: [#] CS223 [Section] 5.1.10 [Statement text]

Output: When this structure is being supplied to the getResource operation, Consumers SHOULD supply the same set of items which would have been supplied using the HTTP proxy method of serving the resource.


Input: [#] CS193 [Section] 5.1.12 [Statement text]

Output: While Consumer policy will govern when values from sources other than the Portlet update the publicValues, Consumers MUST apply Portlet supplied values (i.e. supplied on a portlet url parameter or on a response from performBlockingInteraction or handleEvents) to the publicValues and SHOULD supply the same value to Portlets which provide a navigationalParameterDescription referencing the same QName in the names array.


Input: [#] CS048 [Section] 5.1.13 [Statement text]

Output: The Consumer MUST set the secureClientCommunication flag as the Portlet MAY render different content when it knows the delivery channel is secure.


Input: [#] CS049 [Section] 5.1.13 [Statement text]

Output: In addition to these fully specified Mime types, use of "*" (indicates all Mime types are acceptable) and type/* (where type includes things such as "text") from the HTTP definition[1] MAY be specified.


Input: [#] CS050 [Section] 5.1.13 [Statement text]

Output: Portlets SHOULD generate markup in one of the specified Mime types.


Input: [#] CS051 [Section] 5.1.13 [Statement text]

Output: The Consumer MUST specify either one of the modes from the Portlet's metadata or "wsrp:view" (all Portlets are required to support this mode).


Input: [#] CS052 [Section] 5.1.13 [Statement text]

Output: The Consumer MUST specify either one of the windowStates from the Portlet's metadata or "wsrp:normal" (all Portlets are required to support this windowState).


Input: [#] CS053 [Section] 5.1.13 [Statement text]

Output: When the SOAP binding is in use, the Producer MUST either use one of the markupCharacterSets, UTF-8 or UTF-16 for the response message as the nature of XML requires the character set used for the markup to be the same as the response message.


Input: [#] CS054 [Section] 5.1.13 [Statement text]

Output: validateTag: This field MAY contain a validateTag previously supplied to the Consumer in a MarkupContext structure.


Input: [#] CS055 [Section] 5.1.13 [Statement text]

Output: validNewModes: Current set of modes the Producer MAY request changing to.


Input: [#] CS056 [Section] 5.1.13 [Statement text]

Output: Custom modes, windowStates, userScopes and userAuthentication values MUST be URI's in order to reduce name clashes with any values that may be defined by future versions of this specification.


Input: [#] CS194 [Section] 5.1.15 [Statement text]

Output: As the Producer is ignorant of this encoding and the Consumer is required to consistently encode parameters passed to the Producer in the SOAP message, Consumers MUST ensure that form data is properly decoded before it is passed to the Producer.


Input: [#] CS224 [Section] 5.1.16 [Statement text]

Output: When this field is supplied on the response from a getResource operation, Consumers SHOULD apply the same policy which would have been used for the HTTP proxy method of serving the resource.


Input: [#] CS057 [Section] 5.1.16 [Statement text]

Output: If the value for useCachedMarkup is "true" the markupString and markupBinary fields MUST NOT be returned.


Input: [#] CS058 [Section] 5.1.16 [Statement text]

Output: If the field's (useCachedMarkup) value is "true", any supplied cacheControl field MUST be processed as an update to the cacheControl originally supplied with the cached markup.


Input: [#] CS059 [Section] 5.1.16 [Statement text]

Output: The mimeType field MUST be specified whenever markup is returned, and if the markupBinary field is used to return the markup, the mime type MUST include the character set for textual mime types using the syntax specified in RFC1522 (e.g. "text/html; charset=UTF-8"). In this particular case this character set MAY be different than the response message.


Input: [#] CS060 [Section] 5.1.16 [Statement text]

Output: The character set of the markup a Portlet returns MUST either match that requested in MarkupParams, be UTF-8 or UTF-16.


Input: [#] CS062 [Section] 5.1.16 [Statement text]

Output: The Consumer MUST parse the markup for URL rewriting if the value of requiresUrlRewriting is "true".


Input: [#] CS195 [Section] 5.1.22 [Statement text]

Output: This optional field contains the data for the event and becomes a REQUIRED field when either the relevant EventDescription or the Event structures specify a value for the type field. One example of when this field might not be included is when the event is simply a signal and the event's name thereby carries all of the semantics of the event. Its contents MUST conform to the schema referenced by the type field.


Input: [#] CS196 [Section] 5.1.24 [Statement text]

Output: Consumers MUST rewrite these URLs [redirectURL] in the same manner as those contained within markup the Portlet might return.


Input: [#] CS197 [Section] 5.1.27 [Statement text]

Output: Since the Producer/Portlet is capable of appropriate retries for the processing of any given event, the Consumer MUST NOT retry distributing failed events to the Portlet.


Input: [#] CS064 [Section] 5.1.23 [Statement text]

Output: The Consumer SHOULD supply the returned values, along with any additional or updated publicValues, as the navigational state on the subsequent invocations for this use of the Portlet for at least the duration of the End-User's interactions with this aggregated page.


Input: [#] CS067 [Section] 5.1.30 [Statement text]

Output: As the Producer is ignorant of this encoding and the Consumer is required to consistently encode parameters passed to the Producer in the SOAP message, Consumers MUST ensure that form data is properly decoded before it is passed to the Producer.


Input: [#] CS068 [Section] 5.1.33 [Statement text]

Output: The userContextKey MUST remain invariant for the duration of a Consumer's registration.


Input: [#] CS069 [Section] 5.1.33 [Statement text]

Output: The Consumer MUST NOT assert a user category for which no UserCategoryDescription was part of the Producer's ServiceDescription.


Input: [#] CS070 [Section] 5.2.1.1 [Statement text]

Output: Whenever the cacheControl field of a MarkupResponse structure is filled in the Consumer MAY cache the markup fragment.


Input: [#] CS071 [Section] 5.2.1.1 [Statement text]

Output: The Consumer MUST follow the defined invalidation policies to keep the cache up-to-date from section 5.2.1.2.


Input: [#] CS072 [Section] 5.2.1.1 [Statement text]

Output: If the cacheControl field is empty, the Portlet has provided no guidance and the Consumer MAY apply whatever cache policy it chooses. For a Portlet to indicate the markup is not cacheable, it will need to return a cacheControl structure with a value of zero in the expires field.


Input: [#] CS073 [Section] 5.2.1.2 [Statement text]

Output: Portlets indicating the cached markup can be used SHOULD also supply a new CacheControl structure with a new expiry for the markup.


Input: [#] CS225 [Section] 5.3 [Statement text]

Output: When the Portlet offers a choice to the Consumer between using the getResource operation or the HTTP proxy method to retrieve the resource, the resource served to the End-User SHOULD NOT depend on how the Consumer chooses to retrieve the resource.


Input: [#] CS198 [Section] 5.3 [Statement text]

Output: Resources which are inserted into the Consmer's aggregated page MUST follow the guidelines in [Section 9.4] for the mime types described there and the relevant fragment rules, if any, for other mime types.


Input: [#] CS074 [Section] 5.4 [Statement text]

Output: The Consumer MUST always propagate these End-User interactions to the Producer.


Input: [#] CS075 [Section] 5.4.3 [Statement text]

Output: If the Consumer has set the portletState flag to "readWrite", the Portlet MAY modify its persistent state regardless of whether it is persisted on the Producer or Consumer.


Input: [#] CS076 [Section] 5.4.3 [Statement text]

Output: If the Consumer has set the portletState field to "cloneBeforeWrite", persistent state changes are allowed only if the Producer first clones the Portlet. If the Producer does not clone the Portlet, processing attempts to modify persistent state MUST proceed as if the Consumer had specified "readOnly" for portletState.


Input: [#] CS077 [Section] 5.4.3 [Statement text]

Output: If the Producer clones the Portlet, processing attempts to modify persistent state on the new Portlet SHOULD proceed as if the Consumer had specified "readWrite" for portletState.


Input: [#] CS078 [Section] 5.4.3 [Statement text]

Output: If the Producer returns a new portletHandle without returning a new sessionID, the Consumer MUST associate the current sessionID with the new portletHandle rather than the previous portletHandle.


Input: [#] CS079 [Section] 5.4.3 [Statement text]

Output: If the Consumer has set the portletState flag to "readOnly", the Portlet MUST NOT modify its persistent state regardless of whether it is persisted on the Producer or Consumer and MUST throw a fault message if processing the interaction requires changing its persistent state.


Input: [#] CS080 [Section] 5.4.3 [Statement text]

Output: If the Producer implements access control that prevents Portlets from updating persistent state and a Portlet is unable to process the interaction without such an update, then the fault PortletStateChangeRequired MAY be thrown indicating the interaction processing failed.


Input: [#] CS199 [Section] 5.4.2.3 [Statement text]

Output: The Consumer SHOULD honor a handleEvents invocation returning requests to change mode or windowState provided they do not conflict with other such requests. Since the policy for handling conflicting requests is up to the Consumer implementation, Portlet developers SHOULD be aware that the impact on the overall layout MAY cause the Consumer to not honor a request to change windowState.


Input: [#] CS200 [Section] 5.4.3 [Statement text]

Output: Only if the Portlet's enduring state is modified and it is persisted on the Consumer should a PortletContext be returned to the Consumer and such a PortletContext MUST reference the portletHandle which was supplied by the Consumer.


Input: [#] CS081 [Section] 5.5 [Statement text]

Output: If the Producer's metadata has set the requiresInitCookie field to any value other than “none”, then the Consumer MUST invoke initCookie and supply any returned cookies according to the semantics of the value of requiresInitCookie as defined in section 4.1.17.


Input: [#] CS082 [Section] 5.5 [Statement text]

Output: If at any time the Producer throws a fault message (InvalidCookie) indicating the supplied cookie has been invalidated at the Producer, then the Consumer MUST again invoke initCookie and SHOULD reprocess the invocation that caused the fault message to be thrown and include any data that may have been stored in a session related to a cookie.


Input: [#] CS083 [Section] 5.6 [Statement text]

Output: The Consumer MAY inform the Producer that it will no longer be using a set of sessions by invoking releaseSessions (e.g. the Consumer is releasing resources related to the sessionIDs):


Input: [#] CS084 [Section] 5.6 [Statement text]

Output: After invoking releaseSessions the Consumer MUST NOT include any of the supplied sessionIDs on subsequent invocations.


Input: [#] CS085 [Section] 5.7 [Statement text]

Output: If a Producer indicates that it uses cookies, the Consumer MUST ensure that any cookies the Producer sets are available on all invocations within the Markup interface.


Input: [#] CS086 [Section] 5.7 [Statement text]

Output: In addition, moving cookies from an HTTPS to an HTTP connection opens security issues that MUST be handled in the manner prescribed in RFC2109[2]. Consumers MUST respect the security setting on each cookie.


Input: [#] CS066 [Section] 5.9 [Statement text]

Output: The Consumer MUST respect requests to change the mode outside of exceptional circumstances (e.g. access control restrictions), but the Portlet must not depend on such a request being respected.


Input: [#] CS087 [Section] 5.9.1 [Statement text]

Output: Conformant Portlets MUST support the wsrp:view mode.


Input: [#] CS088 [Section] 5.9.5 [Statement text]

Output: A Portlet MUST map any mode it does not understand to the wsrp:view mode.


Input: [#] CS065 [Section] 5.10 [Statement text]

Output: The Consumer SHOULD choose to respect this request to change the window state, but since the Portlet cannot depend on that choice it MUST NOT encode this new window state into any of its stateful settings. Rather, the Portlet MUST compute any such impact on stateful settings after the Consumer has actually changed the window state.


Input: [#] CS089 [Section] 5.10.1 [Statement text]

Output: The wsrp:normal window state MAY also indicate that the target device has limited display capabilities. Therefore, a Portlet SHOULD restrict the size of its rendered output in this window state.


Input: [#] CS090 [Section] 5.10.1 [Statement text]

Output: Conformant Portlets MUST support the wsrp:normal window state.


Input: [#] CS091 [Section] 5.10.2 [Statement text]

Output: When the window state is wsrp:minimized, the Portlet SHOULD NOT render visible markup, but is free to include non-visible data such as javascript or hidden forms.


Input: [#] CS092 [Section] 5.10.3 [Statement text]

Output: A Portlet SHOULD generate richer content when its window state is wsrp:maximized.


Input: [#] CS093 [Section] 5.10.4 [Statement text]

Output: A Portlet SHOULD generate richer content when its window state is wsrp:solo.


Input: [#] CS094 [Section] 5.10.5 [Statement text]

Output: A Portlet MUST map any window state it does not understand to wsrp:normal.


Input: [#] CS201 [Section] 5.11.2 [Statement text]

Output: Portlets/Producers handling this event SHOULD be aware that idempotency concerns related to the Consumer's processing of the request it received could limit how it processes items returned from the processing of this event.


Input: [#] CS095 [Section] 5.12 [Statement text]

Output: A Producer's ServiceDescription MAY declare support for user categories.


Input: [#] CS096 [Section] 5.12 [Statement text]

Output: A Consumer MAY map End-Users to the user categories a Producer declares in any manner it chooses, including ignoring them.


Input: [#] CS097 [Section] 5.12 [Statement text]

Output: Producers that use user categories SHOULD implement appropriate default behavior in the event a Consumer does not assert any user category for the End-User.


Input: [#] CS098 [Section] 6 [Statement text]

Output: All Producer registration processes MUST result in a unique, opaque token that may be used to refer to the registration.


Input: [#] CS099 [Section] 6.1.1 [Statement text]

Output: The consumerAgent value MUST start with productName.majorVersion.minorVersion where "productName" identifies the product the Consumer installed for its deployment, and "majorVersion" and "minorVersion" are vendor-defined indications of the version of its product.


Input: [#] CS100 [Section] 6.1.1 [Statement text]

Output: registrationProperties: List of registration properties. The names of these properties SHOULD be from the set declared in the registrationPropertyDescription from the Producer's ServiceDescription and are not part of this specification.


Input: [#] CS101 [Section] 6.2 [Statement text]

Output: When the Consumer chooses to end the relationship, it MUST attempt an invocation of the deregister operation so that the Producer may release related resources.


Input: [#] CS102 [Section] 6.2 [Statement text]

Output: When the Producer chooses to invalidate the registration identifier, it MUST inform the Consumer of this through a fault message on the next invocation specifying this registrationHandle so that the Consumer may release related resources.


Input: [#] CS103 [Section] 6.2 [Statement text]

Output: If the Producer's metadata declares registration is not supported (i.e. requiresRegistration flag was set to "false"), then it MUST be valid to not supply a registrationContext to operations with this parameter.


Input: [#] CS104 [Section] 6.2 [Statement text]

Output: Whenever the registration attempt fails a fault message MUST be thrown indicating this to the Consumer


Input: [#] CS105 [Section] 6.2 [Statement text]

Output: A Producer supporting registration MUST allow a Consumer to register itself multiple times with potentially different settings (e.g. billing settings) resulting in multiple registrationHandles [R351].


Input: [#] CS106 [Section] 6.4 [Statement text]

Output: The Consumer MUST NOT consider a relationship with a Producer ended until a successful invocation of deregister.


Input: [#] CS107 [Section] 6.4 [Statement text]

Output: The Consumer MUST NOT use an invalidated registrationHandle, where the invalidation occurs either by passing the handle to deregister or by receiving a InvalidRegistration fault message from the Producer on an invocation supplying the handle.


Input: [#] CS108 [Section] 6.4 [Statement text]

Output: The Producer MUST return a InvalidRegistration fault message whenever a Consumer supplies an invalid registrationHandle.


Input: [#] CS109 [Section] 6.4 [Statement text]

Output: If the deregister operation fails, the Producer MUST return a fault message specifying the reason for the failure.


Input: [#] CS202 [Section] 6.5 [Statement text]

Output: If the nillable response from getRegistrationLifetime is nil, then scheduled destruction is not in use for this registration and the Consumer MUST use the deregister operation to destroy the registration.


Input: [#] CS110 [Section] 7 [Statement text]

Output: Producers MUST expose one or more logically distinct ways of generating markup and handling interaction with that markup [A205], which this specification refers to as Portlets.


Input: [#] CS111 [Section] 7 [Statement text]

Output: A Consumer MAY request a unique configuration of one of these Portlets, either in an opaque manner (e.g. the "edit" button common on aggregated pages which invokes a Portlet-generated page for setting the configuration) or by using the property definitions found in the Portlet's metadata to configure it in an explicit manner


Input: [#] CS112 [Section] 7 [Statement text]

Output: Any Producer that supports cloning portlets on performBlockingInteraction invocations MUST support the releasePortlet operation.


Input: [#] CS203 [Section] 7.1.8 [Statement text]

Output: An array of ExportedPortlet structures where each exported Portlet MUST be represented by a single entry in the array.


Input: [#] CS113 [Section] 7.2 [Statement text]

Output: For security reasons related to exposing the existence of something the caller is not allowed to access, it is RECOMMENDED that a AccessDenied fault be generated both for the case of the supplied portletHandle not being a valid reference in the scope of the supplied registrationHandle and for the case of the user not having access to a valid reference (i.e. by definition access is denied when the Portlet reference is invalid).


Input: [#] CS114 [Section] 7.2 [Statement text]

Output: When generating the PortletDescriptionResponse the Producer SHOULD use the desiredLocales to control what locales are supplied for localized strings.


Input: [#] CS115 [Section] 7.3 [Statement text]

Output: The supplied PortletContext MUST refer to either a Producer Offered Portlet or a previously cloned Consumer Configured Portlet.


Input: [#] CS116 [Section] 7.3 [Statement text]

Output: The initial state of the new Portlet MUST be equivalent to the state of the Portlet referenced by the supplied handle.


Input: [#] CS117 [Section] 7.3 [Statement text]

Output: The new portletHandle MUST be scoped by the registrationHandle in the supplied RegistrationContext and be unique within this registration.


Input: [#] CS118 [Section] 7.3 [Statement text]

Output: If a Producer chooses to return the enduring state of its Portlets to the Consumer, it is RECOMMENDED that the portletHandle encode the supplied registrationHandle. In this case, it is also RECOMMENDED that the portletState encode the portletHandle so that the Producer can do reasonable cross checks that it is receiving a consistent set of handles and state.


Input: [#] CS119 [Section] 7.3 [Statement text]

Output: If the Consumer has not registered, then the Consumer MUST invoke destroyPortlets when it would have deregistered, passing each portletHandle that would have been scoped by a registration.


Input: [#] CS120 [Section] 7.4 [Statement text]

Output: The Consumer MUST inform the Producer that a Consumer Configured Portlet which does not use leasing will no longer be used by invoking either the destroyPortlets or the deregister operation and MUST NOT consider such a Portlet to have been destroyed until one of these operations has been successfully invoked for that Portlet.


Input: [#] CS121 [Section] 7.4 [Statement text]

Output: A Consumer MUST NOT reference any of the supplied portletHandles after successfully invoking destroyPortlets and MAY reclaim resources related to the supplied portletHandles (e.g. portletState).


Input: [#] CS204 [Section] 7.5 [Statement text]

Output: If the optional Lifetime field from getPortletsLifetime is not returned for a particular Portlet, then scheduled destruction is not in use for this Portlet and the Consumer MUST use the destroyPortlets operation to destroy the Portlet.


Input: [#] CS205 [Section] 7.7 [Statement text]

Output: When not returning a fault, the Producer MUST return exactly one entry in its response for each entry in the request to copyPortlets.


Input: [#] CS206 [Section] 7.8 [Statement text]

Output: If the Consumer requires the Producer to export the Portlets by value and the Producer does not support such exports, the ExportByValueNotSupported fault MUST be returned.


Input: [#] CS207 [Section] 7.8 [Statement text]

Output: The returned ExportPortletsResponse contains arrays for both the set of successfully exported Portlets and reasons for each Portlet where the export attempt failed. When not returning a fault, the Producer MUST return exactly one entry in its response for each entry in the request to exportPortlets.


Input: [#] CS208 [Section] 7.8 [Statement text]

Output: The Producer indicates its preferred request size in the recommendedExportSize field of its ServiceDescription. Consumers SHOULD limit their export requests to chunks no larger then this size.


Input: [#] CS209 [Section] 7.9 [Statement text]

Output: The Producer response MUST contain exactly one element for each entry in the list supplied to importPortlets.


Input: [#] CS122 [Section] 7.12 [Statement text]

Output: The supplied set of property changes MUST be processed together. In particular, validation SHOULD only be done considering the entire set as partial updates could easily create an internally inconsistent set of properties. The storage of the update caused by applying the set of property updates SHOULD only occur after the Producer/Portlet executes this validation.


Input: [#] CS123 [Section] 7.12 [Statement text]

Output: The Producer SHOULD serialize invocations of setPortletProperties for any one portletHandle.


Input: [#] CS124 [Section] 7.13 [Statement text]

Output: If the Consumer does not pass a names parameter, the Producer / Portlet MUST treat this as a request to enumerate the properties of the Portlet.


Input: [#] CS125 [Section] 7.14 [Statement text]

Output: While it is possible the set of properties can change with time (e.g. the Portlet dynamically creates or destroys properties), Producers and Portlets SHOULD make the returned modelDescription as complete as possible.


Input: [#] CS126 [Section] 7.14 [Statement text]

Output: When generating the PortletPropertyDescriptionResponse the Producer SHOULD use the desiredLocales to control which locales are supplied for localized strings.


Input: [#] CS127 [Section] 9.1 [Statement text]

Output: The Consumer indicates to the Portlet the preferred character encoding, using the markupCharacterSets field of the MarkupParams structure. It is up to the Portlet to generate markup that complies with this encoding. The Portlet is allowed to generate its markup in either the UTF-8 or UTF-16 character set encodings if it is unable to generate the requested character set. If it is unable to generate markup in any of these character sets, the Portlet MUST return a fault message to the Consumer.


Input: [#] CS128 [Section] 9.2 [Statement text]

Output: As the Portlet writes URLs into the markup it MUST encode them based on the markupType. For example, XML based markup requires that all "&" characters have to be encoded as "&".


Input: [#] CS129 [Section] 9.2 [Statement text]

Output: If a Portlet is unable to completely write the portlet URLs for its markup, it MUST set the requiresUrlRewriting flag in the returned MarkupContext structure to “true”.


Input: [#] CS130 [Section] 9.2 [Statement text]

Output: Portlets MUST adopt the following convention for including non-ASCII characters within portlet URLs in order to comply with W3C recommendations. Represent each character in UTF-8 (see [RFC2279]) as one or more bytes. Escape these characters with the URI escaping mechanism (i.e., by converting each byte to %HH, where HH is the hexadecimal notation of the character value)


Input: [#] CS131 [Section] 9.2 [Statement text]

Output: When URL activations occur, the Consumer MUST process all mode and window state change requests and either honor and reject them prior to invoking the operation indicated by the URL. If the requested mode or window state is for a value that is either invalid or unavailable, the Consumer SHOULD leave the current value unchanged.


Input: [#] CS138 [Section] 9.2 [Statement text]

Output: Since the values a Portlet provides will appear as either an URL parameter value or as part of the path of an URL, these values it MUST be strictly encoded (i.e. "&", "=", "/", and "?" need to be url-escaped) so that special URL characters do not invalidate the processing of the enclosing URL.


Input: [#] CS132 [Section] 9.2.1 [Statement text]

Output: The Consumer is NOT REQUIRED to process URLs not conforming to this format and MAY choose to pass them unchanged, replace them with error text, do a best effort processing or invalidate the entire markup fragment.


Input: [#] CS133 [Section] 9.2.1 [Statement text]

Output: The Consumer is NOT REQUIRED to process escaped characters in parameter names, but rather MAY pass them unchanged to either the user-agent (during URL rewriting) or the Producer (during processing of an activated URL).


Input: [#] CS176 [Section] 9.2.1 [Statement text]

Output: Consumers MUST accept both the "&" character and the corresponding entity reference (i.e. "&") as separators between the name/value pairs as this allows portlets to produce markup fragments valid for a larger range of mime types.


Input: [#] CS134 [Section] 9.2.1.1 [Statement text]

Output: This parameter (wsrp-urlType) MUST be specified first when using the Consumer URL rewriting template and the value selected from the following definitions.


Input: [#] CS135 [Section] 9.2.1.1.1 [Statement text]

Output: All form parameters, submitted as query string parameters using the HTTP GET method, that are not used to encode parameters defined by this specification MUST be passed to performBlockingInteraction as formParameters.


Input: [#] CS136 [Section] 9.2.1.1.2 [Statement text]

Output: The URL MAY specify the wsrp-navigationalState and/or wsrp-navigationalValues portlet URL parameters, whose values the Consumer MUST supply in the opaqueValue and publicValues fields of the NavigationalContext structure, respectively.


Input: [#] CS137 [Section] 9.2.1.1.3 [Statement text]

Output: When a portlet URL specifies "resource" for the wsrp-urlType portlet URL parameter, either the wsrp-resourceID portlet URL parameter or a combination of the wsrp-requiresRewrite and the wsrp-url portlet URL parameters MUST also be specified.


Input: [#] CS210 [Section] 9.2.1.1.3.2 [Statement text]

Output: [wsrp-resourceID]: This parameter provides the resourceID parameter which the Consumer MUST supply when invoking the ?getResource operation.


Input: [#] CS211 [Section] 9.2.1.1.3.4 [Statement text]

Output: [wsrp-resourceState]: The value of this portlet URL parameter defines the state which the Consumer MUST send in the resourceState field of the ResourceParams structure when the URL is activated. If this parameter is missing, the Consumer MUST NOT supply a value in the resourceState field of the ResourceParams structure.


Input: [#] CS226 [Section] 9.2.1.1.3.6 [Statement text]

Output: As a result, the resource generation SHOULD NOT depend on the NavigationalContext, mode or windowState and the generated resource MUST NOT include URIs with a wsrp-urlType of render or blockingAction.


Input: [#] CS177 [Section] 9.2.1.1.3.6 [Statement text]

Output: Normally this occurs if either the referenced resource or a secondary resource which this resource MAY contain URIs with a wsrp-urlType of render or blockingAction.


Input: [#] CS190 [Section] 9.2.1.1.3.6 [Statement text]

Output: This restriction increases the cacheability of the resource over specifying a value of "page" (e.g. for the duration of a user interacting with some other portlet), but the generated resource MUST NOT include URIs with a wsrp-urlType of render or blockingAction.


Input: [#] CS212 [Section] 9.2.1.1.4 [Statement text]

Output: Consumers supporting an extension MUST supply defined extensions to the Templates structure to those Producers indicating support for the same extension in their ServiceDescription.


Input: [#] CS140 [Section] 9.2.1.2 [Statement text]

Output: The value of this portlet URL parameter defines the opaqueValue portion of the Portlet's navigational state the Consumer MUST send to the Producer when the URL is activated. If this parameter is missing, the Consumer MUST NOT supply the opaqueValue portion of the Portlet's navigational state.


Input: [#] CS213 [Section] 9.2.1.3 [Statement text]

Output: Since multiple updates can be specified on a single URL, the following sequence of steps MUST be used when encoding the value for the wsrp-navigationalValues portlet url parameter: A querystring-like [20] value is built from the parameter identifiers and values to be set. Parameters that are an array of strings can be specified by repeating the parameter. For example, if a Portlet has defined three parameters and is setting two of these parameters, one an array of strings (parameter name is ""{http://www.example.com}param1"" with an identifier of ""p1""), and clearing another (parameter name is ""{http://www.example.com}param2"" with an identifier of ""p2"") while leaving the third parameter (parameter name is ""{http://www.example.com}param3"" with an identifier of ""p3"") unchanged, results in; p1=value1&p1=value2&p2= The string built in step #2 is url-encoded so that it can appear as the value of the portlet url parameter. The example becomes; p1%3Dvalue1%26p1%3Dvalue2%26p2%3D The url-encoded string is then used as the value of the wsrp-navigationalValues portlet url parameter.


Input: [#] CS214 [Section] 9.2.1.3 [Statement text]

Output: If values are supplied for the wsrp-navigationalValues portlet URL parameter, the Consumer MUST supply those values in the publicValues field along with the values the Consumer has for the Portlet's navigationalParameters which were not referenced by the wsrp-navigationalValues portlet URL parameter.


Input: [#] CS142 [Section] 9.2.1.4 [Statement text]

Output: The value of this portlet URL parameter defines the interaction state the Consumer MUST send to the Producer when the URL is activated. If this parameter is missing, the Consumer MUST NOT supply the interactionState field of the InteractionParams structure.


Input: [#] CS143 [Section] 9.2.1.5 [Statement text]

Output: The value for wsrp-mode MUST be one of the modes detailed in section 5.8 or a custom mode the Consumer specified as supported during registration.


Input: [#] CS144 [Section] 9.2.1.5 [Statement text]

Output: The wsrp-mode portlet URL parameter MAY be used whenever the wsrp-urlType portlet URL parameter has a value of "blockingAction" or "render".


Input: [#] CS145 [Section] 9.2.1.6 [Statement text]

Output: The value for wsrp-windowState MUST be one of the values detailed in section 5.9 or a custom window state the Consumer specified as supported during registration.


Input: [#] CS146 [Section] 9.2.1.6 [Statement text]

Output: The wsrp-windowState portlet URL parameter MAY be used whenever the wsrp-urlType portlet URL parameter has a value of "blockingAction" or "render".


Input: [#] CS147 [Section] 9.2.1.8 [Statement text]

Output: The value for the wsrp-secureURL is a boolean indicating whether the resulting URL MUST involve secure communication between the client and Consumer, as well as between the Consumer and Producer.


Input: [#] CS148 [Section] 9.2.1.8 [Statement text]

Output: Note that the Consumer's aggregated page MUST be secure if any of the Portlets whose content is being displayed on the page have indicated the need for secure communication for their current markup.


Input: [#] CS215 [Section] 9.2.1.9 [Statement text]

Output: Extensions to the data supplied on the URL which this protocol defines MUST use the following sequence to encode the additoinal information into the wsrp-extensions portlet URL parameter: A querystring-like [20] value is built from the parameter identifiers and values to be set. Parameters that are an array of strings can be specified by repeating the parameter. For example, if a Portlet has two additional parameters, one is an array of strings (parameter name is ""param1"") and and the other a simple string (parameter name is "param2"), results in; "param1=value1&param1=value2&param2=value3" The string built in step #1 is url-encoded so that it can appear as a querystring value or part of the path portion of the URL. The example becomes; "param1%3Dvalue1%26param1%3Dvalue2%26param2%3Dvalue3" The url-encoded string is then used as the value of the wsrp-extensions portlet url parameter or to replace it within a template.


Input: [#] CS149 [Section] 9.2.2 [Statement text]

Output: All content outside the {} pairs and all {} pairs containing tokens the Producer/Portlet does not recognize MUST be treated by the Producer/Portlet as constants the Consumer needs to receive when the portlet URL is activated.


Input: [#] CS216 [Section] 9.2.2 [Statement text]

Output: These tokens are enclosed in curly braces (i.e. "{" and "}") and contain the name of the portlet URL parameter which the Producer MUST replace (using "" for those parameters where the Producer has no value).


Input: [#] CS150 [Section] 9.2.2.1 [Statement text]

Output: The Consumer MUST integrate placeholders for at least the portlet URL parameters wsrp-navigationalState, wsrp-navigationalValues, wsrp-interactionState, wsrp-mode and wsrp-windowState in its template and SHOULD integrate placeholders for the other portlet URL paramaters defined in this specification.


Input: [#] CS151 [Section] 9.2.2.3 [Statement text]

Output: The Consumer MUST integrate placeholders for at least the portlet URL parameters wsrp-navigationalState, wsrp-mode and wsrp-windowState in its template.


Input: [#] CS152 [Section] 9.2.2.5 [Statement text]

Output: The Consumer MUST integrate placeholders for at least the portlet URL parameters wsrp-url, wsrp-resourceID, wsrp-preferOperation, wsrp-requiresRewrite and wsrp-resourceState to allow the Portlet to place all the pieces of information it could use for accessing a resource.


Input: [#] CS153 [Section] 9.2.2.7 [Statement text]

Output: Consumers not supplying all the other non-secure templates MUST set a value for this template.


Input: [#] CS154 [Section] 9.2.2.7 [Statement text]

Output: Since this may become the value for an action oriented template, the Consumer SHOULD integrate placeholders for at least the portlet URL parameters wsrp-navigationalState, wsrp-interactionState, wsrp-mode and wsrp-windowState in this template.


Input: [#] CS155 [Section] 9.2.2.8 [Statement text]

Output: Consumers not supplying all the other secure templates MUST set a value for this template.


Input: [#] CS156 [Section] 9.2.2.8 [Statement text]

Output: Since this may become the value for an action oriented template, the Consumer SHOULD integrate placeholders for at least the portlet URL parameters wsrp-navigationalState, wsrp-interactionState, wsrp-mode and wsrp-windowState in this template.


Input: [#] CS157 [Section] 9.2.2.9 [Statement text]

Output: If the Consumer includes wsrp-portletHandle, wsrp-userContextKey, wsrp-portletInstanceKey, wsrp-sessionID, wsrp-portletStates, or wsrp-pageState in a template, Producer written URLs based on that template MUST replace the specified portlet URL parameter with the value the Consumer separately supplied in a data field.


Input: [#] CS158 [Section] 9.2.4 [Statement text]

Output: As a result, Portlets that include HTML forms with method=get in their markup MUST specify usesMethodGet as "true" in their PortletDescription.


Input: [#] CS159 [Section] 9.3 [Statement text]

Output: Tokens needing uniqueness on the aggregated page MUST be encoded to a Portlet-instance specific namespace [A301]. The Portlet MAY do this by prefixing the name of the resource with the namespacePrefix from the RuntimeContext structure.


Input: [#] CS217 [Section] 9.3 [Statement text]

Output: In order for the semantics of namespace encoding, whether by Consumer rewriting or Producer writing, to serve the purposes of making the encoded items unique on the aggregated page and processable by the Producer/Portlet, should they become part of a user interaction, the namespacePrefix from the RuntimeContext structure MUST be the value used for both Consumer rewriting and Producer writing and MUST be constant for the duration of the portletHandle.


Input: [#] CS160 [Section] 9.3 [Statement text]

Output: Portlets choosing to apply namespace encoding to items that become part of a user interaction MUST process these items with their namespace prefix attached as Consumers MUST NOT remove such prefixes, regardless of whether Consumer rewriting or Producer writing was used to attach the prefix.


Input: [#] CS161 [Section] 9.3.1 [Statement text]

Output: The Consumer will locate such markers and MUST replace them with the same value that was supplied to the Portlet in the namespacePrefix field of the RuntimeContext structure.


Input: [#] CS162 [Section] 9.4 [Statement text]

Output: The disallowed tags listed below are those tags that impact other Portlets or may even break the entire aggregated page. Inclusion of such a tag invalidates the whole markup fragment, which the Consumer MAY replace with an error message.


Input: [#] CS163 [Section] 9.4.1.1 [Statement text]

Output: However, in order to be a conforming Portlet, a Portlet MUST NOT use the tags , , , , , and .


Input: [#] CS164 [Section] 9.4.2.1 & 10.4.3.1 [Statement text]

Output: However, in order to be a conforming Portlet, a Portlet MUST NOT use the tags , , , , , and .


Input: [#] CS165 [Section] 9.5 [Statement text]

Output: Portlets SHOULD use the CSS style definitions from this specification in order to participate in a uniform display of their content by various Consumers.


Input: [#] CS166 [Section] 9.5 [Statement text]

Output: For markup types that support CSS stylesheets, Consumers MUST supply a CSS stylesheet with definitions for the classes defined in section 9.5 of this specification.


Input: [#] CS167 [Section] 10.1 [Statement text]

Output: A Consumer SHOULD provide the specific fields the Portlet declared it needs, unless the information is not available or is restricted by policy (e.g. privacy policy).


Input: [#] CS218 [Section] 11.2 [Statement text]

Output: As the Producer is ignorant of this encoding and the Consumer is required to consistently encode parameters passed to the Producer in the SOAP message, Consumers MUST ensure the data is properly decoded before it is passed to the Producer.


Input: [#] CS219 [Section] 11.2 [Statement text]

Output: Consumers MUST send the value received for the wsrp-urlType portlet URL parameter using the name "wsrp-urlType" as the first element in the array of name/value pairs


Input: [#] CS220 [Section] 11.2 [Statement text]

Output: When processing a WSRP defined value for the wsrp-urlType portlet url parameters, Consumers MUST NOT resend a particular set of wsrp-extra:extendedURLParameters on later invocations of WSRP defined operations.


Input: [#] CS173 [Section] 13 [Statement text]

Output: The SOAP 1.1 faultcode SHOULD be set to the WSRP error code being raised, namespace qualified to be in the "urn:oasis:names:tc:wsrp:v2:types" namespace.


Input: [#] CS174 [Section] 13 [Statement text]

Output: In addition, the SOAP 1.1 fault's detail element MUST contain the corresponding namespaced fault element from the WSRP v2 WSDL as its only content.


Input: [#] CS175 [Section] 13 [Statement text]

Output: When using SOAP 1.2, the Subcode element MUST be present and carry the corresponding WSRP error code in its mandatory Value sub-element. The Subcode element MUST be contained in a SOAP 1.2 Receiver fault code, for the fault messages defined in this specification. SOAP 1.2 faults MAY carry additional content in the Detail sub-element, but MUST carry the corresponding WSRP namespaced fault element.


Input: [#] CS169 [Section] 14 [Statement text]

Output: WSRP_v2_Markup_PortType: All Producers MUST expose this portType. WSRP_v2_ServiceDescription_PortType: All Producers MUST expose this portType.


Input: [#] CS170 [Section] 14 [Statement text]

Output: WSRP_v2_Markup_Binding_SOAP: All Producers MUST expose a port with this binding for the WSRP_v2_Markup_PortType (the Markup portType). WSRP_v2_ServiceDescription_Binding_SOAP: All Producers MUST expose a port with this binding for the WSRP_v2_ServiceDescription_PortType (the ServiceDescription portType).


Input: [#] CS171 [Section] 14 [Statement text]

Output: WSRP_v2_Registration_Binding_SOAP: Producers supporting the Registration portType MUST expose a port with this binding to the WSRP_v2_Registration_PortType.


Input: [#] CS172 [Section] 14 [Statement text]

Output: WSRP_v2_PortletManagement_Binding_SOAP: Producers supporting the PortletManagement portType MUST expose a port with this binding to the WSRP_v2_PortletManagement_PortType.


Input: [#] CS168 [Section] 14 [Statement text]

Output: Normative copies of the WSDL that MUST be referenced by Producers implementing this specification can be found at: http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-types.xsd - The type, message and fault definitions for this specification http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-interfaces.wsdl - The portType definitions for this specification http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-bindings.wsdl - The standard binding definitions for this specification


Input: [#] CS221 [Section] 14 [Statement text]

Output: Producers SHOULD NOT expect Consumers to use a mixture of WSRP v1 and v2 ports when interacting with it. Producers SHOULD use a single wsdl file with distinct service elements for their v1 and v2 support if they support artifacts, such as registrationHandle or portletState, being used with all operations regardless of the version of the standard defining that operation and SHOULD use separate wsdl files for specifying support for different versions of WSRP when artifacts are usable only within the operations defined by a specific version of the WSRP standard.


Input: [Explanation] Returns the number of login attempts since starting the system. [Variable]

Output: @@CONNECTIONS

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the total CPU time (in units of milliseconds) used since starting the system. [Variable]

Output: @@CPU_BUSY

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the information about the return value of the last executed Transact-SQL statement. [Variable]

Output: @@ERROR

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the last inserted value for the column with the IDENTITY property (see Chapter 6). [Variable]

Output: @@IDENTITY

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the identifier of the language that is currently used by the database system. [Variable]

Output: @@LANGID

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the name of the language that is currently used by the database system. [Variable]

Output: @@LANGUAGE

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the maximum number of actual connections to the system. [Variable]

Output: @@MAX_CONNECTIONS

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the identifier for the stored procedure currently being executed. [Variable]

Output: @@PROCID

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the number of rows that have been affected by the last Transact-SQL statement executed by the system. [Variable]

Output: @@ROWCOUNT

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Retrieves the information concerning the local database server. This information contains, among other things, the name of the server and the name of the instance. [Variable]

Output: @@SERVERNAME

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the identifier of the server process. [Variable]

Output: @@SPID

Additional T-SQL operations in SQL Server 2008


Input: [Explanation] Returns the current version of the database system software. [Variable]

Output: @@VERSION

Additional T-SQL operations in SQL Server 2008


Input: [Key] yy [Action]

Output: yank line (copy the line ), 4yy would yank (copy) 4 lines


Input: [Key] p [Action]

Output: paste the last deleted or yanked text into the file at the cursor position


Input: [Key] P [Action]

Output: paste the last deleted or yanked text into the file (ahead of cursor)


Input: [Key] dd [Action]

Output: delete line. A d followed by any moving command in the list above will delete up to that point. For example, dw would delete the next word.


Input: [Key] cw [Action]

Output: change word (type the replacement word or words and then press )


Input: [Key] J [Action]

Output: join two lines together (place cursor on the first of the two lines)


Input: [Key] U [Action]

Output: undo the changes you made to the current line


Input: [Key] . [Action]

Output: (period) redo the last non-motion command


Input: [Key] >> [Action]

Output: shift line to the right.


Input: [Key] << [Action]

Output: shift to the left


Input: [Directory] conf/ [Purpose]

Output: Contains configuration files that apply to the gateway globally (i.e. not cluster specific ).


Input: [Directory] data/ [Purpose]

Output: Contains security and topology specific artifacts that require read/write access at runtime


Input: [Directory] data/topologies/ [Purpose]

Output: Contains topology files that represent Hadoop clusters which the gateway uses to deploy cluster proxies


Input: [Directory] data/security/ [Purpose]

Output: Contains the persisted master secret and keystore dir


Input: [Directory] data/security/keystores/ [Purpose]

Output: Contains the gateway identity keystore and credential stores for the gateway and each deployed cluster topology


Input: [Directory] bin/ [Purpose]

Output: Contains the executable shell scripts, batch files and JARs for clients and servers.


Input: [Directory] data/deployments/ [Purpose]

Output: Contains deployed cluster topologies used to protect access to specific Hadoop clusters.


Input: [Directory] lib/ [Purpose]

Output: Contains the JARs for all the components that make up the gateway.


Input: [Directory] dep/ [Purpose]

Output: Contains the JARs for all of the components upon which the gateway depends.


Input: [Directory] ext/ [Purpose]

Output: A directory where user supplied extension JARs can be placed to extends the gateways functionality.


Input: [Directory] pids/ [Purpose]

Output: Contains the process ids for running ldap and gateway servers


Input: [Directory] samples/ [Purpose]

Output: Contains a number of samples that can be used to explore the functionality of the gateway.


Input: [Directory] templates/ [Purpose]

Output: Contains default configuration files that can be copied and customized.


Input: [Directory] README [Purpose]

Output: Provides basic information about the Apache Knox Gateway.


Input: [Directory] ISSUES [Purpose]

Output: Describes significant know issues.


Input: [Directory] CHANGES [Purpose]

Output: Enumerates the changes between releases.


Input: [Directory] LICENSE [Purpose]

Output: Documents the license under which this software is provided.


Input: [Directory] NOTICE [Purpose]

Output: Documents required attribution notices for included dependencies.


Input: [Directory] DISCLAIMER [Purpose]

Output: Documents that this release is from a project undergoing incubation at Apache.


Input: [Type] limited [Meaning]

Output: Limited-access freeways

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] toll [Meaning]

Output: Limited-access toll highways

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] ramp [Meaning]

Output: Access ramps for limited-access highways

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] us [Meaning]

Output: National highways (e.g. US routes)

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] primary [Meaning]

Output: Primary State/Provincial routes

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] state [Meaning]

Output: State/Provincial routes

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] major [Meaning]

Output: Major Connectors

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] ferry [Meaning]

Output: Ferry Routes

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] local [Meaning]

Output: Local Roads

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Type] editable [Meaning]

Output: User-drawn Roads

GPSBabel development:DeLorme .an1 (drawing) file (an1)


Input: [Key] 5 [Action]

Output: start the test as defined in Settings

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] a [Action]

Output: start Acuity

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] l [Action]

Output: start acuity Letters

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] c [Action]

Output: start Contrast

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] v [Action]

Output: start Vernier

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] e [Action]

Output: start Tumbling E

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] b [Action]

Output: aBout

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] h [Action]

Output: Help

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] u [Action]

Output: settings

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] q [Action]

Output: Quit = Exit

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] k [Action]

Output: “Kindergarten” (don't)

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Key] 55 or [Action]

Output: abort running test

Freiburg Visual Acuity & Contrast Test, homepage


Input: [Attribute] align [Type] String [Description]

Output: The align attribute is a standard HTML attribute that specifies this element's horizontal alignment.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] bgcolor [Type] String [Description]

Output: The bgcolor attribute sets the background color for the table. This value can be the name or the hexadecimal value of the color.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] binding [Type] String [Description]

Output: The value-binding expression linking this component tag to a backing bean property.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] border [Type] String [Description]

Output: The border attribute sets the pixel width of the border to be drawn around the table.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] cellpadding [Type] String [Description]

Output: The cellpadding attribute sets the width between the border of each cell and its contents.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] cellspacing [Type] String [Description]

Output: The cellspacing attribute sets the width of the space between the outside and inside edges of the table as well as the space between cells.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] columnClasses [Type] String [Description]

Output: The firstRowIndexVar attribute sets a name that can be used to reference the firstRowIndexVar parameter. The first row index represents the DISPLAYED UI data component's first row. The firstRowIndexVar parameter is set during request scope.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] datafld [Type] String [Description]

Output: Reserved for future use.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] dataformatas [Type] String [Description]

Output: Reserved for future use.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] datasrc [Type] String [Description]

Output: Reserved for future use.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] dir [Type] String [Description]

Output: HTML: The direction of text display, either 'ltr' (left-to-right) or 'rtl' (right-to-left).

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] enabledOnUserRole [Type] String [Description]

Output: If user is in given role, this component will be rendered normally. If not, no hyperlink is rendered but all nested tags (=body) are rendered.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] first [Type] String [Description]

Output: The index of the first row to be displayed, where 0 is the first row.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] footerClass [Type] String [Description]

Output: The CSS class to be applied to footer cells.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] forceId [Type] String [Description]

Output: If true, this component will force the use of the specified id when rendering.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] forceIdIndex [Type] String [Description]

Output: If false, this component will not append a '[n]' suffix (where 'n' is the row index) to components that are contained within a "list." This value will be true by default and the value will be ignored if the value of forceId is false (or not specified.)

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] forceIdIndexFormula [Type] String [Description]

Output: A formula that overrides the default row index in the construction of table's body components. Example : #{myRowVar.key} Warning, the EL should evaluate to a unique value for each row !

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] frame [Type] String [Description]

Output: HTML: Controls what part of the frame that surrounds a table is visible. Values include: void, above, below, hsides, lhs, rhs, vsides, box, and border.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] headerClass [Type] String [Description]

Output: The CSS class to be applied to header cells.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] id [Type] String [Description]

Output: The developer-assigned ID of this component. The ID must be unique within the scope of the tag's enclosing naming container (e.g. h:form or f:subview). This value must be a static value.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] lang [Type] String [Description]

Output: HTML: The base language of this document.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] newspaperColumns [Type] String [Description]

Output: The number of columns to wrap the table over. Default: 1

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] newspaperOrientation [Type] String [Description]

Output: The orientation of the newspaper columns in the newspaper table - "horizontal" or "vertical". Default: vertical

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onclick [Type] String [Description]

Output: HTML: Script to be invoked when the element is clicked.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] ondblclick [Type] String [Description]

Output: HTML: Script to be invoked when the element is double-clicked.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onkeydown [Type] String [Description]

Output: HTML: Script to be invoked when a key is pressed down over this element.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onkeypress [Type] String [Description]

Output: HTML: Script to be invoked when a key is pressed over this element.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onkeyup [Type] String [Description]

Output: HTML: Script to be invoked when a key is released over this element.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onmousedown [Type] String [Description]

Output: HTML: Script to be invoked when the pointing device is pressed over this element.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onmousemove [Type] String [Description]

Output: HTML: Script to be invoked when the pointing device is moved while it is in this element.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onmouseout [Type] String [Description]

Output: HTML: Script to be invoked when the pointing device is moves out of this element.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onmouseover [Type] String [Description]

Output: HTML: Script to be invoked when the pointing device is moved into this element.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] onmouseup [Type] String [Description]

Output: HTML: Script to be invoked when the pointing device is released over this element.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] preserveDataModel [Type] String [Description]

Output: Indicates whether the state of the whole DataModel should be saved and restored. When set to false, the value-binding for the "value" attribute of this table is executed each time the page is rendered. When set to true, that value-binding is only executed when the component is first created, and the DataModel state is thereafter saved/restored automatically by the component. When column sorting is used for a table this property needs to be false so that the DataModel can be updated to reflect any changes in the sort criteria. Default: false

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] preserveRowStates [Type] String [Description]

Output: Indicates whether the state for each row should not be discarded before the datatable is rendered again. Setting this to true might be hepful if an input component inside the datatable has no valuebinding and the value entered in there should be displayed again. This will only work reliable if the datamodel of the datatable did not change either by sorting, removing or adding rows. Default: false

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] preserveSort [Type] String [Description]

Output: Indicates whether the state of the sortColumn and sortAscending attribute should be saved and restored and written back to the model during the update model phase. Default: true

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] previousRowDataVar [Type] String [Description]

Output: A parameter name, under which the previous RowData Object is set in request scope similar to the rowIndexVar and rowCountVar parameters. Mind that the value of this request scope attribute is null in the first row or when isRowAvailable returns false for the previous row.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rendered [Type] String [Description]

Output: A boolean value that indicates whether this component should be rendered. Default value: true.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] renderedIfEmpty [Type] String [Description]

Output: Indicates whether this table should be rendered if the underlying DataModel is empty. You could as well use rendered="#{not empty bean.list}", but this one causes the getList method of your model bean beeing called up to five times per request, which is not optimal when the list is backed by a DB table. Using renderedIfEmpty="false" solves this problem, because the MyFaces extended HtmlDataTable automatically caches the DataModel and calles the model getter only once per request. Default: true

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowClasses [Type] String [Description]

Output: A comma separated list of CSS class names to apply to td elements in each row.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowCountVar [Type] String [Description]

Output: A parameter name, under which the rowCount is set in request scope similar to the var parameter.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowGroupStyle [Type] String [Description]

Output: Corresponds to the HTML style attribute for grouped rows.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowGroupStyleClass [Type] String [Description]

Output: StyleClass for grouped rows.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowId [Type] String [Description]

Output: The id to use for elements that are generated by the table.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowIndexVar [Type] String [Description]

Output: A parameter name, under which the current rowIndex is set in request scope similar to the var parameter.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnClick [Type] String [Description]

Output: Defines a JavaScript onclick event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnDblClick [Type] String [Description]

Output: Defines a JavaScript ondblclick event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnKeyDown [Type] String [Description]

Output: Defines a JavaScript onkeydown event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnKeyPress [Type] String [Description]

Output: Defines a JavaScript onkeypress event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnKeyUp [Type] String [Description]

Output: Defines a JavaScript onkeyup event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnMouseDown [Type] String [Description]

Output: Defines a JavaScript onmpusedown event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnMouseMove [Type] String [Description]

Output: Defines a JavaScript onmousemove event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnMouseOut [Type] String [Description]

Output: Defines a JavaScript onmouseout event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnMouseOver [Type] String [Description]

Output: Defines a JavaScript onmouseover event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowOnMouseUp [Type] String [Description]

Output: Defines a JavaScript onmouseup event handler for each table row

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowStyle [Type] String [Description]

Output: Corresponds to the HTML style attribute for the row tr tag.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rowStyleClass [Type] String [Description]

Output: Corresponds to the HTML class attribute for the row tr tag.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rows [Type] String [Description]

Output: The number of rows to be displayed. Specify zero for all remaining rows in the table.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] rules [Type] String [Description]

Output: HTML: Controls how rules are rendered between cells. Values include: none, groups, rows, cols, and all.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] sortAscending [Type] String [Description]

Output: Value reference to a model property that gives the current sort direction. The target Boolean property is set to true when the selected sortColumn should be sorted in ascending order, and false otherwise. The method which is bound to the "value" attribute of this table (ie which provides the DataModel used) is expected to use this property to determine how to sort the DataModel's contents.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] sortColumn [Type] String [Description]

Output: Value reference to a model property that gives the current sort column name. The target String property is set to the "columnName" of whichever column has been chosen to sort by, and the method which is bound to the "value" attribute of this table (ie which provides the DataModel used) is expected to use this property to determine how to sort the DataModel's contents.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] sortedColumnVar [Type] String [Description]

Output: A parameter name, under which the a boolean is set in request scope similar to the var parameter. TRUE for the column that is currently sorted, FALSE otherwise.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] style [Type] String [Description]

Output: HTML: CSS styling instructions.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] styleClass [Type] String [Description]

Output: The CSS class for this element. Corresponds to the HTML 'class' attribute.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] summary [Type] String [Description]

Output: HTML: Provides a summary of the contents of the table, for accessibility purposes.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] title [Type] String [Description]

Output: HTML: An advisory title for this element. Often used by the user agent as a tooltip.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] value [Type] String [Description]

Output: An EL expression that specifies the data model that backs this table. The value can be of any type. A value of type DataModel is used directly. Array-like parameters of type java.util.List, array of Object, java.sql.ResultSet, or javax.servlet.jsp.jstl.sql.Result are wrapped in a DataModel. Other values are wrapped in a DataModel as a single row.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] var* [Type] String [Description]

Output: Defines the name of the request-scope variable that will hold the current row during iteration. This value must be a static value.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] varDetailToggler [Type] String [Description]

Output: This variable has the boolean property "currentdetailExpanded" which is true if the current detail row is expanded and the action method "toggleDetail" which expand/collapse the current detail row.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] visibleOnUserRole [Type] String [Description]

Output: If user is in given role, this component will be rendered normally. If not, nothing is rendered and the body of this tag will be skipped.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [Attribute] width [Type] String [Description]

Output: HTML: Specifies the desired width of the table, as a pixel length or a percentage of available space.

t:dataTable tomahawk-dataTable example JSF Tomahawk tag reference Tomahawk tag library MyFaces Tag Reference JavaServer Faces Tag Reference


Input: [CODE] origmono [TYPE]

Output: original monograph cataloging

Workstats | Procedures | Tech Services | MSU Libraries


Input: [CODE] copymono [TYPE]

Output: monograph copy cataloging

Workstats | Procedures | Tech Services | MSU Libraries


Input: [CODE] addimono [TYPE]

Output: monograph added copies, locations, and volumes

Workstats | Procedures | Tech Services | MSU Libraries


Input: [CODE] suppprnt [TYPE]

Output: print supplementary material

Workstats | Procedures | Tech Services | MSU Libraries


Input: [CODE] skymatch [TYPE]

Output: SkyMatch copy cataloging

Workstats | Procedures | Tech Services | MSU Libraries


Input: [CODE] skyprobs [TYPE]

Output: SkyMatch problem cataloging

Workstats | Procedures | Tech Services | MSU Libraries


Input: [Name] closed [Version] Implemented in JavaScript 1.1 [Description]

Output: Determine whether a window is closed or not.


Input: [Name] defaultStatus [Version] Implemented in JavaScript 1.0 [Description]

Output: Retrieves the default message displayed in the window’s status bar at the bottom.


Input: [Name] document [Version] Implemented in JavaScript 1.0 [Description]

Output: Contains information about the current document.


Input: [Name] innerHeight [Version] Implemented in JavaScript 1.2 [Description]

Output: Specifies the vertical dimension(height of the window), in pixels.


Input: [Name] innerWidth [Version] Implemented in JavaScript 1.2 [Description]

Output: Specifies the horizontal dimension(width of the document)), in pixels.


Input: [Name] location [Version] Implemented in JavaScript 1.0 [Description]

Output: Specify the information of the current URL.


Input: [Name] locationbar [Version] Implemented in JavaScript 1.2 [Description]

Output: Test whether the location bar is visible is or not.


Input: [Name] menubar [Version] Implemented in JavaScript 1.2 [Description]

Output: Refers the browser window's menu bar.


Input: [Name] name [Version] Implemented in JavaScript 1.0 [Description]

Output: Get the unique name of a specified window.


Input: [Name] opener [Version] Implemented in JavaScript 1.1 [Description]

Output: Specifies the window of the calling document.


Input: [Name] outerHeight [Version] Implemented in JavaScript 1.2 [Description]

Output: Specifies the vertical dimension, in pixels, of the window's outside boundary.


Input: [Name] outerWidth [Version] Implemented in JavaScript 1.2 [Description]

Output: Specifies the horizontal dimension of the window’s outside boundary.


Input: [Name] pageXOffset [Version] Implemented in JavaScript 1.2 [Description]

Output: Refers the current x-position of a page in a window.


Input: [Name] pageYOffset [Version] Implemented in JavaScript 1.2 [Description]

Output: Refers the current y-position of a page in a window.


Input: [Name] personalbar [Version] Implemented in JavaScript 1.2 [Description]

Output: Refers the browser window's personal bar.


Input: [Name] screenX [Version] Implemented in JavaScript 1.2 [Description]

Output: Specify the x coordinate of the left edge of the window.


Input: [Name] screenY [Version] Implemented in JavaScript 1.2 [Description]

Output: Refers the y-coordinate of the upper edge of a window.


Input: [Name] scrollbars [Version] Implemented in JavaScript 1.2 [Description]

Output: Refers the scroll bars of the browser window..


Input: [Name] status [Version] Implemented in JavaScript 1.0 [Description]

Output: Specifies a string displayed in the browser status bar at the bottom of the window.


Input: [Name] statusbar [Version] Implemented in JavaScript 1.2 [Description]

Output: Refers the status bar of the browser window.


Input: [Name] toolbar [Version] Implemented in JavaScript 1.2 [Description]

Output: Refers the toolbar of the browser window.


Input: [Description] Current logged in user's name. [Variable]

Output: USER


Input: [Description] Colon-separated list of directories to search for binaries. [Variable]

Output: PATH


Input: [Description] Network name of the Xorg display to connect to, if available. [Variable]

Output: DISPLAY


Input: [Description] The current shell. [Variable]

Output: SHELL


Input: [Description] The name of the user's type of terminal. Used to determine the capabilities of the terminal. [Variable]

Output: TERM


Input: [Description] Database entry of the terminal escape codes to perform various terminal functions. [Variable]

Output: TERMCAP


Input: [Description] Type of operating system. [Variable]

Output: OSTYPE


Input: [Description] The system's CPU architecture. [Variable]

Output: MACHTYPE


Input: [Description] The user's preferred text editor. [Variable]

Output: EDITOR


Input: [Description] The user's preferred utility for viewing text one page at a time. [Variable]

Output: PAGER


Input: [Description] Colon-separated list of directories to search for manual pages. [Variable]

Output: MANPATH


Input: [Attribute] AffectViewingBox [Default Value] TRUE [Purpose]

Output: influence of objects on the ViewingBox of a scene


Input: [Attribute] AntiAliased [Default Value] TRUE [Purpose]

Output: antialiased lines and points?


Input: [Attribute] ArrowLength [Default Value] Proportional [Purpose]

Output: scaling of arrows in a vector field


Input: [Attribute] Color [Default Value] RGB::Blue [Purpose]

Output: the main color


Input: [Attribute] Frames [Default Value] 50 [Purpose]

Output: the number of frames in an animation


Input: [Attribute] Legend [Purpose]

Output: makes a legend entry


Input: [Attribute] LegendText [Purpose]

Output: short explanatory text for legend


Input: [Attribute] LegendEntry [Default Value] FALSE [Purpose]

Output: add this object to the legend?


Input: [Attribute] LineColor [Default Value] RGB::Blue [Purpose]

Output: color of lines


Input: [Attribute] LineWidth [Default Value] 0.35 [Purpose]

Output: width of lines


Input: [Attribute] LineColor2 [Default Value] RGB::DeepPink [Purpose]

Output: color of lines


Input: [Attribute] LineColorType [Default Value] Flat [Purpose]

Output: line coloring types


Input: [Attribute] LineColorFunction [Purpose]

Output: functional line coloring


Input: [Attribute] LineColorDirection [Default Value] [0, 1] [Purpose]

Output: the direction of color transitions on lines


Input: [Attribute] LineColorDirectionX [Default Value] 0 [Purpose]

Output: x-component of the direction of color transitions on lines


Input: [Attribute] LineColorDirectionY [Default Value] 1 [Purpose]

Output: y-component of the direction of color transitions on lines


Input: [Attribute] Mesh [Default Value] [11, 11] [Purpose]

Output: number of sample points


Input: [Attribute] Name [Purpose]

Output: the name of a plot object (for browser and legend)


Input: [Attribute] ParameterEnd [Purpose]

Output: end value of the animation parameter


Input: [Attribute] ParameterName [Purpose]

Output: name of the animation parameter


Input: [Attribute] ParameterBegin [Purpose]

Output: initial value of the animation parameter


Input: [Attribute] ParameterRange [Purpose]

Output: range of the animation parameter


Input: [Attribute] TimeEnd [Default Value] 10.0 [Purpose]

Output: end time of the animation


Input: [Attribute] TimeBegin [Default Value] 0.0 [Purpose]

Output: start time of the animation


Input: [Attribute] TimeRange [Default Value] 0.0 .. 10.0 [Purpose]

Output: the real time span of an animation


Input: [Attribute] TipAngle [Default Value] 0.6283185307 [Purpose]

Output: opening angle of arrow heads


Input: [Attribute] TipStyle [Default Value] Open [Purpose]

Output: presentation style of arrow heads


Input: [Attribute] TipLength [Default Value] 1.5 [Purpose]

Output: length of arrow heads


Input: [Attribute] Title [Purpose]

Output: object title


Input: [Attribute] TitleFont [Default Value] [" sans-serif ", 11] [Purpose]

Output: font of object titles


Input: [Attribute] TitlePosition [Purpose]

Output: position of object titles


Input: [Attribute] TitleAlignment [Default Value] Center [Purpose]

Output: horizontal alignment of titles w.r.t. their coordinates


Input: [Attribute] TitlePositionX [Purpose]

Output: position of object titles, x component


Input: [Attribute] TitlePositionY [Purpose]

Output: position of object titles, y component


Input: [Attribute] Visible [Default Value] TRUE [Purpose]

Output: visibility


Input: [Attribute] VisibleAfter [Purpose]

Output: object visible after this time value


Input: [Attribute] VisibleBefore [Purpose]

Output: object visible until this time value


Input: [Attribute] VisibleFromTo [Purpose]

Output: object visible during this time range


Input: [Attribute] VisibleAfterEnd [Default Value] TRUE [Purpose]

Output: object visible after its animation time ended?


Input: [Attribute] VisibleBeforeBegin [Default Value] TRUE [Purpose]

Output: object visible before its animation time starts?


Input: [Attribute] XFunction [Purpose]

Output: function for x values


Input: [Attribute] XMax [Purpose]

Output: final value of parameter "x"


Input: [Attribute] XMesh [Default Value] 11 [Purpose]

Output: number of sample points for parameter "x"


Input: [Attribute] XMin [Purpose]

Output: initial value of parameter "x"


Input: [Attribute] XName [Purpose]

Output: name of parameter "x"


Input: [Attribute] XRange [Purpose]

Output: range of parameter "x"


Input: [Attribute] YFunction [Purpose]

Output: function for y values


Input: [Attribute] YMax [Purpose]

Output: final value of parameter "y"


Input: [Attribute] YMesh [Default Value] 11 [Purpose]

Output: number of sample points for parameter "y"


Input: [Attribute] YMin [Purpose]

Output: initial value of parameter "y"


Input: [Attribute] YName [Purpose]

Output: name of parameter "y"


Input: [Attribute] YRange [Purpose]

Output: range of parameter "y"


Input: [Name] chart.artists.get [Method]

Output: chartArtists


Input: [Name] chart.tracks.get [Method]

Output: chartTracks


Input: [Name] track.search [Method]

Output: trackSearch


Input: [Name] track.get [Method]

Output: track


Input: [Name] track.subtitle.get [Method]

Output: trackSubtitle


Input: [Name] track.lyrics.get [Method]

Output: trackLyrics


Input: [Name] track.snippet.get [Method]

Output: trackSnippet


Input: [Name] track.lyrics.post [Method]

Output: trackLyricsAdd


Input: [Name] track.lyrics.feedback.post [Method]

Output: trackLyricsFeedback


Input: [Name] matcher.lyrics.get [Method]

Output: matcherLyrics


Input: [Name] matcher.track.get [Method]

Output: matcherTrack


Input: [Name] matcher.subtitle.get [Method]

Output: matcherSubtitle


Input: [Name] artist.get [Method]

Output: artist


Input: [Name] artist.search.get [Method]

Output: artistSearch


Input: [Name] artist.albums.get [Method]

Output: artistAlbums


Input: [Name] artist.related.get [Method]

Output: artistRelated


Input: [Name] album.get [Method]

Output: album


Input: [Name] album.tracks.get [Method]

Output: albumTracks


Input: [The instruction] Delete character [The mark in the copy]

Output: through the character


Input: [The instruction] Delete text [The mark in the copy]

Output: through the text


Input: [The instruction] Delete character and close space [The mark in the copy]

Output: through the character


Input: [The instruction] Delete text and close space [The mark in the copy]

Output: through the text


Input: [The instruction] Character to replace marked character [The mark in the margin] The new character [The mark in the copy]

Output: through the character


Input: [The instruction] Text to replace marked text [The mark in the margin] The new text [The mark in the copy]

Output: through the text


Input: [Element] authorizationEntry [Class] org.apache.activemq.security.AuthorizationEntry [Description]

Output: Represents an entry in a {@link DefaultAuthorizationMap} for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] authorizationMap [Class] org.apache.activemq.security.DefaultAuthorizationMap [Description]

Output: Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] authorizationPlugin [Class] org.apache.activemq.security.AuthorizationPlugin [Description]

Output: An authorization plugin where each operation on a destination is checked against an authorizationMap

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] axionJDBCAdapter [Class] org.apache.activemq.store.jdbc.adapter.AxionJDBCAdapter [Description]

Output: Axion specific Adapter. Axion does not seem to support ALTER statements or sub-selects. This means: - We cannot auto upgrade the schema was we roll out new versions of ActiveMQ - We cannot delete durable sub messages that have be acknowledged by all consumers.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] blobJDBCAdapter [Class] org.apache.activemq.store.jdbc.adapter.BlobJDBCAdapter [Description]

Output: This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are:

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] broker [Class] org.apache.activemq.xbean.XBeanBrokerService [Description]

Output: An ActiveMQ Message Broker. It consists of a number of transport connectors, network connectors and a bunch of properties which can be used to configure the broker as its lazily created.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] bytesJDBCAdapter [Class] org.apache.activemq.store.jdbc.adapter.BytesJDBCAdapter [Description]

Output: This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter are:

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] commandAgent [Class] org.apache.activemq.broker.util.CommandAgent [Description]

Output: An agent which listens to commands on a JMS destination

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] compositeDemandForwardingBridge [Class] org.apache.activemq.network.CompositeDemandForwardingBridge [Description]

Output: A demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokers

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] compositeQueue [Class] org.apache.activemq.broker.region.virtual.CompositeQueue [Description]

Output: Represents a virtual queue which forwards to a number of other destinations.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] compositeTopic [Class] org.apache.activemq.broker.region.virtual.CompositeTopic [Description]

Output: Represents a virtual topic which forwards to a number of other destinations.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] connectionDotFilePlugin [Class] org.apache.activemq.broker.view.ConnectionDotFilePlugin [Description]

Output: A DOT file creator plugin which creates a DOT file showing the current connections

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] connectionFactory [Class] org.apache.activemq.spring.ActiveMQConnectionFactory [Description]

Output: A Spring enhanced connection factory which will automatically use the Spring bean name as the clientIDPrefix property so that connections created have client IDs related to your Spring.xml file for easier comprehension from JMX.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] constantPendingMessageLimitStrategy [Class] org.apache.activemq.broker.region.policy.ConstantPendingMessageLimitStrategy [Description]

Output: This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] defaultJDBCAdapter [Class] org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter [Description]

Output: Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. The databases/JDBC drivers that use this adapter are:

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] demandForwardingBridge [Class] org.apache.activemq.network.DemandForwardingBridge [Description]

Output: Forwards messages from the local broker to the remote broker based on demand.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] destinationDotFilePlugin [Class] org.apache.activemq.broker.view.DestinationDotFilePlugin [Description]

Output: A DOT file creator plugin which creates a DOT file showing the current topic & queue hierarchies.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] destinationEntry [Class] org.apache.activemq.filter.DefaultDestinationMapEntry [Description]

Output: A default entry in a DestinationMap which holds a single value.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] fileDurableSubscriberCursor [Class] org.apache.activemq.broker.region.policy.FilePendingDurableSubscriberMessageStoragePolicy [Description]

Output: Pending messages for durable subscribers

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] fixedCountSubscriptionRecoveryPolicy [Class] org.apache.activemq.broker.region.policy.FixedCountSubscriptionRecoveryPolicy [Description]

Output: This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed count of last messages.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] fixedSizedSubscriptionRecoveryPolicy [Class] org.apache.activemq.broker.region.policy.FixedSizedSubscriptionRecoveryPolicy [Description]

Output: This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed amount of memory available in RAM for message history which is evicted in time order.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] forwardingBridge [Class] org.apache.activemq.network.ForwardingBridge [Description]

Output: Forwards all messages from the local broker to the remote broker.

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] imageBasedJDBCAdaptor [Class] org.apache.activemq.store.jdbc.adapter.ImageBasedJDBCAdaptor [Description]

Output: Provides JDBCAdapter since that uses IMAGE datatype to hold binary data. The databases/JDBC drivers that use this adapter are: Sybase MS SQL

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] inboundQueueBridge [Class] org.apache.activemq.network.jms.InboundQueueBridge [Description]

Output: Create an Inbound Queue Bridge

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] inboundTopicBridge [Class] org.apache.activemq.network.jms.InboundTopicBridge [Description]

Output: Create an Inbound Topic Bridge

Schema for namespace: http://activemq.org/config/1.0


Input: [Element] individualDeadLetterStrategy [Class] org.apache.activemq.broker.region.policy.IndividualDeadLetterStrategy [Description]

Output: A {@link DeadLetterStrategy} where each destination has its own individual DLQ using the subject naming hierarchy.

Schema for namespace: http://activemq.org/config/1.0