/ schemaorg Public
Create hosted extensions for internal admin terminology ("meta.") and things-being-discussed ("pending") #1059
General top level tag for issues on the vocabulary
site tools + python code
Infrastructural issues around schema.org site. Most can ignore this!
type:cleanup + clarity
Addresses wording fixes, ambiguities, confusion, bad examples etc
Now that we have the hosted extensions mechanism, we can use it better within our own workflow and site administration infrastructure.
Currently we have several terms in schema.org which are not intended for widespread public usage, but serve as necessary machinery for structuring our schema descriptions. I propose to migrate these into a "meta.schema.org" extension where they can be more clearly documented as such: at least supersededBy, domainIncludes, RangeIncludes. We still need to add a better mechanism for type and enum deprecation too, that would also live under 'meta'.
Currently it is hard for casual participants, and also busy Steering Group members, to keep track of the status of various proposals. Github Pull Requests are naturally very oriented towards implementation detail. Proposal authors sometimes set up ad-hoc temporary *.appspot.com copies of schema.org to illustrate draft proposals, but these can also be hard to keep track of. The proposal here is to add an explicit "pending.schema.org" hosted extension subdomain where relatively mature, substantive or attractive drafts can be included for easier and more widespread review.
The text was updated successfully, but these errors were encountered: