Skip to content

Commit

Permalink
Added patch and tag version
Browse files Browse the repository at this point in the history
Signed-off-by: Steve Springett <[email protected]>
  • Loading branch information
stevespringett committed Aug 9, 2024
1 parent e22383d commit 4c39e4b
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions src/components/InstructionPanel.vue
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,14 @@
<td class="field-name">Tag ID:</td>
<td>The tagId is a globally unique identifier and should be assigned a GUID reference (see ISO/IEC 19770-5 definition for GUID). The tagID provides a unique reference for the specific product, version, edition, revision, etc (essentially, the same binary distribution). If two tagIDs match and the tagCreator is the same, the underlying products they represent are expected to be exactly the same. This allows IT systems to identify if a software item (for example, a patch) is installed simply by referencing the specific tagID value which is likely to be readily available in a software inventory. It is recommended, when possible, that a 16 byte GUID be used for this field as this provides global uniqueness without a significant amount of overhead for space. If use of a 16 byte GUID is not possible, a text based globally unique ID may be constructed, this ID should include a unique naming authority for the tagCreator and sufficient additional details that the tagId is unique for the software product, version, edition, revision, etc. This would likely look as follows (+ is used as a string concatenation symbol): regid + productName + version + edition + revision + ...</td>
</tr>
<tr>
<td class="field-name">Patch:</td>
<td>Set to true if this SWID describes a product patch or modification to a different software element.</td>
</tr>
<tr>
<td class="field-name">Tag Version:</td>
<td>The tag version indicates if a specific release of a software product has more than one tag that can represent that specific release. This may be the case if a software tag producer creates and releases an incorrect tag that they subsequently want to fix, but with no underlying changes to the product the SWID tag represents. This could happen if, for example, a patch is distributed that has a Link reference that does not cover all the various software releases it can patch. A newer SWID tag for that patch can be generated and the tag version value incremented to indicate that the data is updated.</td>
</tr>
</table>
<h2 class="category-title">Tag Creator Fields</h2>
<table>
Expand Down Expand Up @@ -67,3 +75,5 @@ td {
padding: 8px 10px;
}
</style>
<script setup lang="ts">
</script>

0 comments on commit 4c39e4b

Please sign in to comment.