Lists Home |
Date Index |
email@example.com (Danny Ayers) writes:
>I personally think using an uber-framework about syntax and
>business-specific models is the only way around this, and the RDF/OWL
>approach seems a very good candidate.
This won't be a surprise, but to me that's just moving deeper into the
It doesn't help that RDF/OWL are so flexible - in fact, for the vast
majority of cases, I think it hurts. It's difficult enough to tell
people they're now free to create their own XML vocabularies, even
though that's a relatively concrete process that can be explored through
instance documents. (If I start people out with existing documents and
have them add markup to them, I can get most people through this phase.
If I start with schemas, only a small self-selecting group of
programmers and librarians are listening after 30 seconds.)
Going out another level of abstraction loses a lot more people, and I've
never had faith in that particular level of abstraction anyway.
Graphs are cool. Uber-frameworks make me feel like I'm working in a
steel mill when I'm just trying to rivet something.