Submissions:Spatial Graph Adapter (SGA) - Revision history

HollyFerguson at 04:50, 16 July 2016

2016-07-16T04:50:05Z

HollyFerguson at 04:49, 16 July 2016

2016-07-16T04:49:26Z

HollyFerguson at 04:48, 16 July 2016

2016-07-16T04:48:55Z

HollyFerguson at 04:48, 16 July 2016

2016-07-16T04:48:04Z

HollyFerguson at 04:45, 16 July 2016

2016-07-16T04:45:34Z

HollyFerguson at 04:44, 16 July 2016

2016-07-16T04:44:48Z

HollyFerguson at 04:25, 16 July 2016

2016-07-16T04:25:01Z

HollyFerguson at 04:21, 16 July 2016

2016-07-16T04:21:18Z

HollyFerguson at 04:19, 16 July 2016

2016-07-16T04:19:40Z

HollyFerguson: Article is waiting for review.

2016-07-16T04:17:30Z

Article is waiting for review.

@@ Line 29: / Line 29: @@
 Even if we use a common definition for adjacency, such as where two objects would be touching could be considered adjacent, this fails when we want to know, say what columns or walls are adjacent to a space. It is true that they may be touching some building geometries, but what about the cases where you would have adjacent columns, but they are touching only the open air that define that side of a space (not touching but still on that visual or schema induced boundary)? The SGA pattern allows us to extract this type of information and add it as Attributes or ContextualizedRelations to other objects, solving this issue by being able to, for example, group building elements even as what may seem arbitrary in isolated examples. Schemas produce a wide array of these situations, and even more when we start to translate between them.
 |ReusableOWLBuildingBlock=https://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
-|Consequences=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
+|Consequences=[[Image:USOcore3.jpg|700px|thumb|center|SGA Pattern]]
 With the capabilities the SGA pattern provides, it has been found to be useful and as been implemented for IFC, GBXML, and CityGML is currently in progress. Once this mapping was produced and captured via this pattern, further work was possible and completed in the form of View helper files and all of this is being worked into an operational Linked Data Platform to further enhance open data exchange.

@@ Line 29: / Line 29: @@
 Even if we use a common definition for adjacency, such as where two objects would be touching could be considered adjacent, this fails when we want to know, say what columns or walls are adjacent to a space. It is true that they may be touching some building geometries, but what about the cases where you would have adjacent columns, but they are touching only the open air that define that side of a space (not touching but still on that visual or schema induced boundary)? The SGA pattern allows us to extract this type of information and add it as Attributes or ContextualizedRelations to other objects, solving this issue by being able to, for example, group building elements even as what may seem arbitrary in isolated examples. Schemas produce a wide array of these situations, and even more when we start to translate between them.
 |ReusableOWLBuildingBlock=https://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
-|Consequences=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]
+|Consequences=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
 With the capabilities the SGA pattern provides, it has been found to be useful and as been implemented for IFC, GBXML, and CityGML is currently in progress. Once this mapping was produced and captured via this pattern, further work was possible and completed in the form of View helper files and all of this is being worked into an operational Linked Data Platform to further enhance open data exchange.

@@ Line 29: / Line 29: @@
 Even if we use a common definition for adjacency, such as where two objects would be touching could be considered adjacent, this fails when we want to know, say what columns or walls are adjacent to a space. It is true that they may be touching some building geometries, but what about the cases where you would have adjacent columns, but they are touching only the open air that define that side of a space (not touching but still on that visual or schema induced boundary)? The SGA pattern allows us to extract this type of information and add it as Attributes or ContextualizedRelations to other objects, solving this issue by being able to, for example, group building elements even as what may seem arbitrary in isolated examples. Schemas produce a wide array of these situations, and even more when we start to translate between them.
 |ReusableOWLBuildingBlock=https://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
-|Consequences=With the capabilities the SGA pattern provides, it has been found to be useful and as been implemented for IFC, GBXML, and CityGML is currently in progress. Once this mapping was produced and captured via this pattern, further work was possible and completed in the form of View helper files and all of this is being worked into an operational Linked Data Platform to further enhance open data exchange.
+|Consequences=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]
 Our work was inspired by ideas from Spatial Information Theory, biomedical research for the Semanticscience Integrated Ontology (SIO), Mereotopology, and geospatial data efforts via the Open Geospatial Consortium (OGC), although these are not the only works regarding spatial descriptions.
@@ Line 42: / Line 44: @@
 }}
 {{Additional information header}}
 Our work was inspired by ideas from Spatial Information Theory, biomedical research for the Semanticscience Integrated Ontology (SIO), Mereotopology, and geospatial data efforts via the Open Geospatial Consortium (OGC), although these are not the only works regarding spatial descriptions.

@@ Line 42: / Line 42: @@
 }}
 {{Additional information header}}
 Our work was inspired by ideas from Spatial Information Theory, biomedical research for the Semanticscience Integrated Ontology (SIO), Mereotopology, and geospatial data efforts via the Open Geospatial Consortium (OGC), although these are not the only works regarding spatial descriptions.

@@ Line 28: / Line 28: @@
 Even if we use a common definition for adjacency, such as where two objects would be touching could be considered adjacent, this fails when we want to know, say what columns or walls are adjacent to a space. It is true that they may be touching some building geometries, but what about the cases where you would have adjacent columns, but they are touching only the open air that define that side of a space (not touching but still on that visual or schema induced boundary)? The SGA pattern allows us to extract this type of information and add it as Attributes or ContextualizedRelations to other objects, solving this issue by being able to, for example, group building elements even as what may seem arbitrary in isolated examples. Schemas produce a wide array of these situations, and even more when we start to translate between them.
-|ReusableOWLBuildingBlock=https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
+|ReusableOWLBuildingBlock=https://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
 |Consequences=With the capabilities the SGA pattern provides, it has been found to be useful and as been implemented for IFC, GBXML, and CityGML is currently in progress. Once this mapping was produced and captured via this pattern, further work was possible and completed in the form of View helper files and all of this is being worked into an operational Linked Data Platform to further enhance open data exchange.

@@ Line 8: / Line 8: @@
 |Name=Spatial Graph Adapter (SGA) Pattern
 |ContentODPAlsoKnownAs=SGA
-|Intent=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
+|Intent=Link to OWL File: https://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
 PDF of SGA Pattern Image: [[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]
@@ Line 34: / Line 34: @@
 |Scenario=IFC, GBXML, and CityGML (current work)
 |KnownUse=Building translation adapter or lifter pattern
-|CPInstantiationExample=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
+|CPInstantiationExample=Link to OWL File: https://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
-|ExtractedFrom=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
+|ExtractedFrom=Link to OWL File: https://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
 }}
 {{Element list header}}

@@ Line 2: / Line 2: @@
 {{Graphical representation header}}
 {{Graphical representation
-|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
+|ImageName=[[Image:USOcore3.jpg]]
 }}
 {{Content OP Proposal Template
@@ Line 11: / Line 11: @@
 PDF of SGA Pattern Image: [[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]
 To answer the modern, interdisciplinary questions asked within the Building domain, industry tools and data standards need to become far more interoperable in order to be able to provide a full and accurate set of analysis to engineers and designers. To provide this full picture from which to make decisions, we needed a way to resolve the spatial data that tools provide in order to synthesize it together. In addition to missing, incorrect, and inconsistent information, there is also the challenge of not being able to use existing spatial patterns to capture the full granularity or specificity of the geospatial descriptions required to capture full and dynamic geometric contexts.

@@ Line 2: / Line 2: @@
 {{Graphical representation header}}
 {{Graphical representation
-|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]][[Image:File.jpg]]
+|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]][[Image:USOcore3.jpg]]
 }}
 {{Content OP Proposal Template
@@ Line 47: / Line 47: @@
 For the development of the pattern and for versions of data standards worked with thus far, we have crossed-checked our research with a team of Ontologists, Computer Scientists, Architects, Engineers, and other domain experts. We have also built a visualization method to verify what is being populated within the pattern relative to what data was in the original spatial schema instance file. The pattern has been used with a set of six test models ranging in complexity from one room to sixty-plus rooms on multiple levels. Additional models are planned to be tested in future iterations of the work.
 {{Scenarios about me}}
 {{Reviews about me}}
@@ Line 54: / Line 60: @@
 |Event=WOP:2016
 }}

← Older revision		Revision as of 04:17, 16 July 2016
Line 54:		Line 54:
	\|Event=WOP:2016		\|Event=WOP:2016
	}}		}}
		+	[[Category:Waiting for review]]