We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
legalIdentifier
In orgid-json-schema.yaml file it's just a "string" (example 1), while in vocabulary.md it is an object (example 2).
orgid-json-schema.yaml
vocabulary.md
Example `:
"legalEntity": { "legalName": "Acme, Corp.", "alternativeName": "Acme", "legalIdentifier": "US12345567", "identifiers":
Example 2:
{ "type": "Commercial register number", "value": "CH-170.7.000.838-1" }
The text was updated successfully, but these errors were encountered:
Perhaps it's not a bad idea to do something like this though:
{ "legalEntity": { "legalName": "Acme, Corp.", "legalIdentifier": { "authority": "California Secretary of State", "value": "CA12345567", "uri": "https://businesssearch.sos.ca.gov/" } } }
Sorry, something went wrong.
kostysh
No branches or pull requests
In
orgid-json-schema.yaml
file it's just a "string" (example 1), while invocabulary.md
it is an object (example 2).Example `:
Example 2:
The text was updated successfully, but these errors were encountered: