Courses/Wikis-Publishing Platforms - Revision history

Andre at 12:28, 30 March 2020

2020-03-30T12:28:08Z

← Older revision		Revision as of 12:28, 30 March 2020
Line 1:		Line 1:
	~~<slidy theme="a"/>~~

	~~<div style="background:#BFFCFF;width:70%; padding:3px">~~

	=Course Description=		=Course Description=
	== Titel ==		== Titel ==
Line 50:		Line 50:
	** comprehending syntax as a structured language - a markup language - compatible to HTML and other markups, which results in the easy and lossless translation to many publishing formats and forms: websites, EPUBs, paper (through Scribus/inDesign), visual maps (SVG).		** comprehending syntax as a structured language - a markup language - compatible to HTML and other markups, which results in the easy and lossless translation to many publishing formats and forms: websites, EPUBs, paper (through Scribus/inDesign), visual maps (SVG).
	* exploring the possibilities of the wiki's API, as a way to programmatically access information from the wiki, opening up the possibilities for creating generative wikis, which are constantly informed by updates on the wiki.		* exploring the possibilities of the wiki's API, as a way to programmatically access information from the wiki, opening up the possibilities for creating generative wikis, which are constantly informed by updates on the wiki.
	~~</div>~~

	__TOC__		__TOC__
Line 60:		Line 60:
	==Wiki Intro - What are wikis?==		==Wiki Intro - What are wikis?==

	~~==http://publicationstation.wdka.hro.nl/wiki Publishing Platforms==~~

	== Context: wikis as (hybrid) publishing platforms ==		== Context: wikis as (hybrid) publishing platforms ==

Andre: /* Web APIs */

2016-02-24T10:27:04Z

Web APIs

← Older revision		Revision as of 10:27, 24 February 2016
Line 404:		Line 404:

	==Web APIs==		==Web APIs==
	Mediawiki API is a [http://en.wikipedia.org/wiki/Application_programming_interface#Web_APIs Web ~~APIs~~].		Mediawiki API is a [http://en.wikipedia.org/wiki/Application_programming_interface#Web_APIs Web API].

	Essentially it means that the API is accessed thought '''HTTP requests''' and responds using '''JSON or XML object'''.		Essentially it means that the API is accessed thought '''HTTP requests''' and responds using '''JSON or XML object'''.

	==Mediawiki API==		==Mediawiki API==

Andre: /* For whom */

2016-01-18T09:39:19Z

For whom

← Older revision		Revision as of 09:39, 18 January 2016
Line 40:		Line 40:
	== For whom ==		== For whom ==

	For anyone interested in ~~digital/hybrid publishing~~.		For anyone who's interested in finding simple and experimental ways to publish content on the web and in other supports.


	= Course Goals =		= Course Goals =

Andre: /* Planning */

2016-01-18T09:36:33Z

Planning

← Older revision		Revision as of 09:36, 18 January 2016
Line 19:		Line 19:

	== Planning ==		== Planning ==

	~~During three sessions, we'll focus on:~~
	* getting to know Wikis: Wikis origins, goals, and relevance in todays web; But also its syntax, structure,		* getting to know Wikis: Wikis origins, goals, and relevance in todays web; But also its syntax, structure,
	* converting Wiki pages into other formates, using Pandoc: website(HTML pages), EPUB, ICML(inDesign project)		* converting Wiki pages into other formates, using Pandoc: website(HTML pages), EPUB, ICML(inDesign project)

Andre at 10:45, 24 June 2015

2015-06-24T10:45:33Z

@@ Line 1: / Line 1: @@
 <slidy theme="a"/>
-Wikis as Publishing Platforms - 3 x 3 hours course
+<div style="background:#BFFCFF;width:70%; padding:3px">
-[[Wikis-Publishing_Platforms/synopsis and goals]]
+== Instructor ==
 =Day 1=

Andre: /* Day 3: Remediation */

2015-06-02T13:15:04Z

Day 3: Remediation

← Older revision		Revision as of 13:15, 2 June 2015
Line 343:		Line 343:
	We'll continue looking re-mediations of wiki content. In the next day we'll focus on the MediaWiki API, an interface to Mediawiki wikis, which allows retrieving and editing content programatically.		We'll continue looking re-mediations of wiki content. In the next day we'll focus on the MediaWiki API, an interface to Mediawiki wikis, which allows retrieving and editing content programatically.

	=Day 3: Remediation=		=Day 3: Remediation - Mediawiki API=
	''Appropriating and reporposing wikis' content''.		''Appropriating and reporposing wikis' content''.

Andre: /* Day 3: Remediation */

2015-05-20T15:50:17Z

Day 3: Remediation

← Older revision		Revision as of 15:50, 20 May 2015
Line 387:		Line 387:
	* <code>prop=revisions</code> - what [http://www.mediawiki.org/wiki/API:Properties properties] you want from of a page: revision. As no particular revision is specified the latest will be returned		* <code>prop=revisions</code> - what [http://www.mediawiki.org/wiki/API:Properties properties] you want from of a page: revision. As no particular revision is specified the latest will be returned
	* <code>rvprop=content</code> - what specific properties you want from the page revision in question: content. You could also ask for the <code>user</code> who created the last revision, or the <code>comment</code> left by the user. These properties can be combined in a single request. <code>rvprop=content\|user\|comment</code>		* <code>rvprop=content</code> - what specific properties you want from the page revision in question: content. You could also ask for the <code>user</code> who created the last revision, or the <code>comment</code> left by the user. These properties can be combined in a single request. <code>rvprop=content\|user\|comment</code>


	==Example: Page revisions==		==Example: Page revisions==
			??

	==Example: Images in a page==		==Example: Images in a page==
			https://en.wikipedia.org/w/api.php?format=json&action=query&titles=Willem_de_Kooning&prop=images

			==Example: categories a page belongs to==
			https://en.wikipedia.org/w/api.php?format=json&action=query&titles=Willem_de_Kooning&prop=categories

			==Examples: Contributors to a page==
			https://en.wikipedia.org/w/api.php?format=json&action=query&titles=Willem_de_Kooning&prop=contributors

			http://beyond-social.org/wiki/api.php?format=json&action=query&titles=Colophon&prop=contributors

			==Example: Users of a wiki==
			http://beyond-social.org/wiki/api.php?format=json&action=query&list=allusers&aulimit=100

			limit of 100 users


			==Create something with API results==
			Getting wiki's information (content, users, revisions, images, etc) is easy like this.
			Yet, turning it into something else, can be challenging and involve writing scripts to sort the information received from the API calls.

	~~==Example~~: ~~Pages under category==~~		To make life slightly easier for you I'll add a few python scripts that will create:
	~~https://en.wikipedia.org/w/api.php?format=json&action=query&titles=Willem_de_Kooning&prop=categories~~ the ~~categories to which~~ the ~~page Willem_de_Kooning belongs~~ to.		* a map of all the users of a wiki
	~~'''~~		* a history of the recent edits to an article
	~~prop=categories'''~~		* ????

			All these scripts have parameters that affect their behavior, such as the queried wiki page and wiki, dates, etc.

	~~==Examples: Users==~~		All the results are HTML pages, which are driven from template html page, a sort of shell container to the content collected by the API.

			You can change the template's CSS style-sheet as well as structure.

	* what is an API		Just be aware of not changing elements that have <nowiki><!-- container --></nowiki> written inside them.
	** web apis
	* MW API
	* Example of ~~MW API requests~~
	* Python examples

	, an interface to Mediawiki wikis, which allows retrieving and editing content programatically		, an interface to Mediawiki wikis, which allows retrieving and editing content programatically

Andre at 13:09, 20 May 2015

2015-05-20T13:09:28Z

← Older revision		Revision as of 13:09, 20 May 2015
Line 394:		Line 394:

	==Example: Pages under category==		==Example: Pages under category==
			https://en.wikipedia.org/w/api.php?format=json&action=query&titles=Willem_de_Kooning&prop=categories the categories to which the page Willem_de_Kooning belongs to.
			'''
			prop=categories'''


	==Examples: Users==		==Examples: Users==

Andre: /* Day 3: Remediation */

2015-05-20T12:46:59Z

Day 3: Remediation

@@ Line 344: / Line 344: @@
 =Day 3: Remediation=
-Appropriating and reporposing wikis' content.
+''Appropriating and reporposing wikis' content''.
 * what is an API
 ** web apis
@@ Line 354: / Line 405: @@
   , an interface to Mediawiki wikis, which allows  retrieving and editing content programatically
 =Notes on scripts=

Andre at 10:56, 20 May 2015

2015-05-20T10:56:06Z

← Older revision		Revision as of 10:56, 20 May 2015
Line 277:		Line 277:
	There a few web interfaces to Pandoc, such as http://pandoc.org/try/, but they are not as flexible as the command-line interface to Pandoc.		There a few web interfaces to Pandoc, such as http://pandoc.org/try/, but they are not as flexible as the command-line interface to Pandoc.

	==conversions==		==Pandoc conversions: wiki to HTML==
			Convert a file containing mediawiki syntax, into a an HTML file.

			pandoc --from mediawiki --to html5 --standalone input.wiki --output=output.html

			'''pandoc''' - program dedicate to the conversion between different markups.

			'''--from''' - option standing for “from”, is followed by the input format;

			'''--to''' - option standing for “to”, is followed by the output format;

			'''--standalone''' - option standing for “standalone”, produces output with an appropriate header and footer;

			'''--output''' - option for file output;

			'''input.wiki''' - plain-text file with wiki syntax - you need to replace it by its actual name

			==Pandoc conversions: HTML to wiki==
			pandoc --from mediawiki --to html5 --standalone input.wiki --output=output.html

			==Pandoc conversions: wiki to ICML==
			ICML files can be imported into inDesign. See [[Hybrid publishing/publishing resources#working_with_ICML_files ]] for more information.


			==Pandoc conversions: wiki to EPUB==
			It is also possible to use Pandoc to produce an EPUB from a single <pre>.wiki</pre> file, or any other markup accepted by Pandoc.

			A few extra resources, such the cover image, metadata, and stylesheet should be included, as they strongly influence the EPUB's outcome.

			pandoc --from wiki --to epub3 --self-contained --epub-chapter-level=1 --epub-stylesheet=styles.epub.css --epub-cover-image=cover.jpg --epub-metadata=metadata.xml --toc-depth=1 --output=book.epub book.wiki

			New options:
			* '''--epub-chapter-level=1''' - at what titles' level chapters occur: heading 1
			* '''--epub-stylesheet=styles.epub.css''' - css style sheet for epub
			* '''--epub-cover-image=cover.jpg''' - epub cover image
			* '''--epub-metadata=metadata.xml''' -
			* '''--toc-depth=1'''

			Example of metadata.xml
			<source lang="xml">
			<dc:title id="epub-title-1">MAIN TITLE</dc:title>
			<meta refines="#epub-title-1" property="title-type">main</meta>
			<dc:publisher>Your Publisher</dc:publisher>
			<dc:date id="epub-date">2015</dc:date>
			<dc:language>en-US</dc:language>
			<dc:creator id="epub-creator-0">AUTHOR'S NAME</dc:creator>
			<meta refines="#epub-creator-0" property="role" scheme="marc:relators">aut</meta>
			<dc:contributor id="epub-contributor-1">EDITOR'S NAME</dc:contributor>
			<meta refines="#epub-contributor-1" property="role" scheme="marc:relators">edt</meta>
			<dc:contributor id="epub-contributor-5">DESIGNER'S NAME</dc:contributor>
			<meta refines="#epub-contributor-5" property="role" scheme="marc:relators">dsr</meta>
			<dc:subject>TAGS, SEPARATED BY, COMAS</dc:subject>
			<dc:description>PUBLICATION SYNOPSIS</dc:description>
			</source>


			==Conclusion: wiki as hybrid publishing tools==
			Hopefully these examples make more clear what I stated in day#1 wikis are inherently hybrid publishing tools, as
			* wikis are about publishing quickly and easily
			* wiki content can be easily converted to other formats, since it uses a Markup languange.

			As a result many derived works, or re-mediations of wiki content exist. From the more pragmatic examples, such as Wikipedia Export book function, [http://toneelstof.be/ Toneelstof], [http://beyond-social.org/ Beyond Social], or this presentation (both wiki content and slide show); To more artistic interventions such as [http://p-dpa.net/work/iraq-war-wikihistoriography/ The Iraq War: A History of Wikipedia Changelogs] by James Bridle or [http://www.epicpedia.org/ Epicpedia] by Annemieke van der Hoek.


			We'll continue looking re-mediations of wiki content. In the next day we'll focus on the MediaWiki API, an interface to Mediawiki wikis, which allows retrieving and editing content programatically.

			=Day 3: Remediation=
			Appropriating and reporposing wikis' content.

			API or application programming interface is an interface that allows interaction though computer software. It allows things such as apps to be build on top of existing services.
			* what is an API
			** web apis
			* MW API
			* Example of MW API requests
			* Python examples

			, an interface to Mediawiki wikis, which allows retrieving and editing content programatically


	~~=Day 3=~~