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

Loom Type URI Schema #3

Open
crutcher opened this issue Feb 13, 2024 · 0 comments
Open

Loom Type URI Schema #3

crutcher opened this issue Feb 13, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@crutcher
Copy link
Owner

Currently, loom types are identified by URLs pointing to Json Schema Document fragments.

For example: http://tensortapestry.org/schemas/loom/2024-01/node_types.jsd#/nodes/Tensor

Note: this URL is not currently live; but the fragment is well-formed in the current execution system, where the documents are provided to the lookup machinery for JSD schemas.

In a given loom graph extension environment, there will be some family of nodes and annotations defined. The validation of node and annotation types, and other machinery which we wish to associate with these types, is independent of the identification of the types.

It is a design goal to be able to extend identification to safe namespaces, presumably namespaced by common names associated with an extension dialect's domain; but also to namespaces which derive from a given generation environment, possibly with a UUID or hash namespace.

This task is to investigate other URI/URN schemes, to act as an extensible namespace for identifying types, with the goal that it is easy to bind handlers for those types in a given LoomEnvironment.

@crutcher crutcher self-assigned this Feb 13, 2024
@crutcher crutcher added enhancement New feature or request help wanted Extra attention is needed labels Feb 13, 2024
@crutcher crutcher added this to the Optimization Demo milestone Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Status: No status
Development

No branches or pull requests

1 participant