Skip to content

Need terminology for a set of linked or embedded schema resources #935

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

Open
handrews opened this issue May 22, 2020 · 0 comments
Open

Need terminology for a set of linked or embedded schema resources #935

handrews opened this issue May 22, 2020 · 0 comments
Labels

Comments

@handrews
Copy link
Contributor

PR #914 had some confusing language around schema resources being linked vs embedded, and how to think about related sets of schema resources and/or documents.

We should probably have a name for this.

@Relequestual said:

I would call this a "transcluded de-referenced bundle".

  • Transclusion is what is done to the schemas
  • De-referenced is the result of the process
  • Bundle is the end product descriptor

Where "this" is a single-document bundle, I guess with as many de-references as possible?

However, the original context was the set of documents/resources that need to be loaded to validate any instance without having to further load more schema resources. Whether they are linked, embedded, bundled, separated, etc.

This is clearly a more complex naming issue. I'm not 100% sold that we really need this for this draft, but if we do, we need to talk out all of the cases so we should do that in an issue.

I'm not putting this issue in any milestone yet, let's see how it goes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Discussion
Development

No branches or pull requests

2 participants