Re: [wsrp] Public review comment: Support for markup head attributes

[Subbu Allamaraju <subbu@bea.com>]

I agree that this is an open issue, but make take longer to formalize a 
solution.

Here are some examples to consider in this discussion.

<meta http-equiv=Refresh content="900;url=http://blah.com";></meta>

<style type="text/css">...</style>

<link rel="stylesheet" href="x.css" type="text/css" />

<script type="text/javascript>...</script>

<script type="text/javascript" language="JavaScript"
src="something.js"></script>

We need to consider URL/data rewriting as well.

Subbu

Stefan Hepper wrote:
> Currently portlets have no means in WSRP to set attributes that should 
> appear in the head section of the markup returned to the client, like 
> meta tags for search engines or the page title.
> 
> Proposal:
> Introduce a markupHeadAttributes field in response structures. The 
> consumer would be encouraged to forward these attributes in the head 
> section of the markup document to the client if they don't conflict with 
> other attributes set by the consumer (e.g. only one page title is allowed).
> 
> Stefan
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

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