Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add 3DModel type (as a CreativeWork subtype; original proposal was 3DModelObject, subtype of MediaObject) #2140
We can use https://schema.org/encodingFormat to deal with the huge variety of formats, and make the definition inclusive. There are many kind of file that could usefully be seen as carrying 3D models, we should aim to make sure the definition makes it clear the type should be equally useful for VR, AR, scientific data sharing, geospatial data, 3d molecular data etc.
We'll be needing a definition. How about:
We will also want to consider and document the situation where a bundle of several files have been packaged as a .zip or similar archive format.
This is a detail, and not specific to 3D formats except that several approaches use multiple files:
This came up elsewhere w.r.t. datasets, where I had this interim advice:
(I still need to investigate this further, as it does not deal explicitly with several files of different media types, all in the same .zip package.)
As long as we have 3 separate Types to deal with 1. the CONTENT , 2. the FORMATS, 3. the PACKAGING then I don't really care much here. (Those 3 Types, the trifecta of Information Storage, have been around for 10's of years since the beginning of Information and Storage Retrieval)
I've been talking this over with @vholland, we think it'll work better up at the CreativeWork level (as "3DModel"), leaving a generic MediaObject for the specific downloadable "bag of bits" representation. That way you can either have a simple "one 3DModel and one downloadable media object encoding of it" description, or you can say "there's a 3DModel and here are x, y and z alternate representations to download".