'Ontology Design Patterns' - User contributions [en]

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:50:05Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|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]]

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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|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.

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.
|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter 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://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:49:26Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|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]]

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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]]

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.

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.
|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter 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://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:48:55Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|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]]

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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]]

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.

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.
|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter 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://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:48:04Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|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]]

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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.

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.
|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter 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://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{Additional information header}}
[[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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:45:34Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|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]]

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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.

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.
|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter 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://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:44:48Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|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]]

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter 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://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:25:01Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|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
|ExtractedFrom=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:21:18Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern

PDF of SGA Pattern Image: [[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]

[[Image:USOcore3.jpg]]

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|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
|ExtractedFrom=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:19:40Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]][[Image:USOcore3.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|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
|ExtractedFrom=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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.

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:17:30Z

HollyFerguson: Article is waiting for review.

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]][[Image:File.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|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
|ExtractedFrom=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}
[[Category:Waiting for review]]

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:17:22Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]][[Image:File.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|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
|ExtractedFrom=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:16:18Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]][[Image:File.jpg]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern

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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|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
|ExtractedFrom=Link to OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:13:08Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter (SGA) Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter pattern
|CPInstantiationExample=OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
|ExtractedFrom=OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:11:06Z

HollyFerguson:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?

2. Exactly how much of this structural element is exposed and to what spaces?

3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?

4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?

5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

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.
|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter pattern
|CPInstantiationExample=OWL File: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:09:39Z

HollyFerguson: Submissions:Spatial Graph Adapter Pattern 2 moved to Submissions:Spatial Graph Adapter (SGA): Spatial Graph Adapter Pattern shoudl only be this one page under Content ODPs, but there is no way for me to delete the first one. So this change makes t

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).

|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?
2. Exactly how much of this structural element is exposed and to what spaces?
3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?
4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?
5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter pattern
|CPInstantiationExample=https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
|ExtractedFrom=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.
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter Pattern 2

2016-07-16T04:09:39Z

#REDIRECT [[Submissions:Spatial Graph Adapter (SGA)]]

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T04:06:53Z

HollyFerguson: Submissions:Spatial Graph Adapter Pattern moved to Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs): Needed to move to Content ODP (separate Content ODP page made for this pattern but there is no way to delete this one...?)

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=SGA Pattern
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]

SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg

Current OWL File Located at: https://github.com/HollyFerguson/Spatial-Graph-Adapter-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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space (Both creating enclosure or not creating enclosure)?
|Solution=Example Problem Question:
What Building Components are adjacent to this Space (Both creating enclosure or not creating enclosure)?

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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
Current OWL File Located at: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern

[[Category:Waiting for review]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter Pattern

2016-07-16T04:06:53Z

#REDIRECT [[Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)]]

Submissions:Spatial Graph Adapter (SGA)

2016-07-16T04:03:34Z

HollyFerguson: WOP:2016

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
}}
{{Content OP Proposal Template
|SubmittedBy=Holly Ferguson
|Name=Spatial Graph Adapter Pattern
|ContentODPAlsoKnownAs=SGA
|Intent=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.

The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing).

|Domain=http://ontologydesignpatterns.org/wiki/Community:Building_and_Construction
|CompetencyQuestion=1. What spaces is this damaged structural beam a part of (without needing to iterate through every existing spatial component or coordinate set)?
2. Exactly how much of this structural element is exposed and to what spaces?
3. What are all of the spatial elements in this graph that contain void spaces (air spaces in assemblies that could be susceptible to damage)?
4. What thermal or occupancy zones is this assembly associated with (these may or may not have to do with adjacency or locality)?
5. What sets of columns are responsible for supporting floors X and Y?
|ContentODPDescription=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.

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
|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.

|Scenario=IFC, GBXML, and CityGML (current work)
|KnownUse=Building translation adapter or lifter pattern
|CPInstantiationExample=https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
|ExtractedFrom=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.
}}
{{Element list header}}
{{Takes in account review
|TakesInAccountReview=Requested
}}
{{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.

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.

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}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Community:Building and Construction

2016-07-16T03:40:01Z

HollyFerguson: New page: {{Domain Template |Name=Building and Construction |Description=The domain of Building Industry and Building Design Modeling. Also extends to Architecture, Engineering, and other Spatial or...

{{Domain Template
|Name=Building and Construction
|Description=The domain of Building Industry and Building Design Modeling. Also extends to Architecture, Engineering, and other Spatial or GeoSpatial concepts.
}}
{{List of ontologies of this domain}}
{{Additional information header}}

{{My references}}
{{Domain toolbar}}

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T03:08:15Z

HollyFerguson: Article is waiting for review.

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]

SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg

Current OWL File Located at: https://github.com/HollyFerguson/Spatial-Graph-Adapter-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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space (Both creating enclosure or not creating enclosure)?
|Solution=Example Problem Question:
What Building Components are adjacent to this Space (Both creating enclosure or not creating enclosure)?

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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
Current OWL File Located at: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}
[[Category:Waiting for review]]

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T03:07:04Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]

SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg

Current OWL File Located at: https://github.com/HollyFerguson/Spatial-Graph-Adapter-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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space (Both creating enclosure or not creating enclosure)?
|Solution=Example Problem Question:
What Building Components are adjacent to this Space (Both creating enclosure or not creating enclosure)?

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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
Current OWL File Located at: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T03:05:53Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]
SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg
Current OWL File Located at: https://github.com/HollyFerguson/Spatial-Graph-Adapter-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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space (Both creating enclosure or not creating enclosure)?
|Solution=Example Problem Question:
What Building Components are adjacent to this Space (Both creating enclosure or not creating enclosure)?

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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
Current OWL File Located at: https://github.com/HollyFerguson/Spatial-Graph-Adapter-Pattern

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T03:04:03Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]
SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg

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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space (Both creating enclosure or not creating enclosure)?
|Solution=Example Problem Question:
What Building Components are Adjacent to this Space (Both creating enclosure or not creating enclosure)?

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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
No additional information at this time.
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T03:03:12Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]
SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg

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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space (Both creating enclosure or not creating enclosure)?
|Solution=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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
No additional information at this time.
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T02:58:51Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.pdf|600px|thumb|center|SGA Pattern]]
SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks

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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space?
|Solution=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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
No additional information at this time.
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

File:USOcore3.pdf

2016-07-16T02:57:52Z

HollyFerguson: Spatial Graph Adapter (SGA) Pattern

Spatial Graph Adapter (SGA) Pattern

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T02:53:35Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.jpg|600px|thumb|center|SGA Pattern]]
SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks

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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space?
|Solution=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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
No additional information at this time.
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T02:52:43Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=[[Image:USOcore3.jpg|200px|thumb|left|SGA Pattern]]
SGA Pattern: Image: http://ontologydesignpatterns.org/wiki/Image:USOcore3.jpg#filelinks

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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space?
|Solution=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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
No additional information at this time.
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

File:USOcore3.jpg

2016-07-16T02:48:05Z

HollyFerguson: uploaded a new version of "Image:USOcore3.jpg"

Paper Abstract: This research provides a data pattern that allows spatial relationships to be captured at a more granular and descriptive level than has been possible thus far. This pattern is hosted by a modular and extensible framework used for translating between different data formats without needing to change current schemas or work flows. The Spatial Graph Adapter Pattern is used as a modular adapter for Building Industry information leading to interoperability with OGC standards; additionally, the pattern and extensible proof of concept Linked Data Platform is demonstrated with a case study example for BIM data.

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T02:41:23Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (USOcore3.jpg)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space?
|Solution=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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.
}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
No additional information at this time.
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-16T02:39:43Z

HollyFerguson:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Spatial Graph Adapter Pattern (USOcore3.jpg)
}}
{{Alignment OP General Template
|Name=Spatial Graph Adapter Pattern
|SubmittedBy=Holly Ferguson
|AlsoKnownAs=Holly Ferguson
|Author=Holly Ferguson, Charles Vardeman II, Michelle Cheatham, Adila Krisnadhi
}}
{{Alignment OP Description Template
|Domain=Building Information Modeling and Spatial Representations
|Problem=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.
|Solution=The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas model sets our further research in bringing this and other patterns into full use in a Linked Data Platform (ongoing).
|Workflow=After several iterations of studying building industry data standards (in particular, GBXML, IFC, and CityGML), we began to map not only terms between them, but also conceptual level indicators. First we capture the main spatial arrangement of geometric elements which are extracted automatically from a spatial instance file. Secondly, the SGA pattern allows us to contextualize additional relationships to capture schema-specific ideas to ultimately be able to ask all the data questions simultaneously. We do acknowledge that in several cases there could be benefits to aligning it with other mereotopological or SIO pattern concepts, but these have not been necessary thus far.
}}
{{Alignment OP Example Template
|Scenario=What Building Components are Adjacent to this Space?
|Solution=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)?
|Consequences=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.
}}
{{Alignment OP References Template
|Origin=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.
|KnownUse=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.
|RelatedTo=Not applicable at this time, to be added.
|ValidationTest=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.

}}
{{Takes in account review
|TakesInAccountReview=Developed with Ontologists, Computer Scientists, Engineers, and Architects - Will also take into account and make necessary edits from any reviews given about the accompanying paper submitted to WOP:2016.
}}
No additional information at this time.
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2016
}}
{{Submission to event}}

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-15T21:27:11Z

HollyFerguson: Spatial Graph Adapter Pattern (USOcore3.jpg), Axioms, OWL File, Examples

Submissions:Spatial Graph Adapter Pattern (moved to Content ODPs)

2016-07-15T21:18:38Z

HollyFerguson: Spatial Graph Adapter Pattern, Axiomized OWL File, and Descriptions as submitted for review under WOP2016

File:USOcore3.jpg

2016-07-15T20:47:34Z

HollyFerguson: Paper Abstract: This research provides a data pattern that allows spatial relationships to be captured at a more granular and descriptive level than has been possible thus far. This pattern is hosted by a modular and extensible framework used for translat