- From: Henry Lowe <hlowe@omg.org>
- Date: Wed, 03 Jan 2001 09:40:01 -0500
- To: <xml-dist-app@w3.org>
OK, I see where you are going. However, since this isn't about ensuring XP can support adjunct facilities (e.g., signatures), this would probably be a different requirement -- 305 seems to be about ensuring adjunct facilities can be supported. A minimalist (compliant) XP, such as you suggest, should be able to do more than one message, though -- it needs to be able to say "I can't do that" if you ask it to start the car. (Also, on the lighter side, why bother having a door at all if it's always open? Sorry, I couldn't resist that :-) Best regards, Henry ----------------------------------------------------------- At 05:06 PM 01/02/2001 -0800, Henrik Frystyk Nielsen wrote: >> Unless I misunderstand what you are suggesting, I believe >> this would get into subsetting (which probably doesn't help >> interoperability). I was looking for a set of criteria by >> which to judge whether XP meet the goals listed in the original >> DR305, e.g., if XP can't support signatures, it has to be fixed >> (same for reliable delivery, etc.). > >It is not subsetting at all but rather that it should possible to write a >compliant XP receiver or sender that can only receive or send one specific or >a few specific messages. As an example, it should be possible to write a >compliant XP sender in a garage door and have the only message that it can >ever send be "I am open". > >Henrik > >
Received on Wednesday, 3 January 2001 09:40:05 UTC