. "2019-05-24"^^ . "2017-01-31"^^ . _:ub2bL23C10 . _:ub2bL23C10 . _:ub2bL23C10 "Marl\u00E8ne VILLANOVA-OLIVER" . _:ub2bL23C10 . _:ub2bL25C10 . _:ub2bL25C10 . _:ub2bL25C10 "Hy DAO" . _:ub2bL25C10 . _:ub2bL22C18 . _:ub2bL22C18 . _:ub2bL22C18 "Camille BERNARD" . _:ub2bL22C18 . . . "tsnchange" . . _:ub2bL24C10 . _:ub2bL24C10 "J\u00E9r\u00F4me GENSEL" . _:ub2bL24C10 . _:ub2bL24C10 . "This 1.1 version of the ontology enables the description of new operations of restructuration of the TSN: IdentificationRestructuration and HierarchyRestructuration, operation that impact several features at the same time." . "The TSN-Change ontology aims at describing changes that occured from one version of a Territorial Statistical Nomenclature (TSN) (i.e., partition of the territory) and its subsequent (e.g., change in territorial units boundaries to reflect an administrative reorganisation)."@en . "Territorial Statistical Nomenclature Change Ontology"@en . "1.1"^^ . . "The UnitChange concept describes all the changes undergone by a UnitVersion feature from one TSN version to another."@en . "UnitChange"@en . . . . "The IdentificationRestructuration concept is a sub concept of the StructureChange concept. It describes changes that simultaneously affect several TSNFeature by modifying their attributs of identification. Those changes make sense grouped together (e.g., all the sub-units of a Super one are renamed)."@en . "IdentificationRestructuration"@en . . . . "Indicates a Change of which a UnitVersion is an output resource."@en . . "outputUnitVersion"@en . . . . "unitVersionAfter"@en . . . "Indicates a TSNComponent after a change event."@en . . . "after"@en . . . "Indicates a UnitVersion after a change event."@en . . "LowerLevelChange"@en . "Deprecated Class, Class is now preferred. The lower level of a level changes."@en . . . . "The Fusion concept describes the merge of two or more TSNFeatures (e.g., merge of two TerritoryVersion or merge of two UnitVersion), into a single new TSNFeature that did not exist before the change. This operation leads to: (1) the disappearance of all the input TSNFeature(s) (i.e., the identity of the involved TSNFeatures is not extended after the Fusion); (2) the creation of one output TSNFeature whose footprint is equal to the combination of all the footprint of the input TSNFeatures. This concept is equivalent to the \"Fusion\" concept from the classification of territorial events of (Plumejeaud C, Mathian H, Gensel J, Grasland C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 2011;25(10):1597\u20131612)."@en . . . "Fusion"@en . . "lowerChange"@en . . "Indicates a lower Change that is caused by the described Change. The Change hierarchy is alligned on the Nomenclature components hierarchy i.e., Nomenclature > Territory > Level > Unit. Then a change that affect a Territory is above a change that affect the levels of the TSN."@en . . . "date"@en . . . . "Assign a date to the change that occurred."@en . . "Deformation"@en . "Deformation of a TSNFeature describes shape modification without size change between the input NomenclatureVersion and the output NomenclatureVersion. This concept is equivalent to the \"Deformation\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2)."@en . . . "unitVersionBefore"@en . . . . "Indicates a TSNComponent before a change event."@en . "before"@en . . . . "Indicates a UnitVersion before a change event."@en . . . "inputUnitVersion"@en . . "Indicates a Change of which a UnitVersion is an input resource."@en . . . . . . "The Reallocation concept describes operations of redistribution of the spatial area that modify the identity of all the input TSNFeatures (i.e., their identifier is modified), and modify their Geometry. The combination of footprints of the input TSNFeatures is equal to the combination of footprints of the output TSNFeatures. This operation leads to: (1) the disappearance of all the 'n' input TSNFeatures ; (2) the creation of 'p' TSNFeatures as output to the change event by redistribution of the spatial area covered by the 'n' input TSNFeatures. This concept is equivalent to the \"Reallocation\" concept from the classification of territorial events of (Plumejeaud C, Mathian H, Gensel J, Grasland C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 2011;25(10):1597\u20131612)."@en . . "Reallocation"@en . . "label"@en . . "Assign a name to the change that occurred."@en . . . . . . "Indicates a Change of which a LevelVersion is an output resource."@en . . . "outputLevelVersion"@en . . . . "Indicates a LevelVersion after a change event."@en . "levelVersionAfter"@en . . . . "TerritoryBelongingChange"@en . "The Territory a Unit belongs to changes."@en . . . "territoryVersionBefore"@en . . "Indicates a Change of which a TerritoryVersion is an input resource."@en . . . . "inputTerritoryVersion"@en . . . "Indicates a TerritoryVersion before a change event."@en . . . "Disappearance"@en . "The Disappearance concept describes the disappearance (or end) of a TSNFeature (i.e., TerritoryVersion, LevelVersion or UnitVersion) that comes as an input resource to the change event: the TSNFeature no longer exists after the change event i.e., no TSNFeature will carry its identifier in the output NomenclatureVersion. This concept is equivalent to the \"Disappearance\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2)."@en . . . "AcronymChange"@en . . "The acronym of a TSNFeature changes."@en . . "Indicates a NomenclatureVersion before a change event."@en . . "nomenclatureVersionBefore"@en . . "inputNomenclatureVersion"@en . . . "Indicates a Change of which a NomenclatureVersion is an input resource."@en . . . . . . "Integration"@en . "The Integration concept describes the merge of two or more TSNFeatures (e.g., merge of two TerritoryVersion or merge of two UnitVersion), into a single TSNFeature that existed before the change and maintains its identity after the change event (i.e., its identifier is not modified). This operation leads to: (1) the disappearance of at least one input TSNFeature ; (2) the Expansion of the footprint of the output TSNFeatures. Its new footprint is equal to the combination of all the footprint of the input TSNFeatures. This concept is equivalent to the \"Integration\" concept from the classification of territorial events of (Plumejeaud C, Mathian H, Gensel J, Grasland C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 2011;25(10):1597\u20131612)."@en . . . . . . "outputTerritoryVersion"@en . . "Indicates a Change of which a TerritoryVersion is an output resource."@en . . . . "territoryVersionAfter"@en . . "Indicates a TerritoryVersion after a change event."@en . . . "Indicates a NomenclatureVersion after a change event."@en . . "nomenclatureVersionAfter"@en . . . . . "Indicates a Change of which a NomenclatureVersion is an output resource."@en . . "outputNomenclatureVersion"@en . . . . "The name of a TSNFeature changes."@en . . "NameChange"@en . . "Expansion"@en . . "Expansion of a TSNFeature, in terms of shape, means its size increase between the input NomenclatureVersion and the output NomenclatureVersion. This concept is equivalent to the \"Expansion\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2)."@en . . "The Extraction concept describes the split of one TSNFeature (into two or more TSNFeatures) that nevertheless maintains its identity after the change event (i.e., its identifier is not modified). This operation leads to: (1) the Appearance of at least one new TSNFeature as an output of the change event: this/those new TSNFeature(s) take(s) territory from the input TSNFeature ; (2) the Contraction of the footprint of the input TSNFeature that nevertheless still exist after the change event. This concept is equivalent to the \"Extraction\" concept from the classification of territorial events of (Plumejeaud C, Mathian H, Gensel J, Grasland C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 2011;25(10):1597\u20131612)."@en . . "Extraction"@en . . . "SuperUnitChange"@en . . "The Super Unit of a Unit changes i.e., the Identifier of the Super Unit is not the same between the input and output NomenclatureVersion."@en . . . "The HierarchyRestructuration concept is a sub concept of the StructureChange concept. It describes changes that simultaneously affect several TSNFeature by modifying the hierarchy of the TSN. Those changes make sense grouped together (e.g., if a new Level integrate the nomenclature as well as new Unit composing this Level, then all those Appearance event of TSNFeatures will be grouped under one HierarchyRestructuration node)."@en . "HierarchyRestructuration"@en . . . "Appearance"@en . "The Appearance concept describes the appearance (or creation) of a new TSNFeature (i.e., TerritoryVersion, LevelVersion or UnitVersion) as an output to the change event. \"Appearance\" means the identifier of the new TSNFeature is different from all that already exist, in the input and output NomenclatureVersion. This concept is equivalent to the \"Appearance\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2)."@en . . "SubUnitChange"@en . "The Sub Unit(s) of a Unit change(s) i.e., whatever the nature of the change of the Sub Unit(s)."@en . . . "Indicates a societal or other cause to the described Change (e.g., administrative reform)."@en . . "isCausedBy"@en . . . "UpperLevelChange"@en . . . "Deprecated Class, Class is now preferred. The upper level of a level changes."@en . . "Indicates an upper Change that causes the described Change. The Change hierarchy is alligned on the Nomenclature components hierarchy i.e., Nomenclature > Territory > Level > Unit. Then a change that affect a Territory is above a change that affect the levels of the TSN."@en . "upperChange"@en . . . . "The identifier (within the TSN) of a TSNFeature changes."@en . "IdentifierChange"@en . . . . "TerritoryChange"@en . "The TerritoryChange concept describes all the changes undergone by a TerritoryVersion feature from one TSN version to another."@en . . . "The LevelChange concept describes all the changes undergone by a LevelVersion feature from one TSN version to another."@en . "LevelChange"@en . . "The Scission concept describes the split of one TSNFeature (into two or more TSNFeatures) that ceases to exist after the change event. This operation leads to: (1) the disappearance of the input TSNFeature (i.e., the identity of this TSNFeature is not extended after the event i.e., at least the identifier of the TSNFeature is modified); (2) the creation of two or more Units in the NomenclatureVersion V+1 by split of the footprint of the input Unit in NomenclatureVersion V. This concept is equivalent to the \"Scission\" concept from the classification of territorial events of (Plumejeaud C, Mathian H, Gensel J, Grasland C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 2011;25(10):1597\u20131612)."@en . . "Scission"@en . . . "The level a Unit belongs to changes."@en . . "LevelBelongingChange"@en . . . "The description of a TSNFeature changes."@en . "DescriptionChange"@en . . . . "Rectification"@en . "The Rectification concept describes operations of redistribution of the spatial area, without modifying the identity of all the input TSNFeatures (i.e., their identifier is not modified), but modifying their Geometry. The combination of footprints of the input TSNFeatures is equal to the combination of footprints of the output TSNFeatures. This concept is equivalent to the \"Rectification\" concept from the classification of territorial events of (Plumejeaud C, Mathian H, Gensel J, Grasland C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 2011;25(10):1597\u20131612)."@en . . "Contraction"@en . . "Contraction of a TSNFeature, in terms of shape, means its size decrease between the input NomenclatureVersion and the output NomenclatureVersion. This concept is equivalent to the \"Contraction\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2)."@en . . . . . "inputLevelVersion"@en . . "Indicates a Change of which a LevelVersion is an input resource."@en . . . "Indicates a Level before a change event."@en . "levelVersionBefore"@en . . . . "The previous version of a resource in a lineage. For instance a news article updated to correct factual information would point to the previous version of the article with pav:previousVersion. If however the content has significantly changed so that the two resources no longer share lineage (say a new article that talks about the same facts), they can instead be related using pav:derivedFrom. This property is normally used in a functional way, although PAV does not formally restrict this. Earlier versions which are not direct ancestors of this resource may instead be provided using the superproperty pav:hasEarlierVersion. A version number of this resource can be provided using the data property pav:version. To indicate that this version is a snapshot of a more general, non-versioned resource, e.g. 'Weather Today' vs. 'Weather Today on 2013-12-07', see pav:hasVersion. Note that it might be confusing to indicate pav:previousVersion from a resource that also has pav:hasVersion or pav:hasCurrentVersion relations, as such resources are intended to be a long-living and 'unversioned', while pav:previousVersion is intended for use between permalink-like 'snapshots' arranged in a linear history."@en . . "pav:previousVersion"@en . . "The LevelHierarchyChange concept describes changes that affect TSNFeatures that are of type LevelVersion. It describes changes of the Level position within the TSN hierarchy."@en . "LevelHierarchyChange"@en . . . "The Merge concept describes the merge of two or more TSNFeatures (e.g., merge of two TerritoryVersion or merge of two UnitVersion), into a single TSNFeature. This concept is equivalent to the \"Union\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2): \"fusion of 'n' zones into a single entity (union)\"."@en . . "Merge"@en . . . "Indicates a Change resource of which a TSNComponent is an output resource (i.e., a result of the Change event)."@en . . "output"@en . . . "isPredecessorOf"@en . . . . . . . . "Deprecated Property, property is now preferred. Indicates the successor Version of a Version resource."@en . . "isSuccessorOf"@en . . "Deprecated Property, property is now preferred. Indicates the predecessor Version of a Version resource."@en . . . "Redistribution"@en . . "The Redistribution concept describes operations of redistribution of the spatial area covered by 'n' TSNFeature(s) in the input NomenclatureVersion to form 'p' TSNFeature(s) in the output NomenclatureVersion. This concept is equivalent to the \"Re-allocation\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2): \"reallocation of land covered by 'n' initial zones to form 'p' new zones \"."@en . . . . . "hasPreviousVersion"@en . "Indicates the previous Version of a Version resource, in a TSN lineage."@en . . . . "hasNextVersion"@en . "Indicates the next Version of a Version resource, in a TSN lineage."@en . . . . "StructureChange"@en . . "The StructureChange concept describes restructuration operations that impact the TSN and several of its features simultaneously."@en . . "ContinuationChange"@en . "The ContinuationChange concept describes restructuration operations that do not modify the identity of all the involved TSNFeatures that comes as input to the Change Operation."@en . . . "SubLevelChange"@en . "The Sub level of a level changes."@en . . . . "The HierarchyChange concept describes modification of the position of one TSNFeature (LevelVersion or UnitVersion) in the NomenclatureVersion hierarchy. For example, a Unit may change the Level it belongs to."@en . "HierarchyChange"@en . . "The GeometryChange concept describes modification of the Geometry of one TSNFeature (i.e., TerritoryVersion, LevelVersion or UnitVersion). This concept is equivalent to the \"Transformation\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2): \"transformations processes involving chn-ange in shape or size: expansion, contraction and deformation (i.e. shape modification without size change)\"."@en . "GeometryChange"@en . . . "The GeometryRestructuration concept is a sub concept of the StructureChange concept. It describes changes that simultaneously affect several TSNFeature by modifying their Geometry and sometime other attributs of the TSNFeatures. The set of TSNFeatures (TerritoryVersion, LevelVersion or UnitVersion) impacted by the GeometryRestructuration event is determined following the rule described by (Plumejeaud C, Mathian H, Gensel J, Grasland C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 25, 1597\u20131612 (2011)):\"For any event type, a geometrical invariant defines the set of units involved in the one event: the combination of unit footprints that existed prior the event (preceding ones) is equal to the combination of unit footprints that are still in existence after the event (succeeding ones).\". Except in case of GeometryRestructuration caused by a TerritoryChange that affect the external boundaries of the TerritoryVersion observed. Then, in this case, the set of TSNFeature (TerritoryVersion, LevelVersion or UnitVersion) impacted by the StructureChange event is determined following the rule: changes are grouped together if they occur simultaneously, inside a area which extends from the new territory boundaries to unit(s) boundaries that match the ones of unit(s) before the event. This concept is equivalent to the \"evolution of spatial structure\" notion from (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2)."@en . . "GeometryRestructuration"@en . . "The FeatureChange concept describes one or a set of changes that occur simultaneously and affect only one TSNFeature resource (i.e., TerritoryVersion, LevelVersion or UnitVersion). This concept is closed to the concept \"Basic change\" of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2). And, this concept is equivalent to the \"LifeEvent:Transformation\" concept from the model of (Plumejeaud C, Mathian H, Gensel J, Grasland C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 2011;25(10):1597\u20131612)."@en . "FeatureChange"@en . . . "SuperLevelChange"@en . "The Super level of a level changes."@en . . . . . "input"@en . "Indicates a Change resource of which a TSNComponent is an input resource (i.e., an object subject to change)."@en . . . "IdentificationChange"@en . . "The IdentificationChange concept describes change(s) that modify the identifier, name, acronym and/or description attributs of one TSNFeature."@en . . "DerivationChange"@en . . "The DerivationChange concept describes restructuration operations that do modify the identity of TSNFeatures that comes as input to the Change Operation."@en . . "The Change concept is the super class of all types of change that may occur from one TSN version to another. A Change node may group under one node several changes on TSNFeatures that make sense grouped together. As \"a change is rarely isolated and independent from the other changes that occur simultaneously within the other units inside a given area\", we have to link \"together all the various units that were involved in a common territorial change\" (Plumejeaud, C., Mathian, H., Gensel, J., Grasland, C. Spatio-temporal analysis of territorial changes from a multi-scale perspective. International Journal of Geographical Information Science. 25, 1597\u20131612 (2011)). The Change concept is based on the Change Bridge concept of (Kauppinen T, Hyv\u00F6nen E. Modeling and reasoning about changes in ontology time series. In: Ontologies [Internet]. Springer; 2007. p. 319\u2013338. Available from: http://link.springer.com/chapter/10.1007/978-0-387-37022-4_11): \"A change bridge is associated with a change point and tells, what current concepts become obsolete (if any), what new concepts are created (if any), and how the new concepts overlap with older ones.\"."@en . "An occurrent is an entity that unfolds itself in time or it is the instantaneous boundary of such an entity (for example a beginning or an ending) or it is a temporal or spatiotemporal region which such an entity occupies_temporal_region or occupies_spatiotemporal_region (SPAN) (Grenon and Smith definition). "@en . "bfo:Occurrent"@en . "An occurrent is an entity that unfolds itself in time or it is the instantaneous boundary of such an entity (for example a beginning or an ending) or it is a temporal or spatiotemporal region which such an entity occupies_temporal_region or occupies_spatiotemporal_region (SPAN) (Grenon and Smith definition)." . . . "Change"@en . . "Split"@en . "The Split concept describes the split of a TSNFeature, into two or more TSNFeature. This concept is equivalent to the \"Split\" concept of (Claramunt C, Th\u00E9riault M. Managing Time in GIS An Event-Oriented Approach. In: Clifford J, Tuzhilin A, editors. Recent Advances in Temporal Databases. London: Springer London; 1995. p. 23\u201342. Available from: http://link.springer.com/10.1007/978-1-4471-3033-8_2): \"division of a zone into 'n' parts (split)\"."@en . . . . "The UnitHierarchyChange concept describes changes that affect TSNFeatures that are of type UnitVersion. It describes changes of the Unit position within the TSN hierarchy (e.g., change in the level it belongs to and/or Super unit change)."@en . "UnitHierarchyChange"@en .