Repository navigation
Conversation
For organisation-level publishing. Adds optional activity, location and ageRange fields to Organization, which extends the oa:activity and oa:ageRange domains to schema:Organization (schema:location already applies to Organization). Rewords both published definitions in Course.json, the alphabetically first declaring model, so they are no longer event-only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings Organization in line with Modelling Opportunity Data 2.1 Editor's Draft section 5.8.1 (describing an Organization independent of any specific event): - location also accepts an array of Place, a PostalAddress or text. allowReferencing is not set, as the .NET generator does not support it with multiple types; an @id reference is accepted as text. - New optional fields: genderRestriction, alternateName, memberOf (an @id or an Organization) and member (one @id or an array). - A stand-alone Organization in feed mode, either the top-level object ($) or an RPDE item's data, requires name, activity and location, and recommends @id, description, url, sameAs, email and telephone. Organizations in other fields, such as organizer and provider, are unaffected. - FeedItem accepts kind "Organization" and an Organization as data. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Modelling Opportunity Data section 5.8.1 makes beta:dateVerified REQUIRED for organisation-level data. Add it to the required fields for a stand-alone Organization in feed mode (the top-level object and an RPDE item's data). The validator checks that it is present; data must include the beta namespace in @context for it to be recognised. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hkir-dev
approved these changes
Nov 12, 2026
| "#PostalAddress" | ||
| ], | ||
| "alternativeTypes": [ | ||
| "https://schema.org/Text" |
There was a problem hiding this comment.
do we need this. Place.address with a String value can be used for this purpose
| "model": "#Place", | ||
| "alternativeModels": [ | ||
| "ArrayOf#Place", | ||
| "#PostalAddress" |
There was a problem hiding this comment.
do we need this. Place.address with a PostalAddress value can be used for this purpose
| "model": "#Organization", | ||
| "allowReferencing": true, | ||
| "description": [ | ||
| "The `@id` of an organization that this organization is affiliated to. For example, a club can link to its national governing body." |
There was a problem hiding this comment.
This can be an id or a nested Organization object. Description should be updated accordingly.
| "member": { | ||
| "fieldName": "member", | ||
| "sameAs": "https://schema.org/member", | ||
| "requiredType": "ArrayOf#https://schema.org/URL", |
There was a problem hiding this comment.
should this be ArrayOf#Organization instead of URL with "allowReferencing": true
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merging releases data-models 3.0.12 and dispatches the usual updates (validator site, model libraries, developer documentation, test suite).
Summary
Supports publishing data about organisations in their own right, as described in Modelling Opportunity Data 2.1 Editor's Draft section 5.8.1 and discussed in openactive/modelling-opportunity-data#313.
Organization:activity,location,ageRange,genderRestriction,alternateName,memberOf,memberandlicense.locationaccepts aPlace, an array ofPlace, aPostalAddressor text, as in the spec.RPDEFeed), either the top-level object or an RPDE item'sdata, requiresname,activity,locationandbeta:dateVerified, pluslicensefor the top-level object only, and recommends@id,description,url,sameAs,emailandtelephone. This usesimperativeConfigurationWithContextwith the containing field names$anddata, so Organizations used asorganizer,provideror elsewhere are unaffected.FeedItem: acceptskind"Organization"and an Organization asdata.Vocabulary:
oa:activity,oa:ageRangeandoa:genderRestrictiongainschema:Organizationin their domains. The published definitions ofoa:activityandoa:ageRange(taken fromCourse.json) are reworded so they are no longer event-only.Notes
beta:dateVerifiedis in the beta namespace, so data must include"https://openactive.io/ns-beta"in@context(after"https://openactive.io/") for it to be recognised. The validator checks that it is present, not the date format.license: an Organization published on its own must carry its license; one in an RPDE feed should not, as the feed page gives it (spec: Correct the Organization level section and examples modelling-opportunity-data#323). The validator does not flaglicensein a feed item, asshallNotIncludewould make it a failure rather than a SHOULD NOT. The field hassameAsschema:license(as inDataset), which themodels-spec.jsnaming test requires; in data,licensestill expands todc:licensethrough the OpenActive context.locationdoes not setallowReferencing: the .NET generator does not support it on a field with several types. An@idreference is still accepted, as text.$anddatanames. It should be merged after this is released.Verification
activityandlocation; a stand-alone Organization fails withoutlicense, and a feed item without it passes; an organizer in aSessionSeriesis unaffected in both feed modes; the new field types are accepted and invalid values rejected. The corrected spec example passes with no failures.Schema.NET.3DModelforbeta:virtualTour, also in OpenActive.NET#63). The .NETLicenseproperty is generated withnewalthoughSchema.NET.Organizationhas noLicense, which gives warning CS0109 only.When squash-merging, check the suggested commit message does not contain a skip-CI marker.