Description
Append encodeURIComponent(identifier) to the prefix as url.
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.
Append encodeURIComponent(identifier) to the prefix as url.
When to use this tool
Use Persistent Identifier Resolver Prefix Token when you need an explicit identifier split or resolver-string construction.
How to use the tool and how it works
- Enter resolverPrefix, identifier. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read url. Use the output convention below.
Require an HTTP(S)-shaped resolverPrefix ending with slash, a nonempty control-free identifier, and paired surrogates. Append encodeURIComponent(identifier) to the prefix as url.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| resolverPrefix | Resolver Prefix | Required. Text; maximum UTF-16 length 8192. |
| identifier | Identifier | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| url | Url | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"resolverPrefix": "https://example.test/id/",
"identifier": "A/B 2"
},
"output": {
"url": "https://example.test/id/A%2FB%202"
}
}Limitations and assumptions
- The prefix check is lexical rather than full URL validation; the identifier is encoded as one component and no resolver request or persistence guarantee is made.
- 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
Similar or alternative tools
- Identifier Namespace Version Token
Split at the first namespace separator and the final version separator in the tail, requiring nonempty resulting components.
- SKOS Notation Datatype Literal Pair
Serialize notation and datatypeIri as typedIdentity.