Fix #67 - Stan ContentTypes and R - #508
Conversation
- Add R ContentType (we may want to add .Rda/.RData/.data.R and .Rds). - Add Stan ContentTypes.
Raphael-Gazzotti
added
the
ContentType
lzehl
left a comment
lzehl
left a comment
There was a problem hiding this comment.
Additional notes we should discuss:
Vendor Tree (vnd.): This tree is strictly reserved for media types associated with a commercially or legally recognized corporate entity, foundation, or trademarked software producer.
Personal/Vanity Tree (prs.): This tree is designed for non-commercial, community-driven open-source projects, public experimental formats, and validation schemas not bound to a centralized organization.
Experimental Tree (x.): This tree is explicitly restricted to private, internal software ecosystems or closed development pipelines, and it is never intended for public ecosystem distribution.
Legacy Prefix (x-): This historical, hyphenated notation was the original universal standard for all unregistered formats before it was officially deprecated by the IETF to prevent accidental standardization and structural naming collisions.
https://datatracker.ietf.org/doc/html/rfc6838
https://datatracker.ietf.org/doc/html/rfc6648
| ".r" | ||
| ], | ||
| "isBasedOn": null, | ||
| "name": "text/x-r", |
There was a problem hiding this comment.
According to RFC 6838 Section 3.2, the Vendor Tree is intended for media types associated with a commercially or legally recognized entity.
The R language is owned, copyright-held, and officially governed by The R Foundation for Statistical Computing.
The standard domain and naming authority for this group is r-project.org.
Therefore, namespacing the content type under their official entity designation yields: text/vnd.r-project.r-source
Furthermore R has two versions that are not compatible with each other:
- Legacy R 3.x
- Modern R 4.x
so we may want to include the version information here as well.
| ".R", | ||
| ".r" | ||
| ], | ||
| "isBasedOn": null, |
There was a problem hiding this comment.
text/plain (if we don't have it we should register it)
| "fileExtension": [ | ||
| ".stan" | ||
| ], | ||
| "isBasedOn": [ |
There was a problem hiding this comment.
don't understand this relation. I don't think this is correct. should be text/plain
| "@id": "https://openminds.om-i.org/instances/contentTypes/text_x-r" | ||
| } | ||
| ], | ||
| "name": "text/x-stan", |
There was a problem hiding this comment.
According to RFC 6838 Section 3.3, the Personal/Vanity Tree is explicitly reserved for non-commercial, community-driven, experimental, or open-source software spaces that do not belong to a single centralized corporate entity but are publicly developed.
Stan is an open-source probabilistic programming language managed collectively by its community and developer committees without a singular commercial parent company.
Therefore, utilizing the personal/vanity tree to denote its public, community-standard status yields: text/prs.stan
Furthermore stan has two versions that are not compatible with each other:
- Legacy Stan 2.x
- Modern Stan 3.x
So we may want to include the version information here as well.
| "fileExtension": [ | ||
| ".stanfunctions" | ||
| ], | ||
| "isBasedOn": [ |
There was a problem hiding this comment.
I don't think this is correct. This should be text/plain
| "@id": "https://openminds.om-i.org/instances/contentTypes/text_x-r" | ||
| } | ||
| ], | ||
| "name": "text/x-stanfunctions", |
There was a problem hiding this comment.
According to RFC 6838 Section 3.3, the Personal/Vanity Tree is explicitly reserved for non-commercial, community-driven, experimental, or open-source software spaces that do not belong to a single centralized corporate entity but are publicly developed.
Stan is an open-source probabilistic programming language managed collectively by its community and developer committees without a singular commercial parent company.
Therefore, utilizing the personal/vanity tree to denote its public, community-standard status yields: text/prs.stanfunctions
Furthermore stan has two versions that are not compatible with each other:
- Legacy Stan 2.x
- Modern Stan 3.x
stanfunctions seem to only exist for Stan 3.x (for now); so we may want to include the version information here to be specific.
2 participants
Uh oh!
There was an error while loading. Please reload this page.