Identifier Namespace Version Token Tool

Description

Split at the first namespace separator and the final version separator in the tail, requiring nonempty resulting components.

A qualified identifier combines a local token with a namespace, version, or resolver prefix. Literal structure and URL encoding do not establish global identity or persistence.

Split at the first namespace separator and the final version separator in the tail, requiring nonempty resulting components.

When to use this tool

Use Identifier Namespace Version Token when you need an explicit identifier split or resolver-string construction.

How to use the tool and how it works

Enter identifier, namespaceSeparator, versionSeparator. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read namespace, localToken, version, hasVersion. Inspect hasVersion before interpreting the associated values.

Require distinct nonempty namespace and version separators. Split at the first namespace separator and the final version separator in the tail, requiring nonempty resulting components.^[1]

Input field	Meaning and units	Accepted input
identifier	Identifier	Required. Text; maximum UTF-16 length 8192.
namespaceSeparator	Namespace Separator	Required. Text; maximum UTF-16 length 8192.
versionSeparator	Version Separator	Required. Text; maximum UTF-16 length 8192.

Output field	Interpretation	Returned shape
namespace	Namespace	Required. Text; maximum UTF-16 length 8192.
localToken	Local Token	Required. Text; maximum UTF-16 length 8192.
version	Version	Required. Text; maximum UTF-16 length 8192.
hasVersion	Has Version	Required. Boolean.

json

{
  "input": {
    "identifier": "ns:item@v2",
    "namespaceSeparator": ":",
    "versionSeparator": "@"
  },
  "output": {
    "namespace": "ns",
    "localToken": "item",
    "version": "v2",
    "hasVersion": true
  }
}

Limitations and assumptions

Absent version is an empty-string placeholder with hasVersion false; escaping and a universal identifier syntax are not implemented.
Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Check the namespace authority and use a full URI parser or resolver when actual identifier validity matters.

References

Calculation and input contract: information-science/identifier-namespace-version-token — tool.io

Similar or alternative tools

Persistent Identifier Resolver Prefix Token
Append encodeURIComponent(identifier) to the prefix as url.
Public Term Source Namespace
Serialize source, languageLabel, and term as qualifiedKey without modifying their strings.