[OASIS Issue Tracker] (OSLCCORE-166) Examples of URNs for TRS (or elsewhere) should not use urn-3

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=69227#comment-69227 ] 

Andrii Berezovskyi commented on OSLCCORE-166:
---------------------------------------------

We should use https://tools.ietf.org/html/rfc6963 instead.

> Examples of URNs for TRS (or elsewhere) should not use urn-3
> ------------------------------------------------------------
>
>                 Key: OSLCCORE-166
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-166
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>          Components: TRS
>            Reporter: Nick Crossley
>            Priority: Minor
>
> The examples in the TRS spec use URNs for change events. In those URNs, the scheme urn-3 is used. This scheme is reserved for Harvard University, and should not be used for our examples. A more likely scheme for examples is the uuid namespace:
> urn:uuid:6e8bc430-9c3a-11d9-9669-0800200c9a66



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)