Cart
[Home] [By Thread] [By Date] [Recent Entries]
Well, it's good to see XML-DEV ringing in the New Year with (ka-boom)
Yet Another Namespace Thread.... Plus ca change...
[sean mcgrath]
> As I have said before, perhaps it plays into
> the hands of those who know that the real "lock in" lies
> in the semantics which now, in the full glare of standards
> compliance, they can make proprietary.
This is interesting. It would explain two things about the W3C
Namespaces that I've always wondered about (correct me if I'm wrong,
namespace gurus)--
(1) Lack of synonyms -- there's no way to assert, for a single element
(whoops, almost wrote generic identifier) that it belongs to more than
one namespace.
(2) Colonized syntax -- if attribute syntax had been adopted,
information owners would have been able to attach/detach namespaces at
will through defaulting mechanisms, instead of crudding up their
instances with them.
Of course, these are two good ways to avoid lock-in, so perhaps in
retrospect it's not surprising that they weren't adopted.
S.
=====
<!-- "To imagine a language is to imagine a form of life."
- Ludwig Wittgenstein, Philosophical Investigations -->
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/
|
