Lists Home |
Date Index |
"How I wish, How I wish you were here..."
Better late than never. If RNG is a dark horse:
1. How have you incorporated it into your workflow
2. Was that a reasonable thing for a production manager,
web author, etc. to do?
3. Are you pleased enough with it that you would support
a tool vendor that supported it over one that didn't?
4. Given alternatives, which do you use most and which
would you recommend to your successor were you to be promoted
to their manager? (IOW, you have to live with your choices.)
It doesn't matter as much who owns or creates the specification
as it does that we get undeniable value from it and that
we are willing to demand it from our tool vendors by
voting with our feet or our purchases.
From: email@example.com [mailto:firstname.lastname@example.org]
>1. More productive. Can one compose faster,
> is it easier to learn,
>does is do what I need to do in the framework?
is == it ? What do you need to do?
RNG is as powerful as Schema for strongly typed data structures expressed in
XML, more convenient than DTD for document-oriented XML (!), and *much* more
useful for document-oriented than XSD. I suspect that initial uptake is
likely to be in the document crowd, but the ease of learning is likely to be
attractive to the data crowd as well.
(I spend large portions of my day working with schemata of various types and
flavors, but all of the above is merely MHO).
>2. More sustainable. Will a better layered framework using RNG
>result in information that is more efficient to maintain, reuse, etc.?
Certainly better separation of data typing/primitives from complex
structures. Deprecation of defaulting (*such* a good idea ...) means less
ambiguity over the value of such things.
Very flexible system for specifying complex types, and for permitting
flexibility in the instance.
I think of RNG as the dark horse. That it came to the party so late is
regrettable, but almost inevitable. It seems to have taken some of the best
ideas from a couple of very brilliant XML designers/implementors, plus a
supporting cast, and generated a schema language that is aesthetically
pleasing, elegant, easy to use, and easy to implement.