W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > May 2008

Re: PSVI issues

From: Innovimax SARL <innovimax@gmail.com>
Date: Thu, 8 May 2008 15:49:26 +0200
Message-ID: <546c6c1c0805080649m1a627fc4ma810861a0c88b3ef@mail.gmail.com>
To: "Henry S. Thompson" <ht@inf.ed.ac.uk>
Cc: public-xml-processing-model-wg@w3.org

Thanks Henry,

That's the point I wanted to make

Since you said earlier that
[[
b) Implementations SHOULD preserve PSVI properties across steps
     insofar as that is consistent with step semantics.  It is
     implementation-defined what PSVI properties it supports overall,
     and what PSVI properties are lost by what steps.
]]

Then it is obvious for me that you should have
<p:choose>
   <p:when test="p:psvi-available('p:delete')">
    <p:delete match="element(*,my:doomedType)"/>
   </p:when>
   <p:otherwise>
   ...

Am I right ?

Mohamed
On Thu, May 8, 2008 at 3:44 PM, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>
> Mohamed writes:
>
>  > Can you give one or two use cases for psvi-available() ?
>
>  <p:group>
>   <p:validate-with-xml-schema assert-valid="true">
>   <p:input port="schemas">
>    <p:inline>
>     <xs:schema>
>      . . .
>      <xs:element name="doomed" abstract="true" type="my:doomedType"/>
>      . . .
>      <xs:element name="purple" substitutionGroup="my:doomed"/>
>      <xs:element name="mauve" substitutionGroup="my:doomed"/>
>      <xs:element name="burgundy" substitutionGroup="my:doomed"/>
>      . . .
>     </xs:schema>
>    </p:inline>
>   </p:input>
>   </p:validate-with-xml-schema>
>    <p:documentation>
>     <p>This is risky, because if the schema is changed to add elts to
>        or remove elts from the doomed subst. group,
>        this step will need to be updated . . .</p>
>    </p:documentation>
>    <p:delete match="my:purple|my:mauve|my:burgundy"/>
>   </p:otherwise>
>   </p:choose>
>  </p:group>
>
>  I.e., schema validate, and then use a type to do some work if it's
>  there, otherwise revert to an explicit list of elements.  As the
>  comment says, this will be robust wrt schema changes on the first
>  branch, but less so on the second. . .
>
>
>  ht
>  - --
>   Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
>                      Half-time member of W3C Team
>     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
>             Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
>                    URL: http://www.ltg.ed.ac.uk/~ht/
>  [mail really from me _always_ has this .sig -- mail without it is forged spam]
>  -----BEGIN PGP SIGNATURE-----
>  Version: GnuPG v1.2.6 (GNU/Linux)
>
>  iD8DBQFIIwOtkjnJixAXWBoRAlMyAJ9T6CNQa8WO3umZLkqUhqkS/mzLIACfTZyM
>  SmlwbH+pU2fdE3IYafbsNzE=
>  =uq7O
>  -----END PGP SIGNATURE-----
>



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Thursday, 8 May 2008 13:50:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 8 May 2008 13:50:09 GMT