Consider alternative namespace prefix(es)

[caufieldjh]

The current prefixes, like STANDARDSDATASTANDARDORTOOL, are long, not terribly readable, and more specific than they need to be. Consider alternatives:

• Shorten "standards" to something more project-specific, like "BRIDGE2AI" or "B2AI"
• One namespace for all objects
• Namespace subsets, something like B2AI.TOPIC
• Names instead of numbers - they are much more human-readable, though their uniqueness still needs to be enforced (this will already happen as part of validation)

All namespace changes will require updates to https://github.com/bridge2ai/b2ai-standards-registry and potentially elsewhere in Bridge2AI standards, but it will make for more pleasant and usable standards in the long run.

[caufieldjh]

Decided on namespace subsets:

• B2AI for parent namespace
• B2AI.STANDARD for standards (DataStandardOrTool objects)
• B2AI.SUBSTRATE for data substrates (DataSubstrate objects)
• B2AI.TOPIC for data topics (DataTopic objects)
• B2AI.ORGANIZATION for orgs (Organization objects) - yes, this is long, but would prefer to avoid b2ai.org. The URL is owned by the program but it's just a redirect point.
• B2AI.USECASE for use cases (UseCase objects)

[caufieldjh]

LinkML has problems with prefixes containing periods - they don't translate to Python classes properly. I've used underscores in lieu of periods, so the prefixes are:

• B2AI for parent namespace
• B2AI_STANDARD for standards (DataStandardOrTool objects)
• B2AI_SUBSTRATE for data substrates (DataSubstrate objects)
• B2AI_TOPIC for data topics (DataTopic objects)
• B2AI_ORG for orgs (Organization objects) - note that this is nice n' short now since it won't be confused for a URL.
• B2AI_USECASE for use cases (UseCase objects)