It's Its, its' ... Apostrophic!

TalkBack 1 of 16:

Next »

• Thread View
• Flat View

Namespaces

This is the tie-in for what you are talking about. Namespace is an essential and ignored FINAL piece of the programming/systems integration puzzle. Things like Grids and Autonomics REQUIRE consistent, global Namespaces - but it isn't happening.

A Namespace is like a very simple language (it follows linguistic rules).
Syntax - A Namespace is an abstract container (usually a tree structure) which is, or could be filled with ?names? (words that occupy nodes in the tree) that represent real-world things.
Semantics - Names in a Namespace CANNOT have more than one meaning.
Pragmatics - A name?s meaning should be used only once.
A Namespace is always in an optimal state ? The linguistic rules keep ambiguous or erroneous ?names? from becoming a part of the Namespace

In other words - "What's in a name?"

Just getting people to understand Namespace, much less actually implementing it takes a holy crusade and years of being the messenger.

Posted by: Roger Ramjet   Posted on: 01/06/06 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Three Steps You Need to Know to Stop Data Loss Varonis Sensitive data exposed to misuse or loss... it is the stuff of nightmares ... Download Now
• Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now
• Virtualization: Architectural Considerations And Other Evaluation Criteria VMware Of the many approaches to x86 systems virtualization available in the ... Download Now