You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: