Scope of ScHTML. It’s a community-based activity, re-using best practice, but with minimal entry barriers. IOW it can apply to almost every public activity in scholarship (research, education, reference, record). It is not just for submitting publications – it can manage student essays, lab notebooks, Wikipedia entries, chemical databases, etc. See the FAQs http://okfnpad.org/schtml-faqs YOU can contribute questions or suggested answers.
Technology of ScHTML. The minimum entry is simply to be able to create modern well-formed HTML5. Everything beyond that is done by evolving agreements (“conventions”). It can, if necessary, be edited by hand, though we are obviously keen to create a flexible toolchain. In practice this is often already present and a matter of identifying current good tools and good practice.
News from Peter Murray-Rust about the Scholarly HTML (ScHTML) initiative - an activity to develop an HTML5-based markup language for scholarly communication.
Interesting...
Amongst other things, he notes the social and political aspects of this work and the lack of a packaging standard for HTML (which is given as one of the reasons for the current predominance of formats like PDF).
On the latter issue, it is worth noting that HTML5 (as with all other HTML variants) is explicitly a markup language for the Web. Scholarly communication evolved largely off the web. It is not that surprising that there is something of a tension here. This is one of the reasons why it would be nice(r) to see a discussion around changing how scholarly communication happens, given the huge changes brought by the web and social media, rather than just talking about what format is used to ship scholarly content around. In the main, packaging isn't an issue for the web because the distributed nature of stuff is just part of the way things work. It only becomes an issue when you want to talk about non-web approaches, like journals (irrespective of whether they happen to be surfaced on the web or not) that it really becomes an issue. That said, scholarly communication brings with it some particular challenges, like preservation for example, that aren't a major issue for much of the mainstream web. Discuss!
On the former, Peter cites Wikipedia as a (not very good) analogy for the community development of a technology like ScHTML. Seems an odd choice? Looking to community-led standards forums like, say, the Dublin Core, IETF or OASIS might be a better place to start?