Re: XSP Spec Revisited

[Robin Green <gr...@hotmail.com>]

Thanks for the summary Kip.

Kip Hampton <kh...@totalcinema.com> wrote:
>xsp:element
>   reason: generate an element
>   context: any except for /page/structure AND /page/logic/content/
>   attributes: name?
>   child elements: (xsp:name?, xsp:attribute*)
>   results: A dynamically created XML element. The elements name may be
>defined either through the "name" attribute or a nested xsp:name
>element.
>   Note: Discussion is still open as to whether or not an
>xsp:namespace-uri child element is needed and/or desirable.

Well, doesn't SAX2 require a namespace URI?

>xsp:pi
>   Removed in favor of xsp:processing_instruction
>
>xsp:processing_instruction

Shouldn't that be a - instead of a _ to match XSLT?

>   reason: generate a processing instruction
>   context: anywhere?
>   results: A processing_instruction event.
>   Note:
>   Ricardo writes: "Target and data are specified in the usual way: as
>either attributes to the XSP tag when their value is known at generation
>time or as nested elements when their value is to be computed at request
>time."
>   Does this mean we have to add xsp:data and xsp:target elements as
>well? And, assuming we do, is xsp:data a single string or a list of
>xsp:attributes?
>
>xsp:comment
>   reason: generate a comment
>   attributes: none
>   child elements: none.
>   context: anywhere
>   results: A comment event.
>
>xsp:text
>    Removed. (???)

Er, what was it anyway?


_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Re: XSP Spec Revisited

[Donald Ball <ba...@webslingerZ.com>]

On Fri, 1 Dec 2000, Robin Green wrote:

> Thanks for the summary Kip.

seriously.

> Kip Hampton <kh...@totalcinema.com> wrote:
> >xsp:element
> >   reason: generate an element
> >   context: any except for /page/structure AND /page/logic/content/
> >   attributes: name?
> >   child elements: (xsp:name?, xsp:attribute*)
> >   results: A dynamically created XML element. The elements name may be
> >defined either through the "name" attribute or a nested xsp:name
> >element.
> >   Note: Discussion is still open as to whether or not an
> >xsp:namespace-uri child element is needed and/or desirable.
> 
> Well, doesn't SAX2 require a namespace URI?

only if the namespace prefix isn't already mapped, afaik...

- donald