-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add list of previous work that contributed to the science. #199
Conversation
Co-authored-by: Dave Longley <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My earlier comment was hidden:
This (The CG report reference) is effectively the same as the [CCG-RDC-FINAL] reference. I'm fine for spelling it out, but be may want to make the two different references consistent.
The source for CCG-RDC-FINAL is in common/biblio.js.
|
Looks good to me.. |
ON the remark of @davidlehn (#199 (comment)) while it is correct that a proper, scholarly reference system would be nice, let us not spend our time finding one and merging with respec... Alternatively, we could feed all those references into a system like Zotero, and then spit out a properly formatted references. But that would take probably too much time for a one off occasion I agree that the references should be uniform, though. IEEE has a document on citation format: https://ieeeauthorcenter.ieee.org/wp-content/uploads/IEEE-Reference-Guide.pdf, and I am sure that Springer, Elsevier or others have the same. I would think just pick one of those and reformat all references (yes, by hand...) is the shortest and the quickest way of solving this. |
|
According to @iherman 's #199 (comment) , I tried formatting the list made by Manu in my Zotero into the Springer-LNCS format. Some of the references are failing to fetch metadata because they are not scholarly articles. If this LNCS format is okay, I can try making the other ones manually. What do you think?
|
@yamdan, thank you. That looks perfect. Springer's LNCS format is as good as any, the only point that we should be consistent. |
One of them is the proof of correctness and the other is the CCG-RDC-FINAL document -- two documents with very different content, unless I'm missing something?
Yes, I contemplated added Specref entries for every one of those papers... it would take hours to do that (which I don't have). Others are welcome to add all of the entries to specref (but again, doing that for just this spec doesn't seem like a good use of time). So, it's not easy, no... the references were collected over the years from citations in papers that were published in journals (each journal used a slightly different format). I just used the format used in each journal.
Thank you for doing that @yamdan ... any chance you could raise those changes as a change set against this PR? I won't have the spare cycles in the coming weeks to go back through and re-format everything. I'm happy for someone else to take over the reformatting for this PR at this point... it's all editorial work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm perfectly happy with the list of previous work - and I am glad it's in the spec. It shows that this hasn't come out of nowhere and has a long pedigree. One minor gripe - and my apologies if this seems more than a little self-serving - but there is a small group of people who turned up at more or less every meeting who discussed the spec as it evolved and got it through the Rec Track. I'd say they are: Pierre-Antoine, Ivan, Gregg, David, Dave, Kazue, Manu, Ted, Dan, Markus, self. Of course many of those people have, rightly, been credited already but, maybe there's a little space somewhere?
This would usually be added to the Acknowledgements section, but as this is the editors acknowledging others who were helpful in the work. We could add to the end of (or after) the first paragraph the specific contributions of the chairs, Pierre-Antoine, Ivan, Dave, Kazue, Manu, and Ted. Note that Dave and Manu are already called out as participants of the CG. |
I can attempt to make those changes by pushing into your branch (which I believe I can do). It's easier if the branch is on this repo, but possible I believe.
Thanks for getting this far. We still may want to trim the references, as @iherman suggested. |
Co-authored-by: Dave Longley <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Local biblio and respec rendering may have been easier.
Co-authored-by: David I. Lehn <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @gkellogg for updating the list. I found that a few diacritics were removed when I processed it through Zotero...
Co-authored-by: Dan Yamamoto <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks fine to me now, except for my remark on pruning. I won't lie down the road on this, but it looks unnecessary, maybe even presumptuous to me here (there are tons of papers on graph theory, why picking just these few at this point?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the additional work here. Much appreciated.
I did the format update without pushing a decision on pruning. IMO, this sort of depends on what we're trying to achieve. The longer list is probably not practical for people really wanting to dive deep into the history, as it's generally broad, and someone really doing a deep dive might be expected to look at some of the pre-RDF references. Trimming entries prior to RDF may be more concise. This could potentially be a separate issue, and we can merge the work as is, and re-visit the notion of pruning separately. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few small things
Co-authored-by: Ted Thibodeau Jr <[email protected]>
(As agreed in #199 (comment) bringing this as a separate PR.) As argued in #199 (review), I believe it is unnecessary to bring in non-RDF references. It is not meaningful for our readers, and it looks like an arbitrary choice from the _huge_ literature on graph theory in general. (I understand that some of these references may have been relevant for some of the cited works, i.e., they are, sort of, "second level" references. But the only goal of this section is to show that the works relies on a bunch of works that have been done in the RDF community.)
(As agreed in #199 (comment) bringing this as a separate PR.) As argued in #199 (review), I believe it is unnecessary to bring in non-RDF references. It is not meaningful for our readers, and it looks like an arbitrary choice from the _huge_ literature on graph theory in general. (I understand that some of these references may have been relevant for some of the cited works, i.e., they are, sort of, "second level" references. But the only goal of this section is to show that the works relies on a bunch of works that have been done in the RDF community.)
This PR attempts to address issue #19 by adding a history of previous work that contributed to the science that this specification is based upon.
Preview | Diff