Issue 1079 in gbif-providertoolkit: whitespace free identifiers

[gbif-provi...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement

New issue 1079 by tom.con...@gmail.com: whitespace free identifiers
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=1079

What feature would like to see being added to the IPT?

Although a closed set of valid identifier characters would be too much to
ask for
maybe you could at least disallow white space within the primary identifier.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[gbif-provi...@googlecode.com]

Comment #1 on issue 1079 by timrobertson100: whitespace free identifiers
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=1079

Interesting idea. I don't think DwC itself would make restrictions on
this, but the IPT as an implementation can. I can't see a reason why
whitespace should not be restricted in the IPT as it most likely indicates
an issue.

[gbif-provi...@googlecode.com]

Comment #2 on issue 1079 by danstoner: whitespace free identifiers
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=1079

Blocking all whitespace is probably too restrictive.

White space in an identifier is ok as long as it is prefixed with a proper
namespace that supports it. Some catalog numbers definitely have spaces in
them.

So for example, the following form of a Darwin Core Triple ought to be
marked as suspect:

"XYZ Critters 123 45678"

But the following form of the same information (with colons to properly
denote the namespace) would be ok:

"urn:catalog:XYZ:Critters:341 19044"

Thanks,

- Dan Stoner

[gbif-provi...@googlecode.com]

Comment #3 on issue 1079 by danstoner: whitespace free identifiers

http://code.google.com/p/gbif-providertoolkit/issues/detail?id=1079

Blocking all whitespace is probably too restrictive.

White space in an identifier is ok as long as it is prefixed with a proper
namespace that supports it. Some catalog numbers definitely have spaces in
them.

So for example, the following form of a Darwin Core Triple ought to be
marked as suspect:

"XYZ Critters 123 45678"

But the following form of the same information (with colons to properly
denote the namespace) would be ok:

"urn:catalog:XYZ:Critters:123 45678"

[gbif-provi...@googlecode.com]

Comment #4 on issue 1079 by kyle.br...@gmail.com: whitespace free
identifiers
https://code.google.com/p/gbif-providertoolkit/issues/detail?id=1079

Please be aware this issue has been moved to GitHub:
https://github.com/gbif/ipt/issues/1079 Any work on this issue will be
reported there from now on.