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

move fog:referencedContent to OMG #1

Open
mathib opened this issue May 27, 2019 · 1 comment
Open

move fog:referencedContent to OMG #1

mathib opened this issue May 27, 2019 · 1 comment

Comments

@mathib
Copy link

mathib commented May 27, 2019

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):

inst:door1 omg:hasGeometry inst:geometry1 .
inst:geometry1 a omg:Geometry ;
   fog:asObj_v3.0-obj "v 1 0 2 ..."^^xsd:string ;
   fog:hasReferencedContent inst:ref1 .
inst:ref1 a fog:ReferencedContent ;
   fog:asObj_v3.0-mtl "newmtl Mat_1\n Ka 0.000 ..."^^xsd:string ;
   rdfs:label "mymtlfile.mtl" .
@AnnaWagner
Copy link
Collaborator

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

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

No branches or pull requests

2 participants