From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0218_01C5C85E.7C6B8770
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

   You are building an xforms client?

   You now claim you are building support for each of text, XML =
(whatever this means), and unspecified standards from W3C or other
"open = standards organizations".  Did you mean to contradict
your earlier = statement?  Let me quote from your post =
news://news.barkto.com/433baaff$1{at}w3.nls.net

  We have a requirement that going forward most of our forms should be =
of=20
  the XHTML+XFORM variety (google on UK gov e-gif & xform).

Rich

  "Adam" <""4thwormcastfromthemolehill\"{at}the
field.near the bridge"> =
wrote in message news:4341721d$1{at}w3.nls.net...
  Rich wrote:
  > =20
  >=20
  >     "Adam"      > wrote in message
  >     news:4340f3ca{at}w3.nls.net...
  >=20
  >=20
  >     Ummmmmm we are trying to design for the long term.
  >     =20
  >=20
  > =20
  > That's good.  Too bad your mandate is not that but instead something =

  > specific that according to you does not exist.  Worse still, =
something=20
  > you aren't building.
  >

  Rich you are a complete tit. You have no idea what I'm doing & yes I'm =

  building. So nice of you to reveal your complete ignorance so fully.

  >=20
  >     Can you imagine MS even pretending to plan to have a tech which =
will be
  >     "current" 8-12 years from now?
  >     =20
  >=20
  > We have you pretending.=20

  Nope we have you projecting again. No idea why other than to mask MS's =

  complete abscence of any way of comprehending what is going on now in=20
  public IT as your old model is irretreivably broken.

  > "Current" is full of fads.

  Oh indeed which is why we are sticking to W3C stds & not crappy fake=20
  stds put out by single vendors.

  >  My suggestion to=20
  > you if you don't want to be in exactly the position that you claim =
to=20
  > fear is to not tie yourself to a specific format.
  >=20

  A) Text
  B) XML
  C) W3C or other open standards organization where such a standard is=20
  free of vendor claims.

  Get used to it & try to go there yourself or see more Massachusetts =
type=20
  decisions.


  It's going to happen anyway Rich now stop being such a tit.

  Adam
------=_NextPart_000_0218_01C5C85E.7C6B8770
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








   You are
building an xforms =

client?
 
   You now
claim you are =
building support=20
for each of text, XML (whatever this means), and unspecified =
standards from=20
W3C or other "open standards organizations".  Did you
mean to = contradict=20
your earlier statement?  Let me quote from your post news://news.barkto.com/433baaff$1{at}w3.nls.net">news://news.barkto.=
com/433baaff$1{at}w3.nls.net
 

  We have a requirement that going forward =
most of our=20
  forms should be of the XHTML+XFORM variety (google on UK gov e-gif =
&=20
  xform).
 
Rich
 

  "Adam" <""4thwormcastfromthemole=">mailto:"4thwormcastfromthemolehill\"{at}the'>"4thwormcastfromthemole=
hill\"{at}the=20
  field.near the bridge"> wrote in message news:4341721d$1{at}w3.nls.net...Rich=20
  wrote:>  >
>     "Adam"
=
<mmmmm_beer_mmmm_donuts{at}moesmailto:mmmmm_beer_mmmm_donuts{at}moes">mmmmm_beer_mmmm_donuts{at}moes
A>>    =20
  <mailto:mmmmm_beer_mmmm_donuts=">mailto:mmmmm_beer_mmmm_donuts{at}moes">mailto:mmmmm_beer_mmmm_donuts=
{at}moes>>=20
  wrote in message>     news:4340f3ca{at}w3.nls.net...>=
=20
  >
>     Ummmmmm we are
trying to =
design for=20
  the long
term.>     
> =
> =20
  > That's good.  Too bad your mandate is not that but =
instead=20
  something > specific that according to you does not =
exist.  Worse=20
  still, something > you aren't
building.>Rich you =
are a=20
  complete tit. You have no idea what I'm doing & yes I'm =
building. So=20
  nice of you to reveal your complete ignorance so
fully.>=20
  >     Can you
imagine MS even pretending to =
plan to=20
  have a tech which will
be>    
"current" =
8-12 years=20
  from
now?>     
> > We =
have you=20
  pretending. Nope we have you projecting again. No idea why =
other than=20
  to mask MS's complete abscence of any way of comprehending what is =
going=20
  on now in public IT as your old model is irretreivably =
broken.>=20
  "Current" is full of fads.Oh indeed which
is why we are =
sticking to=20
  W3C stds & not crappy fake stds put out by single=20
  vendors.>  My suggestion to
> you if you don't =
want to=20
  be in exactly the position that you claim to > fear is to not =
tie=20
  yourself to a specific format.> A)
TextB) XMLC) =
W3C or=20
  other open standards organization where such a standard is free of =
vendor=20
  claims.Get used to it & try to go there
yourself or see =
more=20
  Massachusetts type decisions.It's
going to happen =
anyway Rich=20
  now stop being such a
tit.Adam

------=_NextPart_000_0218_01C5C85E.7C6B8770--

--- BBBS/NT v4.01 Flag-5