Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link to Open Vocabs in Section 10 from property descriptions #309

Open
clenk opened this issue Mar 7, 2023 · 4 comments
Open

Link to Open Vocabs in Section 10 from property descriptions #309

clenk opened this issue Mar 7, 2023 · 4 comments

Comments

@clenk
Copy link

clenk commented Mar 7, 2023

When reading the description of an object property that uses an open vocabulary or enum, it would be nice to be able to click a link right to the section that defines that vocabulary or enum. Currently I have to either scroll way down to find it, or scroll up to the table of contents to click the link there, or use the search function of my document viewer.

This can be considered low priority and just nice-to-have for a future version of the specification.

@rpiazza
Copy link
Contributor

rpiazza commented Mar 7, 2023

I have always felt the same way. It could be part of STIX 2.1.1 :-)

@jordan2175
Copy link

I proposed this years ago, but I think we should pull all of the vocabularies out of the document and put them in a registry. Either an OASIS Github or OASIS website, or even IANA. This way vocabs could be added to without updating the spec. The versions of the vocab would be defined by the date the were last updated. You would map which vocab version to the STIX version based on the modified timestamp of the STIX object. So if the SDO had a modified timestamp of "March 2023" then the vocab would be the version that was valid at March 2023". Or something like that.

@ejratl
Copy link
Contributor

ejratl commented Mar 14, 2023

We will add the links to 2.1.1.

Removing the vocabs from the specification all together would impact the readability of the specification. However, we can achieve the same result by having open vocab extensions in the STIX common-objects repo that can get updated out of cycle from the document updates. The current OASIS Open STIX validator uses the lists from the spec and would need to be updated to refer to the new extended lists.

@jordan2175
Copy link

I would counter argue that RFCs that point to IANA for their vocabs have been very successful for several decades.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants