[ink] a bare anyURI is inadequate as inkml:ink.documentID

Reference:
http://www.w3.org/TR/2006/WD-InkML-20061023/#inkElement

You have given no interoperable definition of what kinds of
assertions constitute "application intent" and content formats should
define what semantics they denote independent of the processors.
So the bounds on when two files can bear the same URI as this
attribute are undefined.

Just don't let yourselves get caught in the rathole around URIs as to
what sort of repeatability constitutes an identity to which such a
symbol can be attached.

Instead, use Dublin Core to identify the contents if there is the
intent for the contents to be a published entity for which it makes
sense to compare identity codes.

In other words, you may use dc:identifier for this symbol but you
should only do that in the context of a dc:creator and a dc:date, for
example.

Al

Received on Tuesday, 19 December 2006 02:08:37 UTC