Skip to content
New issue

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

style: using monospace for identifiers #48

Merged
merged 1 commit into from
Jun 2, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ export const structure = (S) =>
1. Create and describe Concepts.
- All fields _except_ Preferred Label and Base IRI are optional, and are to be used as best fits the needs of your information modeling task.
- Preferred Label is the preferred lexical label for a resource in a given language. In the current version of Taxonomy Manager, the Preferred Label is automatically used as the final segment for a concept's unique identifier (its URI).
- Base IRI is the root IRI (Internationalized Resource Identifier) used to create unique concept identifiers. Unique identifiers allow for the clear an unambiguous identification of concepts across namespaces, for example between https://shipparts.com/vocab#Bow and https://wrappingsupplies.com/vocab#Bow. In the plugin, previously used Base IRI values are pre-populated for new concepts. For a wider introduction to concept identifiers, see [Cool URIs for the Semantic Web](https://www.w3.org/TR/cooluris/).
- Base IRI is the root IRI (Internationalized Resource Identifier) used to create unique concept identifiers. Unique identifiers allow for the clear an unambiguous identification of concepts across namespaces, for example between `https://shipparts.com/vocab#Bow` and `https://wrappingsupplies.com/vocab#Bow`. In the plugin, previously used Base IRI values are pre-populated for new concepts. For a wider introduction to concept identifiers, see [Cool URIs for the Semantic Web](https://www.w3.org/TR/cooluris/).
- Concepts may optionally be added to a Concept Scheme as Top Concepts, to represent the broadest concepts of a particular hierarchy and provide efficient access points to broader/narrower concept hierarchies
- All Concept fields map to elements of the machine readable data model described in the [W3C SKOS Recommendation](https://www.w3.org/TR/skos-reference/).
1. Tag resources with concepts and then integrate into search indexing, filtering, navigation, and semantic web services.
Expand Down
6 changes: 3 additions & 3 deletions src/modules/baseIriField.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -13,16 +13,16 @@ export default [
title: 'Base URI',
type: 'url',
validation: (Rule) =>
Rule.required().error('Please supply a base URI in the format http://example.com/'),
Rule.required().error(`Please supply a base URI in the format 'http://example.com/'`),
description: (
<details>
<summary>
The root URI (Uniform Resource Identifier) used to create unique concept identifiers.
</summary>
<DescriptionDetail>
Unique identifiers allow for the clear an unambiguous identification of concepts across
namespaces, for example between https://shipparts.com/vocab#Bow and
https://wrappingsupplies.com/vocab#Bow.
namespaces, for example between <code>https://shipparts.com/vocab#Bow</code> and {}
<code>https://wrappingsupplies.com/vocab#Bow</code>.
</DescriptionDetail>
<DescriptionDetail>
In most cases, it makes sense for your base URI to be the root or a subdirectory of your
Expand Down