W3C home > Mailing lists > Public > semantic-web@w3.org > July 2014

Making sense of Linked Research

From: carmen <_@whats-your.name>
Date: Thu, 24 Jul 2014 20:25:36 +0000
To: semantic-web@w3.org
Message-ID: <20140724202536.GA4131@x.clearwire-wmx.net>
> XHTML+RDFa and has screen and print stylesheets. The screen styles are what you would normally see in your Web browser

it appears a "handheld" stylesheet was selected here, due to a screen-size if():
and (max-device-width : 1024px) {
body { font-size: 2em; }
/*end of @media handheld*/

are em sizes cumulative? 3.5em and 130% are also in there and now everything's enormous http://i.imgur.com/GMAZsMg.png
body should = 1em, as the device's useragent will pick an appropriate pixel size given display DPI?

ctrl-(---) beats usual text-nonexistence issues, with JS+Cookies required and now if google-analytic's _gaq() or similarly-named doesn't fire that often tends to exception-out things before the JS got around to loading the text, assuming you'd even enabled it - so don't block ads either.. maybe postfacto or with even more JS to supply a simulacra of google's scripts which feign success

> Go ahead and dereference the URI to RDF.

 curl -IH "Accept: application/rdf+xml, text/n3, text/turtle" http://csarven.ca/sense-of-lsd-analysis
HTTP/1.1 200 OK
Content-Type: text/html;

would 406 be more appropriate, as curl didn't ask for text/html, or a wildcard that would match it like */*? http://tools.ietf.org/html/rfc7231#section-6.5.6

> jump through hoops and fire to access a PDF document

and also respect to those who don't make this a nightmare. a lot of workshops seem to be using 

http://ceur-ws.org/Vol-1097/

tho weird doc-format, forces the notion of physical pages of which a single column never fits on physical screen-heights, which wouldn't be a problem if one could just linearly scroll downwards but pages are 2-column necessitating a scroll back up and across then back across again when done,+ needing a PDF plugin, which for whatever licensing reasons hasn't been included in popular linux distribution's chromium/mozilla builds until a clean-roomed pure-JS version recently came along which unfortunately is just too slow on anything less than bleeding-edge hardware, which makes even a modern webpage feel as fast and convenient as a nice C programming displaying to a vt100 terminal on localhost

surely there is more to academia than proving conformity to baroque conventions, if that is even a thing - here accomodating foremost/exclusively people who want to print layout-lossless on paper or fast-machines/huge-screens (niche) vs publishing in HTML or UTF-8 text

> get its act together to eat its own dogfood. The community is at best stuck on *1-star*

some are dog-fooding.. maybe we should highlight successes and important failed-attempts , in case people are too modest to mention their own work relentlessly to get over the noise of us stodgy luddite-whiners who can smell reinvention from page-boundaries away

Geocities-style LD hosting for anyone, based on trivially-implemented and/or freely-available static file hosting,
https://github.com/lmatteis/ldstatic

shipping, customer-tested RDF validation systems
http://mw.logbook.am/thread/20140720135821.GC30771@w3.org#/msg/8ff/CAHb4HxhX36kRujBZVVbwWKOthYdJYVZ4qiS4tFHaCEtWJACA@mail.gmail.com

writing decent articles,
http://ruben.verborgh.org/blog/2013/11/29/the-lie-of-the-api/
Received on Thursday, 24 July 2014 20:25:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:42:52 UTC