cold dead raw fish (CDRF)

Handy Hex codes for HTML and URL character encoding

Character encoding and decoding numeric entities

HTML  URL   Description
----  ---   ----------------------
  %20=  space
! %21=! exclamation point bang
" %22=" quote aka double quote
# %23=# pound sign hash sign
% %25=% percent
& %26=& ampersand
' %27=' apostrophe aka single quote
( %28=( left parenthesis open paren
) %29=) right parenthesis close paran
* %2A=* asterisk star
+ %2B=+ plus
- %2D=- minus hyphen
. %2E=. period
/ %2F=/ forward slash (backslash = %5C)
0-9 %30-%39 = digits 0 - 9 zero through nine
: %3A=: colon,,, &#59; %3B=; semicolon
&#60; %3C=< less than,,, &#62; %3E=> greater than
&#61; %3D== equals
&#63; %3F=? question mark
&#64; %40=@ at sign
&#65;-&#90; %41-%5A = upper case letters A - Z
&#91;, &#93; %5B=[, %5D=] square brackets
&#92; %5C=\ backslash (forward slash = %2F)
&#94; %5E=^ carrot,,,,, %5F=_ underscore
&#97;-&#122; %61-%7A = lower case letters a - z
&#123; %7B={, &#125; %7D=} curley braces curly brackets
&#124; %7C=| vertical bar
&#126; %7E=~ tilde tidle

VERY GOOD Java XSLT article, Xalan, Saxon, Jaxp, JDOM, CSV to SAX, etc

This is long and about 7 years old, but a great article / sample chapter.  It has lots of nuts and bolts.

It starts here, part 1 of 9:

http://www.onjava.com/pub/a/onjava/excerpt/java_xslt_ch5/index.html

Other parts of note:

Part 2 has "hello world" for XSLT with Xalan and Saxon

Part 3 does the same thing with JAXP which allows you to switch XSLT processors between Xalan and Saxon by just using Java properties.

Part 5 talks about files vs. URLs / URIs and how to convert back and forth (usefull even if you're not doing XSLT, streams, readers, etc.)

Parts 5, 6, 7 and 8 talk about turning CSV data into XML for processing by writing a custom SAX parser that turns CSV record and field breaks into SAX start and end token events, and then sends it to DOM, XSLT, etc.  Nice to see a full example of this, although I don't think it will handle CSV generated from Excel when it has nested linebreaks in the cell, but that could be added.

And for the finale, part 9 gives THREE WAYS to interface in-memory JDOM structures with JAXP for XSLT transforms, wow!

Lots of useful "how to" info, though may be a bit out of date.

Summary of IBM article on SOAP / WSDL / XML Encoding / Schema styles

Russell Butek has an excellent article on the IBM web site about the various options for declaring SOAP services with WSDL.  Though he goes through many of the combinations, I wanted a much shorter cheat sheet table.

There are 3 main factors, which give a total of 8 possible combinations (though in reality some are not valid).

1. RPC vs. Document
2. Encoded vs. Literal
3. Unwrapped vs. Wrapped

This is the summary table I came up with (last row is the commonly used combination):

State	Combo			Used	Note
0:	RPC	Encoded	Unwrapped:	Seldom	Used with special data / graphs that need true references, and where a reference to an object can appear more than once.
1:	RPC	Encoded	Wrapped:	Never	Wrapped implies Literal
2:	RPC	Literal	Unwrapped:	Seldom	In the very rare case: Used if you have overloaded methods AND different methods with same args.  Example: Have A(i), A(f,f) and B(f,f); two methods called A, and two methods with args (f,f).  Maybe bad idea to overload anyway.
3:	RPC	Literal	Wrapped:	Never	Although Wrapped implies Literal, in practice, Wrapped only used with Doc / Literal (wasteful w RPC / Literal)
4:	Document	Encoded	Unwrapped:	Never	Nobody follows this style. It is not WS-I compliant.
5:	Document	Encoded	Wrapped:	Never	Wrapped implies Literal
6:	Document	Literal	Unwrapped:	Seldom	Used if you have overloaded methods (two methods with same name but different args).  Maybe bad idea to overload anyway.
7:	Document	Literal	Wrapped:	Most Common	Loved by Microsoft and WS-I (disambiguation committee).  Also gives a soap:body with one node, which also gives the name of the method.  The tradeoff is a more complex wsdl

A really helpful article.  I found the link to it from Jive's Clearspace Web Services Dev Guide.

Intel patented XML based GUI specification / generation?

Intel is listed as having patent # 6941521, filed 3/29/02, granted 9/6/05.
Method for dynamically generating a user interface from XML-based documents

Basically, describe a UI in XML, and have it "rendered" as an actual GUI, perhaps in SWING or AWT, .net, etc.  And I had thought that you'd also need to make references to event handler routines, perhaps in some other class file.

I'm not a lawyer, and I don't know the timeline of other such efforts, so no slight at Intel intended, but I had thought this was a well established idea prior to '02 ?

For example, isn't XUL mostly that?  In my notes I had:

• XUL starting page and XUL Planet
•  Luxor XUL
• CookSwing
• JFCML JFC / Swing / XML Markup language
• SwiXAT here and here
•  SwiXml
•  Jelly Swing, XML based UI builder (defunct)

Comments welcome, maybe there's some detail of it that's different, or maybe in '02 it was really new.