Reece H. Dunn

I see how that would work for `fn:parse-html` and the context item, as those would create the system-generated URIs automatically and make them available via `doc` as you said. I...

Another point -- doing something like `$html//template//p/ancestor::body` would not work with the separate document implementation, as the root element of the template document will not have the template as a...

I'm happy to go with option 1 in that case (treating the template sub-items as children) for now, and deferring this to a future XSLT/XPath/XQuery version. That would mean that...

> A *story arc* is an individual story (with a beginning, middle, and end) that has a start and end date that spans one or more episodes/issues. It may be...

Yes I am and yes that makes sense. I proposed several subclasses of `StoryArc` for media-specific story arcs in the issue description like there are for seasons, episodes, etc.

I'm not sure how a story arc can span media types -- media specific story arcs will be the more common. Sure, you can have movie/radio/TV/etc. adaptations of story arcs,...

I'm happy for just the StoryArc type to be added. The motivation for the subtypes is: 1. mirroring the existing PodcastSeries/PodcastSeason/PodcastEpisode, ComicSeries/ComicIssue/ComicStory, etc. types; 2. being able to restrict part...

See https://github.com/DefinitelyTyped/DefinitelyTyped/issues/69932, specifically https://github.com/DefinitelyTyped/DefinitelyTyped/issues/69932#issuecomment-2199585234.

I support being able to perform the set operations on atomic types -- it makes expressions like `(1, 2) union (1, 3)` possible. Having the rules explicitly defined makes it...

@dnovatchev It would be helpful if you could list the desirable generator properties that are missing. Note that the following works without having to keep state in the map: ```xquery...