Skip to content


Browse files Browse the repository at this point in the history
experiment using URNs as the OID to avoid potential collision somewhere
down the road with generated UUIDs.

OID appears to be limited to 36 characters
  • Loading branch information
James Babb committed Dec 4, 2017
1 parent 3ef5a74 commit b299cdf
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 2 deletions.
18 changes: 17 additions & 1 deletion midpoint/assets/objects/01_sis_resources.xml
@@ -1,6 +1,22 @@
<?xml version="1.0" encoding="UTF-8"?>

<!-- TODO: is hard coding an OID going to be a problem? -->

OIDs can be set to anything as long as they are unique across the entire midpoint installation.
Trying to use a URN to avoid collisions between an institution's own stuff and TIER-provided configs
does work but...
There is a passage about properly generating all OIDs using something like `uuid` but Tom & I read that
as avoiding semantically significant *numeric* OIDs. using something like a URN creates namespaces that
are seperated by the naming convention already.
Something to discuss...

<resource xmlns=""
Expand All @@ -9,7 +25,7 @@


<name>SIS DB Source</name>

Expand Down
2 changes: 1 addition & 1 deletion midpoint/assets/objects/02_sis_tasks.xml
Expand Up @@ -19,7 +19,7 @@
<objectRef oid="6573361b-20c9-4d79-8f00-f1445b5902a1" type="c:ResourceType"><!--SIS DB Source--></objectRef>
<objectRef oid="urn:wisc:midpoint-poc:sis-db" type="c:ResourceType"><!--SIS DB Source--></objectRef>
Expand Down

0 comments on commit b299cdf

Please sign in to comment.