OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (COEL-164) "Unique" Pseudonymous Keys

     [ https://issues.oasis-open.org/browse/COEL-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Snelling updated COEL-164:

For case 1 verify that an error is to returned in case of a clash when registering new CIDs and DIDs.

Add non-normative text to section 7.1 describing moving data between DEs generally and in the case of a clash.

> "Unique" Pseudonymous Keys 
> ---------------------------
>                 Key: COEL-164
>                 URL: https://issues.oasis-open.org/browse/COEL-164
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Improvement
>         Environment: Whole document
>            Reporter: Joss Langford
> Can we guarantee uniqueness of keys issued by the IDA unless it holds records (which it does not)? The Data Engine can guarantee uniqueness as it does hold the records and you should not be able to register the same key twice (although I haven’t tested this and I don’t think we have specified it). I think we are relying on the standard low clash rates for GUIDs - but is this clear?

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]