- From: T.V Raman <raman@google.com>
- Date: Wed, 28 Mar 2007 13:46:15 -0700
- To: jjb@ibiblio.org
- Cc: public-html@w3.org
+1 on extensibility --- forcing everything in as non-optional leads to bloatware. Additionally, there needs to be some architectural framework for language extensibility that is symmetrically mirrored on the UA side i.e. as you deploy a language extension, there needs to be a reliable mechanism for the UA to discover what plugin or UA extension would handle the newly introduced language extension. John Joseph Bachir writes: > > > On Tue, 27 Mar 2007, Maciej Stachowiak wrote: > > > http://esw.w3.org/topic/HTML/ProposedDesignPrinciples > > > > I'd appreciate feedback on these. Are any important principles missing? > > Are any of these wrong? Do they need refinement? > > How about "optional extensibility is more important than new features". > > Instead of introducing new features, introduce a system by which users may > add their own features. > > Yes, I dream of syntactic macros in HTML. > > But my fantasies aside, I think some note about the value of extensibility > should be included. > > -- > John Bachir > http://lyceum.ibiblio.org/ > http://blog.johnjosephbachir.org/ > aim/yim/msn/jabber.org/gtalk: johnjosephbachir > 713-494-2704 > irc://irc.freenode.net/lyceum -- Best Regards, --raman Title: Research Scientist Email: raman@google.com WWW: http://emacspeak.sf.net/raman/ Google: tv+raman GTalk: raman@google.com, tv.raman.tv@gmail.com PGP: http://emacspeak.sf.net/raman/raman-almaden.asc
Received on Wednesday, 28 March 2007 20:46:28 UTC