[wsrp] RE: [wsia] [wsrp-interfaces] Draft spec v0.5

[Sasha Aickin <AlexanderA@plumtree.com>]

I have a question about getMarkup.  Do we expect the markup sent back from the method to be XML-encoded or not?  That is, let's say we want to return the markup "Hello, <strong>World</strong>".  Does the SOAP response look like: 

<markup xsi:type="xsd:string">Hello, &lt;strong&gt;World&lt;/strong&gt;</markup>

or like:

<markup xsi:type="markup">Hello, <strong>World</strong></markup>

As currently specified, only the former possibility is allowed, since markup is specified with type xsd:string.  I think this is great, because it will allow us to send non-XML conformant documents like HTML.  Further, if we do decide that markup will be sent as an XML-encoded string, then we could use XML elements to specify Consumer side URL rewriting, like so:

<markup xsi:type="xsd:string">Please click &lt;a href=&quot<wsia:rewriteURL type="Action" navigationState="somestate"/>&quot;&gt;here&lg;/a&gt;</markup>

If we don't decide to have Consumer URL writing use XML elements, though, I think there's another solution that might be more effective than the "wsia:QXqKYZJVUWj7G" token.  We could use Unicode characters from one of the "private use" areas of Unicode (U+E000-U+F8FF, U+F0000-U+FFFFD, or U+100000-U+10FFFD).  These characters are specifically designed for private use by applications, and you can easily put them into XML with character entities (e.g. &#xE123;).  Further, since ampersand has an escape character in XML, you can specify when you send portlet content whether you are sending the actual control character or text that should display as the control character (e.g. &amp;#xE123; vs. &#xE123;).

Cheers,
Sasha.

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Friday, August 30, 2002 10:19 AM
To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org
Subject: [wsia] [wsrp-interfaces] Draft spec v0.5



The doc file has now grown to 11MB ....

(See attached file: Draft Spec v0.5.ZIP)