mathib / fog-ontology Goto Github PK

For certain formats, it's useful to add the comment (text description and/or add a property e.g. defined in GOM: hasMultipleParts as an annotation property for fog:hasObjId-group) that the grouping can imply that there are 1..n potential geometry parts in a geometry file that together form a single geometry description. An geometry application should be aware of this.

Known formats:

• OBJ with OBJ groups > it seems that multiple OBJ groups with the same name can occur

Consider to add ThreeJS JSON as another geometry serialization to FOG, as proposed by @MadsHolten

• can it be considered as a geometry exchange format?
• are there versions of the geometry format?
• link to the official description of the geometry format (per version)?
• are there different serializations of the geometry format? (e.g. as for IFC, there is is an IFC-SPFF serialization, next to an IFC-XML serialization)
• for support of the omg:isPartOfGeometry patterns with subproperties of omg:hasReferencedGeometryId: what are the different ways to identify an individual geometry or groups of geometries in ThreeJS JSON?