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

New term proposal: ac:Digital3DResource #248

Open
baskaufs opened this issue Dec 4, 2022 · 5 comments
Open

New term proposal: ac:Digital3DResource #248

baskaufs opened this issue Dec 4, 2022 · 5 comments

Comments

@baskaufs
Copy link

baskaufs commented Dec 4, 2022

During the 2022-11-10 Audubon Core Maintenance Group working session it was decided to propose minting an Audubon Core class term that could be used as a value for dc:type/dcterms:type when the subject resource was a digital 3D resource. We would then request that DataCite include it in their controlled vocabulary for datacite:resourceTypeGeneral. Because of potential issues with having a local name starting with a non-alphabetic character, the local name Digital3DResource was chosen over 3DDigitalResource. The term metadata proposed here come from a proposal submitted to the DCMI usage board that they chose not to act upon. See #243 for rationale and reasons why existing type terms are inadequate. At the working session, it was decided to fast-track this particular term addition in order to be able to start working towards getting it accepted by DataCite without needing to wait for completion of the entire 3D Task Group proposal.

Term name: ac:Digital3DResource

Label: Digital 3D Resource

IRI: http://rs.tdwg.org/ac/terms/Digital3DResource

Controlled value string: Digital3DResource

Definition: One or more binary files primarily intended to hold information about the three-dimensional geometry (surface or volume) of a real or non-real object, set of objects, or scene.

Usage: The term IRI should be used as a value for dcterms:type (http://purl.org/dc/terms/type). The controlled value string should be used as a value for dc:type (http://purl.org/dc/elements/1.1/type).

Notes: Such files can be used by software to digitally render views of the subject, make measurements, conduct analyses, and create physical 3D replicas. This term includes resources composed of one or more files that are used to compute a 3D geometry (e.g., X-ray projections for computed tomography scans or photograph sets for photogrammetry). For avoidance of doubt, 2D renderings (views) produced from a Digital3DResource should not be included in this class, but stereo image pairs, anaglyphs, and other formats that hold information about 3D geometry may be included.

Type: http://www.w3.org/2000/01/rdf-schema#Class

Submitted by @baskaufs on behalf of the 3D imagery and Data Task Group.

@baskaufs
Copy link
Author

baskaufs commented Dec 5, 2022

Changed proposal language "We would then request that DataCite include it in their controlled vocabulary for dcterms:type
to "We would then request that DataCite include it in their controlled vocabulary for datacite:resourceTypeGeneral" upon request by Adam Rountrey of the 3D Task Group.

@magpiedin
Copy link
Contributor

Many thanks Steve -- got my support

re:Adam's point on avoiding confusion around 'Collection' in the proposal's Notes section, I changed

  • "A file or collection of files that are intended to be used to compute a three dimensional geometry (e.g., X-ray projections for computed tomography scans or photograph sets for photogrammetry) are also included."

    to:

  • "This term includes resources composed of one or more files that are used to compute a 3D geometry (e.g., X-ray...)"

...If adding that as a "Usage" suggestion (here or in dc:type) is more appropriate instead -- similar to the existing recommendation to use "Text" for images of text -- maybe something along these lines:

  • "A file or collection of files (including sets of images or measurements) which are intended to be used to compute a 3D geometry SHOULD be given a value of 'Digital3DResource' for dc:type."

Implementation/experience notes are also drafted here if any help explain how the term meets efficacy/stability needs.

@douglasmb
Copy link

douglasmb commented Dec 6, 2022 via email

@baskaufs
Copy link
Author

baskaufs commented Dec 6, 2022

@douglasmb The changes are being made in the original proposal at the top of the issue tracker page. If you are seeing these comments in an email, click on the little "view it on GitHub" link at the bottom of the email, then scroll up to the top of the page. You should be able to see the current state of the proposal (definition, usage, notes) in the first comment box.

@douglasmb
Copy link

I changed the definition to remove use of "collection"

@edwbaker edwbaker added the next meeting agenda Issues to be discussed at next MG meeting label Dec 8, 2022
@edwbaker edwbaker added this to the 3D Task Group milestone Feb 21, 2024
@edwbaker edwbaker added 3D future-meeting and removed next meeting agenda Issues to be discussed at next MG meeting labels Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants