Subgraph operations - Revision history

Teemu Mätäsniemi at 14:57, 22 November 2013

2013-11-22T14:57:51Z

← Older revision		Revision as of 14:57, 22 November 2013
Line 57:		Line 57:

	=== Export/import ===		=== Export/import ===

			Requirements
			* Developing import contributors a deveploper wants to list URIs of externals and possible change some of them while importing. This features enables e.g. moving of data of diagrams although different type declarations are used. Also, other kind of usage is possible. This requirement relates to a resolving of URIs feature.
			* Developing export contributors a developer wants to know all external URIs. Thus, the developer can be aware of data which is not included into exported data.

			Design guidelines (derived from baseline behaviour and aids in export/import operations)
			* Define a symbol of a component type in the context of the component type
			* Define a diagram of a composite in the context of the composite

	=== Copy/paste ===		=== Copy/paste ===

Tuukka Lehtonen: /* Exceptions to baseline behavior */

2013-11-18T09:14:35Z

Exceptions to baseline behavior

← Older revision		Revision as of 09:14, 18 November 2013
Line 60:		Line 60:
	=== Copy/paste ===		=== Copy/paste ===

			* All diagram elements
			** Template-diagram templatization tags must be removed (MOD.IsTemplatized)
			** Generate fresh names for all copied elements within the target diagram's context
			** Include element in the target diagram's ordered set
			** Add database metadata comment for element copy

			In addition, follow these rules for specific element types:
	* Diagram reference elements		* Diagram reference elements
	** Follow ''All diagram elements'' rules
	** Assertion: Copying must ensure that MOD.HasParentComponent correctly refers to the copied parent component		** Assertion: Copying must ensure that MOD.HasParentComponent correctly refers to the copied parent component
	** Offset all copied element positions based on the paste specification		** Offset all copied element positions based on the paste specification
	* Diagram connections		* Diagram connections
	** Follow ''All diagram elements'' rules
	** Move connection to front of the target diagram's ordered set to push it behind all other elements		** Move connection to front of the target diagram's ordered set to push it behind all other elements
	** Offset each route line in the connection by the offset specified in the paste specification based on the route line direction (horizontal/vertical)		** Offset each route line in the connection by the offset specified in the paste specification based on the route line direction (horizontal/vertical)
	* Diagram flags		* Diagram flags
	** Follow ''All diagram elements'' rules
	** Offset all copied element positions based on the paste specification		** Offset all copied element positions based on the paste specification
	** If flag is disconnected after copy, remove its L0.HasLabel.		** If flag is disconnected after copy, remove its L0.HasLabel.
	** If flag and its counterpart were both copied and the flag pair is diagam-local, FlagLabelingScheme must be used to set the same L0.HasLabel for both flags.		** If flag and its counterpart were both copied and the flag pair is diagam-local, FlagLabelingScheme must be used to set the same L0.HasLabel for both flags.
	* Diagram monitors		* Diagram monitors
	** Follow all ''All diagram elements'' rules
	** If the component the monitors refers to (DIA.HasMonitorComponent) a component that was not included in the copy, the monitor element position must be recalculated to be:		** If the component the monitors refers to (DIA.HasMonitorComponent) a component that was not included in the copy, the monitor element position must be recalculated to be:
	*** original monitored element world position + offset from paste specification		*** original monitored element world position + offset from paste specification
	* Other diagram elements		* Other diagram elements
	** Follow ''All diagram elements'' rules
	** Offset all copied element positions based on the paste specification		** Offset all copied element positions based on the paste specification


	* All diagram elements
	** Template-diagram templatization tags must be removed (MOD.IsTemplatized)
	** Generate fresh names for all copied elements within the target diagram's context
	** Include element in the target diagram's ordered set
	** Add database metadata comment for element copy

	=== Removal ===		=== Removal ===

Tuukka Lehtonen: /* Copy/paste */

2013-11-18T08:33:50Z

Copy/paste

← Older revision		Revision as of 08:33, 18 November 2013
Line 61:		Line 61:

	* Diagram reference elements		* Diagram reference elements
			** Follow ''All diagram elements'' rules
	** Assertion: Copying must ensure that MOD.HasParentComponent correctly refers to the copied parent component		** Assertion: Copying must ensure that MOD.HasParentComponent correctly refers to the copied parent component
	** ~~Follow~~ all ~~''Other diagram elements'' rules~~		** Offset all copied element positions based on the paste specification
	* Diagram connections		* Diagram connections
	** ~~TODO~~		** Follow ''All diagram elements'' rules
			** Move connection to front of the target diagram's ordered set to push it behind all other elements
			** Offset each route line in the connection by the offset specified in the paste specification based on the route line direction (horizontal/vertical)
	* Diagram flags		* Diagram flags
	** Follow ~~all~~ ''~~Other~~ diagram elements'' rules		** Follow ''All diagram elements'' rules
	** If flag is disconnected after copy, remove its L0.HasLabel. ~~Otherwise~~ the flag ~~must a diagram~~-local ~~pair of connected flags and~~ FlagLabelingScheme ~~shall~~ be used to set the same L0.HasLabel for both flags.		** Offset all copied element positions based on the paste specification
			** If flag is disconnected after copy, remove its L0.HasLabel.
			** If flag and its counterpart were both copied and the flag pair is diagam-local, FlagLabelingScheme must be used to set the same L0.HasLabel for both flags.
	* Diagram monitors		* Diagram monitors
	** TODO		** Follow all ''All diagram elements'' rules
	** Follow all ''~~Other~~ diagram elements'' rules		** If the component the monitors refers to (DIA.HasMonitorComponent) a component that was not included in the copy, the monitor element position must be recalculated to be:
			*** original monitored element world position + offset from paste specification
	* Other diagram elements		* Other diagram elements
			** Follow ''All diagram elements'' rules
			** Offset all copied element positions based on the paste specification


			* All diagram elements
	** Template-diagram templatization tags must be removed (MOD.IsTemplatized)		** Template-diagram templatization tags must be removed (MOD.IsTemplatized)
	** Generate fresh names for all copied elements within the target diagram's context		** Generate fresh names for all copied elements within the target diagram's context
	** Include ~~all elements~~ in the target diagram's ordered set		** Include element in the target diagram's ordered set
	** Offset all copied element positions based on the paste specification
	** Add database metadata comment for element copy		** Add database metadata comment for element copy

Tuukka Lehtonen: /* Exceptions to baseline behavior */

2013-11-18T07:01:25Z

Exceptions to baseline behavior

← Older revision		Revision as of 07:01, 18 November 2013
Line 59:		Line 59:

	=== Copy/paste ===		=== Copy/paste ===

			* Diagram reference elements
			** Assertion: Copying must ensure that MOD.HasParentComponent correctly refers to the copied parent component
			** Follow all ''Other diagram elements'' rules
			* Diagram connections
			** TODO
			* Diagram flags
			** Follow all ''Other diagram elements'' rules
			** If flag is disconnected after copy, remove its L0.HasLabel. Otherwise the flag must a diagram-local pair of connected flags and FlagLabelingScheme shall be used to set the same L0.HasLabel for both flags.
			* Diagram monitors
			** TODO
			** Follow all ''Other diagram elements'' rules
			* Other diagram elements
			** Template-diagram templatization tags must be removed (MOD.IsTemplatized)
			** Generate fresh names for all copied elements within the target diagram's context
			** Include all elements in the target diagram's ordered set
			** Offset all copied element positions based on the paste specification
			** Add database metadata comment for element copy

	=== Removal ===		=== Removal ===

Hannu Niemisto: /* Baseline behavior */

2013-11-12T21:22:40Z

Baseline behavior

← Older revision		Revision as of 21:22, 12 November 2013
Line 52:		Line 52:
	* Import creates all internal resources in TG file as new resources and adds all the statements in TG. The references to external resources are resolved by URI and if the resource does not exist a dummy resource is created. The root of the TG is attached by ConsistsOf to the target of the import operation.		* Import creates all internal resources in TG file as new resources and adds all the statements in TG. The references to external resources are resolved by URI and if the resource does not exist a dummy resource is created. The root of the TG is attached by ConsistsOf to the target of the import operation.
	* Copy/paste behaves just like export/import.		* Copy/paste behaves just like export/import.
	* Removal ~~removes~~ all the resource in the context of C.		* Removal unlinks all the resource in the context of C from the external resources.

	== Exceptions to baseline behavior ==		== Exceptions to baseline behavior ==

Tuukka Lehtonen: /* Baseline behavior */

2013-11-12T15:42:21Z

Baseline behavior

← Older revision		Revision as of 15:42, 12 November 2013
Line 49:		Line 49:

	Now, we can define baseline behaviors:		Now, we can define baseline behaviors:
	* Export writes all resources in the context of C as internal resources to the transferable graph, together with all their statements excluding a PartOf-statements from C. Resources external to C are referred by URI. C is marked the root of TG.		* Export writes all resources in the context of C as internal resources to the transferable graph, together with all their statements excluding PartOf-statements from C. Resources external to C are referred by URI. C is marked the root of TG.
	* Import creates all internal resources in TG file as new resources and adds all the statements in TG. The references to external resources are resolved by URI and if the resource does not exist a dummy resource is created. The root of the TG is attached by ConsistsOf to the target of the import operation.		* Import creates all internal resources in TG file as new resources and adds all the statements in TG. The references to external resources are resolved by URI and if the resource does not exist a dummy resource is created. The root of the TG is attached by ConsistsOf to the target of the import operation.
	* Copy/paste behaves just like export/import.		* Copy/paste behaves just like export/import.

Tuukka Lehtonen at 15:38, 12 November 2013

2013-11-12T15:38:19Z

← Older revision		Revision as of 15:38, 12 November 2013
Line 6:		Line 6:
	* Copy/paste		* Copy/paste
	** What is copied?		** What is copied?
	** How ~~the~~ references from the copied part to the uncopied part ~~are~~ handled?		** How are references from the copied part to the uncopied part handled?
	* Removal		* Removal
	** What is removed?		** What is removed?
	** How ~~the~~ references between the removed and the unremoved resources ~~are~~ handled?		** How are references between the removed and the unremoved resources handled?
	Moreover in many cases copy/paste should behave similarly to export/import		Moreover in many cases copy/paste should behave similarly to export/import
	and immediate removal of an imported object should usually restore the database to the		and immediate removal of an imported object should usually restore the database to the

Tuukka Lehtonen at 15:37, 12 November 2013

2013-11-12T15:37:46Z

← Older revision		Revision as of 15:37, 12 November 2013
Line 3:		Line 3:
	* Export/import		* Export/import
	** What is exported?		** What is exported?
	** How ~~the~~ references from the exported part to the unexported part ~~are~~ handled?		** How are references from the exported part to the unexported part handled?
	* Copy/paste		* Copy/paste
	** What is copied?		** What is copied?

Tuukka Lehtonen at 15:37, 12 November 2013

2013-11-12T15:37:15Z

← Older revision		Revision as of 15:37, 12 November 2013
Line 1:		Line 1:
	This page discusses ~~about~~ three common operations that handle some subgraph of the whole Simantics database.		This page discusses three common operations that handle some subgraph of the whole Simantics database.
	They all have very similar issues:		They all have very similar issues:
	* Export/import		* Export/import

Hannu Niemisto: /* Baseline behavior */

2013-11-12T13:48:01Z

Baseline behavior

← Older revision		Revision as of 13:48, 12 November 2013
Line 50:		Line 50:
	Now, we can define baseline behaviors:		Now, we can define baseline behaviors:
	* Export writes all resources in the context of C as internal resources to the transferable graph, together with all their statements excluding a PartOf-statements from C. Resources external to C are referred by URI. C is marked the root of TG.		* Export writes all resources in the context of C as internal resources to the transferable graph, together with all their statements excluding a PartOf-statements from C. Resources external to C are referred by URI. C is marked the root of TG.
	* Import creates all internal resources in TG file as new resources and ~~add~~ all the statements in TG. The references to external resources are resolved by URI and if the resource does not exist a dummy resource is created. The root of the TG is attached by ConsistsOf to the target of the import operation.		* Import creates all internal resources in TG file as new resources and adds all the statements in TG. The references to external resources are resolved by URI and if the resource does not exist a dummy resource is created. The root of the TG is attached by ConsistsOf to the target of the import operation.
	* Copy/paste behaves just like export/import.		* Copy/paste behaves just like export/import.
	* Removal removes all the resource in the context of C.		* Removal removes all the resource in the context of C.