Skip to content

Conversation

@PhRosenberger
Copy link
Contributor

Reference to a related issue in the repository

Related to #356

Add a description

This is my proposal for a citation style. Please check before I change all existing citations and add missing ones.

Mention a member

@jdsika could you do the check?

Check the checklist

  • My code and comments follow the style guidelines and contributors guidelines of this project.
  • I have performed a self-review of my own code.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests / travis ci pass locally with my changes.

@PhRosenberger PhRosenberger mentioned this pull request Jan 22, 2020
@jdsika jdsika added this to the v3.1.3 milestone Jan 22, 2020
@jdsika jdsika requested a review from vkresch January 22, 2020 16:14
@jdsika jdsika added the Documentation Everything which impacts the quality of the documentation and guidelines. label Jan 22, 2020
@jdsika
Copy link
Contributor

jdsika commented Jan 22, 2020

What citation style is this?

- For more than 3 authors, place "et al." after the third one
- For more than 1 editor, place "et al." after the first one
- Naming pages at the end is optional, to ease finding in long texts or for direct citations
- Scheme is as follows (replace tags with corresponding values):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree

@PhRosenberger
Copy link
Contributor Author

What citation style is this?

It is similiar to APA, but not identical. Here, the is at the end, whereas APA defines the in () after the author.

We can go for APA completely to have something standardized.
What do you think?

In the meantime, I continue and try out italic in document title of the reference, so there will be some slight changes.

@PhRosenberger PhRosenberger changed the title Documentation/citation style WIP:Documentation/citation style Jan 23, 2020
@jdsika
Copy link
Contributor

jdsika commented Jan 23, 2020

Complete apa is good.

@PhRosenberger
Copy link
Contributor Author

So we will go for full APA style.

@PhRosenberger
Copy link
Contributor Author

I have pushed the citation style section in the doc.
Next step is to change existing citations and add missing ones.

@vkresch
Copy link
Contributor

vkresch commented Jan 24, 2020

@jdsika @PhRosenberger Just as side note for checking the sphinx rst syntax I use this site.

Copy link
Contributor

@vkresch vkresch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PhRosenberger Thank you for the standardization according to DIN overall looks really good. I only found really minor issues and small questions.

**Citation style for different sources:**

- Within the text, the number system is used with the number of the source in brackets [#] for mentioning.
- We use the so called "APA style"`link <https://apastyle.apa.org/>`_ from the American Psychological Association for referencing ().
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change the link into "APA style <https://apastyle.apa.org/>_" and remove the brackets at the end.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the support, will be changed.

- In the references list, the number in brackets [#] is followed by a full citation.
- For writing the title in italic, use <em>title</em>
- Author names are written as <surname>, <initial(s)> like Authorname, A. A.
- Editor names are written as <initial(s)> <surname> like B. B. Editorname
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Minor issue) Decide on consistent period usage for bullet points.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

//
// \par References:
// - [2] SHEPARD, Frank D. Reduced visibility due to fog on the highway.
// - [2] SHEPARD, Frank D. <em>Reduced visibility due to fog on the highway.</em>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the bullet point here be removed too like in the example in comment.rst?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not done with the .proto files, so yes, I will remove the bullet points.

// - [2] SHEPARD, Frank D. Reduced visibility due to fog on the highway.
// - [2] SHEPARD, Frank D. <em>Reduced visibility due to fog on the highway.</em>
// Transportation Research Board, 1996.
// - [3] [StVO 17 chapter
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, too? (bullet point removal)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

Copy link
Contributor Author

@PhRosenberger PhRosenberger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jdsika @PhRosenberger Just as side note for checking the sphinx rst syntax I use this site.

I use CLion as IDE, which has y build in interpreter, which is very comfy:-)

//
// \par Reference:
// [1] Rapp, C.: Grundlagen der Physik, in: Hydraulik für Ingenieure und Naturwissenschaftler, Springer Vieweg, Wiesbaden, 2017, p. 105
// [1] Rapp, C. (2017). Grundlagen der Physik. <em>In Hydraulik für Ingenieure und Naturwissenschaftler</em> (pp.23-36). Springer Vieweg. Wiesbaden, Germany. https://doi.org/10.1007/978-3-658-18619-7_3. p. 105.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I am wondering if the length of the line for the reference in the comments could be to long like this.
@vkresch and @jdsika is there a limitation or style-standard for this?

@PhRosenberger
Copy link
Contributor Author

So, I am done with the existing citations. For adding new citations, where they are missing, I would propose to create a new branch. Actually, it took a lot of time to find a good citation style and especially for correcting the existing ones, so finding missing citations will take probably even more time.

A possible work-around could be to wait for ISO23150 to be publicly available and cite this then. What do you think, @jdsika, @vkresch, and others?

@PhRosenberger
Copy link
Contributor Author

Actually, the line breaking with " \n " from the last commit fails because of the non-ASCII testing.
Should we change the code or the test?

@vkresch
Copy link
Contributor

vkresch commented Jan 27, 2020

@PhRosenberger it's mostly because of the character "ß" in "Straßenverkehrs-Ordnung" and "ü" in "für". So basically we need to decide if we want to cite only in english or only in german. If we decide on german then we need to remove the non-ascii test. This could cause some bugs/erros in the doxygen generation since this is the reason behind the test. This should be tested accordingly.
To stay with german we could also use "ue" instead of "ü" and "ss" instead of "ß".
@jdsika what do you think?

@jdsika
Copy link
Contributor

jdsika commented Jan 27, 2020

I would go for an "english only" style

@PhRosenberger
Copy link
Contributor Author

I would go for an "english only" style

Does this mean only English sources?
Could be difficult regarding e.g. DIN standards..

I prefer to change writing into "ss", "ue", "ae", and "oe".

@PhRosenberger
Copy link
Contributor Author

Ready for merge into master now.

@PhRosenberger
Copy link
Contributor Author

PhRosenberger commented Feb 5, 2020

@jdsika and @vkresch can we merge this branch now?
Still open:

  • Is there a limitation on line legth for the citations as comments?
  • Is writing the German letters ü, ä, ö, ß with ue, oe, ae, ss fine for everybody?

@jdsika jdsika requested a review from vkresch February 5, 2020 14:32
@jdsika
Copy link
Contributor

jdsika commented Feb 5, 2020

I am fine with ö as oe!
@vkresch please review

Copy link
Contributor

@vkresch vkresch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I'm not sure if the line length influences the doxygen ouput. Normally it shouldn't.

@jdsika jdsika merged commit b64133d into master Feb 5, 2020
@jdsika
Copy link
Contributor

jdsika commented Feb 5, 2020

@PhRosenberger thank you very much - good job!

@pmai pmai deleted the documentation/citation-style branch April 27, 2020 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Everything which impacts the quality of the documentation and guidelines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants