 |
 |
 |
Right. They don't know about namespaces and don't
care this season. Over time as IP and conformance
to cited standards becomes more important, they will.
So the namespace is just the implementation means.
The coupler is the features as expressed in the
extensions (as denoted by the namespace), and that
is life as normal among competing providers of
specification-based products. As I thought,
technology push vs customer pull. The fun
is that for some technologies, as you note,
the technologists are the customers. Note that
the namespacesAreEvil thread is stable; no matter
how perturbed, it returns to the same predictable
points on the topic map.
It would be fun to have a technology that extracted
such topic points from perma-threads, mapped them,
then visualized them such that one could see if
they are stable, non-linear chaotic, and what if
any strange attractors emerge, then what the nature
of these are.
len
From: Dare Obasanjo [mailto:dareo@m...]
If your customers are XML geeks I'd expect not. If your customers are
reqular people who just want software to work then they are just an
implementation detail.
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |