On E2, a "node" is this entire page you are viewing. There are several different types of nodes - every single page you view on E2 is, in effect, a "node". Most nodes are like this one, with several writeups within it. If you are just viewing my writeup, without the others below, then you are on the single writeup display page and should click the link all of node, there are X more writeups in this node that you see just above this writeup. You can also adjust how you view E2 by going to your preferences link in your Epicenter nodelet on the right. We highly recommend you choose display type "full" because most people use it and all writeups are displayed.
This is an "E2node" and within an e2node any number of writeups by any number of users (one writeup max per user) can be added. A writeup is what you are reading right now, this is 'dem bones' writeup for the node "node". There are a number of writeups below mine that give different definitions for different contexts of the word "node". If there were a song called "node" its lyrics would most likely be below. If there were a play entitled "node" the play's author and basic plot would most likely be below.
Users will often refer to writeups as nodes or nodes as writeups. For instance, a user would say in the chatterbox "I'm working on a new node" or "Check out my node on reptiles". What the user really means is "Check out my writeup in reptiles". Nobody "owns" a node. It makes little difference if your writeup is first or fifth. After fifth you might want to consider not adding a writeup unless you've really got something new to say.
A nodeshell is a node with no writeups. A floating title.
Besides "E2nodes" there is a "document" node type. A 'document' node is one large page with a single "writeup". A document will not have a particular author assigned to it - only E2 staff can create a document. For examples of different documents check out
back to E2 Glossary
See also node analysis.
As an extra thought: Since any number of components can be connected to a node, it can used as a method for locating components. If one names each node, and then indicates, for each component, which terminals of the component connect to which nodes, one has an unambiguous mapping of a circuit; this is, for example, the approach that spice uses.
In regards to human physiology, lymph nodes are another term for the glands of the lymphatic system in the body. They are small organs shaped like beans which contain thousands of leukocytes embedded in the tissue. The bloodstream passes through these lymph nodes which filter out toxins from the body. These nodes also produce phagocytes which assist the body's immune system. During infection of a humanoid system, more phagocytes are produced from these nodes, causing them to swell, causing inflamation and sometimes painful discomfort. These can most noticably be detected by physicians in the armpit, on the neck, or near the groin. Sometimes malignancies caused by cancer can reach the lymphatic system, and travel through the body at a disasterous rate.
In these data structures the node serves as a temporary location that a pointer is pointing to for a program variable to traverse the data structure or access the data within it. A node usually contains a link or links to other nodes in the structure as well as some data.
There are two basic kinds of nodes. There is a parent node, which has links to other nodes and leaf nodes, which do not.
In E2 we try and avoid leaf nodes with hardlinks and softlinks.
This object represents a single node within the document tree. As such, it provides methods for dealing with the tree hierarchy, including handling child nodes. Be aware that not all objects that inherit from Node actually permit child nodes (e.g. Text nodes). Further, it provides "standard" attributes of nodeName, nodeValue and attributes which may or may not map to the specific object's attributes (e.g. Comment nodes do not have attributes). For details of a particular Node type, see the relevant write up:
The number against each entry above corresponds to its nodeType value. Values up to 200 are reserved.
As of DOM2, only Element nodes have attributes.
The NodeList returned is null if there are no child nodes.
Null if there are no child nodes.
Introduced in DOM Level 2. See namespaceURI.
Introduced in DOM Level 2. Null if there is no namespace specified. The value is the literal value used when the node was created, not resolved in any way. Under DOM2, only Element and Attribute nodes have namespaces and only then when created with the new methods.
The node following this one at the current level of the hierarchy. Null if this is the last node beneath its parent.
The value of nodeName is dependent upon the nodeType. Individual write ups will indicate the actual value.
See above for a list of current node types and their type numbers. The DOM implementation probably provides symbolic constants (e.g. "DOCUMENT_TYPE_NODE") for these values - use them.
The content of nodeValue is dependent upon the nodeType. Individual write ups will indicate what is returned.
The exceptions thrown are:
Modified in DOM Level 2. The document object that "owns" this node, i.e. that was used to create it. Note that document nodes and DocumentType nodes that are not in use have null ownerDocuments.
This node's "parent" within the hierarchy. Null if the node hasn't been added to or has been removed from the hierarchy. (Always null for Attribute, Document, DocumentFragment, Entity and Notation nodes.) When null, nextSibling and previousSibling are null.
The node preceeding this one at the current level of the hierarchy. Null if this is the first node beneath its parent.
Functionally equivalent to insertBefore(newChild, null).
Returns a copy of this node. The copy's parentNode is null. Child nodes copied are:
There are other, subtle effects of cloneNode:
Note that cloning an immutable subtree results in a mutable copy, but the children of an EntityReference clone are readonly. In addition, clones of unspecified Attr nodes are specified.
Introduced in DOM Level 2. In DOM2, returns false unless this is an Entity node that is parent to one or more Attribute nodes.
Returns false until this node is parent to one or more nodes.
If newChild is already a child of this node, it is removed. If refChild is not null, the insertion point is positioned before it. If null, then the insertion point is after the current last child node. newChild is then added at the insertion point.
If newChild is a DocumentFragment, all the contained nodes are added to this node's children.
Modified in DOM Level 2. Checks whether a feature (assumed to pass the hasFeature check on the DOMImplementation) is supported by this node. The parameters are the same as hasFeature.
Merges all logically adjacent Text nodes.
oldChild is removed from this node's children (and returned).
If newChild is already a child of this node, it is removed. oldChild is removed (and returned) and newChild is added in its place. If newChild is a DocumentFragment, all the contained nodes are added to this node's children.
Nodes (or, sometimes, "nodules") are calluses that form on the vocal cords in response to misuse. If you're lucky, they'll go away by themselves. If you're typical, you'll have to have surgery.
When I met my college girlfriend, she had just had node surgery, and was prohibited to speak. We met at the music library, where we worked as desk clerks, helping people find things and checking materials in and out. Because she couldn't speak for those first few weeks, we communicated by leaving notes for each other on the desk blotter.
In plant propagation, nodes are very important becuase they are the areas where opportunistic roots may form. When a cutting is taken, at least one node must be found in each cutting so the plant can form new roots. (usually at least 2 nodes is better as they are often reluctant to produce leaves and roots from the same node) In other techniques, such as layering, an entire node or series of nodes are buried in dirt or another medium, while the nodes are still connected to the parent plant as well. If things go well, these areas will form new roots, and may be detatched to form a new plant.
