transition to anyURI

[ahankinson]

From kep...@edirom.de on August 08, 2011 10:26:56

All existing IDREF attributes will be collected in a datatype of type anyURI. All IDREFs will be collected in a separate datatype with a list of anyURIs.

Original issue: http://code.google.com/p/music-encoding/issues/detail?id=1

[ahankinson]

From pd...@virginia.edu on August 10, 2011 07:20:44

I'll handle this one.

Status: Accepted
Owner: pd...@virginia.edu

[ahankinson]

From pd...@virginia.edu on August 10, 2011 11:31:11

Prcedure --

a. create data.IDREF datatype, analogous to data.URI
b. replace IDREF with data.URI and IDREFS with list of data.URI
c. for consistency, replace <rng:data type="anyURI"/> with <rng:ref name="data.URI"/>
d. Since we'll be using anyURI now, shouldn't we also remove any distinction between internal and external pointing elements; that is, between and and between and ? and can go away.

Adding a new data.IDREF datatype allows a customization that restores the use of IDREF(S).

[ahankinson]

From pd...@virginia.edu on August 10, 2011 12:05:29

Labels: Milestone-ReleaseNext Component-Logic

[ahankinson]

From pd...@virginia.edu on August 12, 2011 12:59:13

This issue was closed by revision r357 .

Status: Fixed

[ahankinson]

From pd...@virginia.edu on August 10, 2011 11:31:11

Prcedure --

a. create data.IDREF datatype, analogous to data.URI
b. replace IDREF with data.URI and IDREFS with list of data.URI
c. for consistency, replace <rng:data type="anyURI"/> with <rng:ref name="data.URI"/>
d. Since we'll be using anyURI now, shouldn't we also remove any distinction between internal and external pointing elements; that is, between and and between and ? and can go away.

Adding a new data.IDREF datatype allows a customization that restores the use of IDREF(S).