Upgrade Miscellany context to version 1.0.1 #1002
Copy link
Copy link
Labels
activitypub/complianceSpecification complianceSpecification compliancecomponent/vocabActivity Vocabulary relatedActivity Vocabulary related
Description
Activity
- addedcomponent/vocabActivity Vocabulary relatedActivity Vocabulary relatedactivitypub/complianceSpecification complianceSpecification compliance
on Aug 21, 2026 - linked a pull request that will close this issuefix: update miscellany context to 1.0.1 to fix bug with re-compaction #1003
on Aug 21, 2026
Metadata
Metadata
Assignees
Labels
activitypub/complianceSpecification complianceSpecification compliancecomponent/vocabActivity Vocabulary relatedActivity Vocabulary related
Type
Fields
Priority
None yet
Effort
None yet
There is a new version of the miscellany context, 1.0.1. It fixes a bug when re-compacting documents that don't include a type on the boolean terms (
manuallyAcceptsFollowers,sensitive).You can see an example here. The "sensitive" term is re-compacted as "as:sensitive":
https://json-ld.org/playground/next/#json-ld=%7B%22%40context%22%3A%5B%22https%3A%2F%2Fwww.w3.org%2Fns%2Factivitystreams%22%2C%7B%22sensitive%22%3A%22as%3Asensitive%22%7D%5D%2C%22sensitive%22%3Atrue%7D&context=%7B%22%40context%22%3A%5B%22https%3A%2F%2Fwww.w3.org%2Fns%2Factivitystreams%22%2C%22https%3A%2F%2Fpurl.archive.org%2Fmiscellany%2F1.0.0%22%5D%7D&startTab=tab-compacted
The corrected context does not show the same problem; the "sensitive" term is just "sensitive":
https://json-ld.org/playground/next/#json-ld=%7B%22%40context%22%3A%5B%22https%3A%2F%2Fwww.w3.org%2Fns%2Factivitystreams%22%2C%7B%22sensitive%22%3A%22as%3Asensitive%22%7D%5D%2C%22sensitive%22%3Atrue%7D&context=%7B%22%40context%22%3A%5B%22https%3A%2F%2Fwww.w3.org%2Fns%2Factivitystreams%22%2C%22https%3A%2F%2Fpurl.archive.org%2Fmiscellany%2F1.0.0%22%5D%7D&startTab=tab-compacted
It is very frustrating that even when we want to make very stable, normal things, we sometimes have to make small changes. I apologize for the problem.