Comments (8)
@paolobrasolin the syntax looks great to me! If there is no group
given we can keep the reference in the "default" reference group.
from asciidoctor-bibliography.
I agree with @opoudjis that we have a strong need to separate bibliography groups. However I don't think BibTeX is the right place to do it because it corrupts the BibTeX file -- the BibTeX file is simply the database for ALL bibliography items and is often just a huge collection that is shared between multiple documents (sorry I do that a lot).
On the other hand, the MMark concept of "upgrading" bibliography item types from "informative" to "normative" does not resonate with me because the groups are simply "different".
How about we consider something like this?
cite:[rfc1234,group="group1"]
cite:[rfc2345,group="group2"]
[bibliography]
=== Group 1 References
bibliography::[group1]
=== Group 2 References
bibliography::[group2]
from asciidoctor-bibliography.
I agree that grouping should be done in the document, not the bibtex file.
We should also consider the possibility that one bibliography item can belong to two or more groups.
from asciidoctor-bibliography.
Indeed, and the decision whether a bibliography item should belong to multiple groups should be decided by the βciterβ.
from asciidoctor-bibliography.
I agree with @ronaldtse and @blablatros in thinking that DB data should be agnostic with respect to groupings. Groups are in essence "roles" and will almost surely depend upon the specific use the citer makes of the entries.
I gave some thought to groupings when writing the macro parser and laid some simple groundwork.
What I had in mind was using the target syntax for asciidoctor macros. I.e.:
cite:group1[rfc1234]
cite:group2[rfc2345]
[bibliography]
=== Group 1 References
bibliography::group1[]
=== Group 2 References
bibliography::group2[]
How does that look?
from asciidoctor-bibliography.
That works. The abbreviations "norm" and "info" are going to be more user-friendly, and we can assume them for asciidoctor-rfc.
from asciidoctor-bibliography.
It is better to let the users choose group names.
For example, social sciences, especially history, often groups references into "primary" and "secondary".
from asciidoctor-bibliography.
@blablatros indeed we should allow users to choose group names.
I think @opoudjis just means that in the asciidoctor-rfc
gem we could have some special syntax to use those bibliography groups, because those are specific requirements of an RFC. Or perhaps we don't even need to specify those specific groups at all since the syntax above is quite clean and simple?
from asciidoctor-bibliography.
Related Issues (20)
- Bug with custom attributes when translating to DocBook HOT 3
- Question: own styles HOT 1
- :bibliography-database: not set via asciidoctor-epub3 for included documents HOT 6
- Bib entry with identical author and year HOT 18
- Minor APA format issue HOT 4
- Converting directly with Ruby HOT 2
- Variable interpolation breaks include
- anomalies when using Asciidoctor's ifeval::[] and asciidoctor-bibliography HOT 3
- Errors with asciidoctor-pdf HOT 2
- Numbered bibliography
- Comparison with asciidoc-bib and asciidoctor-bibtex
- A problem building Nokogiri, when installing on Windows HOT 7
- Migrate to GitHub Actions from Travis
- Change default branch to main HOT 1
- Including "bibliography:[]" without using citations in document throws error
- The generated bibliography is incomplete HOT 6
- Citations get parsed within inline source code environment HOT 2
- Multi-Citation of more than two keys not working HOT 5
- [enhancement] nocite macro for bibliography entry without expicit citation HOT 1
- Incompatibility with asciidoctor version >= 2.0 HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from asciidoctor-bibliography.