Issue 419 - changing Identity id from URI format to plain string

[kstreeter]

This PR is to address issue #419, where the definition of @id in the Identity schema is too constrained for real usage. This PR changes the field from @id to xdm:id, and updates all of the examples.

[kstreeter]

@chrisdegroot, @cmathis, @jwen-adobe, @cluby-adobe, @saurabhere, @gabebarcelos-adobe this is a proposed breaking change to the Identity schema to address concerns about the need to support unstructured identity values. Please take a look and let me know if this change is acceptable. I know it will have impact on existing data generators, but lets have the schedule impact discussion in another forum and just review technical correctness here. Thank you!

[jwen-adobe]

@kstreeter This looks good from tooling perspective based on my test.

[cdegroot-adobe]

Technically this PR does remove the need for URIs, but the examples still are URIs.

What is the reason we are not using URL encoding? The cases where there are non URL safe characters is a corner case.

[cdegroot-adobe]

This looks clear and addresses the requirements as i understand them.

[saurabhere]

Looks good. So, _id becomes id in XED for identities. Hope this is communicated to all the consumers(UPS, siphon)

[saurabhere]

Can this also include similar changes in the orgunit.schema and geounit.schema ?

[cdegroot-adobe]

@saurabhere this change is limited to the Identity schema. The standard in XDM is to use @id for the globally unique identifier of all entities.

[cdegroot-adobe]

@fmeschbe - we need to include this in the July 16th milestone.

[fmeschbe]

Should we really use an ISBN example where ISBN is already properly covered with an official URN namespace ?

In addition, the xdm:id field is identifyig consumers as per the description, where an ISBN is not exactly a consumer ;-)

[fmeschbe]

This example, while not exactly wrong, does not seem to reflect the intent of this PR.