Add UUID to requirements (and other specification items)?

[Gedare Bloom]

On Fri, Aug 2, 2019 at 5:17 AM Sebastian Huber
<sebastian.huber at embedded-brains.de> wrote:
>
> Hello,
>
> do you think an UUID
> (https://en.wikipedia.org/wiki/Universally_unique_identifier) is useful
> to have for all requirements (and other specification items)? The
> proposal for identifiers already ensures that all identifiers have a
> proper namespace (e.g. RTEMS), so there is no strong need to have also
> an UUID. It could be useful if you import the RTEMS requirements into
> another system. Support for this would need a patch for Doorstop.
>
> https://github.com/jacebrowning/doorstop/issues/344
>
> I am not sure if it is worth to do this.
>
I think it is better to have the human-readable unique IDs. It makes
references to requirements easier to understand in context. Since we
want those to be unique, and we have central control over generating
them, there's no need for the UUID mechanism.

> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel