Christoph Paeper <ch**************@nurfuerspam.de> wrote:
3) Adopt a development model that has impetus.
Such as?
Therein lies a challenge, the current model seems to rely on some
personnel time being granted from commercial companies or from academic
institutions. There is little incentive within such a structure to drive
forward the development process with the required vigor. Adopting a
commercial model has the potential of solving that, but that poses other
challenges like "where does the revenue come from?".
4) Adopt a single/central code base that all implementors must use with
version control that encourages users to keep updated.
Mandatory code is never good, reference implementations can be OTOH.
The current situation is that the implementation differences and
different bugs between the various browsers contributes significantly to
the frustration amongst authors, and the resulting disappointing
adaptation of the technology.
5) Put designers in charge of setting the goals.
Real designers are hard to find (not only in webdesign). The much
available "deezyners" OTOH would have gotten us pixel-perfect layout and
nothing else.
That's why half the development team should consist of technicians.
6) Put technicians in charge of implementation.
Good engineers are also rare. Let alone people who can write
specifications that are understandable *and* implementable
Designers should form the other half the development team, they will
complain when the technicians come up with the mumbo jumbo that can
currently be found in the css specs. Currently the specs require
significant technical skills to be understood properly, this is madness
since it is the designers who are supposed to use the language.
But a question that should precede the creation of a new style language
should be "is it realistic to expect designers to learn what may to some
extent be a technical language?".
If as I suspect the answer to that question is no, then it may be
necessary to incorporate the development of a shell application that
will write the code as an integral part of creating a good style and
layout language. How "good" a language is should be measured in no small
part by how it is adopted by the people who it is for. For a successful
adaptation to happen it needs attractive features and it must be easy to
use by the people that it is for.
That would suggest that a commercial company is best suited to develop
such a language, they can generate the required revenue from selling the
authoring software, and since designers are the customers there is
impetus to create the sort of features designers would like. Amateur
content creators could be catered for by a free "lite" version of such
software. To further facilitate adoption the language format should
continue to be plain text.
7) Ensure that the above two groups work constructively together.
If you get good design and technology people together, that shouldn't be a
problem, because both groups would know enough about the other field to be
reasonable in theirs.
Designers and technicians are two very distinct breads of animals, in my
experience they don't often understand or value one another.
that css has failed to achieve what it should have achieved, and that
it's features are poor. Poor as it is, it's the best system that we
currently have to our disposal.
The worst thing about CSS (and many other standards that don't require
certification) is incomplete and incorrect support in implementations.
Hence my argument for a single code base, this in itself has obvious
drawbacks, but the resulting uniform rendering and version control is
imo more important.
But I wouldn't be surprised if ultimately css fails and gets replaced by
a proprietary commercial product,
Images, PDF and Flash have their niches, but those are replacements for
the combination of CSS and HTML (or XML), not for CSS alone.
Therein lies a fundamental obstacle to the commercial development of a
style language. Commercial companies that don't have competition
typically don't give a monkey about open content formats, in fact most
would consider them as a threat to their revenue. Which is why
Macromedia is attempting to peddle Flash as the all in one replacement
for all those "difficult" web publishing languages.
--
Spartanicus