Re: non-matched output port

/ Innovimax SARL <innovimax@gmail.com> was heard to say:
| So neither delete nor replace are restricted to elements !
| What are they restricted on ?
|
| Delete can match :
| * Element : OK
| * Attribute : OK
| * Namespace : ?
| * Comment : OK
| * Text : OK
| * PI : OK
| * node() : ? (because of Namespace)

I don't think delete should be able to delete namespace nodes.
I think they should just be silently ignored by the p:delete step.

| Replace can match and replace them by a document :
| * Element : OK
| * Attribute : NO
| * Namespace : NO
| * Comment : Why not ?
| * Text : Why not ?
| * PI : Why not ?
| * node() : NO (because of Namespace and attributes)

At the moment, I think it's only elements. It could be changed to
allow elements, comments, text nodes, and PIs.

I think p:replace should silently ignore namespace nodes. It should be
an error to attempt to replace an attribute. And I mean a dynamic
error. Attempting to replace //div/@class should only raise an error
if the document in question actually contains a div with a class
attribute; I don't want to have to do static analysis on the pattern.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Reason's last step is the recognition
http://nwalsh.com/            | that there are an infinite number of
                              | things which are beyond it.-- Pascal