> I hear REST advocates discussing the pervasive use of
> RDF topic maps, but in my world they never really were
> considered, and aren't likely to be.
RDF and Topic Maps just offer two standardized data models. And while
I've personally used RDF in projects with great success, it's not for
everything. The take-home point from a REST POV though, is simply to
standardize on a data model; make it part of the information
communicated by the messages (usually by associating the data model
with the media type, ala application/rdf+xml).
XML Schema problems are, IMO, a direct result of its inability to
provide for the use of a data model; not even necessarily to
standardize on one, but instead to focus so much on *syntax* that
developers & authors miss the forest for the trees. And FWIW, RelaxNG
or other syntax-focused languages aren't much better from this POV.
> XML Schemas seem
> to be the approach du jour, though their versioning
> and extensibility techniques are awfully complicated.
> I'm curious how and when we as an industry will
> address that.
They provide nothing very useful in terms of versioning. It's
basically roll-your-own. Standardizing on a data model with built-in
versioning & extensibility avoids all that, and is often worth it even
the data model isn't a great fit for your application.
I'd even go out on a limb and say that if you're using schemas,
there's a 97% chance that you'll have extensibility and integration
problems down the road.
Mark.
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
