Open baskaufs opened 1 year ago
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.
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:
Implementation/experience notes are also drafted here if any help explain how the term meets efficacy/stability needs.
thanks Kate and all -
Im not sure how to find where these changes are currently being made.
If 'collection' is being removed from the comments, is it also being removed from the definition itself?
Doug :)
On Tue, Dec 6, 2022 at 12:35 AM Kate Webbink @.***> wrote:
Many thanks Steve -- got my support
re:Adam's point on avoiding confusion around 'Collection http://purl.org/dc/dcmitype/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 https://ac.tdwg.org/termlist/#dc_type 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 https://docs.google.com/document/d/138Kf5xFyOjpaFuD4YQFE9fJKB5eHgqwj/edit#heading=h.j0agv6572lfl if any help explain how the term meets efficacy/stability needs.
— Reply to this email directly, view it on GitHub https://github.com/tdwg/ac/issues/248#issuecomment-1338791458, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCA2POAPPUMXACQKWVED4DWL3GCDANCNFSM6AAAAAASTOUJXA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Doug M. Boyer, Ph.D. Associate Professor Department of Evolutionary Anthropology Director/Founder MorphoSource Data Repository Duke University Box 90383 Biological Sciences Building 130 Science Drive Durham, NC 27708 919-684-8542 (Fax) 919-668-3348 (Office)
@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.
I changed the definition to remove use of "collection"
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 fordatacite:resourceTypeGeneral
. Because of potential issues with having a local name starting with a non-alphabetic character, the local nameDigital3DResource
was chosen over3DDigitalResource
. 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 fordc: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.