improve-sst-reference #333
Conversation
| @@ -73,9 +73,11 @@ informative: | |||
| title: "Structured Streams: A New Transport Abstraction" | |||
| author: | |||
| - ins: B. Ford | |||
| date: 2007-08 | |||
| date: 2007-10 | |||
There was a problem hiding this comment.
The paper contains a date of August 2007. Where did you find the October date?
There was a problem hiding this comment.
over here: http://www.sigcomm.org/node/2648 - I guess August was the conference date, and October was the publication date.
There was a problem hiding this comment.
xml2rfc should be able to simply cite this paper by its DOI; see https://www.rfc-editor.org/pipermail/rfc-interest/2016-December/009805.html. (But I have no idea how to do this from kramdown.)
There was a problem hiding this comment.
That would give you: https://xml2rfc.tools.ietf.org/public/rfc/bibxml-doi/reference.DOI.10.1145/1282427.1282421.xml?anchor=SST
<reference anchor='SST' >
<front>
<title>Structured streams</title>
<author initials="B." surname="Ford" fullname="Bryan Ford">
<organization></organization>
</author>
<date year="2007" month="October"/>
</front>
<seriesInfo name="ACM SIGCOMM Computer Communication Review" value="Vol. 37, pp. 361"/>
<seriesInfo name="DOI" value="10.1145/1282427.1282421"/>
</reference>
...which is cool, but, for instance, doesn't have the direct link to the actual paper.
There was a problem hiding this comment.
Looking at the kramdown-rfc2629 code, it doesn't look like it yet supports the bibxml7 directory. Here are the currently-supported references:
"RFC" => "bibxml", "I-D" => "bibxml3", "W3C" => "bibxml4", "3GPP" => "bibxml5",
"ANSI" => "bibxml2",
"CCITT" => "bibxml2",
"FIPS" => "bibxml2",
"IANA" => "bibxml2",
"IEEE" => "bibxml2",
"ISO" => "bibxml2",
"ITU" => "bibxml2",
"NIST" => "bibxml2",
"OASIS" => "bibxml2",
"PKCS" => "bibxml2",
There was a problem hiding this comment.
This is odd. This depends on how you write the ref. SIGCOMM was in Aug 2007, the current citation could say Proceedings of ACM SIGCOMM, August 2007. ACM CCR carries all SIGCOMM publications in the next issue, as a special issue, which must have come out in Oct 2007. I'd keep the Proceedings date, since that's what's usually used.
There was a problem hiding this comment.
Yeah, if you cite it as "proceedings", you cite the conference date. If you cite it as published in CCR, you cite the issue publication date.
There was a problem hiding this comment.
Inspired by this, I learned a new appreciation (read: loathing) for ruby in the course of adding DOI support to kramdown. It ended up consequential to solving a bunch of other problems.
|
What are we doing with this PR? |
|
I've fixed the build error and merged as PR #386 (removed the url since it was breaking the 80-col rule. The url is unnecessary anyways.) |
|
I've a PR open on kramdown-rfc2629 that will eventually make this redundant. |
No description provided.