Microdata Problem Descriptions - Revision history

Hixie at 21:38, 4 May 2009

2009-05-04T21:38:32Z

← Older revision		Revision as of 21:38, 4 May 2009
Line 9:		Line 9:
	* Paul sometimes gives talks on various topics, and announces them on his blog. He would like to mark up these announcements with proper scheduling information, so that his readers' software can automatically obtain the scheduling information and add it to their calendar. Importantly, some of the rendered data might be more informal than the machine-readable data required to produce a calendar event. ''Also of importance: Paul may want to annotate his event with a combination of existing vocabularies and a new vocabulary of his own design. (why?)''		* Paul sometimes gives talks on various topics, and announces them on his blog. He would like to mark up these announcements with proper scheduling information, so that his readers' software can automatically obtain the scheduling information and add it to their calendar. Importantly, some of the rendered data might be more informal than the machine-readable data required to produce a calendar event. ''Also of importance: Paul may want to annotate his event with a combination of existing vocabularies and a new vocabulary of his own design. (why?)''
	* David can use the data in a web page to generate a custom browser UI for adding an event to our calendaring software without using brittle screen-scraping.		* David can use the data in a web page to generate a custom browser UI for adding an event to our calendaring software without using brittle screen-scraping.
			* http://livebrum.co.uk/: the author would like people to be able to grab events and event listings from his site and put them on their site with as much information as possible retained. "The fantasy would be that I could provide code that could be cut and pasted into someone else's HTML so the average blogger could re-use and re-share my data."
			* User should be able to subscribe to http://livebrum.co.uk/ then sort by date and see the items sorted by event date, not publication date.

	REQUIREMENTS:		REQUIREMENTS:
Line 18:		Line 20:
	* The information should be convertible into a dedicated form (RDF, JSON, XML, iCalendar) in a consistent manner, so that tools that use this information separate from the pages on which it is found have a standard way of conveying the information.		* The information should be convertible into a dedicated form (RDF, JSON, XML, iCalendar) in a consistent manner, so that tools that use this information separate from the pages on which it is found have a standard way of conveying the information.
	* Should be possible for different parts of an event to be given in different parts of the page. For example, a page with calendar events in columns (with each row giving the time, date, place, etc) should still have unambiguous calendar events parseable from it.		* Should be possible for different parts of an event to be given in different parts of the page. For example, a page with calendar events in columns (with each row giving the time, date, place, etc) should still have unambiguous calendar events parseable from it.
			* Should be possible for authors to find out if people are reusing the information on their site.
			* Code should not be ugly (e.g. should not be mixed in with markup used mostly for styling).
			* There should be "obvious parsing tools for people to actually do anything with the data (other than add an event to a calendar)".
			* Solution should not feel "disconnected" from the Web the way that calendar file downloads do.

	----		----

Hixie: /* Annotations */

2009-04-30T04:34:27Z

Annotations

← Older revision		Revision as of 04:34, 30 April 2009
Line 122:		Line 122:
	* Originating vocabulary documents should be discoverable.		* Originating vocabulary documents should be discoverable.
	* Machine-readable vocabulary information shouldn't be on a separate page than the human-readable explanation.		* Machine-readable vocabulary information shouldn't be on a separate page than the human-readable explanation.
			* There must not be restrictions on the possible ways vocabularies can be expressed (e.g. the way DTDs restricted possible grammars in SGML).

	----		----

Hixie: /* Search */

2009-04-28T22:45:39Z

← Older revision		Revision as of 22:45, 28 April 2009
Line 200:		Line 200:

	SCENARIOS:		SCENARIOS:
	* Kjetil is searching for new hardware for his desktop and most of the specs he does not care about too much, but he's decided that he wants a 45 nm CPU with at least a 1333 MHz FSB and at least 2800 MHz clock frequency, and a thermal energy of at most 65 W. The motherboard needs to have at least 2 PCI ports, unless it has an onboard Wifi card, and it needs to accommodate for at least 12 GB of DDR3 RAM, which needs to match the FSB frequency. Furthermore, all components should be well supported by Linux and the RAID controller should have at least RAID acceleration. None of the sites have information about the RAID controllers.		* Kjetil is searching for new hardware for his desktop and most of the specs he does not care about too much, but he's decided that he wants a 45 nm CPU with at least a 1333 MHz FSB and at least 2800 MHz clock frequency, and a thermal energy of at most 65 W. The motherboard needs to have at least 2 PCI ports, unless it has an onboard Wifi card, and it needs to accommodate for at least 12 GB of DDR3 RAM, which needs to match the FSB frequency. Furthermore, all components should be well supported by Linux and the RAID controller should have at least RAID acceleration. None of the manufacturer sites have information about the RAID controllers, that information is only available form various forums.
	* Fred is going to buy a property. The property needs to be close to the forest, yet close to a train station that will take him to town in less than half an hour. It needs to have a stable snow-fall in the winter, and access to tracks that are regularly prepared for XC skating. The property should be of a certain size, and proximity to kindergarten and schools. It needs to have been regulated for residential use and have roads and the usual infrastructure. Furthermore, it needs to be on soil that is suitable for geothermal heating yet have a low abundance of uranium. It should have a good view of the fjord to the southeast.		* Fred is going to buy a property. The property needs to be close to the forest, yet close to a train station that will take him to town in less than half an hour. It needs to have a stable snow-fall in the winter, and access to tracks that are regularly prepared for XC skating. The property should be of a certain size, and proximity to kindergarten and schools. It needs to have been regulated for residential use and have roads and the usual infrastructure. Furthermore, it needs to be on soil that is suitable for geothermal heating yet have a low abundance of uranium. It should have a good view of the fjord to the southeast.

Line 206:		Line 206:
	* Performing search searches should be feasible and cheap.		* Performing search searches should be feasible and cheap.
	* It should be possible to perform such searches without relying on a third-party to seek out the information.		* It should be possible to perform such searches without relying on a third-party to seek out the information.
			* The tool that collects information must not require the information to be marked up in some special way, since manufacturers don't include all the information, and users on forums (where the information can sometimes be found) are unlikely to mark it up in some particularly machine-readable way.

	== Cross-site communication ==		== Cross-site communication ==

Hixie: /* Annotations */

2009-04-28T22:03:20Z

Annotations

← Older revision		Revision as of 22:03, 28 April 2009
Line 104:		Line 104:
	* The syntax should be resilient to intentional copy-and-paste authoring: people copying data into the page from a page that already has data should not have to know about any declarations far from the data.		* The syntax should be resilient to intentional copy-and-paste authoring: people copying data into the page from a page that already has data should not have to know about any declarations far from the data.
	* The syntax should be resilient to unintentional copy-and-paste authoring: people copying markup from the page who do not know about these features should not inadvertently mark up their page with inapplicable data.		* The syntax should be resilient to unintentional copy-and-paste authoring: people copying markup from the page who do not know about these features should not inadvertently mark up their page with inapplicable data.
	* Any additional markup or data used to allow the machine to understand the actual information shouldn't be redundantly repeated.		* Any additional markup or data used to allow the machine to understand the actual information shouldn't be redundantly repeated (e.g. on each cell of a table, when setting it on the column is possible).

	----		----

Hixie: /* Annotations */

2009-04-28T22:02:55Z

Annotations

← Older revision		Revision as of 22:02, 28 April 2009
Line 104:		Line 104:
	* The syntax should be resilient to intentional copy-and-paste authoring: people copying data into the page from a page that already has data should not have to know about any declarations far from the data.		* The syntax should be resilient to intentional copy-and-paste authoring: people copying data into the page from a page that already has data should not have to know about any declarations far from the data.
	* The syntax should be resilient to unintentional copy-and-paste authoring: people copying markup from the page who do not know about these features should not inadvertently mark up their page with inapplicable data.		* The syntax should be resilient to unintentional copy-and-paste authoring: people copying markup from the page who do not know about these features should not inadvertently mark up their page with inapplicable data.
			* Any additional markup or data used to allow the machine to understand the actual information shouldn't be redundantly repeated.

	----		----

Hixie at 19:58, 28 April 2009

2009-04-28T19:58:19Z

← Older revision		Revision as of 19:58, 28 April 2009
Line 64:		Line 64:
	* Tara runs a video sharing web site for people who want licensing information to be included with their videos. When Paul wants to blog about a video, he can paste a fragment of HTML provided by Tara directly into his blog. The video is then available inline in his blog, along with any licensing information about the video.		* Tara runs a video sharing web site for people who want licensing information to be included with their videos. When Paul wants to blog about a video, he can paste a fragment of HTML provided by Tara directly into his blog. The video is then available inline in his blog, along with any licensing information about the video.
	* Fred's browser can tell him what license a particular video on a site he is reading has been released under, and advise him on what the associated permissions and restrictions are (can he redistribute this work for commercial purposes, can he distribute a modified version of this work, how should he assign credit to the original author, what jurisdiction the license assumes, whether the license allows the work to be embedded into a work that uses content under various other licenses, etc).		* Fred's browser can tell him what license a particular video on a site he is reading has been released under, and advise him on what the associated permissions and restrictions are (can he redistribute this work for commercial purposes, can he distribute a modified version of this work, how should he assign credit to the original author, what jurisdiction the license assumes, whether the license allows the work to be embedded into a work that uses content under various other licenses, etc).
			* Flickr has images that are CC-licensed, but the pages themselves are not.
			* Blogs may wish to reuse CC-licensed images without licensing the whole blog as CC, but while still including attribution and license information (which may be required by the licenses in question).

	REQUIREMENTS:		REQUIREMENTS:

Hixie: /* Annotations */

2009-04-28T19:20:01Z

Annotations

@@ Line 77: / Line 77: @@
 == Annotations ==
 USE CASE: Annotate structured data that HTML has no semantics for, and which nobody has annotated before, and may never again, for private use or use in a small self-contained community.
@@ Line 103: / Line 102: @@
 * The syntax should be resilient to intentional copy-and-paste authoring: people copying data into the page from a page that already has data should not have to know about any declarations far from the data.
 * The syntax should be resilient to unintentional copy-and-paste authoring: people copying markup from the page who do not know about these features should not inadvertently mark up their page with inapplicable data.
 ----
@@ Line 110: / Line 126: @@
 SCENARIOS:
 * Fred writes a page about Napoleon. He can highlight the word Napoleon in a way that indicates to the reader that that is a person. Fred can also annotate the page to indicate that Napoleon and France are related concepts.
 == Search ==

Hixie: /* Exposing known data types in a reusable way */

2009-04-28T19:03:21Z

Exposing known data types in a reusable way

← Older revision		Revision as of 19:03, 28 April 2009
Line 48:		Line 48:
	* A scholar and teacher wants to publish scholarly documents or content that includes extensive citations that readers can then automatically extract so that they can find them in their local university library. These citations may be for a wide range of different sources: an interview posted on YouTube, a legal opinion posted on the Supreme Court web site, a press release from the White House.		* A scholar and teacher wants to publish scholarly documents or content that includes extensive citations that readers can then automatically extract so that they can find them in their local university library. These citations may be for a wide range of different sources: an interview posted on YouTube, a legal opinion posted on the Supreme Court web site, a press release from the White House.
	* A blog, say ''htmlfive.net'', copies content wholesale from another, say ''blog.whatwg.org'' (as permitted and encouraged by the license). The author of the original content would like the reader of the reproduced content to know the provenance of the content. The reader would like to find the original blog post so he can leave comments for the original author.		* A blog, say ''htmlfive.net'', copies content wholesale from another, say ''blog.whatwg.org'' (as permitted and encouraged by the license). The author of the original content would like the reader of the reproduced content to know the provenance of the content. The reader would like to find the original blog post so he can leave comments for the original author.
	* ''Chaals could improve the Opera intranet if he had a mechanism for identifying the original source of various parts of a page. ~~(why?)''~~		* Chaals could improve the Opera intranet if he had a mechanism for identifying the original source of various parts of a page, as that would let him contact the original author quickly to report problems or request changes.

	REQUIREMENTS:		REQUIREMENTS:

Hixie: /* Exposing known data types in a reusable way */

2009-04-28T19:02:27Z

Exposing known data types in a reusable way

← Older revision		Revision as of 19:02, 28 April 2009
Line 36:		Line 36:
	* Machine-readable contact information shouldn't be on a separate page than human-readable contact information.		* Machine-readable contact information shouldn't be on a separate page than human-readable contact information.
	* The information should be convertible into a dedicated form (RDF, JSON, XML, vCard) in a consistent manner, so that tools that use this information separate from the pages on which it is found have a standard way of conveying the information.		* The information should be convertible into a dedicated form (RDF, JSON, XML, vCard) in a consistent manner, so that tools that use this information separate from the pages on which it is found have a standard way of conveying the information.
	* Should be possible for different parts of ~~an event~~ to be given in different parts of the page. For example, a page with contact details for people in columns (with each row giving the name, telephone number, etc) should still have unambiguous grouped contact details parseable from it.		* Should be possible for different parts of a contact to be given in different parts of the page. For example, a page with contact details for people in columns (with each row giving the name, telephone number, etc) should still have unambiguous grouped contact details parseable from it.

	----		----

Hixie: /* Blogging */

2009-04-28T19:00:27Z

Blogging

← Older revision		Revision as of 19:00, 28 April 2009
Line 227:		Line 227:
	* Rob wants to publish a large vocabulary in RDFS and/or OWL. Rob also wants to provide a clear, human readable description of the same vocabulary, that mixes the terms with descriptive text in HTML.		* Rob wants to publish a large vocabulary in RDFS and/or OWL. Rob also wants to provide a clear, human readable description of the same vocabulary, that mixes the terms with descriptive text in HTML.

			----

			USE CASE: Allow blogs to be aggregated along subject lines.

			SCENARIOS:
			* At University of Mary Washington, many faculty encourage students to blog about their studies to encourage more discussion using an instance of WordPress MultiUser. A student with have a blog might be writing posts relevant to more than one class. Professors would like to then aggregate relevant posts into one blog.

	== Data extraction from sites without explicit cooperation from those sources ==		== Data extraction from sites without explicit cooperation from those sources ==