Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simple property to link an element/zone to its geometry? #37

Closed
maximelefrancois86 opened this issue Jun 20, 2018 · 4 comments
Closed

Simple property to link an element/zone to its geometry? #37

maximelefrancois86 opened this issue Jun 20, 2018 · 4 comments

Comments

@maximelefrancois86
Copy link
Member

@maximelefrancois86 maximelefrancois86 commented Jun 20, 2018

We could define a simple Datatype Property to link a bot:Zone or bot:Element to its geometry

bot:hasSimpleGeometry a owl:DatatypeProperty ;
  rdfs:domainIncludes bot:Zone , bot:Element .

that datatype property could link any bot:Zone or bot:Element to a literal that encodes its geometry. This could be left open and be defined as:

simpleGeometry as a geo:wktLiteral

<site> a bot:Site ;
  bot:hasSimpleGeometry """POLYGON((-77.050125 38.892086, -77.039482 38.892036, -77.039482 38.895393,
-77.033669 38.895508, -77.033585 38.892052, -77.031906 38.892086, -77.031883 38.887474, -
77.050232 38.887142, -77.050125 38.892086 ))"""^^geo:wktLiteral.

simpleGeometry as a Virtual Reality Markup Language

<element> a bot:Element ;
  bot:hasSimpleGeometry """#VRML V2.0 utf8
Shape {
  appearance Appearance {
    material Material {
      diffuseColor  .8 0 .2
      shininess .7
    }
  }
  geometry Cylinder {
    radius 1
    height 8
    side FALSE
    top TRUE
    bottom FALSE
  }
}"""^^<https://www.iana.org/assignments/media-types/model/vrml>
@pipauwel
Copy link
Contributor

@pipauwel pipauwel commented Jun 21, 2018

LDAC2018: we can add the following properties to BOT:

bot:hasZeroPoint a owl:DatatypeProperty ;
schema:domainIncludes bot:Site .

bot:hasSimpleGeometry a owl:DatatypeProperty ;
schema:domainIncludes bot:Zone , bot:Element .

bot:hasComplexGeometry a owl:ObjectProperty ;
schema:domainIncludes bot:Zone , bot:Element .

Loading

@maximelefrancois86
Copy link
Member Author

@maximelefrancois86 maximelefrancois86 commented Jun 21, 2018

What about using transformation matrices:

bot:CoordinateSystemPositioning a owl:Class

bot:baseCoordinateSystem a owl:ObjectProperty ;
  rdfs:domain bot:CoordinateSystemPositioning ;
  schema:rangeIncludes bot:Zone, bot:Element .

bot:relativeCoordinateSystem a owl:ObjectProperty ;
  rdfs:domain bot:CoordinateSystemPositioning ;
  schema:rangeIncludes bot:Zone, bot:Element .

bot:transformationMatrix a owl:DatatypeProperty; 
domain bot:CoordinateSystemPositioning ;
range cdt:4dmatrix .

Loading

@GeorgFerdinandSchneider
Copy link
Collaborator

@GeorgFerdinandSchneider GeorgFerdinandSchneider commented Jun 21, 2018

I like the idea but would like to stress the fact that BOT should be kept minimal.

Why not follow a modular paradigm such as SEAS, SAREF etc.?

geom4bot:hasSimpleGeometry a owl:DatatypeProperty ;
  rdfs:domainIncludes bot:Zone , bot:Element .

Loading

@pipauwel
Copy link
Contributor

@pipauwel pipauwel commented Jun 21, 2018

LDAC2018: let's keep the minimal approach for now (hasSimpleGeometry added), and keep the transformation matrices and coordinatesystems out for now (to be handled in the group that works on geometry, outside of this community group).

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants