Scholarly HTML

[mrchristian]

do the scholarly HTML files use this Scholarly markup, I know sounds like a silly question, but just need a reality check. Although w3C group seems inactive, so here https://vivliostyle.github.io/vivliostyle_doc/samples/scholarly/index.html

I'm seeing if I can render the HTML outputs from a 'mining session' using the paginated CSS setup from the lovely Vivliostyle people https://vivliostyle.org/

Like so https://vivliostyle.github.io/vivliostyle.js/viewer/vivliostyle-viewer.html#x=https://vivliostyle.github.io/vivliostyle_doc/samples/scholarly/index.html

I should be able to make an inventory of the papers, somehow, then some custom CSS and might work :-) In terms of outputting as standalone website, MD for internal GitHub viewing will be different.

[petermr]

On Sat, Sep 21, 2019 at 10:08 AM Simon Worthington ***@***.***> wrote: do the scholarly HTML files use this Scholarly markup, I know sounds like a silly question, but just need a reality check. Although w3C group seems inactive, so here https://vivliostyle.github.io/vivliostyle_doc/samples/scholarly/index.html

not really. we designed it and then it was forked and its never really been used.

I'm seeing if I can render the HTML outputs from a 'mining session' using the paginated CSS setup from the lovely Vivliostyle people https://vivliostyle.org/

The nlm2html uses simple html (probably 1.0) and tries to extract semantics in a title attribute. the publishers don't conform so there will need ot be normlization. If you and colleagues are interested and willing this is a good time to think about it

Like so https://vivliostyle.github.io/vivliostyle.js/viewer/vivliostyle-viewer.html#x=https://vivliostyle.github.io/vivliostyle_doc/samples/scholarly/index.html I should be able to make an inventory of the papers, somehow, then some custom CSS and might work :-) In terms of outputting as standalone website, MD for internal GitHub viewing will be different.

do whatever you can and think is useful. you won't break anything.

…

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#19?email_source=notifications&email_token=AAFTCSZFPLB6E2SRCQMR7ODQKXQB5A5CNFSM4IY5SE52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HM2BDSQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFTCS5ERJQOFT7F4I2ZFSTQKXQB5ANCNFSM4IY5SE5Q> .

-- Peter Murray-Rust Founder ContentMine.org and Reader Emeritus in Molecular Informatics Dept. Of Chemistry, University of Cambridge, CB2 1EW, UK