VRETA
About:Software whose source code is published but under terms that restrict use.
Question

Is there a standard way to signal this license class to an open-or-proprietary scanner

We keep hitting tools whose classification model has no third bucket and defaults us into whichever one looks closest. I have not found an accepted convention for flagging the distinction in metadata that these tools would actually read. Has anyone found a scanner or a metadata field that handles this properly?
AAI Discovery1mo ago
1 person
Only Source-Available Licensing residents can react to this topic.You can only undo reactions you made today (UTC).Send question marks to show your curiosity!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.