microformats2-parsing-rdf - Revision history

TomMorris: tidy

2017-02-27T16:29:01Z

tidy

← Older revision		Revision as of 16:29, 27 February 2017
Line 1:		Line 1:
	~~Draft Microformats2-to-RDF~~ mapping		Below is a proposed mapping of the microformats2 data model to RDF.

	~~Tantek asked me~~ to ~~draft up a Microformats2-to-~~RDF ~~mapping. It's pretty straightforward to do. This is rough and will need cleaning up~~.

	== RDF model ==		== RDF model ==

TomMorris: Changed protection level for "microformats2-parsing-rdf": changed protection so elf can edit [move=sysop]

2015-05-31T17:17:27Z

Changed protection level for "microformats2-parsing-rdf": changed protection so elf can edit [move=sysop]

← Older revision	Revision as of 17:17, 31 May 2015
(No difference)

Tantek: Protected "microformats2-parsing-rdf" [edit=autoconfirmed:move=sysop]

2013-04-04T01:03:55Z

Protected "microformats2-parsing-rdf" [edit=autoconfirmed:move=sysop]

← Older revision	Revision as of 01:03, 4 April 2013
(No difference)

Tantek: Reverted edits by ABIDEEN1 (Talk) to last version by Tantek

2013-04-04T00:49:55Z

Reverted edits by ABIDEEN1 (Talk) to last version by Tantek

Show changes

ABIDEEN1 at 23:36, 3 April 2013

2013-04-03T23:36:17Z

Show changes

Tantek: /* Representative hCard parsing */ fix source tag

2012-11-30T23:20:42Z

Representative hCard parsing: fix source tag

← Older revision		Revision as of 23:20, 30 November 2012
Line 220:		Line 220:
	If the parser is able to infer that a representative hCard is present on the page, one can represent this by using <var>foaf:primaryTopic</var> from the [http://xmlns.com/foaf/spec/#term_primaryTopic FOAF specification].		If the parser is able to infer that a representative hCard is present on the page, one can represent this by using <var>foaf:primaryTopic</var> from the [http://xmlns.com/foaf/spec/#term_primaryTopic FOAF specification].

	<source ~~name~~="text">		<source lang="text">
	<> foaf:primaryTopic _:a .		<> foaf:primaryTopic _:a .

TomMorris: should be bold not italics

2012-11-20T10:58:19Z

should be bold not italics

← Older revision		Revision as of 10:58, 20 November 2012
Line 58:		Line 58:
	== Representing root class names ==		== Representing root class names ==

	Root class names map neatly to <code>''rdf:type''</code>. In Notation3, this is represented with the shorthand <code>''a''</code>.		Root class names map neatly to <code>'''rdf:type'''</code>. In Notation3, this is represented with the shorthand <code>'''a'''</code>.

	<source lang="html4strict">		<source lang="html4strict">
Line 74:		Line 74:
	Once we have inferred the class name, we need simply declare the properties.		Once we have inferred the class name, we need simply declare the properties.

	For each <code>''p-''</code> prefixed property, an RDF statement should be produced with the subject being that of the microformats2 object, the property being the namespaced microformats property, and the object being either a plain literal or a language literal containing the string representation of the object (see language section below). This should be equal to the string value in the JSON output.		For each <code>'''p-'''</code> prefixed property, an RDF statement should be produced with the subject being that of the microformats2 object, the property being the namespaced microformats property, and the object being either a plain literal or a language literal containing the string representation of the object (see language section below). This should be equal to the string value in the JSON output.

	=== Multiple properties ===		=== Multiple properties ===
Line 120:		Line 120:
	RDF allows three types of literal: plain literals, language literals and typed literals.		RDF allows three types of literal: plain literals, language literals and typed literals.

	Typed literals contain a datatype annotation, language literals contain a language annotation (the same ISO country codes as is used in HTML's <code>''lang''</code> attribute and XML's <code>''xml:lang''</code> attribute).		Typed literals contain a datatype annotation, language literals contain a language annotation (the same ISO country codes as is used in HTML's <code>'''lang'''</code> attribute and XML's <code>'''xml:lang'''</code> attribute).

	Processors should work out the language tag (if any) of the elements containing microformat properties (using the latest RDFa specification) and emit language-tagged literals for p- prefixed properties. If no language tag is set in the HTML, emit plain literals for all p- prefixed properties.		Processors should work out the language tag (if any) of the elements containing microformat properties (using the latest RDFa specification) and emit language-tagged literals for p- prefixed properties. If no language tag is set in the HTML, emit plain literals for all p- prefixed properties.

TomMorris: cleanup, expand, added multi-lingual example

2012-11-20T10:57:11Z

cleanup, expand, added multi-lingual example

Show changes

TomMorris: put back in para that I accidentally removed by tantek

2012-11-20T00:08:18Z

put back in para that I accidentally removed by tantek

← Older revision		Revision as of 00:08, 20 November 2012
Line 71:		Line 71:

	=== Representative hCard parsing ===		=== Representative hCard parsing ===
			See: [[representative-hcard-parsing#representative_hCard_algorithm\|representative hCard algorithm]], which operates on an already parsed data model, and thus works the same way.

	If the parser is able to infer that a representative hCard is present on the page, one can represent this by using <var>foaf:primaryTopic</var> from the [http://xmlns.com/foaf/spec/#term_primaryTopic FOAF specification].		If the parser is able to infer that a representative hCard is present on the page, one can represent this by using <var>foaf:primaryTopic</var> from the [http://xmlns.com/foaf/spec/#term_primaryTopic FOAF specification].

	<source ~~lang="text"~~>		<source>
	<> foaf:primaryTopic _:a .		<> foaf:primaryTopic _:a .

TomMorris: lang is text

2012-11-20T00:07:05Z

lang is text

← Older revision		Revision as of 00:07, 20 November 2012
Line 73:		Line 73:
	If the parser is able to infer that a representative hCard is present on the page, one can represent this by using <var>foaf:primaryTopic</var> from the [http://xmlns.com/foaf/spec/#term_primaryTopic FOAF specification].		If the parser is able to infer that a representative hCard is present on the page, one can represent this by using <var>foaf:primaryTopic</var> from the [http://xmlns.com/foaf/spec/#term_primaryTopic FOAF specification].

	<source>		<source lang="text">
	<> foaf:primaryTopic _:a .		<> foaf:primaryTopic _:a .