NIST's Research Data Framework, 37033-37035 [2023-11916]
Download as PDF
ddrumheller on DSK120RN23PROD with NOTICES1
Federal Register / Vol. 88, No. 108 / Tuesday, June 6, 2023 / Notices
if they otherwise meet the scope definition,
regardless of whether they are ready for use
at the time of importation.
The following aluminum extrusion
products are excluded: aluminum extrusions
made from aluminum alloy with an
Aluminum Association series designations
commencing with the number 2 and
containing in excess of 1.5 percent copper by
weight; aluminum extrusions made from
aluminum alloy with an Aluminum
Association series designation commencing
with the number 5 and containing in excess
of 1.0 percent magnesium by weight; and
aluminum extrusions made from aluminum
alloy with an Aluminum Association series
designation commencing with the number 7
and containing in excess of 2.0 percent zinc
by weight.
The scope also excludes finished
merchandise containing aluminum
extrusions as parts that are fully and
permanently assembled and completed at the
time of entry, such as finished windows with
glass, doors with glass or vinyl, picture
frames with glass pane and backing material,
and solar panels. The scope also excludes
finished goods containing aluminum
extrusions that are entered unassembled in a
‘‘finished goods kit.’’ A finished goods kit is
understood to mean a packaged combination
of parts that contains, at the time of
importation, all of the necessary parts to fully
assemble a final finished good and requires
no further finishing or fabrication, such as
cutting or punching, and is assembled ‘‘as is’’
into a finished product. An imported product
will not be considered a ‘‘finished goods kit’’
and therefore excluded from the scope of the
Order merely by including fasteners such as
screws, bolts, etc. in the packaging with an
aluminum extrusion product.
The scope also excludes aluminum alloy
sheet or plates produced by other than the
extrusion process, such as aluminum
products produced by a method of casting.
Cast aluminum products are properly
identified by four digits with a decimal point
between the third and fourth digit. A letter
may also precede the four digits. The
following Aluminum Association
designations are representative of aluminum
alloys for casting: 208.0, 295.0, 308.0, 355.0,
C355.0, 356.0, A356.0, A357.0, 360.0, 366.0,
380.0, A380.0, 413.0, 443.0, 514.0, 518.1, and
712.0. The scope also excludes pure,
unwrought aluminum in any form.
The scope also excludes collapsible tubular
containers composed of metallic elements
corresponding to alloy code 1080A as
designated by the Aluminum Association
where the tubular container (excluding the
nozzle) meets each of the following
dimensional characteristics: (1) length of 37
millimeters (‘‘mm’’) or 62 mm, (2) outer
diameter of 11.0 mm or 12.7 mm, and (3)
wall thickness not exceeding 0.13 mm.
Also excluded from the scope of this Order
are finished heat sinks. Finished heat sinks
are fabricated heat sinks made from
aluminum extrusions the design and
production of which are organized around
meeting certain specified thermal
performance requirements and which have
been fully, albeit not necessarily
individually, tested to comply with such
requirements.
VerDate Sep<11>2014
19:24 Jun 05, 2023
Jkt 259001
Also excluded from the scope of the Order
is certain rectangular wire produced from
continuously cast rolled aluminum wire rod,
which is subsequently extruded to dimension
to form rectangular wire. The product is
made from aluminum alloy grade 1070 or
1370, with no recycled metal content
allowed. The dimensions of the wire are 5
mm (+/¥ 0.05 mm) in width and 1.0 mm (+/
¥ 0.02 mm) in thickness. Imports of
rectangular wire are provided for under
HTSUS category 7605.19.000.
Imports of the subject merchandise are
provided for under the following categories
of the Harmonized Tariff Schedule of the
United States (HTSUS): 6603.90.81.00,
7604.21.00.00, 7604.21.00.10, 7604.21.00.90,
7604.29.10.00, 7604.29.10.10, 7604.29.10.90,
7604.29.30.10, 7604.29.30.50, 7604.29.30.60,
7604.29.30.90, 7604.29.50.30, 7604.29.50.60,
7604.29.50.50, 7604.29.50.90, 7606.12.30.91,
7606.12.30.96, 7608.20.00.30, 7608.20.00.90,
7609.00.00, 7610.10.00, 7610.90.00,
7615.10.20.15, 7615.10.20.25, 7615.10.30,
7615.10.30.15, 7615.10.30.25, 7615.10.50.20,
7615.10.50.40, 7615.10.71, 7615.10.71.25,
7615.10.71.30, 7615.10.71.55, 7615.10.71.80,
7615.10.91, 7615.10.91.00, 7615.19.10,
7615.19.30, 7615.19.50, 7615.19.70,
7615.19.90, 7615.20.00, 7615.20.00.00,
7616.10.90.90, 7616.99.10, 7616.99.50,
7616.99.51, 8302.10.30.00, 8302.10.60.30,
8302.10.60.60, 8302.10.60.90, 8302.20.00.00,
8302.30.30.10, 8302.30.30.60, 8302.41.30.00,
8302.41.60.15, 8302.41.60.45, 8302.41.60.50,
8302.41.60.80, 8302.42.30.10, 8302.42.30.15,
8302.42.30.65, 8302.49.60.35, 8302.49.60.45,
8302.49.60.55, 8302.49.60.85, 8302.50.00.00,
8302.60.90.00, 8305.10.00.50, 8306.30.00.00,
8414.59.60.90, 8415.90.80.45, 8418.99.80.05,
8418.99.80.50, 8418.99.80.60, 8419.90.10.00,
8422.90.06.40, 8424.90.90.80, 8473.30.20.00,
8473.30.51.00, 8479.89.94, 8479.89.98,
8479.90.85.00, 8479.90.94, 8481.90.90.60,
8481.90.90.85, 8486.90.00.00, 8487.90.00.80,
8503.00.95.20, 8508.70.00.00, 8513.90.20,
8515.90.20.00, 8516.90.50.00, 8516.90.80.50,
8517.70.00.00, 8529.90.73.00, 8529.90.97.60,
8536.90.80.85, 8538.10.00.00, 8541.90.00.00,
8543.90.88.80, 8543.90.88.85, 8708.10.30.50,
8708.29.15.00, 8708.29.25.00, 8708.29.50.60,
8708.29.51.60, 8708.80.65.90, 8708.99.68.90,
8714.93.05.00, 8803.30.00.60, 9013.90.50.00,
9013.90.90.00, 9031.90.90.95, 9031.90.91.95,
9401.90.50.81, 9401.99.90.81, 9403.10.00,
9403.20.00, 9403.90.10.40, 9403.90.10.50,
9403.90.10.85, 9403.90.25.40, 9403.90.25.80,
9403.90.40.05, 9403.90.40.10, 9403.90.40.60,
9403.90.50.05, 9403.90.50.10, 9403.90.50.80,
9403.90.60.05, 9403.90.60.10, 9403.90.60.80,
9403.90.70.05, 9403.90.70.10, 9403.90.70.80,
9403.90.80.10, 9403.90.80.15, 9403.90.80.20,
9403.90.80.41, 9403.90.80.51, 9403.90.80.61,
9403.99.10.40, 9403.99.90.10, 9403.99.90.15,
9403.99.90.20, 9403.99.90.41, 9405.99.40.20,
9506.11.40.80, 9506.51.40.00, 9506.51.60.00,
9506.59.40.40, 9506.70.20.90, 9506.91.00.10,
9506.91.00.20, 9506.91.00.30, 9506.99.05.10,
9506.99.05.20, 9506.99.05.30, 9506.99.15.00,
9506.99.20.00, 9506.99.25.80, 9506.99.28.00,
9506.99.55.00, 9506.99.60.80, 9507.30.20.00,
9507.30.40.00, 9507.30.60.00, 9507.30.80.00,
9507.90.60.00, and 9603.90.80.50.
The subject merchandise entered as parts
of other aluminum products may be
classifiable under the following additional
PO 00000
Frm 00029
Fmt 4703
Sfmt 4703
37033
Chapter 76 subheadings: 7610.10, 7610.90,
7615.19, 7615.20, and 7616.99, as well as
under other HTSUS chapters. In addition, fin
evaporator coils may be classifiable under
HTSUS numbers: 8418.99.80.50 and
8418.99.80.60. While HTSUS subheadings
are provided for convenience and customs
purposes, the written description of the
scope of this Order is dispositive.
[FR Doc. 2023–12052 Filed 6–5–23; 8:45 am]
BILLING CODE 3510–DS–P
DEPARTMENT OF COMMERCE
National Institute of Standards and
Technology
NIST’s Research Data Framework
National Institute of Standards
and Technology, Department of
Commerce.
ACTION: Notice of availability; request
for comment.
AGENCY:
The National Institute of
Standards and Technology (NIST) seeks
comments on NIST’s Research Data
Framework (RDaF or Framework). The
RDaF is a tool that aims to help shape
the future of open data access and
research data management. A broader
range of stakeholder views is needed for
refining the next version of the RDaF.
The current draft of the RDaF is
available electronically from the NIST
website at: https://doi.org/10.6028/
NIST.SP.1500-18r1. All individuals and
organizations with influence on and
who are influenced by research data
management are encouraged to offer
their input.
DATES:
For Comments:
Comments must be received by 5 p.m.
Eastern time on July 6, 2023. Written
comments should be submitted
according to the instructions in the
ADDRESSES and SUPPLEMENTARY
INFORMATION sections below.
Submissions received after that date
may not be considered.
ADDRESSES: Comments can be submitted
by either of the following methods:
• Email: rdaf@nist.gov. Include
‘‘Research Data Framework’’ in the
subject line of the message.
Instructions: Attachments will be
accepted in plain text, Microsoft Word,
or Adobe PDF formats. Comments
containing references, studies, research,
and other empirical data that are not
widely published should include copies
or electronic links of the referenced
materials.
All submissions, including
attachments and other supporting
materials, will become part of the public
record and subject to public disclosure.
SUMMARY:
E:\FR\FM\06JNN1.SGM
06JNN1
37034
Federal Register / Vol. 88, No. 108 / Tuesday, June 6, 2023 / Notices
ddrumheller on DSK120RN23PROD with NOTICES1
NIST reserves the right to publish
comments publicly, unedited and in
their entirety. Sensitive personal
information, such as account numbers
or Social Security numbers, or names of
other individuals, should not be
included. Submissions will not be
edited to remove any identifying or
contact information. Do not submit
confidential business information, or
otherwise sensitive or protected
information. Comments that contain
profanity, vulgarity, threats, or other
inappropriate language or content will
not be considered.
FOR FURTHER INFORMATION CONTACT:
Alda Yuan, Physical Scientist, Office of
Data and Informatics, National Institute
of Standards and Technology, 100
Bureau Drive, Gaithersburg, MD 20899,
301–975–2451, or by email to rdaf@
nist.gov.
SUPPLEMENTARY INFORMATION:
I. Background
NIST is leading the development of a
Research Data Framework (RDaF or
Framework) with involvement and
input from national and international
leaders in the broad research data
stakeholder community. Research data
is defined here as ‘‘the recorded factual
material commonly accepted in the
scientific community as necessary to
validate research findings.’’ 1 The RDaF
offers a map of the research data space,
taking a lifecycle approach to organize
research data-related activities and
concepts. Through a community-driven
process, NIST identified organizational
and individual needs and activities tied
to research data management. NIST’s
goal is that all elements of the research
data lifecycle will be defined and
explained to allow for self-assessments
by stakeholders, and that informative
references will provide best practices,
standards, and applicable research for
research data management and
dissemination. The RDaF includes
sample ‘‘profiles’’ that incorporate those
research data management activities
associated with a given job function or
role. Individual researchers and
organizations involved in the research
data lifecycle will be able to tailor these
profiles to suit their unique needs.
The overarching goal of the RDaF is
to provide stakeholders with a
structured approach to develop a
customizable strategy for the
management of research data. The
audience for the RDaF is the entire
research data community, including all
organizations and individuals engaged
in any activities concerned with
12
CFR 200.315(e)(3).
VerDate Sep<11>2014
19:24 Jun 05, 2023
Jkt 259001
research data management, from Chief
Executive Officers and Chief Data
Officers to librarians and researchers.
The RDaF is driven by the research
data stakeholder community who can
use the framework for multiple
purposes, from identifying best
practices for research data management
and dissemination to changing the
research data culture in an organization.
To ensure that the RDaF is a consensus
document, NIST has held community
engagement workshops as the primary
mechanism to gather stakeholder input
on refinements to the preliminary
framework published in February 2021.
Thus far, the workshops have taken
place in three phases, each resulting in
further examination and refinement of
the topics and subtopics in the six
lifecycle stages that form the Framework
Core.
Further refinement of the RDaF Core
requires feedback from a broader range
of potential adopters including
researchers in diverse settings. NIST
aims to create a flexible and modular
system and the RDaF should be able to
accommodate many types of research
data and research tools. To this end,
NIST seeks feedback on both the scope
and completeness of the RDaF Core.
Respondents are encouraged—but are
not required—to respond to each of the
questions below which are relevant to
their role and their position within the
research data management ecosystem.
The questions are organized into
categories covering the content of the
six RDaF lifecycle stages, the topics and
subtopics nested within these stages,
definitions, informative resources,
overarching themes, and customizable
profiles, which are subsets of the more
than 330 stages/topics/subtopics. Civic
participation and evidence-based policy
making require access to research data.
The RDaF will provide government
agencies, public and private
institutions, as well as individual
citizens, with the tools and knowledge
necessary to share high-quality,
reproducible data more easily,
equitably, and safely.
this notice in generating version 2.0 of
the RDaF. However, the following
questions reflect particular areas where
the team would appreciate stakeholder
perspective. When providing feedback
addressing these specific questions, you
may reference the question code to
assist with consideration of your
comment.
NIST is interested in receiving
responses to the following questions
from the stakeholder community:
Section 1—Completeness and Coverage
of the RDaF
1.1 Are the lifecycle stages and the
topics comprehensive? Are any topics
missing?
1.2 Are the subtopics
comprehensive? Are any subtopics
missing?
1.3 Are the overarching themes
comprehensive? Are any missing?
1.4 Is the concept of using profiles
for implementing the RDaF clear? Is it
useful?
1.5 Of the eight generic profiles
offered, is there at least one similar to
your job function? Are there any
additional ones you would suggest?
1.5 Are the informative references
comprehensive? Are any resources
missing?
1.6 What additional organizations
would you add to the key organizations
in Appendix D?
Section 2—RDaF Content
2.1 Are the definitions offered for
the topics clear, correct, and
comprehensive?
2.2 Are the definitions offered for
the subtopics clear, correct, and
comprehensive?
2.3 Do the generic profiles for which
you have personal knowledge typically
cover the most relevant topics and
subtopics for that role?
2.4 Are the informative references
well-tailored to the topics and
subtopics? Do they enable users to fully
explore those topics and subtopics in
greater depth?
2.5 Would a glossary with
definitions of granular terms such as
II. Request for Comments
‘‘tools’’ be helpful or redundant with the
All responses that comply with the
existing subtopic and topic definitions?
requirements listed in the DATES and
2.6 Does the lifecycle stage graphic
ADDRESSES sections of this notice will be (Fig. 1) convey that the various stages
considered. Respondents may organize
are networked and cyclical rather than
their submissions in response to this
sequential and linear?
notice in any manner.
Section 3—Usage of the RDaF
While NIST has reached a certain
level of completeness as a result of
3.1 How do you envision using the
extensive stakeholder engagement, this
Framework?
3.2 Taking one of the generic
notice seeks feedback from a broader
profiles as a guide, how easy would it
group of users, including the general
be for you to create a customized
public. The NIST team will carefully
profile?
consider all feedback obtained through
PO 00000
Frm 00030
Fmt 4703
Sfmt 4703
E:\FR\FM\06JNN1.SGM
06JNN1
Federal Register / Vol. 88, No. 108 / Tuesday, June 6, 2023 / Notices
3.3 Do you envision using the RDaF
as a guide for your individual role or as
an organizational evaluation tool? What
additional tools would assist in either
effort?
3.4 Would you find a network graph
tool that allows free exploration of the
relationships among the various
elements (e.g., topics, subtopics, and
profiles) of the framework useful?
(Authority: 15 U.S.C. 272(b) & (c))
Alicia Chambers,
NIST Executive Secretariat.
[FR Doc. 2023–11916 Filed 6–5–23; 8:45 am]
BILLING CODE 3510–13–P
DEPARTMENT OF COMMERCE
National Oceanic and Atmospheric
Administration
[RTID 0648–XC837]
Taking and Importing Marine
Mammals; Taking Marine Mammals
Incidental to the U.S. Navy Training
and Testing Activities in the Point
Mugu Sea Range Study Area
National Marine Fisheries
Service (NMFS), National Oceanic and
Atmospheric Administration (NOAA),
Commerce.
ACTION: Notice; modification of letter of
authorization.
AGENCY:
NMFS has modified its Letter
of Authorization (LOA) issued to the
United States Navy (Navy) on July 7,
2022, for the taking of marine mammals
incidental to training and testing
activities conducted in the Point Mugu
Sea Range (PMSR) study area and
launch events from San Nicolas Island
(SNI) over the course of seven years
(2022–2029). Specifically, NMFS has
removed certain reporting requirements
related to explosives use, to be
consistent with other LOAs issued for
similar activities conducted by the
Navy. The mitigation and mitigation
related monitoring measures of the LOA
remain unchanged, and the removal of
these reporting measures do not change
the findings made for the regulations or
the original LOA or result in any change
in the number of estimated or
authorized takes.
DATES: The modified LOA is valid
through July 6, 2029.
FOR FURTHER INFORMATION CONTACT:
Craig Cockrell, Office of Protected
Resources, NMFS, (301) 427–8401.
Electronic copies of the original
application and supporting documents
(including NMFS Federal Register
notices of the original proposed and
final rules, and the initial LOA), may be
ddrumheller on DSK120RN23PROD with NOTICES1
SUMMARY:
VerDate Sep<11>2014
19:24 Jun 05, 2023
Jkt 259001
obtained online at: https://
www.fisheries.noaa.gov/action/
incidental-take-authorization-us-navytesting-and-training-activities-pointmugu-sea-range. In case of problems
accessing these documents, please call
the contact listed above.
SUPPLEMENTARY INFORMATION:
Background
The MMPA prohibits the ‘‘take’’ of
marine mammals, with certain
exceptions. Sections 101(a)(5)(A) and
(D) of the MMPA (16 U.S.C. 1361 et
seq.) direct the Secretary of Commerce
(as delegated to NMFS) to allow, upon
request, the incidental, but not
intentional, taking of marine mammals
by U.S. citizens who engage in a
specified activity (other than
commercial fishing) within a specified
geographical region if certain findings
are made and either regulations are
issued or, if the taking is limited to
harassment, a notice of a proposed
incidental take authorization may be
provided to the public for review.
Authorization for incidental takings
shall be granted if NMFS finds that the
taking will have a negligible impact on
the species or stock(s) and will not have
an unmitigable adverse impact on the
availability of the species or stock(s) for
taking for subsistence uses (where
relevant). Further, NMFS must prescribe
the permissible methods of taking and
other ‘‘means of effecting the least
practicable adverse impact’’ on the
affected species or stocks and their
habitat, paying particular attention to
rookeries, mating grounds, and areas of
similar significance, and on the
availability of such species or stocks for
taking for certain subsistence uses
(referred to in shorthand as
‘‘mitigation’’); and requirements
pertaining to the monitoring and
reporting of such takings.
Following rulemaking, NMFS issued
final regulations and an LOA
authorizing the Navy to take marine
mammals, by Level A and Level B
harassment only, incidental to training
and testing activities (which qualify as
military readiness activities) involving
the use of at-surface and near-surface
explosive detonations throughout the
PMSR Study Area, as well as launch
events from San Nicolas Island (SNI).
(87 FR 40888, July 8, 2022). The
regulations and LOA are effective from
July 7, 2022, through July 6, 2029, and
include mitigation, monitoring, and
reporting requirements.
Modification Request and Analysis
On October 11, 2022, NMFS received
a request from the Navy for a
modification of the LOA to remove part
PO 00000
Frm 00031
Fmt 4703
Sfmt 4703
37035
of the reporting requirements in Section
7 of the LOA, which governs the Annual
PMSR Study Area Training and Testing
Activity Report. Specifically, Navy
requested removal of item 7.f.1.(i and
ii), which requires information about
each explosives event completed during
the year and marine mammal
observations by Navy Lookouts in
association with explosives activities.
These requirements are parallel to
those that have been required for higherimpact Navy activities, such as Major
Training Exercises involving multiple
platforms or units utilizing hullmounted active sonar for exercises of
comparatively longer durations (days to
a month) or Sinking Exercise, which
consist of explosive detonations of
higher net explosive weight used to sink
a ship (85 FR 46302; July 31, 2020). In
contrast, these requirements are not
consistent with the required reporting
measures in LOAs issued to the Navy
for explosive activities for all of their
other major training and testing rules
(e.g., Hawaii Southern California
Training and Testing, Atlantic Fleet
Training and Testing), which have been
established through years of
coordination with the Navy after notice
and public comment (85 FR 41780; July
10, 2020 and 84 FR 70712; December 23,
2019), and were inadvertently included
in the PMSR.
In addition to being inconsistent with
the reporting requirements broadly
coordinated with the Navy for similar
activities in LOAs for other areas, the
Navy advises that the measures in
question are infeasible at the PMSR, as
the indicated information cannot be
effectively collected from the aircraft
used in the exercises, due to the speed
and the height of the aircraft; and
additional vessels and personnel are not
allowed in the impact zones.
NMFS’ PMSR incidental take
regulation at 50 CFR 218.17 addresses
LOA modification requests by the
applicant (Navy):
(b) For LOA modification or renewal
requests by the applicant that include
changes to the activity or to the
mitigation, monitoring, or reporting
measures (excluding changes made
pursuant to the adaptive management
provision in paragraph (c)(1) of this
section) that do not change the findings
made for the regulations in this subpart
or result in no more than a minor
change in the total estimated number of
takes (or distribution by species or
years), NMFS may publish a notice of
LOA in the Federal Register, including
the associated analysis of the change,
and solicit public comment before
issuing the LOA.
E:\FR\FM\06JNN1.SGM
06JNN1
Agencies
[Federal Register Volume 88, Number 108 (Tuesday, June 6, 2023)]
[Notices]
[Pages 37033-37035]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2023-11916]
-----------------------------------------------------------------------
DEPARTMENT OF COMMERCE
National Institute of Standards and Technology
NIST's Research Data Framework
AGENCY: National Institute of Standards and Technology, Department of
Commerce.
ACTION: Notice of availability; request for comment.
-----------------------------------------------------------------------
SUMMARY: The National Institute of Standards and Technology (NIST)
seeks comments on NIST's Research Data Framework (RDaF or Framework).
The RDaF is a tool that aims to help shape the future of open data
access and research data management. A broader range of stakeholder
views is needed for refining the next version of the RDaF. The current
draft of the RDaF is available electronically from the NIST website at:
https://doi.org/10.6028/NIST.SP.1500-18r1. All individuals and
organizations with influence on and who are influenced by research data
management are encouraged to offer their input.
DATES:
For Comments:
Comments must be received by 5 p.m. Eastern time on July 6, 2023.
Written comments should be submitted according to the instructions in
the ADDRESSES and SUPPLEMENTARY INFORMATION sections below. Submissions
received after that date may not be considered.
ADDRESSES: Comments can be submitted by either of the following
methods:
Email: [email protected]. Include ``Research Data Framework''
in the subject line of the message.
Instructions: Attachments will be accepted in plain text, Microsoft
Word, or Adobe PDF formats. Comments containing references, studies,
research, and other empirical data that are not widely published should
include copies or electronic links of the referenced materials.
All submissions, including attachments and other supporting
materials, will become part of the public record and subject to public
disclosure.
[[Page 37034]]
NIST reserves the right to publish comments publicly, unedited and in
their entirety. Sensitive personal information, such as account numbers
or Social Security numbers, or names of other individuals, should not
be included. Submissions will not be edited to remove any identifying
or contact information. Do not submit confidential business
information, or otherwise sensitive or protected information. Comments
that contain profanity, vulgarity, threats, or other inappropriate
language or content will not be considered.
FOR FURTHER INFORMATION CONTACT: Alda Yuan, Physical Scientist, Office
of Data and Informatics, National Institute of Standards and
Technology, 100 Bureau Drive, Gaithersburg, MD 20899, 301-975-2451, or
by email to [email protected].
SUPPLEMENTARY INFORMATION:
I. Background
NIST is leading the development of a Research Data Framework (RDaF
or Framework) with involvement and input from national and
international leaders in the broad research data stakeholder community.
Research data is defined here as ``the recorded factual material
commonly accepted in the scientific community as necessary to validate
research findings.'' \1\ The RDaF offers a map of the research data
space, taking a lifecycle approach to organize research data-related
activities and concepts. Through a community-driven process, NIST
identified organizational and individual needs and activities tied to
research data management. NIST's goal is that all elements of the
research data lifecycle will be defined and explained to allow for
self-assessments by stakeholders, and that informative references will
provide best practices, standards, and applicable research for research
data management and dissemination. The RDaF includes sample
``profiles'' that incorporate those research data management activities
associated with a given job function or role. Individual researchers
and organizations involved in the research data lifecycle will be able
to tailor these profiles to suit their unique needs.
---------------------------------------------------------------------------
\1\ 2 CFR 200.315(e)(3).
---------------------------------------------------------------------------
The overarching goal of the RDaF is to provide stakeholders with a
structured approach to develop a customizable strategy for the
management of research data. The audience for the RDaF is the entire
research data community, including all organizations and individuals
engaged in any activities concerned with research data management, from
Chief Executive Officers and Chief Data Officers to librarians and
researchers.
The RDaF is driven by the research data stakeholder community who
can use the framework for multiple purposes, from identifying best
practices for research data management and dissemination to changing
the research data culture in an organization. To ensure that the RDaF
is a consensus document, NIST has held community engagement workshops
as the primary mechanism to gather stakeholder input on refinements to
the preliminary framework published in February 2021. Thus far, the
workshops have taken place in three phases, each resulting in further
examination and refinement of the topics and subtopics in the six
lifecycle stages that form the Framework Core.
Further refinement of the RDaF Core requires feedback from a
broader range of potential adopters including researchers in diverse
settings. NIST aims to create a flexible and modular system and the
RDaF should be able to accommodate many types of research data and
research tools. To this end, NIST seeks feedback on both the scope and
completeness of the RDaF Core. Respondents are encouraged--but are not
required--to respond to each of the questions below which are relevant
to their role and their position within the research data management
ecosystem. The questions are organized into categories covering the
content of the six RDaF lifecycle stages, the topics and subtopics
nested within these stages, definitions, informative resources,
overarching themes, and customizable profiles, which are subsets of the
more than 330 stages/topics/subtopics. Civic participation and
evidence-based policy making require access to research data. The RDaF
will provide government agencies, public and private institutions, as
well as individual citizens, with the tools and knowledge necessary to
share high-quality, reproducible data more easily, equitably, and
safely.
II. Request for Comments
All responses that comply with the requirements listed in the DATES
and ADDRESSES sections of this notice will be considered. Respondents
may organize their submissions in response to this notice in any
manner.
While NIST has reached a certain level of completeness as a result
of extensive stakeholder engagement, this notice seeks feedback from a
broader group of users, including the general public. The NIST team
will carefully consider all feedback obtained through this notice in
generating version 2.0 of the RDaF. However, the following questions
reflect particular areas where the team would appreciate stakeholder
perspective. When providing feedback addressing these specific
questions, you may reference the question code to assist with
consideration of your comment.
NIST is interested in receiving responses to the following
questions from the stakeholder community:
Section 1--Completeness and Coverage of the RDaF
1.1 Are the lifecycle stages and the topics comprehensive? Are any
topics missing?
1.2 Are the subtopics comprehensive? Are any subtopics missing?
1.3 Are the overarching themes comprehensive? Are any missing?
1.4 Is the concept of using profiles for implementing the RDaF
clear? Is it useful?
1.5 Of the eight generic profiles offered, is there at least one
similar to your job function? Are there any additional ones you would
suggest?
1.5 Are the informative references comprehensive? Are any resources
missing?
1.6 What additional organizations would you add to the key
organizations in Appendix D?
Section 2--RDaF Content
2.1 Are the definitions offered for the topics clear, correct, and
comprehensive?
2.2 Are the definitions offered for the subtopics clear, correct,
and comprehensive?
2.3 Do the generic profiles for which you have personal knowledge
typically cover the most relevant topics and subtopics for that role?
2.4 Are the informative references well-tailored to the topics and
subtopics? Do they enable users to fully explore those topics and
subtopics in greater depth?
2.5 Would a glossary with definitions of granular terms such as
``tools'' be helpful or redundant with the existing subtopic and topic
definitions?
2.6 Does the lifecycle stage graphic (Fig. 1) convey that the
various stages are networked and cyclical rather than sequential and
linear?
Section 3--Usage of the RDaF
3.1 How do you envision using the Framework?
3.2 Taking one of the generic profiles as a guide, how easy would
it be for you to create a customized profile?
[[Page 37035]]
3.3 Do you envision using the RDaF as a guide for your individual
role or as an organizational evaluation tool? What additional tools
would assist in either effort?
3.4 Would you find a network graph tool that allows free
exploration of the relationships among the various elements (e.g.,
topics, subtopics, and profiles) of the framework useful?
(Authority: 15 U.S.C. 272(b) & (c))
Alicia Chambers,
NIST Executive Secretariat.
[FR Doc. 2023-11916 Filed 6-5-23; 8:45 am]
BILLING CODE 3510-13-P