You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: