You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think fog:ReferencedContent and fog:hasReferencedContent should move from FOG to OMG, as it can be applicable to more then one geometry schema.
The above terminology is now used when connecting a building object to an RDF literal with embedded geometry description and the content and name of an additional file also has to be connected (e.g. a material file in the case of OBJ, or a texture file in the case of OBJ/glTF or an additional binary geometry file in glTF):
Add a new node to OMG for geometry textures/materials - Node should be able to describe both. Specific subclasses/properties should be part of FOG, then.
Approach-independent
I think
fog:ReferencedContent
andfog:hasReferencedContent
should move from FOG to OMG, as it can be applicable to more then one geometry schema.The above terminology is now used when connecting a building object to an RDF literal with embedded geometry description and the content and name of an additional file also has to be connected (e.g. a material file in the case of OBJ, or a texture file in the case of OBJ/glTF or an additional binary geometry file in glTF):
The text was updated successfully, but these errors were encountered: