Requirements for Active Output Terminal Labeling

Brought to you by: b-andersen, dwieschebrock, eichelberg, kathrin, martinuro

#63 Requirements for Active Output Terminal Labeling

Milestone: Clean-up

Status: closed

Owner: Martin

Labels: currently in discussion (2) PhysicalConnector (4)

Updated: 2022-02-15

Created: 2021-05-31

Creator: Martin

Private: No

Do we need a section on the labeling for active output terminals in terms of physical connectors? See requirements R5004, R5005, R5006 (maybe more).

Human readable labels are meant by this ticket.

Related

10721 HF Device Content Gathering: ~~#34~~
10721 HF Device Content Gathering: ~~#36~~

Discussion

Martin - 2021-09-16

assigned_to: Martin

Milestone: 12.0 Q2-2021 --> 13.0: Q3-2021
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -1 +1,3 @@
-Do we need a section on the labeling for active output terminals in terms of physical connectors? See requirements R5004, R5005, R5005 (maybe more)
+Do we need a section on the labeling for active output terminals in terms of physical connectors? See requirements R5004, R5005, R5006 (maybe more).
+
+Human readable labels are meant by this ticket.

Martin - 2021-10-19

labels: --> currently in discussion

status: open --> in-doc

Milestone: 13.0: Q3-2021 --> 14.0: Q4-2021
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martin - 2021-10-19

Requirements and clarification added, see commits [c02955] and [6cc986] -> currently section 6.1.1.2 "Physical Connectors and Labeling of Virtual Terminals"

See commit [0812f0] for current document.

Related

Commit: [0812f0]
Commit: [6cc986]
Commit: [c02955]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martin - 2021-10-19

labels: currently in discussion --> currently in discussion, PhysicalConnector
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martin - 2022-01-24

Milestone: 14.0: Q4-2021 --> Clean-up
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martin - 2022-01-24

@all Review the current content.

When PKP is fully stable, we can check whether we can reduce the number of requirements, e.g., R5006 might be fully covered by BPKP and could be reduced to a note.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martin - 2022-01-31

status: in-doc --> expert-review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martin - 2022-02-15

status: expert-review --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martin - 2022-02-15

Successfully reviewed during tCon 15.02.2022

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.