parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged".
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered conformant with this standard.
         
Drop "well formed" and "fully merged" and say what the conditions are that the topic map graph components and graph must meet.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
Delete entirely (see comments)
         
It has been my impression that the topic map graph is timeless, that is that all operations that
can be performed have been performed at the time the graph is inspected. If something purporting to
be a topic map cannot be expressed in the topic map graph, then it fails to conform to the topic map
graph. In processing a topic map instance in some syntax into a topic map graph representation, there
may be some undefined period of time in which all operations have not been performed but is that an
issue for this standard?
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged". Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
The following subclauses name and define the rules and cases for constructing topic map graph components and the entire topic map graph. Topic map instances, when mapped to the topic map graph, either conform or fail to conform to the topic map graph. The topic map graph provides both a canonical model for Topic Map Applications as well as a means of comparing topic maps expressed in different syntaxes for their conformance to all or part of the topic map graph. (Topic map Applications are not required to use or produce the topic map graph but topic map instances from Topic Map Applications as well as Topic Map Applications themselves, can be measured against the topic map graph.)
         
Heavy revision to drop the notions of "well formed" and "fully merged." Any Topic Map Application or
topic map instance may fail to conform in one or more ways to the topic map graph. The utility of the
topic map graph is in defining a means of determining where Topic Map Appications or topic map instances
diverge from the topic map graph.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged".
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered conformant with this standard.
         
Drop "well formed" and "fully merged" and say what the conditions are that the topic map graph components and graph must meet.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
Delete entirely (see comments)
         
It has been my impression that the topic map graph is timeless, that is that all operations that
can be performed have been performed at the time the graph is inspected. If something purporting to
be a topic map cannot be expressed in the topic map graph, then it fails to conform to the topic map
graph. In processing a topic map instance in some syntax into a topic map graph representation, there
may be some undefined period of time in which all operations have not been performed but is that an
issue for this standard?
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged". Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
The following subclauses name and define the rules and cases for constructing topic map graph components and the entire topic map graph. Topic map instances, when mapped to the topic map graph, either conform or fail to conform to the topic map graph. The topic map graph provides both a canonical model for Topic Map Applications as well as a means of comparing topic maps expressed in different syntaxes for their conformance to all or part of the topic map graph. (Topic map Applications are not required to use or produce the topic map graph but topic map instances from Topic Map Applications as well as Topic Map Applications themselves, can be measured against the topic map graph.)
         
Heavy revision to drop the notions of "well formed" and "fully merged." Any Topic Map Application or
topic map instance may fail to conform in one or more ways to the topic map graph. The utility of the
topic map graph is in defining a means of determining where Topic Map Appications or topic map instances
diverge from the topic map graph.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged".
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered conformant with this standard.
         
Drop "well formed" and "fully merged" and say what the conditions are that the topic map graph components and graph must meet.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
Delete entirely (see comments)
         
It has been my impression that the topic map graph is timeless, that is that all operations that
can be performed have been performed at the time the graph is inspected. If something purporting to
be a topic map cannot be expressed in the topic map graph, then it fails to conform to the topic map
graph. In processing a topic map instance in some syntax into a topic map graph representation, there
may be some undefined period of time in which all operations have not been performed but is that an
issue for this standard?
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged". Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
The following subclauses name and define the rules and cases for constructing topic map graph components and the entire topic map graph. Topic map instances, when mapped to the topic map graph, either conform or fail to conform to the topic map graph. The topic map graph provides both a canonical model for Topic Map Applications as well as a means of comparing topic maps expressed in different syntaxes for their conformance to all or part of the topic map graph. (Topic map Applications are not required to use or produce the topic map graph but topic map instances from Topic Map Applications as well as Topic Map Applications themselves, can be measured against the topic map graph.)
         
Heavy revision to drop the notions of "well formed" and "fully merged." Any Topic Map Application or
topic map instance may fail to conform in one or more ways to the topic map graph. The utility of the
topic map graph is in defining a means of determining where Topic Map Appications or topic map instances
diverge from the topic map graph.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged".
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered conformant with this standard.
         
Drop "well formed" and "fully merged" and say what the conditions are that the topic map graph components and graph must meet.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
Delete entirely (see comments)
         
It has been my impression that the topic map graph is timeless, that is that all operations that
can be performed have been performed at the time the graph is inspected. If something purporting to
be a topic map cannot be expressed in the topic map graph, then it fails to conform to the topic map
graph. In processing a topic map instance in some syntax into a topic map graph representation, there
may be some undefined period of time in which all operations have not been performed but is that an
issue for this standard?
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged". Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
The following subclauses name and define the rules and cases for constructing topic map graph components and the entire topic map graph. Topic map instances, when mapped to the topic map graph, either conform or fail to conform to the topic map graph. The topic map graph provides both a canonical model for Topic Map Applications as well as a means of comparing topic maps expressed in different syntaxes for their conformance to all or part of the topic map graph. (Topic map Applications are not required to use or produce the topic map graph but topic map instances from Topic Map Applications as well as Topic Map Applications themselves, can be measured against the topic map graph.)
         
Heavy revision to drop the notions of "well formed" and "fully merged." Any Topic Map Application or
topic map instance may fail to conform in one or more ways to the topic map graph. The utility of the
topic map graph is in defining a means of determining where Topic Map Appications or topic map instances
diverge from the topic map graph.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged".
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered conformant with this standard.
         
Drop "well formed" and "fully merged" and say what the conditions are that the topic map graph components and graph must meet.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
Delete entirely (see comments)
         
It has been my impression that the topic map graph is timeless, that is that all operations that
can be performed have been performed at the time the graph is inspected. If something purporting to
be a topic map cannot be expressed in the topic map graph, then it fails to conform to the topic map
graph. In processing a topic map instance in some syntax into a topic map graph representation, there
may be some undefined period of time in which all operations have not been performed but is that an
issue for this standard?
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged". Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
The following subclauses name and define the rules and cases for constructing topic map graph components and the entire topic map graph. Topic map instances, when mapped to the topic map graph, either conform or fail to conform to the topic map graph. The topic map graph provides both a canonical model for Topic Map Applications as well as a means of comparing topic maps expressed in different syntaxes for their conformance to all or part of the topic map graph. (Topic map Applications are not required to use or produce the topic map graph but topic map instances from Topic Map Applications as well as Topic Map Applications themselves, can be measured against the topic map graph.)
         
Heavy revision to drop the notions of "well formed" and "fully merged." Any Topic Map Application or
topic map instance may fail to conform in one or more ways to the topic map graph. The utility of the
topic map graph is in defining a means of determining where Topic Map Appications or topic map instances
diverge from the topic map graph.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged".
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered conformant with this standard.
         
Drop "well formed" and "fully merged" and say what the conditions are that the topic map graph components and graph must meet.
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
Delete entirely (see comments)
         
It has been my impression that the topic map graph is timeless, that is that all operations that
can be performed have been performed at the time the graph is inspected. If something purporting to
be a topic map cannot be expressed in the topic map graph, then it fails to conform to the topic map
graph. In processing a topic map instance in some syntax into a topic map graph representation, there
may be some undefined period of time in which all operations have not been performed but is that an
issue for this standard?
—pdurusau@emory.edu
parid0484 | Sun, 19 Jan 2003 16:17:10
The following subclauses name and define the rules and cases to which topic map graph components and entire topic map graphs must conform in order to be considered "well formed", and the additional rules to which topic map graphs must conform in order to be considered "fully merged". Topic map graphs that are under construction may or may not be well-formed, but only well-formed topic map graphs are eligible to become fully merged, in addition to being well-formed.
The following subclauses name and define the rules and cases for constructing topic map graph components and the entire topic map graph. Topic map instances, when mapped to the topic map graph, either conform or fail to conform to the topic map graph. The topic map graph provides both a canonical model for Topic Map Applications as well as a means of comparing topic maps expressed in different syntaxes for their conformance to all or part of the topic map graph. (Topic map Applications are not required to use or produce the topic map graph but topic map instances from Topic Map Applications as well as Topic Map Applications themselves, can be measured against the topic map graph.)
         
Heavy revision to drop the notions of "well formed" and "fully merged." Any Topic Map Application or
topic map instance may fail to conform in one or more ways to the topic map graph. The utility of the
topic map graph is in defining a means of determining where Topic Map Appications or topic map instances
diverge from the topic map graph.
—pdurusau@emory.edu