[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
Re: Re: [Project] XML, Byte Encoded XML, How does it talk ?
- To: ukha_d@xxxxxxx
- Subject: Re: Re: [Project] XML, Byte Encoded XML, How does it
talk ?
- From: Stuart Grimshaw <stuart@xxxxxxx>
- Date: Thu, 24 May 2001 14:47:19 +0100
- Delivered-to: rich@xxxxxxx
- Delivered-to: mailing list ukha_d@xxxxxxx
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- References: <9eir43+n63a@xxxxxxx>
- Reply-to: ukha_d@xxxxxxx
On Thursday 24 May 2001 12:25 pm, you wrote:
> Valid concern!
>
> There's nothing in the translation that I have suggested which
> prevents you from refining, extending or redefining the messages -
> since it is simply a remapping of the XML, not a replacement.
That's true. There's nothing in most protocols to stop you redefining it.
All I was really concerened about was duplicating work for ourselves.
I think the beXML is a good idea, and looks good to be the answer to our
problem, but at the moment we don't know fully what that problem is :-)
I don't want to have to go through all this again when we design the units
and find that there's something the protocol can't handle.
--
,,,
(o o)
===========================oOO==(_)==OOo==============================
Stuart Grimshaw www.schoolsnet.com sg@xxxxxxx
Special Projects Developer t: 07976 625221
Schoolsnet LTD .oooO Oooo. f: 0870 7060260
===========================( )==( )===============================
\ ( ) /
\_) (_/
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Home |
Main Index |
Thread Index
|