search

w3c-cg / planning

Other
6 stars 0 forks source link

Reusable Domain Modules #10

Open AdamSobieski opened 2 years ago

AdamSobieski commented 2 years ago

This issue is about reusable domain modules, supporting and enabling the capability for domains to import, include, or reference one another.

<domain xmlns="..." version="0.1.5">
  <head>
    <import src="..." />
  </head>
  <body>...</body>
</domain>

With reusable domain modules that can be imported by other domains, there could be well-known or built-in domain modules, e.g., for numerical datatypes, for defining the type for actions, and for defining the types for datasets such as knowledgebases or graphs.

Any thoughts on these topics?

AdamSobieski commented 1 year ago

We might want to look into package management technologies, including package formats, their metadata, and their manifest files, while considering how best to allow teams of content authors to create reusable, interrelated, and interdependent domain modules. This would be particularly useful when domain modules could, like software libraries and components, be versioned or editioned independently of one another.

Also, I recently found Plow, a "package management solution for OWL ontologies, with support for specifying dependencies between packages via SemVer ranges."