Test proposal for source_lang property

[peinjoh]

"3.2.1.10 Document Property - Source Language" on CSAF 2.0 and "3.2.2.11 Document Property - Source Language" on CSAF 2.1 state:

The property MUST be present and set for any CSAF document with the value translator in /document/publisher/category. The property SHALL NOT be present if the document was not translated.

Test 6.1.15 covers the first part, i.e. if /document/publisher/category is translator, source_lang must be set.

As far as I understand, the second part, i.e. the source_lang being set on a document that has /document/publisher/category set to anything else than translator, is not covered by a test so far.

Please clarify if this should be covered by a test.

This issue was announced here: https://groups.oasis-open.org/discussion/new-issue-test-proposal-for-source-lang-property

[sthagen]

I think the requirement is not necessarily technical:

The property SHALL NOT be present if the document was not translated.

Could a document quux exiost, where content comes from a document baz written in different source language and the document publisher is still not a translator?

[peinjoh]

I think it can, see below. Is this the correct usage of those fields?

If the document is based on an security researchers article (exp. english), and the article itself is provided in another language as a translation (exp. french), and the article's translation were used as the source of the document. source_lang would be the original article's language (english), lang would be french, the category would not be translator.

An the other hand, the Translator Conformance Target describes

The resulting translated document: [...] provides the /document/source_lang to contain the language of the original document (and SHOULD only be set by CSAF Translators)

I'm not sure what the scope the prose of this conformance target is though.

[sthagen]

Thank you for providing such a use case. I propose to leave the prose as is for now.
I further recommend to the TC, to revisit all classes of possible mixed-language use cases before any change of wording.

[tschmidtb51]

The conformance clause 9 "CSAF Translator" describes that

[t]he program:

• satisfies the "CSAF Post-Processor" conformance profile.

which states:

[...] the post-processor:

• satisfies the "CSAF Consumer" conformance profile.
• satisfies the "CSAF Producer" conformance profile.

So, the hard requirement to set the source_lang AND the document category translator is just imposed on this specific type of tool. Consequently, there can be (and potentially already are) CSAFs that have the source_lang but not the document category translator.

[tschmidtb51]

As far as I understand, the second part, i.e. the source_lang being set on a document that has /document/publisher/category set to anything else than translator, is not covered by a test so far.

BTW: IMHO, that is really hard to test. How do you know that a document was not translated?

[peinjoh]

How do you know that a document was not translated?

Thank you for clearing this up to me! I now understand why testing for this would not make sense.