Kingsley, you can go here (http://idpf.org/epub) for info and specs. And you can go here (http://www.pressbooks.com) to access the tool I was talking about in my previous email. EPUB¹s intention is indeed to provide open, ³webby² publication. (Though not all vendors want that - and their rendering engines don¹t have to make use of everything that¹s provided). EPUB can be read by (gasp) Adobe Digital Editions, but many like to use Calibre, which is more open and less proprietary.
On 10/1/14, 2:32 PM, "Kingsley Idehen" <[email protected]> wrote: >On 10/1/14 1:10 PM, Laura Dawson wrote: >> What about EPUB, which is xHTML and has support for Schema.org markup? >>It >> also provides for fixed-layout. > >Laura, > >As long as it reflects what we are requesting of others, in regards to >Linked Open Data publication, it's all good :-) > >Do you have a sample link? > >Kingsley >> >> On 10/1/14, 12:55 PM, "Kingsley Idehen" <[email protected]> wrote: >> >>> On 10/1/14 12:35 PM, Sarven Capadisli wrote: >>>> On 2014-10-01 18:12, Fabien Gandon wrote: >>>>> Dear Saven, >>>> Thank your for your response Fabien. >>>> >>>>> The scientific articles are presenting scientific achievements in a >>>>> format that is suitable for human consumption. >>>>> Documents in a portable format remain the best way to do that for a >>>>> conference today. >>>> I acknowledge the current state of matters for sharing scientific >>>> knowledge. However, the concern was whether ESWC was willing to >>>> promote Web native technologies for sharing knowledge, as opposed to >>>> solely insisting on Adobe's PDF, a desktop native technology. >>>> >>>> If my memory serves me correctly, the Web "took off" not because of >>>> PDF, but due to plain old simple HTML. You know just as well that HTML >>>> was intended for scientific knowledge sharing at large scale, for >>>> human as well as machine consumption. >>>> >>>>> However: >>>>> - all the metadata of the conference are published as linked data >>>>>e.g. >>>>> http://data.semanticweb.org/conference/eswc/2014/html >>>> This is great. But, don't you think that we can and ought to do better >>>> than just metadata? >>>> >>>>> - authors are encouraged to publish, the datasets and algorithms they >>>>> use in their research on the Web following its standards. >>>> I think we all know too well that this is something left as optional >>>> that very few follow-up. There is no reproducibility "police" in SW/LD >>>> venues. Simply put, we can't honestly reproduce the research because >>>> all of the important atomic components that are discussed in the >>>> papers e.g., from hypothesis, variables, to conclusions, are not >>>> precisely identified or easily discoverable. Most of the time, one has >>>> to hunt down the authors for that information. IMHO, this severely >>>> limits scientific progress on Web Science. >>>> >>>> Will you compromise on the submission such that the submissions can be >>>> in PDF and/or in HTML(+RDFa)? >>> +1 >>> >>> We need to get over this hurdle. We can't expect to be taken seriously >>> if we don't wire what we espouse into the fabric of our existence. >>> >>> -- >>> Regards, >>> >>> Kingsley Idehen >>> Founder & CEO >>> OpenLink Software >>> Company Web: http://www.openlinksw.com >>> Personal Weblog 1: http://kidehen.blogspot.com >>> Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen >>> Twitter Profile: https://twitter.com/kidehen >>> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about >>> LinkedIn Profile: http://www.linkedin.com/in/kidehen >>> Personal WebID: >>>http://kingsley.idehen.net/dataspace/person/kidehen#this >>> >>> >> >> > > >-- >Regards, > >Kingsley Idehen >Founder & CEO >OpenLink Software >Company Web: http://www.openlinksw.com >Personal Weblog 1: http://kidehen.blogspot.com >Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen >Twitter Profile: https://twitter.com/kidehen >Google+ Profile: https://plus.google.com/+KingsleyIdehen/about >LinkedIn Profile: http://www.linkedin.com/in/kidehen >Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this > >
