Skip to content

Merge develop into release/15.0.0#1452

Closed
stevenchalem wants to merge 189 commits into
release/15.0.0from
develop
Closed

Merge develop into release/15.0.0#1452
stevenchalem wants to merge 189 commits into
release/15.0.0from
develop

Conversation

@stevenchalem

@stevenchalem stevenchalem commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

Replaced by #1453

Brings release/15.0.0 up to date with changes made for release 14.1.0.

Jamie-SA and others added 30 commits October 22, 2025 14:25
Co-authored-by: Rebecca Younes <rebecca.younes@semanticarts.com>
This reverts commit 2797780.
don't bundle Contributing.md

Co-authored-by: Rebecca Younes <rebecca.younes@semanticarts.com>
Merge `issue-1327-fix-readme` into `main`
@stevenchalem stevenchalem requested a review from rjyounes April 23, 2026 22:37
@stevenchalem

Copy link
Copy Markdown
Contributor Author

I can't resolve these conflicts myself due to branch permissions. Both conflicts are in ontologies/gistCore.ttl and are explained by release notes already on release/15.0.0:

Conflict 1 — gist:Determination
Keep release/15.0.0's rdfs:subClassOf gist:Task and "activity…" definition (per release note #1260 — "Made gist:Determination a direct subclass of gist:Task rather than of gist:Event"). Take develop's "sulfur" spelling in the example.

Conflict 2 — gist:containedText
Keep both sides: release/15.0.0's rdfs:range rdf:PlainLiteral (per release note #1302 — "Set ranges of gist:containedText… to rdf:PlainLiteral") AND develop's refined skos:definition ("Relates an entity containing textual information to the string constituting that textual information."). The two changes aren't semantically conflicting — they just happened to land on adjacent lines.

@rjyounes

Copy link
Copy Markdown
Collaborator

Closing - replaced by #1453.

@rjyounes rjyounes closed this Apr 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.