Open jordan2175 opened 6 months ago
We talked about this today and the consensus is we should do this. Everyone on the call thought this would be a very good idea. We need to think about how best to do this and what types of deliverables should there be. Some thought that we may need more than 1 type of deliverable that fits in to this class.
There are other types of research papers. Vulnerabilities reports. Threat Intel reports. The could enable peer review of the TC. We would want to figure out how to get these indexed by scholar lists. It could be a revenue driver, the paper can be sponsored by a company. Maybe certain levels of membership get to add their Logo to the paper. A paper could be be supported by these companies and their logos added.
Added text to the following definitions: OASIS Deliverable, OASIS Non-Standards Draft Deliverable, and OASIS Non-Standards Final Deliverable. I also added sections for the following definitions: Technical Report, and Technical Report Draft
We need to create a template for this as well
Things to consider (from Mateusz)
Where will they by published: Zenodo? ArXiv? OASIS website? other? Will they be searchable by Google Scholar?
There are three ways to obtain a DOI number:
Publish with a DOI-assigning publisher (journal or conference, e.g., IEEE)
Self-publish with a DOI-assigning Organization (Possibly what we want):
Use a repository that assigns DOIs:
Another question is, where are we going to host these documents? Under the "publishing TC"? Or are we going to invest in a shared page with all documents with filters, search, metadata, abstract preview, showing the authors, etc.? Both? Or should we utilize arXiv as a publishing source and DOI provider? (The last would be more or less like number 3 in the comment above. However, arXiv has more strict processes than Zenodo.)
I would like to see us create a new deliverable, or series of new deliverables. One of which could be Technical Report. This should be a research based / academic based paper or report. I also strongly believe that this kind of deliverable should have Authors not Editors (thought it may also have Editors). The TC could approve the report to be published but it would be driven by the Authors. OASIS should own the content as it exists in the OASIS Template. But the actual content of the report or paper would be owned by the Authors. Meaning that they could also look to publish this via the IEEE or some other academic journal at a later time. I think there may be other deliverables that would fit into the same vein.