<h1 id="ensure-unique-project-element-names"><a aria-hidden="true" class="anchor-heading icon-link" href="#ensure-unique-project-element-names"></a>Ensure Unique Project Element Names</h1>
<h2 id="notes"><a aria-hidden="true" class="anchor-heading icon-link" href="#notes"></a>notes</h2>
<ul>
<li>e.g., unique part numbers within a project</li>
<li>any instance of a component in DOF needs to have a (fully qualified?) singular definitive name; this should be one-to-one and onto</li>
<li>need to address how this works with sub-projects and name-spacing
<ul>
<li>see object-oriented paradigm</li>
<li>see fully-qualified naming processes</li>
</ul>
</li>
<li>needs to be addressed in m30ml</li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/oshw-pm-user-stories/notes/7ctuobfwqys97iap4qkjwqf">Developer Ensure Unique Project Element Names</a></li>
</ul>

Ensure Unique Project Element Names


# Preamble

Welcome to the *How do you share your Open-Source Hardware project* workshop summary report. During the workshop we worked with participants to identify what we can do as a community to make it easier to share, communicate, and collaborate on OSHW projects. The following content is the result of that work.

![](/assets/oshw-logo.svg){}

# Desired Core Capabilities

![[2-a-better-way.1-core-capabilities]]

# Minimum Required Data Model

![[2-a-better-way.2-pillars]]

# User Stories

![[3-user-stories.user-stories-list]]
