Datanode

A data node may be metadata about another.

This property basically represents the proximity of some data node to another, without assuming any other kind of relation at domain or structural level.

A data node that should be used together with another. We intend consistency in a general sense: two data nodes are consistent because they agree (ie, they do not disagree...).

It can be the case that a single data node is verified to be correct. It can then be marked to be consistent with itself.

Two nodes have different potential. Two data nodes using different vocabularies or two copies of the same data in different places.

We relate with this property a data node to a collection of attributes used in it. We distinguish attributes from relations because the first does qualify its range but only its domain (saying that a person is 1.82m tall does not change our knowledge about 1.82m).

Indicates a data node which includes information that is now old or outdated. We don't indicate it to be also a part, this is to discuss.

We choose the term descriptor to indicate generically the element used to bind/map/qualify a value with respect to its entity. Practically, this term maps to

• "Field" in Object Oriented Programming;
• "Predicate" in First Order Logic
• Column identifier (Attribute) in Relation Database terminology
• rdf:Property in the Resource Description Framework

Are we sure a stand-in is always a derivation?

A data node may be related to another by improving its currency.

The range of this property is a data node which enumerates a set of terms that are all used by the subject data node to name structural elements, like attribute names or types.

When a data node :hasVocabulary another, we expect the latter to be the collection of terms used by the data node to name its properties and types.
How to know if there is some term that is not part of that vocabulary? In other words, is it relevant to know whether a vocabulary is complete or not wrt some data?

A data node that should not be used together with another. We intend consistency in a general sense: two data nodes are inconsistent because they do not agree.

It can be the case that a single data node is corrupted to some respect. It can then be marked to be inconsistent with itself.

This relation indicates that a data node is the origin of another, in the sense that the second have been produced using the first as main information source.

Is this property transitive?

This is used to relate a data node to its metadata.

Two data nodes have similar potential. This may refer to any kind of feature, being it structural (they share schemas), physical (they are both in XML) or related to the domain (they both talk about Music Artists) - just to make few examples.

This property indicates that data includes a mention to something which is included in another data node.
Talking about RDF datasets, this refer to the mention of a URI belonging to another dataset. For example, a dataset about employees could mention a Geonames location.

It looks like there could be a more generic property here, which refer to the fact of sharing some signatures (identifiers), without assuming an order or direction of the reference. Two data nodes may simply use the same identifier independently from the intention of making a reference to anything else (then the identifier itself). Does this make sense?

This is the Top Property of Datanode.

The second is intended to be a self contained model that is (partly) used in the data node.

We distinguish the schema and the vocabulary as follows. A vocabulary is the enumeration of a set of terms. A schema organize a set of terms in a system of some sort. A list of body parts is not the anatomy of a body. The furniture is not an interior design model.

Use this property to represent a temporal relation between two data nodes that are meant to be the same at a different point in time. The property is symmetric and does not specify a direction.
This property is not transitive. While it can be argued that the identity of something tracked temporarly should not change, thus implying transitivity, we want support the case when a data note has more then one following version (branching). Avoiding transitivity allows it.