https://www.w3.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=DanbriW3C Wiki - User contributions [en]2024-03-28T13:17:19ZUser contributionsMediaWiki 1.41.0https://www.w3.org/wiki/index.php?title=RdfSyntax&diff=115475RdfSyntax2023-01-31T17:03:37Z<p>Danbri: </p>
<hr />
<div>__NOTOC__<br />
RDF has no single syntax; RDF is just a standard way of modeling ideas. That said, it's gotta be expressed.<br />
<br />
= RDF Serializations =<br />
<br />
(Trying to make this list as comprehensive as possible. If you know of one I've missed, link to it here.)<br />
<br />
Various forms are:<br />
* XML-based:<br />
** '''[[RdfXmlSyntax]] ("RDF/XML syntax")''' - the most common<br />
** [http://infomesh.net/2001/07/bswl/ Basic Semantic Web Language (BSWL)]<br />
** [http://www.w3.org/TR/grddl/ GRDDL] - not really a serialization in itself but a way of mapping from non-RDF XML to RDF.<br />
** [http://swdev.nokia.com/rdfx/RDFX.html RDFX] - includes excellent support for reification (assertions about assertions)<br />
** [http://www.textuality.com/xml/RPV.html RPV]<br />
** [http://asynchronous.org/rx/ Rx] - a similar feel to RDF/XML<br />
** [http://wiki.oasis-open.org/office/RXR RXR] - similar to TriX<br />
** [http://www.wasab.dk/morten/blog/archives/2008/04/04/introducing-spog SPOG] - a dialect of the SPARQL XML results format.<br />
** [http://djpowell.net/schemas/treetriples/1/SyntaxSpec.html TreeTriples]<br />
** [http://sw.nokia.com/trix/TriX.html TriX] - a "raw"-ish XML form<br />
** Ideas that don't seem fully-formed (yet):<br />
*** [http://lists.w3.org/Archives/Public/www-rdf-interest/2002Mar/0128 Notation3 in XML] - sketch of an idea<br />
*** [http://infolab.stanford.edu/~melnik/rdf/syntax.html Simplified Syntax for RDF] (property names are not URIs??)<br />
*** [http://lists.w3.org/Archives/Public/www-rdf-interest/2003Jun/0076 XENT] - sketch of an idea; Turtle/XML hybrid.<br />
* [[NotationThree]], which has various dialects, some of which go beyond the RDF data model (as does N3 itself):<br />
** [http://www.w3.org/2000/10/swap/grammar/n3rules-report.html N3 Rules]<br />
** [http://www.w3.org/2000/10/swap/grammar/n3rdf-report.html N3 RDF]<br />
** [[ShorthandRDF]]<br />
** [http://www.dajobe.org/2004/01/turtle/ Turtle] - Terse RDF Triple Language<br />
** [[PieNt]] -- essentially an early draft of Turtle.<br />
** [http://www.w3.org/TR/rdf-testcases/#ntriples N-Triples] - a "raw" form; just lists of [[triple]]s<br />
** [http://www4.wiwiss.fu-berlin.de/bizer/TriG/ TriG]<br />
** [http://buzzword.org.uk/2009/microturtle/spec MicroTurtle]<br />
** [http://sw.deri.org/2008/07/n-quads/ N-Quads]<br />
* JSON-based:<br />
** [http://json-ld.org/ JSON-LD] - Rather than force RDF on developers, eases developers into RDF, using models they're already familiar with deploying.<br />
** [http://n2.talis.com/wiki/RDF_JSON_Specification RDF/JSON]<br />
*** [http://n2.talis.com/wiki/RDF_PHP_Specification RDF PHP] - same idea, but PHP code rather than JSON.<br />
** [http://code.google.com/p/backplanejs/wiki/Rdfj Rdfj]<br />
** [http://buzzword.org.uk/2008/jsonGRDDL/spec jsonGRDDL] - analogous to XML's GRDDL<br />
** [http://weborganics.co.uk/dataset/ Dataset Transformations] - Uses json to navigate the contents of html and outputs the result as RDF/XML<br />
** [[JSON+RDF]] - a more in-depth look at the state of RDF in JSON.<br />
* [https://t.co/ishnxfrCxU RDF/POST] - serialization on top of application/x-www-form-urlencoded ([http://www.lsrn.org/semweb/rdfpost.html previous URL] and [https://web.archive.org/web/20230000000000*/http://www.lsrn.org/semweb/rdfpost.html history])<br />
* HTML embedded:<br />
** [http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml eRDF]<br />
** [[RDFa]] ("XHTML+RDFa"), plus other RDFa host languages:<br />
*** [http://www.w3.org/TR/SVGTiny12/ SVG 1.2 Tiny]<br />
*** [http://developer.yahoo.com/searchmonkey/smguide/datarss.html DataRSS (RDFa in Atom)]<br />
*** HTML+RDFa<br />
** [[poshRDF]]<br />
** [[N3inHTML]]<br />
** [http://inamidst.com/sw/hturtle/ hTurtle]<br />
** [http://www.w3.org/TR/microdata/ Microdata] - an offshoot of the HTML5 spec<br />
* [http://evan.prodromou.name/RDF_serialization_to_s-expressions RDF as S-expressions]<br />
* [http://www.urf.name/specification/ Uniform Resource Framework (URF)] - a superset of RDF.<br />
<br />
== Comparison ==<br />
<br />
(This doesn't need to be quite as comprehensive.)<br />
<br />
{| border="1" cellpadding="2" cellspacing="0"<br />
| '''Syntax'''<br />
| '''Basis'''<br />
| '''Named Graphs'''<br />
| '''Rules'''<br />
| '''Status'''<br />
|-<br />
| RDF/XML<br />
| XML<br />
| no<br />
| no<br />
| W3C Rec<br />
|-<br />
| TriX<br />
| XML<br />
| yes<br />
| no<br />
| proposal<br />
|-<br />
| SPOG<br />
| XML, SPARQL Results<br />
| yes<br />
| no<br />
| SPARQL result format is a W3C Rec<br />
|-<br />
| Notation3<br />
| -<br />
| yes<br />
| yes<br />
| W3C Team Submission<br />
|-<br />
| Turtle<br />
| Notation3<br />
| no<br />
| no<br />
| W3C Team Submission<br />
|-<br />
| N-Triples<br />
| Notation3<br />
| no<br />
| no<br />
| W3C Rec (sort of)<br />
|-<br />
| TriG<br />
| Notation3<br />
| yes<br />
| no<br />
| proposal<br />
|-<br />
| RDF/JSON<br />
| JSON<br />
| no<br />
| no<br />
| proposal on Talis wiki<br />
|-<br />
| RDF/POST<br />
| HTTP<br />
| no<br />
| no<br />
| proposal<br />
|-<br />
| eRDF<br />
| (X)HTML<br />
| no<br />
| no<br />
| proposal on Talis wiki<br />
|-<br />
| XHTML+RDFa<br />
| XHTML<br />
| no, but [http://buzzword.org.uk/2009/rdfa4/spec proposed]<br />
| no<br />
| W3C Rec<br />
|-<br />
| Microdata<br />
| (X)HTML<br />
| no<br />
| no<br />
| W3C WD<br />
|}<br />
<br />
== Limited Syntaxes ==<br />
<br />
Some serializations are only capable of representing a subset of the RDF data model.<br />
<br />
* RDF/XML requires property URIs to be encoded as XML QNames. Some URIs cannot be abbreviated this way. In practice, vocabulary designers tend to take this into account, so it's not much of a problem.<br />
* Microdata cannot represent datatypes for literals, and cannot handle cyclical relationships between blank nodes.<br />
* BSWL doesn't support blank nodes.<br />
* Certain unicode control characters are forbidden by XML, even when escaped as numeric character references. Unless an XML-based RDF serialisation provides an additional escaping mechanism, literals containing these characters cannot be serialised.</div>Danbrihttps://www.w3.org/wiki/index.php?title=RdfSyntax&diff=115474RdfSyntax2023-01-31T17:02:45Z<p>Danbri: updated url as requested in https://twitter.com/namedgraph/status/1620454540406571009</p>
<hr />
<div>__NOTOC__<br />
RDF has no single syntax; RDF is just a standard way of modeling ideas. That said, it's gotta be expressed.<br />
<br />
= RDF Serializations =<br />
<br />
(Trying to make this list as comprehensive as possible. If you know of one I've missed, link to it here.)<br />
<br />
Various forms are:<br />
* XML-based:<br />
** '''[[RdfXmlSyntax]] ("RDF/XML syntax")''' - the most common<br />
** [http://infomesh.net/2001/07/bswl/ Basic Semantic Web Language (BSWL)]<br />
** [http://www.w3.org/TR/grddl/ GRDDL] - not really a serialization in itself but a way of mapping from non-RDF XML to RDF.<br />
** [http://swdev.nokia.com/rdfx/RDFX.html RDFX] - includes excellent support for reification (assertions about assertions)<br />
** [http://www.textuality.com/xml/RPV.html RPV]<br />
** [http://asynchronous.org/rx/ Rx] - a similar feel to RDF/XML<br />
** [http://wiki.oasis-open.org/office/RXR RXR] - similar to TriX<br />
** [http://www.wasab.dk/morten/blog/archives/2008/04/04/introducing-spog SPOG] - a dialect of the SPARQL XML results format.<br />
** [http://djpowell.net/schemas/treetriples/1/SyntaxSpec.html TreeTriples]<br />
** [http://sw.nokia.com/trix/TriX.html TriX] - a "raw"-ish XML form<br />
** Ideas that don't seem fully-formed (yet):<br />
*** [http://lists.w3.org/Archives/Public/www-rdf-interest/2002Mar/0128 Notation3 in XML] - sketch of an idea<br />
*** [http://infolab.stanford.edu/~melnik/rdf/syntax.html Simplified Syntax for RDF] (property names are not URIs??)<br />
*** [http://lists.w3.org/Archives/Public/www-rdf-interest/2003Jun/0076 XENT] - sketch of an idea; Turtle/XML hybrid.<br />
* [[NotationThree]], which has various dialects, some of which go beyond the RDF data model (as does N3 itself):<br />
** [http://www.w3.org/2000/10/swap/grammar/n3rules-report.html N3 Rules]<br />
** [http://www.w3.org/2000/10/swap/grammar/n3rdf-report.html N3 RDF]<br />
** [[ShorthandRDF]]<br />
** [http://www.dajobe.org/2004/01/turtle/ Turtle] - Terse RDF Triple Language<br />
** [[PieNt]] -- essentially an early draft of Turtle.<br />
** [http://www.w3.org/TR/rdf-testcases/#ntriples N-Triples] - a "raw" form; just lists of [[triple]]s<br />
** [http://www4.wiwiss.fu-berlin.de/bizer/TriG/ TriG]<br />
** [http://buzzword.org.uk/2009/microturtle/spec MicroTurtle]<br />
** [http://sw.deri.org/2008/07/n-quads/ N-Quads]<br />
* JSON-based:<br />
** [http://json-ld.org/ JSON-LD] - Rather than force RDF on developers, eases developers into RDF, using models they're already familiar with deploying.<br />
** [http://n2.talis.com/wiki/RDF_JSON_Specification RDF/JSON]<br />
*** [http://n2.talis.com/wiki/RDF_PHP_Specification RDF PHP] - same idea, but PHP code rather than JSON.<br />
** [http://code.google.com/p/backplanejs/wiki/Rdfj Rdfj]<br />
** [http://buzzword.org.uk/2008/jsonGRDDL/spec jsonGRDDL] - analogous to XML's GRDDL<br />
** [http://weborganics.co.uk/dataset/ Dataset Transformations] - Uses json to navigate the contents of html and outputs the result as RDF/XML<br />
** [[JSON+RDF]] - a more in-depth look at the state of RDF in JSON.<br />
* [https://t.co/ishnxfrCxU RDF/POST] - serialization on top of application/x-www-form-urlencoded (http://www.lsrn.org/semweb/rdfpost.html previous URL] and [https://web.archive.org/web/20230000000000*/http://www.lsrn.org/semweb/rdfpost.html history])<br />
* HTML embedded:<br />
** [http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml eRDF]<br />
** [[RDFa]] ("XHTML+RDFa"), plus other RDFa host languages:<br />
*** [http://www.w3.org/TR/SVGTiny12/ SVG 1.2 Tiny]<br />
*** [http://developer.yahoo.com/searchmonkey/smguide/datarss.html DataRSS (RDFa in Atom)]<br />
*** HTML+RDFa<br />
** [[poshRDF]]<br />
** [[N3inHTML]]<br />
** [http://inamidst.com/sw/hturtle/ hTurtle]<br />
** [http://www.w3.org/TR/microdata/ Microdata] - an offshoot of the HTML5 spec<br />
* [http://evan.prodromou.name/RDF_serialization_to_s-expressions RDF as S-expressions]<br />
* [http://www.urf.name/specification/ Uniform Resource Framework (URF)] - a superset of RDF.<br />
<br />
== Comparison ==<br />
<br />
(This doesn't need to be quite as comprehensive.)<br />
<br />
{| border="1" cellpadding="2" cellspacing="0"<br />
| '''Syntax'''<br />
| '''Basis'''<br />
| '''Named Graphs'''<br />
| '''Rules'''<br />
| '''Status'''<br />
|-<br />
| RDF/XML<br />
| XML<br />
| no<br />
| no<br />
| W3C Rec<br />
|-<br />
| TriX<br />
| XML<br />
| yes<br />
| no<br />
| proposal<br />
|-<br />
| SPOG<br />
| XML, SPARQL Results<br />
| yes<br />
| no<br />
| SPARQL result format is a W3C Rec<br />
|-<br />
| Notation3<br />
| -<br />
| yes<br />
| yes<br />
| W3C Team Submission<br />
|-<br />
| Turtle<br />
| Notation3<br />
| no<br />
| no<br />
| W3C Team Submission<br />
|-<br />
| N-Triples<br />
| Notation3<br />
| no<br />
| no<br />
| W3C Rec (sort of)<br />
|-<br />
| TriG<br />
| Notation3<br />
| yes<br />
| no<br />
| proposal<br />
|-<br />
| RDF/JSON<br />
| JSON<br />
| no<br />
| no<br />
| proposal on Talis wiki<br />
|-<br />
| RDF/POST<br />
| HTTP<br />
| no<br />
| no<br />
| proposal<br />
|-<br />
| eRDF<br />
| (X)HTML<br />
| no<br />
| no<br />
| proposal on Talis wiki<br />
|-<br />
| XHTML+RDFa<br />
| XHTML<br />
| no, but [http://buzzword.org.uk/2009/rdfa4/spec proposed]<br />
| no<br />
| W3C Rec<br />
|-<br />
| Microdata<br />
| (X)HTML<br />
| no<br />
| no<br />
| W3C WD<br />
|}<br />
<br />
== Limited Syntaxes ==<br />
<br />
Some serializations are only capable of representing a subset of the RDF data model.<br />
<br />
* RDF/XML requires property URIs to be encoded as XML QNames. Some URIs cannot be abbreviated this way. In practice, vocabulary designers tend to take this into account, so it's not much of a problem.<br />
* Microdata cannot represent datatypes for literals, and cannot handle cyclical relationships between blank nodes.<br />
* BSWL doesn't support blank nodes.<br />
* Certain unicode control characters are forbidden by XML, even when escaped as numeric character references. Unless an XML-based RDF serialisation provides an additional escaping mechanism, literals containing these characters cannot be serialised.</div>Danbrihttps://www.w3.org/wiki/index.php?title=TPAC/2019/SessionIdeas&diff=110397TPAC/2019/SessionIdeas2019-09-17T08:17:34Z<p>Danbri: linked background doc</p>
<hr />
<div>You are invited to propose [https://www.w3.org/2019/09/TPAC/ TPAC 2019] '''Technical Plenary Day''' breakout sessions in advance of the meeting. Booking closes on Tuesday, September 17th at 5 pm local time. <br />
<br />
See the [[TPAC/2019/FAQ | TPAC 2019 FAQ]] for more information. The draft session grid is at https://w3c.github.io/tpac-breakouts/sessions.html.<br />
<br />
<div style="float:right;clear:right">__TOC__</div><br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead (it's a good idea to let them know ahead of time)<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
* '''Please place new proposal at the bottom of this document'''<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (yourself, if so sign using 4 tildes; optional: name a desired session leader) and an email address<br />
* one sentence session summary<br />
* type of session: (e.g.: open discussion, talk, panel, etc.)<br />
* goals of session<br />
* additional speakers/panelists (to help reduce conflicts when one person is needed in more than one place)<br />
* any timing constraint you already know (e.g. you expect to invite someone in a different time zone)<br />
* if you can guess, whether you'll need a {big | medium | small} room (we can't guarantee you'll get it, however)<br />
* add an "Interested" bullet for people to sign up for sessions<br />
</ul><br />
<br />
== From an idea to a breakout ==<br />
<br />
<span style="color:#ff0000">'''The goal is to have a near-final breakout sessions schedule by the night before the plenary (Tuesday, September 17th).</span><br />
<br />
This ensures a more inclusive process in how the breakout sessions are defined and scheduled (thus avoiding any mad scramble). An HTML and mobile-friendly filled-out session grid for the day’s breakout sessions will be generated by the Team. [[TPAC/2019/FAQ#How_does_the_agenda_get_built.3F|Read more in our FAQ]].<br />
<br />
== Proposed sessions ==<br />
<br />
=== EXAMPLE session with session name ===<br />
* Proposer: <nowiki>~~~~</nowiki> (Instruction: remove <nowiki><nowiki> and </nowiki></nowiki> around the tildas. Explanation: The 4 tildas will sign YOUR name and include a timestamp of your proposal.)<br />
* Email address of proposer: <br />
* Summary (one-sentence or so): <br />
* Type of session (e.g.: open discussion, talk, panel, etc.): <br />
* Goals:<br />
* [optional] shortname (used for minting an IRC channel for the breakout)<br />
* [optional] Additional speakers/panelists:<br />
* [optional] Timing constraint: (e.g. you expect to invite someone in a different time zone)<br />
* [optional] Estimated room capacity: {big | medium | small} room<br />
<br />
=== ReSpec - so many new features! ===<br />
* Proposer: Marcos Cáceres<br />
* Email address of proposer: mcaceres@mozilla.com <br />
* Summary (one-sentence or so): Covering all the exciting advancements we've made in the last year, including automatic cross references, smart citations, MDN integration, and more! <br />
* Type of session: talk and open discussion <br />
* Goals: Introduce Editors to new features. <br />
* shortname: #pub<br />
* Additional speakers/panelists: Sid Vishnoi, Kagami Sascha Rosylight <br />
* [optional] Estimated room capacity: medium room<br />
<br />
=== Japan Language Requirements Task Force: Evolving the JLReq document ===<br />
* Proposer: [[User:Nmccully|Nathaniel McCully]] ([[User talk:Nmccully|talk]]) 16:29, 2 August 2019 (UTC)<br />
* Email address: nmccully@adobe.com<br />
* Summary: Explanation of the JLReq v2 effort currently underway, and a glimpse into the roadmap of a v3, that seeks to serve the needs of developers of layout engines for modern, dynamic media that support high-quality Japanese layout<br />
* Type of session: talk<br />
* Goals: To inform that this is happening, and get more people interested in the issues of high-end Japanese typography and layout in the context of responsive modern digital media.<br />
* shortname: jlreq<br />
<br />
=== Results from MDN Developer Survey ===<br />
* Proposer: [[User:Dom|Dominique Hazaël-Massieux]] ([[User talk:Dom|talk]]) 06:52, 5 August 2019 (UTC)<br />
* Email address: dom@w3.org<br />
* Summary: Meet the MDN Product Advisory Board and discuss how the results of the [https://hacks.mozilla.org/2019/07/mdn-web-developer-designer-survey/ MDN Developer Survey] can impact W3C's agenda<br />
* Type of session: short talk & discussion<br />
* Goals: Bring input to the MDN Product Advisory Board to see how MDN documentation can evolve to better meet the need from the W3C community; learn about the MDN Developer Survey and discuss what conclusions to draw from its results in terms of the W3C standardization agenda<br />
* Additional speakers/panelists: Kadir Topal, Dan Appelquist, Jory Burson, Travis Leithead, Joe Medley<br />
* shortname: mdn<br />
* Estimated room capacity: medium room<br />
<br />
=== Mini App Standardization ===<br />
* Proposer: [[User:laq|Angel Li]] 10:14, 14 August 2019 (UTC)<br />
* Email address: angelli.laq@alibaba-inc.com<br />
* Summary: Meet the major Mini App players, introduction of [https://www.w3.org/TR/mini-app-white-paper/ '''Mini App white paper'''] drafted by W3C Chinese IG, discuss the way forward for Mini App Standardization in W3C.<br />
* Type of session: short talk & discussion<br />
* Goals: help the global web community to better understand Mini App and the value of its standardization, find proper way to move forward in W3C.<br />
* shortname: MiniApp<br />
* Estimated room capacity: medium room (note: polycom to support remote attendees if possible)<br />
* Interested: [[User:Chris|Chris Lilley]] ([[User talk:Chris|talk]]) 13:54, 27 August 2019 (UTC)<br />
<br />
=== Web Packaging ===<br />
(Including Signed Exchanges and Bundles.)<br />
* Proposer: [[User:Jyasskin|Jeffrey Yasskin]] ([[User talk:Jyasskin|talk]]) 18:41, 14 August 2019 (UTC)<br />
* Email address of proposer: jyasskin@google.com<br />
* Summary (one-sentence or so): Discuss W3C feelings about the [Web Packaging proposal](https://github.com/WICG/webpackage).<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): Short talk & discussion<br />
* Goals: Ensure everyone knows the state of the IETF discussion and the Chromium implementation; recruit collaborators; discover concerns and needed changes; get advice about what route through the W3C/WHATWG processes to follow.<br />
* shortname: wpack<br />
* Additional speakers/panelists: [[User:Kyasuda2|Kinuko Yasuda]]<br />
* Timing constraint: TBD<br />
* Estimated room capacity: medium room<br />
<br />
=== A target privacy threat model for the Web ===<br />
* Proposer: [[User:Jyasskin|Jeffrey Yasskin]] ([[User talk:Jyasskin|talk]]) 19:04, 14 August 2019 (UTC) (However, I'd love to have someone else lead this.)<br />
* Email address of proposer: jyasskin@google.com<br />
* Summary (one-sentence or so): Proposals for new features often encounter resistance from folks who want the Web Platform to defend its users' privacy better than it does today. This often surprises the authors of those proposals, who were designing against the Web's current, implicit, and weak privacy threat model. Making our privacy goals explicit could avoid those surprises and reduce the load on privacy reviewers.<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): Open discussion<br />
* Goals: Explore the interest in developing a target privacy threat model for the Web.<br />
* shortname: privthreatmodel<br />
* Additional speakers/panelists: [Your name here]<br />
* Timing constraint: <br />
: morning session would be preferable for East Coast remote attendees -- [[User:Npdoty|Nick Doty]] ([[User talk:Npdoty|talk]])<br />
* Estimated room capacity: large room --- with polycom to support remote attendees<br />
* Dial in: Phone: https://meet.google.com/tel/aoe-vzqz-stt; Computer: https://meet.google.com/aoe-vzqz-stt<br />
<br />
=== Next Generation TextTrackCue ===<br />
* Proposers: [[User:Ecarlson2|Eric Carlson]] ([[User talk:Ecarlson2|talk]]) 20:18, 15 August 2019 (UTC), [[User:Eoconnor|Theresa O'Connor]], [[User:PLemieux|Pierre-Anthony Lemieux]]<br />
* Email address of proposers: eric.carlson@apple.com,hober@apple.com,pal@sandflow.com<br />
* Summary: TextTrackCue enhancements for programmatic subtitle and caption presentation. We've been making progress since FOMS this past spring. Please see our FOMS slides for the basic idea: https://www.icloud.com/keynote/0GJUbJwWfA2i77M2JysKjj45w#Generic_Text_Cue_-_FOMS_2019<br />
* Type of session: talk and open discussion<br />
* Goals: Engage with browser engineers and media experts & gauge interest in pursuing this as new web API<br />
* shortname: textcueapi<br />
* Estimated room capacity: medium room (~20 people)<br />
<br />
=== JS Built-In Modules ===<br />
* Proposer: [[User:dcrousso|Devin Rousso]] ([[User talk:dcrousso|talk]]) 22:05, 15 August 2019 (UTC)<br />
* Email address of proposer: dcrousso@apple.com<br />
* Summary (one-sentence or so): introduction to the concept of JS Built-In Modules, as well as an overview of the currently proposed governance model<br />
* Type of session: talk<br />
* Goals: disseminate knowledge of JS Built-In modules to other hosts built on top of JavaScript (e.g. web browsers), and introduce the proposed governance model to potential stakeholders of additional JS Built-In Module namespaces (e.g. web:)<br />
* Additional speakers: Michael Saboff <msaboff@apple.com> (call-in TC39 proposal champion)<br />
* Timing constraint: friendly towards PST<br />
* Estimated room capacity: medium room<br />
* shortname: jsbuiltin<br />
<br />
=== WebTransport status and next steps ===<br />
* Proposer: Peter Thatcher<br />
* Email address of proposer: pthatcher@google.com<br />
* Summary (one-sentence or so): Discuss [https://github.com/WICG/web-transport WebTransport API] and next steps for a WG or CG<br />
* Type of session: short talk (maybe demo too) & discussion<br />
* Goals: Ensure everyone is up to date on the latest API, implementation status, and interaction with the IETF ([https://mailarchive.ietf.org/arch/browse/webtransport/ link to mailing list]; [https://tools.ietf.org/wg/dispatch/minutes link to DISPATCH minutes]); determine when and how we should create a WG or CG; discuss advanced API topics such as how best to use WHATWG streams, how to handle congestion control, and stream prioritization<br />
* Shortname: webtransport<br />
* Estimated room capacity: medium room<br />
* Interested:<br />
** [[User:Halvestr|Harald Alvestrand]] ([[User talk:Halvestr|talk]]) 12:04, 12 September 2019 (UTC)<br />
** [[User:Ricea|Adam Rice]] ([[User talk:Ricea|talk]]) 09:06, 16 September 2019 (UTC)<br />
<br />
=== Web stories ===<br />
* Proposer: [[User:Coralie|Coralie Mercier]] ([[User talk:Coralie|talk]]) 15:45, 20 August 2019 (UTC)<br />
* Email address of proposer: coralie@w3.org<br />
* Summary: Feedback and brainstorming for (re)introducing the Web Consortium to the public. The W3C Comm team wants to get background stories from our Members and community about how they were drawn to the Web (before the Web, or their first involvement with the Web). There is a path for how everyone in our community has come to the Web, what they see happening now and what they see in the future.<br />
* Type of session: open discussion<br />
* Goals: We want to gather stories in order to tell a compelling story to the public. W3C Comm team may use this as part of an upcoming crowdfunding campaign.<br />
* shortname: webstories<br />
* Estimated room capacity: medium room<br />
* Interested:<br />
** ...<br />
<br />
=== WebGPU ===<br />
* Proposer: Myles C. Maxfield<br />
* Email address of proposer: mmaxfield@apple.com<br />
* Summary (one-sentence or so): Update on the progress of WebGPU, and group discussion about future directions and what to focus on<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): Talk and open discussion<br />
* Goals: Help people understand the direction that WebGPU is going, and get feedback from the broader community<br />
* [optional] shortname (used for minting an IRC channel for the breakout): webgpu<br />
* [optional] Additional speakers/panelists: Dean Jackson, anyone else in the CG<br />
* [optional] Estimated room capacity: medium room?<br />
<br />
=== DataCue and "Time marches on" in HTML ===<br />
* Proposers: [[User:chrisn|Chris Needham]] ([[User talk:chrisn|talk]]) 11:45, 22 August 2019 (UTC)<br />
* Email address of proposers: chris.needham@bbc.co.uk<br />
* Summary: The DataCue API for media-synchronised metadata and interactivity events is part of HTML5, but not implemented across all browsers, and existing implementations vary. There are also issues with the ''time marches on'' algorithm in HTML for triggering timed interactivity events<br />
* Type of session: talk and open discussion<br />
* Goals: To advance the DataCue API design between media experts and browser developers, and discuss how to improve synchronisation of media and associated content on the web<br />
* Shortname: #datacue<br />
* Timing constraint: Please avoid overlap with the Next Generation TextTrackCue breakout, as it's largely the same participants<br />
* Estimated room capacity: medium room<br />
<br />
=== Portals (status and next steps) ===<br />
* Proposer: [[User:Jbroman|Jeremy Roman]] ([[User talk:Jbroman|talk]]) 18:44, 22 August 2019 (UTC)<br />
* Email address of proposer: jbroman@google.com<br />
* Summary: Discuss Portals and next steps for a WG or CG. Portals allow for seamless navigation between different documents, same and cross origin, embedded or not. See hands-on article and WICG repository.<br />
* Type of session: short talk (possibly a few demos) followed by discussion<br />
* Goals: Ensure everyone is up to date on the latest proposed API, implementation status, use cases and interest from developers; determine what are the next steps, and concerns if any; discuss advanced API topics or use cases.<br />
* Shortname: portals<br />
* Estimated room capacity: medium room<br />
<br />
=== Ad Measurement and Privacy ===<br />
* Proposer: [[User:johnwilander|John Wilander]]<br />
* Email address of proposer: wilander@apple.com<br />
* Summary: We will discuss Apple's proposed and implemented [https://wicg.github.io/ad-click-attribution/index.html Private Click Measurement] and Google's proposed [https://github.com/csharrison/conversion-measurement-api Click Through Conversion Measurement].<br />
* Type of session: Open discussion <br />
* Goals: Discuss the open issue of fraud detection and what is required to ship this feature.<br />
* Estimated room capacity: Medium room<br />
* shortname: ad-privacy<br />
<br />
=== Input for workers/worklets ===<br />
* Proposer: [[User:Nzolghadr|Navid Zolghadr]] ([[User talk:Nzolghadr|talk]]) 14:16, 26 August 2019 (UTC)<br />
* Email address of proposer: nzolghadr@chromium.org, majidvp@chromium.org<br />
* Summary: Towards exposing [https://wicg.github.io/input-for-workers input events to Workers and Worklets].<br />
* Type of session: Open discussion<br />
* Goals: Discuss use cases and implications, brainstorm the API<br />
* shortname: workerinput<br />
* Additional speakers/panelists: Majid Valipour<br />
* Estimated room capacity: medium<br />
<br />
=== Privacy Budget ===<br />
* Proposer [[User:Blassey|Brad Lassey]]<br />
* Email address of the proposer: lassey@google.com<br />
* Summary: Chrome proposed a [https://github.com/bslassey/privacy-budget "privacy budget"] to limit the ability for websites to fingerprint users. We's like to have a discussion around this proposal and its implications.<br />
* Type of session: Open discussion<br />
* Goals: Determine interest level from implementers, discuss concerns.<br />
* Shortname: privacybudget<br />
* Estimated room capacity: medium<br />
* Interested:<br />
<br />
=== Trust Tokens ===<br />
* Proposer: [[User:blassey|Brad Lassey]]<br />
* Email address of the proposer: lassey@google.com<br />
* Summary: Cloudflare proposed the concept of the [https://privacypass.github.io/ Privacy Pass protocol] to avoid repeatedly showing captchas to Tor users and Chrome expanded on the idea to propose a more general purpose [https://github.com/dvorak42/trust-token-api Trust Token API] for conveying user trust between parties in order to prevent fraud.<br />
* Type of session: Open discussion<br />
* Goals: Determine interest level from implementers, discuss concerns.<br />
* Shortname: trusttokens<br />
* Additional speakers/panelists: [[User:Kleber|Michael Kleber]]<br />
* Estimated room capacity: medium<br />
* Interested:<br />
<br />
=== OpenJS Foundation Collaboration ===<br />
* Proposer: [[User:Jburson|Jordana Burson]] ([[User talk:Jburson|talk]]) 14:28, 28 August 2019 (UTC)<br />
* Email address of proposer: jory@bocoup.com<br />
* Summary (one-sentence or so): Members of the OpenJS Foundation cross project council would like to propose a 'BoF' conversation about how to build and strengthen healthy collaborations between foundation projects and W3C groups.<br />
* Type of session: open discussion<br />
* Goals: Discuss efforts underway in the foundation to recruit participation from our project communities into various W3C efforts. Discuss opportunities for cross-org collaboration. Highlight areas where OpenJSF projects would be additive to W3C. <br />
* [optional] shortname (used for minting an IRC channel for the breakout): openjs<br />
* [optional] Additional speakers/panelists: Christian Bromann, Brian Kardell, Dan Appelquist, Tobie Langel<br />
* [optional] Timing constraint: (e.g. you expect to invite someone in a different time zone): none<br />
* [optional] Estimated room capacity: {big | medium | small} room: small<br />
<br />
=== Supporting privacy-focused ads selection ===<br />
* Proposer: [[User:Kleber|Michael Kleber]] ([[User talk:Kleber|talk]]) 00:40, 29 August 2019 (UTC)<br />
* Email address of the proposer: kleber@google.com<br />
* Summary: Discussion of various ideas for how browsers could support ad selection use cases which today rely on users having a consistent cross-site identity. Chrome has explainers out for [https://github.com/jkarlin/floc "Federated Learning of Cohorts" (FLoC)] and [https://github.com/michaelkleber/pigin "Private Interest Groups, Including Noise (PIGIN)"].<br />
* Type of session: Open discussion<br />
* Goals: Determine interest level from implementers, discuss concerns.<br />
* Shortname: adselection<br />
* Estimated room capacity: medium<br />
* Interested:<br />
<br />
=== XR Accessibility ===<br />
* Proposer: [[User:Joconnor|Joshue O Connor]] ([[User talk:Joconnor|talk]]) 14:11, 29 August 2019 (UTC)Joshue O Connor<br />
* Email address: joconnor@w3.org<br />
* Summary: Explore how to grow a broader accessibility community in the areas of XR (Virtual and Augmented Reality).<br />
* Type of session: Talk and Open Discussion <br />
* Goals: Figure out how to bring together the accessibility community to build capability, collaboration and community engagement in developing standards that address the challenges of making Virtual and Augmented Reality accessible. <br />
* Shortname: xra11y<br />
* Additional speakers/panelists: TBD<br />
* Estimated room capacity: medium room<br />
<br />
=== Standardizing user activation behavior ===<br />
* Proposer: [[User:Mustaq|Mustaq Ahmed]] ([[User talk:Mustaq|talk]]) 14:15, 29 August 2019 (UTC)<br />
* Email address of proposer: mustaq@google.com<br />
* Summary: We are proposing to replace the user activation model implied by the current HTML spec with a simple-to-implement model because the current model doesn't reflect the reality (https://github.com/whatwg/html/issues/1903).<br />
* Type of session: Open discussion<br />
* Goals: Trying to reach consensus on our proposed change to the spec (https://github.com/whatwg/html/pull/3851).<br />
* shortname: user-activation<br />
* Additional speakers/panelists: Domenic Denicola<br />
* Timing constraint: Pacific Time Zone friendly if possible, for remote participation.<br />
* Estimated room capacity: medium<br />
<br />
=== WebCodecs ===<br />
* Proposer: [[User:Pthatcher|Peter Thatcher]] ([[User talk:Pthatcher|talk]]) 01:04, 30 August 2019 (UTC) <br />
* Email address of proposer: pthatcher@google.com<br />
* Summary: Discuss WebCodecs (https://discourse.wicg.io/t/webcodecs-proposal/3662)<br />
* Type of session: short talk (maybe demo too) & discussion<br />
* Goals: Get input from potential users of the API to see what use cases we need to make sure are well supported, as well as from experts of codecs. <br />
* Shortname: webcodecs<br />
* Estimated room capacity: small room<br />
* Interested:<br />
** [[User:Halvestr|Harald Alvestrand]] ([[User talk:Halvestr|talk]]) 12:02, 12 September 2019 (UTC)<br />
** [[User:Ricea|Adam Rice]] ([[User talk:Ricea|talk]]) 09:06, 16 September 2019 (UTC)<br />
<br />
=== Bullet Chatting ===<br />
* Proposer: [[User:Song Xu|Song Xu]] ([[User talk:Song Xu|talk]]) <br />
* Email address of proposer: xusong@migu.cn<br />
* Summary: Introduce what Bullet Chatting is, and introduce the Bullet Chatting [https://w3c.github.io/danmaku/index_en.html proposal] drafted by W3C Chinese Interest Group. Discuss the way forward for Bullet Chatting standardization in W3C.<br />
* Type of session: talk & discussion<br />
* Goals: Help the global web community to better understand Bullet Chatting and the value of its standardization, and looking for teams interested in Bullet Chatting standardization, hoping to get some feedback and support, and get advice about what the W3C workflow. <br />
* Shortname: bulletchat<br />
* Estimated room capacity: small room (note: polycom to support remote attendees if possible)<br />
<br />
=== Efficient audio/video processing ===<br />
* Proposer: François Daoust / Dominique Hazaël-Massieux / 02 September 2019<br />
* Email address of proposer: fd@w3.org, dom@w3.org<br />
* Summary: W3C groups (e.g. WebRTC WG, Machine Learning for the Web CG, Audio WG, Media WG, Immersive Web WG) discuss, develop and/or dream about ways to process audio/video streams efficiently. Use cases include barcode reading, face/gesture tracking, emotion analysis, funny hats, background removal or blurring, augmented reality, video overlays, voice effects, or custom codecs. Would it be useful and possible to develop a common mechanism that different APIs could leverage to hook together with streams of media while avoiding useless memory copies? What could such a mechanism look like?<br />
* Type of session: open discussion<br />
* Goals: Look at use cases and at how they can be implemented today, assess possible performance gains if they were implemented with a more efficient mechanism, refine scope for possible work on the topic, and gauge interest among parties.<br />
* Additional speakers/panelists: Rijubrata Bhaumik, Paul Adenot, Peter Thatcher, Joshue O Connor<br />
* Shortname: mediaprocessing<br />
* Estimated room capacity: medium<br />
* Interested:<br />
** [[User:Halvestr|Harald Alvestrand]] ([[User talk:Halvestr|talk]]) 12:03, 12 September 2019 (UTC)<br />
<br />
=== HTML 3D Element & Native GLTF ===<br />
* Proposer: [[User:zyu5|Zhiqiang Yu]], [[User:sushraja| Sushanth Rajasankar]]<br />
* Email address: yuzhiqiang5@huawei.com, sushraja@microsoft.com<br />
* Summary: A proposal on HTML 3D element to bring rich 3D & AR experience to Web with a single line of code. Use cases include on-line shopping, creative advertisement, education, etc. Another related idea is for a scene element proposal https://github.com/immersive-web/proposals/issues/52. Demo prototypes will be provided.<br />
* Type of session: short talk & discussion<br />
* Goals: Gauge developer interest in native 3D support in HTML (similar to image/audio/video tag) and looking forward to a wider collaboration with the community, as well as standardization in W3C.<br />
* shortname: HTML-3D<br />
* Estimated room capacity: medium room<br />
<br />
=== Voice assistants - opportunities for standardization? ===<br />
* Proposer: [[User:Philarcher|Phil Archer, GS1]] ([[User talk:Philarcher|talk]]) 09:28, 3 September 2019 (UTC)<br />
* Email address of proposer: phil.archer@gs1.org<br />
* Summary (one-sentence or so): Voice assistants present exciting new methods to interact with the Web but how can/should we develop standards that benefit all stake holders from start ups to tech giants? <br />
* Type of session: Discussion<br />
* Goals: To identify parties most interested in the generic area of voice interaction and to narrow that down to a set of more specific areas of interest. E-commerce? Fact checking? Media streaming? APIs for Skills, More ...<br />
* [optional] shortname: voice<br />
* [optional] Additional speakers/panelists: Léonie Watson, Mark Hakkinen<br />
* [optional] Estimated room capacity: small room<br />
<br />
=== Github tools and Bots to assist Chairing ===<br />
* Proposer: [[User:Adaroseedwards|Ada Rose Cannon]] ([[User talk:Adaroseedwards|talk]]) 10:19, 3 September 2019 (UTC)<br />
* Email address of proposer: ada@ada.is <br />
* Summary: I'm a lazy chair and have created bots and scripts to help me chair, this is to show some of the tools I use to help leverage Github's APIs to help chair. I would also be interested in other tools people use to automate some of their teams.<br />
* Type of session: Presentation + Discussion<br />
* Goals: Share tools used.<br />
* [optional] shortname: groupautomation<br />
* [optional] Estimated room capacity: small room<br />
<br />
=== WebAuthn network transport discussion ===<br />
* Proposer(s): James Barclay, [[User:Nmooney|Nick Mooney]] ([[User talk:Nmooney|talk]]) 17:02, 3 September 2019 (UTC)<br />
* Emails: {jbarclay,nmooney}@duosecurity.com<br />
* Summary: Discuss the development of a new network-based transport as an addition to the WebAuthn specification.<br />
* Type: talk, open discussion<br />
* Goals: motivate the need for a network-based WebAuthn transport, discuss how this might look as part of the specification, discuss phishing resistance and proximity<br />
* Shortname: #webauthnnetwork<br />
* Estimated room capacity: medium<br />
<br />
=== DID (Decentralized Identifier) Q&A ===<br />
* Proposer: [[User:Drummondreed|Drummond Reed]] ([[User talk:Drummondreed|talk]]) 17:53, 3 September 2019 (UTC)<br />
* Email address of proposer: drummond.reed@evernym.com<br />
* Summary: DIDs are a new form of cryptographically-verifiable identifier, and TPAC will host the first meeting of the new W3C DID WG. This is a chance to learn more about DIDs.<br />
* Type of session: open discussion<br />
* Goals: The primary goal is to answer questions about DIDs and help W3C members understand the market interest in this new type of identifier.<br />
* Shortname: #did<br />
* Additional speakers/panelists: Dan Burnett, Brent Zendel, Manu Sporny, Christopher Allen, Ken Ebert, Helen Garneau<br />
* Estimated room capacity: medium room (possibly large depending on level of interest)<br />
* Scheduling note: please try not to schedule at the same time as the session "A Non-Technical Discussion on DIDs and self-sovereign identity"<br />
<br />
=== UndoManager API ===<br />
* Proposer: [[User:Whsieh|Wenson Hsieh]] ([[User talk:Whsieh|talk]]) 20:28, 3 September 2019 (UTC)<br />
* Email address of proposer: wenson_hsieh@apple.com<br />
* Summary (one-sentence or so): The UndoManager API allows web applications to modify the platform undo stack, and scope undo stacks to elements. For more information, refer to the explainer here: https://github.com/whsieh/UndoManager as well as a draft of the spec here: https://rniwa.github.io/undo-api.<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): talk, open discussion<br />
* Goals: Introduce a proposal for the UndoManager API, which allows web applications to modify and inspect the platform’s undo stack. This has implications for all types of web apps, with particular relevance to editing and productivity apps. We hope to establish context for the UndoManager API, demo a prototype of the API, and gain feedback for our proposal.<br />
* Shortname: undomanager<br />
* Additional speakers/panelists: Megan Gardner<br />
* Estimated room capacity: small room<br />
<br />
=== Linked Data Security ===<br />
* Proposer: [[User:Msporny|Manu Sporny]] ([[User talk:Msporny|talk]]) 22:11, 3 September 2019 (UTC)<br />
* Email address of proposer: msporny@digitalbazaar.com<br />
* Summary (one-sentence or so): Should we standardize: RDF Dataset Canonicalization, Linked Data Proofs, Linked Data Signatures, RSA2019Signature, Ed25519Signature, and if so, on what timeline?<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): open discussion<br />
* Goals: Determine if certain Linked Data Security technologies are ready for standardization.<br />
* [optional] ldsec<br />
* [optional] Additional speakers/panelists: Ivan Herman, Gregg Kellogg, Benjamin Young, Robert Sanderson<br />
* [optional] Timing constraint: Don't overlap with DID session<br />
* [optional] Estimated room capacity: small<br />
<br />
=== What is the Future of W3C ===<br />
* Proposer: [[Tantek]] (Mozilla, and former AB member) ([[User:Tantekelik|Tantek Çelik]] ([[User talk:Tantekelik|talk]]) 22:58, 3 September 2019 (UTC))<br />
* Email address of proposer: tantek@cs.stanford.edu<br />
* Summary: How should W3C evolve to better serve the web community? The AB and AC are discussing changes to its structure, but they need to hear from stakeholders about the mission and the structure designed to achieve it.<br />
* Type of session: open discussion<br />
* shortname: #future<br />
* Timing constraint: prefer Pacific Time Zone friendly time if possible for remote participation<br />
* Estimated room capacity: medium<br />
* Additional speakers/panelists: Travis Leithead (Microsoft, for Michael Champion who may participate remotely, former AB member), Chris Wilson (Google, AB member)<br />
* Goals: A discussion to understand the community's level of consensus on fundamental questions:<br />
** Mission – W3C’s traditional mission statement is “lead the web to its full potential”. Does the community believe W3C’s basic value proposition need updating, perhaps to focus on some combination of documenting how the web actually works, certifying which products comply with the consensus standards, and focusing on the most pressing challenges to the original vision?<br />
** Leadership – The founding Director is no longer involved with W3C’s day to day operations, but the “Director” has a key role in the process and governance. Would the community be more comfortable with finding another neutral person with considerable expertise who can commit the time to being Director, or delegating tasks such as adjudicating formal objections to some sort of elected council?<br />
** Staffing – What role or roles should the Team prioritize and focus on? Mechanics of consensus building, or technical guidance on solutions?<br />
* Interested:<br />
** [[User:Coralie|Coralie Mercier]] ([[User talk:Coralie|talk]]) 17:31, 4 September 2019 (UTC)<br />
** ...<br />
<br />
=== Web of Things PlugFest ===<br />
* Proposer: [[User:Ashimura|Kazuyuki Ashimura]] ([[User talk:Ashimura|talk]]) 17:21, 4 September 2019 (UTC)<br />
* Email address of proposer: ashimura@w3.org<br />
* Summary: The WoT-IG/WG would like to have its PlugFest demo at 13:30-14:30 to (1) present what kind of demos are included and (2) show actual demos which include various scenarios and combinations of devices/applications for IoT purposes.<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): Presentaton and Demo<br />
* Goals: Show what is done by the WoT WG/IG based on the WoT standards to all the TPAC attendees and encourage people to collaborate with the group (and join the group :). This time we'd like to show several different combinations of devices/applications and scenarios based on the WoT specifications. Please see also the [https://github.com/endouhhc/wot/blob/master/plugfest/2019-tpac-fukuoka/README.md PlugFest preparation page].<br />
* shortname: wot-pf<br />
* Timing constraint: 13:30-14:30<br />
* Estimated room capacity: big room<br />
<br />
=== Introduction to W3C ===<br />
* Proposer: [[User:Plehegar|Philippe Le Hégaret]] ([[User talk:Plehegar|talk]]) 20:12, 4 September 2019 (UTC)<br />
* Email address of proposer: plh@w3.org<br />
* Summary: If you're a new Group participant in the W3C, this session will guide you through the W3C labyrinth and allow you to contribute to the Web<br />
* Type of session: talk, tutorial, open discussion<br />
* Goals: Make sure attendees are up-to-speed on how to participate in their Groups, get familiar with various documentations and tools used by W3C, including GitHub.<br />
* shortname: #w3c-intro<br />
* Timing constraint: none<br />
* Estimated room capacity: small room<br />
<br />
=== Standardizing 360 video ===<br />
* Proposer: [[User:SamiraAtMicrosoft|Samira Hirji]] ([[User talk:SamiraAtMicrosoft|talk]])<br />
* Email address of proposer: Samira.Hirji@microsoft.com<br />
* Type of session: open discussion<br />
* Goals: Bring awareness to current challenges of playing spherical video content and discuss options for standardizing.<br />
* shortname: #360video<br />
* Timing constraint: none<br />
* Estimated room capacity: small room<br />
<br />
=== For a More Capable Web—Project Fugu === <br />
* Proposer: [[User:Tsteiner|Thomas Steiner]] ([[User_talk:Tsteiner|talk]]), [[User:Akostiai|Anssi Kostiainen]] ([[User talk:Akostiai|talk]]), John Jansen<br />
* Email addresses of proposers: tomac@google.com, anssi.kostiainen@intel.com, john.jansen@microsoft.com<br />
* Summary: To remain relevant with native/hybrid/mini apps, web apps, too, need access to a comparable set of APIs. In this session, we briefly touch upon the APIs being worked on by the cross-company Capabilities Project (aka. Project Fugu), and then open the floor for an open discussion on why we see the browser-accessible web in danger if we don’t move it forward now, despite all fully acknowledged challenges around privacy, security, and compatibility.<br />
* Type of session: Open discussion<br />
* Goals: The session strives to explain our sense of urgency for keeping the web an attractive application platform given fierce competition. The main objective is building an understanding of the arguments of multiple sides: those who argue the web can’t compete if it’s not equally capable, and those who argue this is not an option for reasons including, but not limited to, privacy or security.<br />
* Shortname: capable-web<br />
* Estimated room capacity: medium room<br />
<br />
=== A Non-Technical Discussion on Decentralized Identifier (DIDs) & Self-Sovereign Identity (SSI) ===<br />
* Proposer: [[User:Hgarneau|Helen Garneau]] ([[User talk:Hgarneau|talk]]) 16:48, 6 September 2019 (UTC)Hgarneau<br />
* Email address of proposer: Helen Garneau | helen@sovrin.org<br />
* Summary (one-sentence or so): DIDs are disruptive new technology possessing the possibility to overturn the status quo of data exchange across all industry verticals. But how do we explain this to policy makers, budget decision makers, and customers? Let's discuss how to bring this tech into the non-tech narrative. <br />
* Type of session: open discussion<br />
* Goals: The primary goal is to have a non-technical discussion about DIDs and prepare W3C members with the messaging they need to make the case publicly for this new type of identifier.<br />
* Shortname: #didtalk<br />
* Additional speakers/panelists: Drummond Reed, Ken Ebert<br />
* Estimated room capacity: medium room<br />
* Scheduling note: Please don't schedule at same time as DID Q&A session.<br />
<br />
=== JSON-LD 1.1 Update ===<br />
* Proposer: [[User:Gkellogg|Gregg Kellogg]] ([[User talk:Gkellogg|talk]]) 17:07, 6 September 2019 (UTC)<br />
* Email address of proposer: gregg@greggkellogg.net<br />
* Summary (one-sentence or so): Update on JSON-LD since the 1.0 recommendation, focusing on new features.<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): talk<br />
* Goals: The goal is to give users of JSON-LD 1.0 an update on features in the forthcoming JSON-LD 1.1 release, and what the impact on publishing and processing documents may be.<br />
* [optional] #json-ld<br />
* [optional] Estimated room capacity: small room<br />
<br />
=== Introducing: Audiobooks! ===<br />
* Proposer: [[User:Wendyreid|Wendy Reid]] ([[User talk:Wendyreid|talk]]) 19:58, 6 September 2019 (UTC)<br />
* Email address of proposer: wendy.reid@rakuten.com<br />
* Summary (one-sentence or so): Introducing the work of the Publishing Working Group on our Audiobooks specification. If you're interested in audiobooks, podcasts, or just publishing, come join us. <br />
* Type of session (e.g.: open discussion, talk, panel, etc.): Talk with discussion<br />
* Goals: Introduce the W3C to the work of the Publishing Working Group, get more feedback on our efforts, raise awareness. <br />
* [optional] #pwg-audio (this channel exists already)<br />
* [optional] Estimated room capacity: small room<br />
<br />
=== Digital Transformation, the Sentient Web and Cognitive Agents ===<br />
* Proposer: [[User:dsr|Dave Raggett]] ([https://www.w3.org/Data/events/tpac2019/digital-transformation.pdf talk])<br />
* Email address of proposer: dsr@w3.org<br />
* Summary: Framing the aims and challenges for the <em title="The adoption of advanced digital technologies to enable businesses to become more efficient, more flexible and more nimble in respect to changing business needs.">Digital Transformation of industry</em>, the emergence of the <em title="Ecosystems of services involving awareness based upon sensor data and reasoning based upon graph data and rules together with AI/ML.">Sentient Web</em> and new approaches to [https://www.w3.org/Data/demos/chunks/chunks.html cognitive agents] based upon decades of progress in Cognitive Psychology that pave the way for a new paradigm for AI, focusing on human oriented computing.<br />
* Type of session: Talk with discussion and demos<br />
* Goals: Introduce the W3C to opportunities for addressing Digital Transformation with graph data and rules, together with highly scalable graph algorithms and AI/ML<br />
* Shortname: #digital-transformation<br />
* Estimated room capacity: medium room<br />
* Interested:<br />
<br />
=== Process 2020 ===<br />
* Proposer: fantasai, plh, dsinger, [[User:Frivoal|Florian Rivoal]] ([[User talk:Frivoal|talk]]) 07:09, 9 September 2019 (UTC)<br />
* Email address of proposer: tpac@florian.rivoal.net<br />
* Summary: Discussion of Process2020 Proposals (continuous development, registries)<br />
* Type of session: open discussion<br />
* Goals: Get feedback from community and develop consensus on Process2020 proposals<br />
* shortname: #w3process<br />
* Estimated room capacity: big or medium room<br />
<br />
=== Building a Smartweb Powered by Blockchain ===<br />
* Proposer: [https://www.w3.org/users/116710 Rong Chen]<br />
* Email address of proposer: chenrong@elastos.org<br />
* Summary: A Smartweb has its own DIDs, browsers, micro-websites, and instant mini-apps; but has no explicit IP addresses, nor communication protocols, to prevent network attacks or 3rd party apps from stealing users data.<br />
* Type of session: talk & open discussion<br />
* Goals: Proposing a New Web that Runs Apps to the W3C<br />
* shortname: #smartweb<br />
* Additional speakers/panelists: [https://www.w3.org/users/116688 Yipeng Su], [https://www.w3.org/users/115515 Jingyu Niu]<br />
* Estimated room capacity: big room<br />
* Interested:<br />
<br />
=== Authentication by Communication Network ===<br />
* Proposer: Jia Qiang (Bill) <br />
* Email address of proposer: jiaqiang@chinamobile.com<br />
* Summary: Introduce what Telecom Authentication is, and introduce the security risks and solutions of Telecom Authentication, especially when using WEB, instead of client, to authenticate. <br />
* Type of session: talk & discussion<br />
* Goals: Introduce Telecom Authentication to the global web community, to help a better understanding of Telecom Authentication and how the Telecom Authentication is applied by telecom operators. From those teams who are interested in Telecom Authentication standardization, hope to share visions and experiences. Any advices is favourable. <br />
* Shortname: telecom-authn<br />
* Estimated room capacity: small room (with projector )<br />
<br />
=== A new approach to large DOM and virtual scrollers using rendersubtree ===<br />
* Proposer: [[User:Fergal|Fergal Daly]] ([[User talk:Fergal|talk]]) 09:25, 11 September 2019 (UTC)<br />
* Email address of proposer: fergal@chromium.org<br />
* Summary: Describe our work on using [https://github.com/WICG/display-locking display locking/rendersubtree] to prototype the [https://github.com/WICG/virtual-scroller virtual-scroller custom element] that allows large amounts of content to be present in the DOM without causing performance problems (the name may change since it's not actually JSON-DOM virtualization). This is in contrast to traditional virtualization which achieves performance by keeping most of the content outside of the DOM. By keeping content in the DOM, we retain accessibility, indexability and in-page find.<br />
* Type of session: talk & discussion<br />
* Goals: Raise awareness and start discussion about this problem and solution. Demonstrate a use of rendersubtree.<br />
* Shortname: virtual-scroller<br />
* Estimated room capacity: medium room (with projector)<br />
* Additional speakers/panelists: chrishtr@chromium.org, domenic@chromium.org, rakina@chromium.org, vmpstr@chromium.org<br />
<br />
=== WebRTC Insertable Streaming Codecs ===<br />
Moved to "efficient audio/video processing" breakout<br />
<br />
=== Registries at the W3C ===<br />
* Proposer: [[User:Dsinger2|David Singer]] ([[User talk:Dsinger2|talk]]) 16:56, 12 September 2019 (UTC)<br />
* Email address of proposer: singer@apple.com<br />
* Summary (one-sentence or so): Discuss the [https://www.w3.org/wiki/Registries proposals] for formalizing Registries at the W3C<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): discussion<br />
* Goals: connect with people/groups that need Registries, to explore how they could work with the proposed formalization<br />
* Shortname: #registries<br />
* Additional speakers/panelists: [[User:Frivoal|Florian Rivoal]], Elika Etemad<br />
* Estimated room capacity: medium? room<br />
<br />
=== Improving Spoken Presentation of Content ===<br />
* Proposer: [https://www.w3.org/users/35712 Mark Hakkinen] [https://www.w3.org/users/98332 Irfan Ali]<br />
* Email address of proposer: mhakkinen@ets.org <br />
* Summary (one-sentence or so): Assistive Technology users are just one beneficiary of improved spoken presentation of Web content. Learn about why this is important and emerging approaches from the [https://www.w3.org/WAI/pronunciation/ APA Pronunciation Task Force]. <br />
* Type of session: talk and open discussion <br />
* Goals: Raise awareness, exchange ideas, and encourage participation in the pronunciation task force.<br />
* shortname: #pronunciation<br />
* Additional speakers/panelists: TBD <br />
* [optional] Estimated room capacity: small room<br />
<br />
=== Personalization of Web Content ===<br />
* Proposer: [[User:Clapierre|Charles LaPierre]] ([[User talk:Clapierre|talk]]) 19:01, 12 September 2019 (UTC)<br />
* Email address of proposer: charlesl@benetech.org<br />
* Summary: People have very different needs. some people can not do numeric information, but others prefer numbers to words, some people with severe language disabilities use of symbols to represent words, but one of the main challenges is transforming content for these different needs. We are working on an extreme personalization standard that let people with cognitive and learning disabilities join the online community and share information and communicate across groups. Are there more use-cases and new user groups for this technology?<br />
Here are our [https://github.com/w3c/personalization-semantics/wiki/Use-cases Use Case Examples]. Here is a link to our [https://w3c.github.io/personalization-semantics/ latest working draft of our explainer document]<br />
* Type of session: Demo and open discussion <br />
* Goals: Find additional use cases, and see if we could be using a better mechanism. <br />
* shortname: #personalization<br />
* Additional speakers/panelists: Janina Sajka, Lisa Seeman<br />
* Timing constraint: Will try to include Lisa Seeman (UTC+2) possibly Steve Lee (UTC+1)<br />
* Estimated room capacity: small room<br />
<br />
=== WebRTC combined with IMS ===<br />
* Proposer: [[User:xiayefeng|Yefeng Xia]]<br />
* Email address: xiayefeng@chinamobile.com<br />
* Summary: A proposal on networking scheme for deploying WebRTC end-to-end real-time audio and video communication applications in SIP-based IMS network architecture.<br />
* Type of session: short talk & discussion<br />
* Goals: With the continuous improvement of WebRTC related standards and technologies, the combination of WebRTC technology and IMS will renew more vitality.<br />
* shortname: WebRTC & IMS<br />
* Estimated room capacity: small room<br />
<br />
=== Multiscreen/foldables ===<br />
* Proposer: [[User:dlibby|Daniel Libby]]<br />
* Email address: dlibby@microsoft.com<br />
* Summary: Discuss series of related proposals in the multiscreen/foldables area<br />
* Type of session: Discussion<br />
* Goals: Rationalize existing proposals to ensure we're on the same page for primitives that should be exposed to the Web.<br />
* shortname: #multiscreen<br />
* Estimated room capacity: small room<br />
<br />
=== Images on the Web ===<br />
* Proposer: [[User:CConcola|Cyril Concolato]]<br />
* Email address: cconcolato@netflix.com<br />
* Summary: discuss evolutions of image formats on the Web<br />
* type of session: open discussion<br />
* Goals: Discuss the growing overlap between video formats and codecs, and image formats and codecs (e.g. AV1 AVIF, HEVC HEIF, MIAF) and the consequences for browsers, content providers and users.<br />
* additional speakers/panelists: [[User:Dsinger2|David Singer]] <br />
* no specific timing constraint <br />
* room size: medium<br />
<br />
=== Spec Editing Infrastructure ===<br />
* Proposer: Tobie Langel<br />
* Email address: tobie@unlock.com<br />
* Summary: Open discussion about spec editing infrastructre: what we have (pr-preview, respec, specref, bikeshed, etc), what's missing and how to fund it<br />
* Type: discussion<br />
* additional speakers: Marcos Caceres, James Graham, Simon Pieters<br />
* room size: medium<br />
<br />
=== New Module types: JSON, CSS, HTML ===<br />
* Proposer: [[User:Daniec|Daniel Clark]] ([[User talk:Daniec|talk]]) 04:19, 16 September 2019 (UTC)<br />
* Email address of proposer: daniec@microsoft.com<br />
* Summary: Introduce JSON, CSS, and HTML modules and discuss open issues<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): Talk followed by open discussion<br />
* Goals: Introduce and provide motivation for new JSON, CSS, and HTML module types. Share status of the proposals and implementations. Discuss open design questions.<br />
* Shortname: new-modules<br />
* Estimated room capacity: medium room<br />
<br />
=== web-platform-tests update & discussion ===<br />
* Proposer: [[User:Foolip|Philip Jägenstedt]] ([[User talk:Foolip|talk]]) 05:09, 16 September 2019 (UTC)<br />
* Email address of proposer: foolip@google.com<br />
* Summary: [https://github.com/web-platform-tests/wpt web-platform-tests] and [https://wpt.fyi/results/ wpt.fyi] are even better than last year. This session gives an update on what's improved, and we're looking for feedback on what you still need.<br />
* Type of session Short presentation, then open for discussion.<br />
* Goals: Highlight new capabilities of wpt and wpt.fyi, gather feedback about top pain points for users.<br />
* Shortname: wpt<br />
* Estimated room capacity: medium<br />
<br />
=== Edge Computing for the Web ===<br />
* Proposer: Dan Druta, Sudeep Divakaran, Song Xu<br />
* Email address of proposer: dd5826@att.com, sudeep.divakaran@intel.com, xusong@migu.cn<br />
* Summary: With advancements in edge compute, there is a paradigm shift that has a positive impact on applications architecture that can leverage capabilites like low latency.<br />
* Type of session Short presentation, then open for discussion.<br />
* Goals: identify opportunities for web APIs for Edge computing, capitalize on 5G features and look at challenges around security and privacy.<br />
* Shortname: edge-computing<br />
* Estimated room capacity: medium<br />
<br />
=== Introducing aria-virtualcontent ===<br />
* Proposer: [[User:rossen|Rossen Atanassov]] ([[User talk:rossen|talk]]) 05:14, 16 September 2019 (UTC)<br />
* Email address of proposer: ratan@microsoft.com<br />
* Summary: Introduce a method of making large virtualized content accessible.<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): Talk followed by open discussion<br />
* Goals: Introduce and provide motivation for new HTML attribute `aria-vistrualcontent`. Demonstrate what such capability enables. Share some early prototype feedback. Gather feedback and solicit implementer interest. <br />
* Shortname: aria-virtualcontent<br />
* Estimated room capacity: medium room<br />
<br />
=== Anti-Homograph-Attacks ===<br />
* Proposer: [[User:Yoshiroyoneya|Yoshiro Yoneya]] ([[User talk:Yoshiroyoneya|talk]]) 01:44, 17 September 2019 (UTC)<br />
* Email address of proposer: yoshiro.yoneya@jprs.co.jp<br />
* Summary: IDN homograph attack is widely used for phishing users to malicious web sites. There are several countermeasures for this attack, but they depend on Web applications' implementations. From the end users' perspective, countermeasures should be common between Web applications to get better user experience. Where is the right place to discuss such countermeasures?<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): talk and discussion<br />
* Goals: Get enough attraction of people to form community group and start working. <br />
* shortname: aha<br />
* Estimated room capacity: small room<br />
<br />
=== Getting text direction into RDF ===<br />
* Proposer: [[User:Charles|Charles &#39;chaals&#39; (McCathie) Nevile]] ([[User talk:Charles|talk]]) 04:51, 17 September 2019 (UTC)<br />
* Email address of proposer: charles.nevile@consensys.net<br />
* Summary (one-sentence or so): RDF text literals do not have direction information. For a small class of strings, this is a big problem. There have been discussions and proposals, and the goal is to frame the problem and find a way to move torward resolving it. See also [https://w3c.github.io/rdf-dir-literal/ rdf-dir-literal] document.<br />
* Type of session (e.g.: open discussion, talk, panel, etc.): discussion<br />
* Goals:<br />
* shortname rdf-dir-literal<br />
* [optional] Additional speakers/panelists:possibly Richard Ishida, Ivan Herman, Omar Alhaddad, Gregg Kellogg, Addison Philipps, ... <br />
* Atttending: Danbri<br />
* Timing constraint: (please don't clash with i18n, or mini-apps)<br />
* Estimated room capacity: small room</div>Danbrihttps://www.w3.org/wiki/index.php?title=SemanticSitemap&diff=101640SemanticSitemap2017-02-28T04:39:13Z<p>Danbri: added archive.org links</p>
<hr />
<div>__NOTOC__<br />
'''[http://sw.deri.org/2007/07/sitemapextension/ Semantic Web Crawling: A Sitemap Extension]''' is an extension to the [http://www.sitemaps.org/ Sitemap protocol] targeted at the '''efficient discovery and use of RDF data'''. The extension allows data publishers to '''state where documents containing RDF data are located''', and to advertise alternative means to access it, such as '''data dumps and SPARQL endpoints'''. Semantic Web clients and crawlers can use this information to choose the most efficient access method for the task they have to perform.<br />
<br />
The extension is developed within the [http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData Linking Open Data] community project.<br />
<br />
This page collects materials related to the effort.<br />
<br />
== Specifications ==<br />
<br />
* [http://sw.deri.org/2007/07/sitemapextension/ Semantic Web Crawling: A Sitemap Extension]: Latest version of the spec, hosted at DERI<br />
<br />
== Implementations ==<br />
<br />
Leandro Lopez::<br />
; : A Java implementation has been kindly contributed by [[LeandroLopez]]. Includes support code by [[AndreasHarth]].<br />
* [http://sw.deri.org/2007/07/sitemapextension/SemanticSitemap-1.2.zip SemanticSitemap-1.2.zip] ([http://web.archive.org/web/*/http://sw.deri.org/2007/07/sitemapextension/SemanticSitemap-1.2.zip archive.org])<br />
* [http://sw.deri.org/2007/07/sitemapextension/SemanticSitemap-Tests.zip SemanticSitemap-Tests.zip] ([http://web.archive.org/web/*/http://sw.deri.org/2007/07/sitemapextension/SemanticSitemap-Tests.zip archive.org])<br />
<br />
== Slides and publications ==<br />
<br />
@@@ Add links<br />
<br />
== Examples ==<br />
<br />
* http://purl.uniprot.org/sitemap.xml<br />
* http://www.rdfabout.com/sitemap.xml<br />
* http://dbpedia.org/sitemap.xml<br />
* http://budapest.rkbexplorer.com/sitemap.xml<br />
<br />
== Discussion ==<br />
<br />
Discussion of the Semantic Sitemap mostly takes place on the [http://simile.mit.edu/mailman/listinfo/linking-open-data Linking Open Data list].<br />
<br />
@@@ Add links to relevant threads on LOD list</div>Danbrihttps://www.w3.org/wiki/index.php?title=GeoInfo&diff=99951GeoInfo2016-09-19T17:06:36Z<p>Danbri: IRC log links</p>
<hr />
<div>__NOTOC__<br />
Places are a recurring theme in the [[SemanticWeb]], along with people,<br />
documents, times, and money. (see [[FriendOfaFriend]], [[DublinCore]], [[RdfCalendar]],<br />
as well as [[SeedApplications]] and [[VocabularyMarket]]). See [[GeoOnion]] for an attempt to relate lat/long points to 'within n metres of' concentric circles that encompass them.<br />
<br />
So far, we have a [http://www.w3.org/2003/01/geo/ lat/long vocab page and workspace].<br />
The coolest thing about it is probably that the [http://geourl.org/ GeoURL]<br />
database, with zillions of web pages related to lat/long, can be queried with<br />
results in RDF using this vocabulary; results look like...<br />
<br />
<br />
<pre><nowiki><br />
<rdf:RDF<br />
xmlns:dc="http://purl.org/dc/elements/1.1/"<br />
xmlns:foaf="http://xmlns.com/foaf/0.1/"<br />
xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"<br />
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
<br />
<rdf:Description rdf:about="http://www.cs.cmu.edu/~sprite/index.html"><br />
<dc:title>Bridget Spitznagel</dc:title><br />
<foaf:topic rdf:parseType="Resource"><br />
<geo:lat>40.442673</geo:lat><br />
<geo:long>-79.945815</geo:long><br />
</foaf:topic><br />
</rdf:Description><br />
</rdf:RDF><br />
</nowiki></pre><br />
<br />
<br />
Nearby: [[GeoOnion]], [[CoordinateProperty]]<br />
=== Q & A ===<br />
<br />
[[Category:Faq]]<br />
<br />
''Is there an upcoming [[ScheduledTopicChat]] on this stuff?''<br />
<br />
* hmm... not clear.<br />
* stay tuned to www-rdf-interest [[MailingLists]] for notice, which should come a week or so in advance.<br />
<br />
''What's on the agenda?''<br />
<br />
* review of outstanding stuff from 16Apr, 30 Apr, 28 May:<br />
** [[ActionItems]] on libby, danbri, danc, @@others?<br />
* ''your agenda request here''<br />
<br />
''Has there been any [[ScheduledTopicChat]] on this stuff?''<br />
<br />
* [http://rdfig.xmlhack.com/2003/05/28/2003-05-28.html 28 May weblog]: GML, shapefiles, geotools, [http://fri.sfasu.edu/data/geographic/world/shape/ timezone shapefiles]<br />
* [http://rdfig.xmlhack.com/2003/04/30/2003-04-30.html 30 Apr weblog]<br />
* [http://rdfig.xmlhack.com/2003/04/16/2003-04-16.html#1050501406.933781 notes from 16Apr], [http://www.w3.org/2002/12/cal/test/20030416geomtg.rdf 16 Apr geo meeting calendar]<br />
* [http://lists.w3.org/Archives/Public/www-rdf-calendar/2003Apr/0010.html 9Apr summary]<br />
<br />
Updated by --[[User:Danbri|Dan Brickley]] ([[User talk:Danbri|talk]]) 17:03, 19 September 2016 (UTC) Sept 2016 for new domain name on these links and IRC logs: <br />
<br />
* http://swig.planetrdf.com/2003/05/28/2003-05-28.html<br />
* http://swig.planetrdf.com/2003/04/30/2003-04-30.html<br />
* http://swig.planetrdf.com/2003/04/16/2003-04-16.html#1050501406.933781<br />
* http://chatlogs.planetrdf.com/rdfig/2003-05-28.html<br />
* http://chatlogs.planetrdf.com/rdfig/2003-04-30.html<br />
* http://chatlogs.planetrdf.com/rdfig/2003-04-16.html<br />
<br />
<br />
<br />
''Who's working on this stuff?''<br />
<br />
The following folks have shown interest:<br />
<br />
* [[DanBri]] (prefers weds for #rdfig chats)<br />
* [[LibbyMiller]]<br />
* [[MortenFrederiksen]].<br />
* [[JoWalsh]]<br />
* [[DanConnolly]]<br />
* ChaalsMcCN<br />
* [[KjetilKjernsmo]]<br />
<br />
See also attendance records for previous chats, above.<br />
<br />
''Is this a formal standardization effort?''<br />
<br />
* It is more of an experiment in representing mapping and location data within the RDF graph data model.<br />
<br />
''Is anybody building an RDF vocabulary for stuff like latitude/longitude?''<br />
* the [http://www.w3.org/2003/01/geo/ lat/long vocab page and workspace] is nearby. It's based on [http://www.wgs84.com/ WGS 84 - World Geodetic System 1984]. See also the [http://www.wgs84.com/wgs84/wgs84.htm Background document]<br />
* [http://www.w3.org/2000/10/swap/pim/earthMap.n3 Earth Maps, Latitudes, and Longitudes: An RDF Schema] (in RDF/N3, based on Xplanet) (is it WGS84? can we define sub-properties?)<br />
* [http://www.mapbureau.com/rdfmap/spec.html RDFMap spec] ([http://groups.yahoo.com/group/rss-dev/message/2922 rss-dev announcment] and [http://groups.yahoo.com/group/rss-dev/message/2950 follow up]).<br />
* DAML GEO stuff: [http://www.daml.org/listarchive/daml-spatial/index.html daml-spatial list archive]<br />
* SUMO; e.g. [http://www.daml.org/listarchive/daml-spatial/0004.html spatial ontology starter] Adam Pease 27 Jan 2003 to daml-spatial<br />
* the [http://www.cyc.com/cycdoc/vocab/geography-vocab.html cyc geography vocabulary] was released in DAML/RDF/XML form: [http://opencyc.sourceforge.net/daml/cyc.daml cyc.daml]. ''@@when? there's a newer release, too, isn't there?''<br />
* [[GeoRDF]]<br />
* [[GeoMetadataOverSvg]]<br />
* [http://www.geonames.org/ontology/ Geonames.org Ontology]<br />
<br />
''Need to be careful about specifity''<br />
<br />
''OK, but you can't put RDF into XHTML and have it (easily) validate. So what's the best way to get georeferencing data into an (X)HTML page? There seem to be many choices, without a clear winner. The [[DublinCore]] DC.Coverage.spatial type would seem to be the most desireable, but is perhaps the one that is least defined (at least it is confusing to implement)''<br />
<br />
(X)HTML georeferencing formats:<br />
* [http://dublincore.org/documents/dcmi-point/ DCMIPOINT]<br />
* [http://www.getty.edu/research/tools/vocabulary/tgn/ The Getty Thesaurus of Geographic Names (TGN)]<br />
* [http://geourl.org/ GeoURL]<br />
* [http://geotags.com/geo/geotags2.html Geo Tags]<br />
<br />
RSS georeferencing formats:<br />
* [http://igargoyle.com/rss/1.0/modules/spatial/ dcterms:spatial RSS 1.0 module]<br />
<br />
RSS Reader using [[GeoInfo]]:<br />
* [www.plazoo.com/info/de/newsreader.asp RSS Reader from plazoo]<br />
<br />
Other georeferencing formats:<br />
* [http://lcweb.loc.gov/marc/ MARC]<br />
* [http://gcmd.gsfc.nasa.gov/User/difguide/difman.html DIF]<br />
* [http://fgdc.er.usgs.gov/ FGDC]<br />
* [http://fgdc.er.usgs.gov/metadata FGDC]<br />
* [http://www.opengeospatial.org/] and Open GIS standards [http://www.opengeospatial.org/specs/?page=specs OpenGIS-Specs] Check out GML.<br />
* [http://www.isotc211.org/ ISO]<br />
* [http://ceonet.gc.ca/ GeoConnections]<br />
* [http://www.anzlic.org.au/ ANZLIC (Australian)]<br />
<br />
''Further reading on georeferencing metadata''<br />
* [http://alexandria.sdc.ucsb.edu/ The Alexandria Project]<br />
* [http://www.esri.com/news/arcuser/0402/docmanage3of3.html]<br />
* [http://www.geovrml.org/issues/ GeoVRML]<br />
* [http://www.ncgia.ucsb.edu/globalgrids-book/internet/]<br />
* [http://www.in-duce.net/archives/2003/05/20/geotags_in_exif_headers.php Geotags in EXIF Headers]<br />
<br />
''Is anybody using this wgs_84 vocab?''<br />
''Are there collaborative RDF knowledgebases about geo info I can contribute to?''<br />
* [http://geourl.org/ GeoURL] maps lat/long to web pages and their dc:title, plus the geo:lat/geo:long of a related foaf:topic. e.g. [http://geourl.org/rdf/?lat=51&lon=-3.00000000000001 weather at G7WBE] see also info on [http://geourl.org/add.html locating and adding yourself] (''does this use wgs_84? or somethign else?'')<br />
* [http://space.frot.org/ spacenamespace] (sample record for [http://space.frot.org/a_space/Bethnal_Green_Station Bethnal_Green_Station], now using our wgs_84 vocab)<br />
<br />
''How accurate are lat/lon coordinates?''<br />
[http://elib.cs.berkeley.edu/manis/GeorefGuide.html Georeferencing Guidelines] contains a lot of useful background information on georeferencing, but most importantly, contains a table that details the level of uncertainty (in meters) associated with various levels of precision in WGS-84 coordinates.<br />
<br />
''what do you mean by WGS_84 vocab?''<br />
* WGS-84 refers to a certain projection. see [http://www.wgs84.com/wgs84/wgs84.htm info on WGS-84] and [http://www.colorado.edu/geography/gcraft/notes/coordsys/coordsys.html coordinate systems] overview<br />
<br />
So why doesn't the WGS-84 vocab explicitly reference wgs-84 in the resulting RDF data? Not having the string WGS-84 near the lat/lon coordinates may make it unclear to software which coordinate system is referenced. Especially since the schema states ''A point, typically described using a coordinate system relative to Earth, such as WGS84.''?<br />
<br />
''Business cards have geographical info; anybody playing with that?''<br />
<br />
* see [[GeoVcard]]<br />
<br />
''Travel planning is a pain; does the [[SemanticWeb]] help?''<br />
<br />
* see [[TravelTools]]<br />
<br />
''Speaking of travel... can I use the [[SemanticWeb]] to find restaurants when I travel?''<br />
<br />
* see [[RestaurantRecommendation]] and [[OpeningHoursUseCase]]<br />
<br />
''What if I want to blog about the places I visit?<br />
* [http://www.excio.com Geoblogging Tool]<br />
<br />
''Any other RDF data about places?''<br />
* [http://www.daml.org/2001/02/geofile/ DAML Geofile Descriptions]<br />
* [http://www.kms.dk/adresser Address location data for Denmarks 2.2 million official addresses] - Coordinates are in "EUREF 89 (WGS84) UTM zone 32". Also available in RDF/XML from the [http://dk.space.frot.org/ Danish node] of the [http://space.frot.org/ spacenamespace] project.<br />
* [http://www.govtrack.us/data/rdf/ GovTrack]'s usgeo.uf1.towns.n3 and usgeo.uf1.villages.n3 contain lat/long coords of all towns and census-places in the U.S., using wgs_84.<br />
<br />
''does anyone have some pointers for storing TGN-like geographic place information in RDF? specifically, place containership i.e. a place called england contains a place called sussex?''<br />
* The TAP KB does; e.g. [http://tap.stanford.edu/cgi-bin/kb.pl?node=CountryUnited_Kingdom&op=show&syn=10&browse=all CountryUnited_Kingdom]<br />
<br />
''OK, so lat/long seems done; what about relations between places... inRegion, cospatial and the like?''<br />
<br />
* Hmm... [[BuildOrBuyTerms]]... use the [http://www.cyc.com/cyc-2-1/toc.html cyc] terms? or make synonyms?<br />
<br />
An intern at W3C is going to work on an SVG tool for putting things on maps and being able to use different kinds of description - lat/long, named places, etc. He starts on 2003-05-05. The 4 month project is not yet completely defined, and suggestions (via mailing list) are welcome.<br />
<br />
''Are there any cool SVG visualization tools?''<br />
* [http://www.jibbering.com/2002/8/foaf-people-map.svg SVG foafmap] (plot of [http://www.jibbering.com/foaf/ foafnaut] nearestAirport data)<br />
<br />
''How can I map city names to latitude/longitude?''<br />
* see [[CityLookup]], a use case for mapping weather underground data to lat/long with cwm<br />
* [http://geourl.org/resources.html GeoURL's resources page] has lots of useful links for finding lat/long from maps<br />
<br />
''How can I compute distances between places?''<br />
* [http://infomesh.net/2001/12/map/ RDF And Distances], by Sean Palmer. Uses Cwm to generate a set of distances from town to town in the U.S.A., based upon map coordinates. (also schema: [http://infomesh.net/info/geo/ infomesh-geo])<br />
<br />
''Any work on U.S. Postal info, like city/state/zip? Can I print mailing labels from RDF data?''<br />
* [http://www.w3.org/2000/10/swap/pim/usps An RDF Schema for United States Postal Addressing Standards] by [[DanConnolly]] (in RDF/N3)<br />
* [http://www.w3.org/2000/10/swap/pim/jobieLabels.pl jobieLabels.pl] in [http://www.w3.org/2000/10/swap/pim/ swap pim] works in limited cases (specific RDF schema, printer, avery label size); though it's written in perl and you could adapt it to your situation.<br />
<br />
''Are there sources of data out there that I might mine for geographic data?''<br />
* [http://www.census.gov/geo/www/tiger/zip1999.html US Zip Codes]<br />
* [http://www.itatwork.freeserve.co.uk/waypoints.htm UK waypoints] (over 5000 waypoints for download)<br />
* [http://freegis.org/geo-data.en.html Free Geo Data]<br />
* [http://www.itatwork.freeserve.co.uk/waypoints.htm UK waypoints] (over 5000 waypoints for download)<br />
* [http://bbs.qqfans.com waypoints] (over 8000 waypoints for download)<br />
* [http://www.bangor.ac.uk/is/iss025/osgbfaq.htm The Ordnance Survey of Britain and Conversion of Latitude and Longitude to/from OS references] FAQ notes by Phil Brady (includes information on conversion code, including MS Excel .xls and Quickbasic versions)<br />
* NGA's [http://earth-info.nga.mil/gns/html/index.html GEOnet Names Server] seems to be the source for the U.N.'s <br />
<br />
[http://unstats.un.org/unsd/citydata/default.asp Capital cities and cities of 100,000 and more inhabitants], which [[DanConnolly]] [http://www.w3.org/2000/04/mem-news/teamToGlobe.n3 team2Globe.n3]<br />
<br />
''How about existing open source software I can build on?''<br />
* [http://search.cpan.org/author/MSCHWERN/Geo-TigerLine-0.01/ Geo]</div>Danbrihttps://www.w3.org/wiki/index.php?title=GeoInfo&diff=99950GeoInfo2016-09-19T17:03:34Z<p>Danbri: updated</p>
<hr />
<div>__NOTOC__<br />
Places are a recurring theme in the [[SemanticWeb]], along with people,<br />
documents, times, and money. (see [[FriendOfaFriend]], [[DublinCore]], [[RdfCalendar]],<br />
as well as [[SeedApplications]] and [[VocabularyMarket]]). See [[GeoOnion]] for an attempt to relate lat/long points to 'within n metres of' concentric circles that encompass them.<br />
<br />
So far, we have a [http://www.w3.org/2003/01/geo/ lat/long vocab page and workspace].<br />
The coolest thing about it is probably that the [http://geourl.org/ GeoURL]<br />
database, with zillions of web pages related to lat/long, can be queried with<br />
results in RDF using this vocabulary; results look like...<br />
<br />
<br />
<pre><nowiki><br />
<rdf:RDF<br />
xmlns:dc="http://purl.org/dc/elements/1.1/"<br />
xmlns:foaf="http://xmlns.com/foaf/0.1/"<br />
xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"<br />
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
<br />
<rdf:Description rdf:about="http://www.cs.cmu.edu/~sprite/index.html"><br />
<dc:title>Bridget Spitznagel</dc:title><br />
<foaf:topic rdf:parseType="Resource"><br />
<geo:lat>40.442673</geo:lat><br />
<geo:long>-79.945815</geo:long><br />
</foaf:topic><br />
</rdf:Description><br />
</rdf:RDF><br />
</nowiki></pre><br />
<br />
<br />
Nearby: [[GeoOnion]], [[CoordinateProperty]]<br />
=== Q & A ===<br />
<br />
[[Category:Faq]]<br />
<br />
''Is there an upcoming [[ScheduledTopicChat]] on this stuff?''<br />
<br />
* hmm... not clear.<br />
* stay tuned to www-rdf-interest [[MailingLists]] for notice, which should come a week or so in advance.<br />
<br />
''What's on the agenda?''<br />
<br />
* review of outstanding stuff from 16Apr, 30 Apr, 28 May:<br />
** [[ActionItems]] on libby, danbri, danc, @@others?<br />
* ''your agenda request here''<br />
<br />
''Has there been any [[ScheduledTopicChat]] on this stuff?''<br />
<br />
* [http://rdfig.xmlhack.com/2003/05/28/2003-05-28.html 28 May weblog]: GML, shapefiles, geotools, [http://fri.sfasu.edu/data/geographic/world/shape/ timezone shapefiles]<br />
* [http://rdfig.xmlhack.com/2003/04/30/2003-04-30.html 30 Apr weblog]<br />
* [http://rdfig.xmlhack.com/2003/04/16/2003-04-16.html#1050501406.933781 notes from 16Apr], [http://www.w3.org/2002/12/cal/test/20030416geomtg.rdf 16 Apr geo meeting calendar]<br />
* [http://lists.w3.org/Archives/Public/www-rdf-calendar/2003Apr/0010.html 9Apr summary]<br />
<br />
Updated by --[[User:Danbri|Dan Brickley]] ([[User talk:Danbri|talk]]) 17:03, 19 September 2016 (UTC) Sept 2016 for new domain name on these links: <br />
<br />
* http://swig.planetrdf.com/2003/05/28/2003-05-28.html<br />
* http://swig.planetrdf.com/2003/04/30/2003-04-30.html<br />
* http://swig.planetrdf.com/2003/04/16/2003-04-16.html#1050501406.933781<br />
<br />
''Who's working on this stuff?''<br />
<br />
The following folks have shown interest:<br />
<br />
* [[DanBri]] (prefers weds for #rdfig chats)<br />
* [[LibbyMiller]]<br />
* [[MortenFrederiksen]].<br />
* [[JoWalsh]]<br />
* [[DanConnolly]]<br />
* ChaalsMcCN<br />
* [[KjetilKjernsmo]]<br />
<br />
See also attendance records for previous chats, above.<br />
<br />
''Is this a formal standardization effort?''<br />
<br />
* It is more of an experiment in representing mapping and location data within the RDF graph data model.<br />
<br />
''Is anybody building an RDF vocabulary for stuff like latitude/longitude?''<br />
* the [http://www.w3.org/2003/01/geo/ lat/long vocab page and workspace] is nearby. It's based on [http://www.wgs84.com/ WGS 84 - World Geodetic System 1984]. See also the [http://www.wgs84.com/wgs84/wgs84.htm Background document]<br />
* [http://www.w3.org/2000/10/swap/pim/earthMap.n3 Earth Maps, Latitudes, and Longitudes: An RDF Schema] (in RDF/N3, based on Xplanet) (is it WGS84? can we define sub-properties?)<br />
* [http://www.mapbureau.com/rdfmap/spec.html RDFMap spec] ([http://groups.yahoo.com/group/rss-dev/message/2922 rss-dev announcment] and [http://groups.yahoo.com/group/rss-dev/message/2950 follow up]).<br />
* DAML GEO stuff: [http://www.daml.org/listarchive/daml-spatial/index.html daml-spatial list archive]<br />
* SUMO; e.g. [http://www.daml.org/listarchive/daml-spatial/0004.html spatial ontology starter] Adam Pease 27 Jan 2003 to daml-spatial<br />
* the [http://www.cyc.com/cycdoc/vocab/geography-vocab.html cyc geography vocabulary] was released in DAML/RDF/XML form: [http://opencyc.sourceforge.net/daml/cyc.daml cyc.daml]. ''@@when? there's a newer release, too, isn't there?''<br />
* [[GeoRDF]]<br />
* [[GeoMetadataOverSvg]]<br />
* [http://www.geonames.org/ontology/ Geonames.org Ontology]<br />
<br />
''Need to be careful about specifity''<br />
<br />
''OK, but you can't put RDF into XHTML and have it (easily) validate. So what's the best way to get georeferencing data into an (X)HTML page? There seem to be many choices, without a clear winner. The [[DublinCore]] DC.Coverage.spatial type would seem to be the most desireable, but is perhaps the one that is least defined (at least it is confusing to implement)''<br />
<br />
(X)HTML georeferencing formats:<br />
* [http://dublincore.org/documents/dcmi-point/ DCMIPOINT]<br />
* [http://www.getty.edu/research/tools/vocabulary/tgn/ The Getty Thesaurus of Geographic Names (TGN)]<br />
* [http://geourl.org/ GeoURL]<br />
* [http://geotags.com/geo/geotags2.html Geo Tags]<br />
<br />
RSS georeferencing formats:<br />
* [http://igargoyle.com/rss/1.0/modules/spatial/ dcterms:spatial RSS 1.0 module]<br />
<br />
RSS Reader using [[GeoInfo]]:<br />
* [www.plazoo.com/info/de/newsreader.asp RSS Reader from plazoo]<br />
<br />
Other georeferencing formats:<br />
* [http://lcweb.loc.gov/marc/ MARC]<br />
* [http://gcmd.gsfc.nasa.gov/User/difguide/difman.html DIF]<br />
* [http://fgdc.er.usgs.gov/ FGDC]<br />
* [http://fgdc.er.usgs.gov/metadata FGDC]<br />
* [http://www.opengeospatial.org/] and Open GIS standards [http://www.opengeospatial.org/specs/?page=specs OpenGIS-Specs] Check out GML.<br />
* [http://www.isotc211.org/ ISO]<br />
* [http://ceonet.gc.ca/ GeoConnections]<br />
* [http://www.anzlic.org.au/ ANZLIC (Australian)]<br />
<br />
''Further reading on georeferencing metadata''<br />
* [http://alexandria.sdc.ucsb.edu/ The Alexandria Project]<br />
* [http://www.esri.com/news/arcuser/0402/docmanage3of3.html]<br />
* [http://www.geovrml.org/issues/ GeoVRML]<br />
* [http://www.ncgia.ucsb.edu/globalgrids-book/internet/]<br />
* [http://www.in-duce.net/archives/2003/05/20/geotags_in_exif_headers.php Geotags in EXIF Headers]<br />
<br />
''Is anybody using this wgs_84 vocab?''<br />
''Are there collaborative RDF knowledgebases about geo info I can contribute to?''<br />
* [http://geourl.org/ GeoURL] maps lat/long to web pages and their dc:title, plus the geo:lat/geo:long of a related foaf:topic. e.g. [http://geourl.org/rdf/?lat=51&lon=-3.00000000000001 weather at G7WBE] see also info on [http://geourl.org/add.html locating and adding yourself] (''does this use wgs_84? or somethign else?'')<br />
* [http://space.frot.org/ spacenamespace] (sample record for [http://space.frot.org/a_space/Bethnal_Green_Station Bethnal_Green_Station], now using our wgs_84 vocab)<br />
<br />
''How accurate are lat/lon coordinates?''<br />
[http://elib.cs.berkeley.edu/manis/GeorefGuide.html Georeferencing Guidelines] contains a lot of useful background information on georeferencing, but most importantly, contains a table that details the level of uncertainty (in meters) associated with various levels of precision in WGS-84 coordinates.<br />
<br />
''what do you mean by WGS_84 vocab?''<br />
* WGS-84 refers to a certain projection. see [http://www.wgs84.com/wgs84/wgs84.htm info on WGS-84] and [http://www.colorado.edu/geography/gcraft/notes/coordsys/coordsys.html coordinate systems] overview<br />
<br />
So why doesn't the WGS-84 vocab explicitly reference wgs-84 in the resulting RDF data? Not having the string WGS-84 near the lat/lon coordinates may make it unclear to software which coordinate system is referenced. Especially since the schema states ''A point, typically described using a coordinate system relative to Earth, such as WGS84.''?<br />
<br />
''Business cards have geographical info; anybody playing with that?''<br />
<br />
* see [[GeoVcard]]<br />
<br />
''Travel planning is a pain; does the [[SemanticWeb]] help?''<br />
<br />
* see [[TravelTools]]<br />
<br />
''Speaking of travel... can I use the [[SemanticWeb]] to find restaurants when I travel?''<br />
<br />
* see [[RestaurantRecommendation]] and [[OpeningHoursUseCase]]<br />
<br />
''What if I want to blog about the places I visit?<br />
* [http://www.excio.com Geoblogging Tool]<br />
<br />
''Any other RDF data about places?''<br />
* [http://www.daml.org/2001/02/geofile/ DAML Geofile Descriptions]<br />
* [http://www.kms.dk/adresser Address location data for Denmarks 2.2 million official addresses] - Coordinates are in "EUREF 89 (WGS84) UTM zone 32". Also available in RDF/XML from the [http://dk.space.frot.org/ Danish node] of the [http://space.frot.org/ spacenamespace] project.<br />
* [http://www.govtrack.us/data/rdf/ GovTrack]'s usgeo.uf1.towns.n3 and usgeo.uf1.villages.n3 contain lat/long coords of all towns and census-places in the U.S., using wgs_84.<br />
<br />
''does anyone have some pointers for storing TGN-like geographic place information in RDF? specifically, place containership i.e. a place called england contains a place called sussex?''<br />
* The TAP KB does; e.g. [http://tap.stanford.edu/cgi-bin/kb.pl?node=CountryUnited_Kingdom&op=show&syn=10&browse=all CountryUnited_Kingdom]<br />
<br />
''OK, so lat/long seems done; what about relations between places... inRegion, cospatial and the like?''<br />
<br />
* Hmm... [[BuildOrBuyTerms]]... use the [http://www.cyc.com/cyc-2-1/toc.html cyc] terms? or make synonyms?<br />
<br />
An intern at W3C is going to work on an SVG tool for putting things on maps and being able to use different kinds of description - lat/long, named places, etc. He starts on 2003-05-05. The 4 month project is not yet completely defined, and suggestions (via mailing list) are welcome.<br />
<br />
''Are there any cool SVG visualization tools?''<br />
* [http://www.jibbering.com/2002/8/foaf-people-map.svg SVG foafmap] (plot of [http://www.jibbering.com/foaf/ foafnaut] nearestAirport data)<br />
<br />
''How can I map city names to latitude/longitude?''<br />
* see [[CityLookup]], a use case for mapping weather underground data to lat/long with cwm<br />
* [http://geourl.org/resources.html GeoURL's resources page] has lots of useful links for finding lat/long from maps<br />
<br />
''How can I compute distances between places?''<br />
* [http://infomesh.net/2001/12/map/ RDF And Distances], by Sean Palmer. Uses Cwm to generate a set of distances from town to town in the U.S.A., based upon map coordinates. (also schema: [http://infomesh.net/info/geo/ infomesh-geo])<br />
<br />
''Any work on U.S. Postal info, like city/state/zip? Can I print mailing labels from RDF data?''<br />
* [http://www.w3.org/2000/10/swap/pim/usps An RDF Schema for United States Postal Addressing Standards] by [[DanConnolly]] (in RDF/N3)<br />
* [http://www.w3.org/2000/10/swap/pim/jobieLabels.pl jobieLabels.pl] in [http://www.w3.org/2000/10/swap/pim/ swap pim] works in limited cases (specific RDF schema, printer, avery label size); though it's written in perl and you could adapt it to your situation.<br />
<br />
''Are there sources of data out there that I might mine for geographic data?''<br />
* [http://www.census.gov/geo/www/tiger/zip1999.html US Zip Codes]<br />
* [http://www.itatwork.freeserve.co.uk/waypoints.htm UK waypoints] (over 5000 waypoints for download)<br />
* [http://freegis.org/geo-data.en.html Free Geo Data]<br />
* [http://www.itatwork.freeserve.co.uk/waypoints.htm UK waypoints] (over 5000 waypoints for download)<br />
* [http://bbs.qqfans.com waypoints] (over 8000 waypoints for download)<br />
* [http://www.bangor.ac.uk/is/iss025/osgbfaq.htm The Ordnance Survey of Britain and Conversion of Latitude and Longitude to/from OS references] FAQ notes by Phil Brady (includes information on conversion code, including MS Excel .xls and Quickbasic versions)<br />
* NGA's [http://earth-info.nga.mil/gns/html/index.html GEOnet Names Server] seems to be the source for the U.N.'s <br />
<br />
[http://unstats.un.org/unsd/citydata/default.asp Capital cities and cities of 100,000 and more inhabitants], which [[DanConnolly]] [http://www.w3.org/2000/04/mem-news/teamToGlobe.n3 team2Globe.n3]<br />
<br />
''How about existing open source software I can build on?''<br />
* [http://search.cpan.org/author/MSCHWERN/Geo-TigerLine-0.01/ Geo]</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structured_Data_Schemas&diff=99647Semantic Web Structured Data Schemas2016-09-08T14:18:01Z<p>Danbri: added more scoping info</p>
<hr />
<div>This page provides a rough agenda and other info for the face to face meeting of Community Groups working in fields related to vocabularies, Semantic Web and related technologies at [https://www.w3.org/2016/09/TPAC/ TPAC 2016]. This was initiated by members of [https://www.w3.org/community/schemaorg/ schema.org]-related groups and the Semantic Web Interest Group to take advantage of the opportunity to meet face to face during TPAC. While all interested parties are welcome the formal room size is small (20), we encourage observers to join in discussions or consider giving up seats for more active participants if needed. We do not expect typical attendees of this meeting to make a dedicated trip to TPAC purely for it; rather it is oriented towards existing TPAC attendees who share an interest in schemas, hence the loose / ad-hoc agenda.<br />
<br />
<br />
==Topics==<br />
<br />
The goal of the meeting is to encourage cross-group discussion about approaches to the collaborative creation, maintainance and evolution of structured data schemas, particularly those designed for wide-scale adoption and iterative development.<br />
<br />
The general topics for discussion will be:<br />
<br />
* Vocabulary development - how can W3C better support vocab development and maintenance, allowing for flexibility and agility without diluting stability.<br />
* Possible future standardization work.<br />
* Potentially discussion of specific topical schemas, if sufficient parties express interest.<br />
<br />
==Agenda==<br />
<br />
As the meeting occurs on TPAC's final day (see [https://www.w3.org/2016/09/TPAC/schedule.html schedule]), we can assume that some participants will have to leave early. Rather than arrange a rigid agenda we have built in scope for self-organization and ad-hoc presentations that draw upon the prior week's TPAC discussions. As a W3C TPAC event we must also assume that many relevant parties will have been unable to travel to the event, and that some very interested parties will be overcommitted and needed in other TPAC events happening simultaneously. <br />
<br />
* 09:00 Intro/welcome, Dan Brickley (chair, schema.org CG, SWIG)<br />
* 09:20 - The W3C perspective for the day, Phil Archer<br />
* 09:30 - Brief Introductions (30 seconds max each) <br />
* 09:45-10:30 - Lightning Talks (5 or 10 mins depending on how many proposed in Wiki below(*).<br />
* 10:30-10:35 - Agenda hacking (collecting suggestions from intros, lightning talks etc.).<br />
* 10:35-11:15 - Morning break (noting that coffee etc stops at 11) - Hall 4, First floor<br />
* 11:15-12:00 - Topical Discuss session no.1. (*)<br />
* 12:00-12:45 - Schema.org, W3C CGs and Github: discussion on the schema.org approach (Dan Brickley session lead)<br />
* 12:45-2:00 - LUNCH - Restaurant, First floor<br />
* 2:00-3:00 - Timeslot to be allocated. (2nd lightning talk session?)<br />
* 3:00-3:45 - Afternoon break - Hall 4, First floor<br />
* 3:45-4:45 - Timeslot to be allocated<br />
* 17:00 Wrap up <br />
<br />
== Lightning Talk and Unallocated Timeslot topics==<br />
<br />
(*) Short talks / presentation /demos are encouraged. Please propose here (or link to [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/ mailing list suggestions]) and we can integrate into the agenda during TPAC and in the morning 'agenda hacking' session.<br />
<br />
* Topic: I18N/L18N, [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/0024.html usecases and designs for language-varying content] from Alexandre Bertails<br />
* Short discussion topic(?): JSON-LD - context files (their role and impact) - Dan Brickley<br />
* Linked Data Fragments, Property Graphs, Linked Data API - how come these aren't W3C standards but POWDER is? - Phil Archer on how W3C decides what to do next.<br />
* Presentation of the [https://doremus-anr.github.io/schema-visualizer/ schema.org visualizer] tool ([https://github.com/DOREMUS-ANR/schema-visualizer/ code]) for visualizing Event and CreativeWork ... and general use of schema.org in the [http://doremus.org/ DOREMUS project] where we have translated the FRBRoo model in schema.org - Raphael Troncy<br />
* Presentation of the [http://nice.3cixty.com/ 3cixty platform] that consumes and produces schema.org metadata in the domain of culture and tourism, return of experience and advertisement for the [http://www.meetup.com/fr-FR/paris-web-of-data/events/232635663/?eventId=232635663 SEO - schema.org meetup] organized in Google Paris - Raphael Troncy<br />
* Your session idea here.<br />
<br />
==Location==<br />
Room 1.06, First floor<br />
<br />
==Registration==<br />
The meeting is '''public''' in that anyone may join it, but you need to be [https://www.w3.org/2002/09/wbs/35125/TPAC2016 registered for TPAC] itself. The room capacity is limited to 20 people which we think means it might be a tight squeeze.<br />
<br />
See also [https://www.w3.org/2002/09/wbs/35125/TPAC2016/registrants#SWDSCG registered attendees list], based on form filled out during TPAC registration.</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structured_Data_Schemas&diff=99640Semantic Web Structured Data Schemas2016-09-08T13:00:42Z<p>Danbri: Fixed URL link syntax.</p>
<hr />
<div>This page provides a rough agenda and other info for the face to face meeting of Community Groups working in fields related to vocabularies, Semantic Web and related technologies at [https://www.w3.org/2016/09/TPAC/ TPAC 2016]. This was initiated by members of [https://www.w3.org/community/schemaorg/ schema.org]-related groups and the Semantic Web Interest Group to take advantage of the opportunity to meet face to face during TPAC. While all interested parties are welcome the formal room size is small (20), we encourage observers to join in discussions or consider giving up seats for more active participants if needed.<br />
<br />
<br />
==Topics==<br />
<br />
The goal of the meeting is to encourage cross-group discussion about approaches to the collaborative creation, maintainance and evolution of structured data schemas, particularly those designed for wide-scale adoption and iterative development.<br />
<br />
The general topics for discussion will be:<br />
<br />
* Vocabulary development - how can W3C better support vocab development and maintenance, allowing for flexibility and agility without diluting stability.<br />
* Possible future standardization work.<br />
* Potentially discussion of specific topical schemas, if sufficient parties express interest.<br />
<br />
==Agenda==<br />
<br />
As the meeting occurs on TPAC's final day (see [https://www.w3.org/2016/09/TPAC/schedule.html schedule]), we can assume that some participants will have to leave early. Rather than arrange a rigid agenda we have built in scope for self-organization and ad-hoc presentations that draw upon the prior week's TPAC discussions. As a W3C TPAC event we must also assume that many relevant parties will have been unable to travel to the event, and that some very interested parties will be overcommitted and needed in other TPAC events happening simultaneously. <br />
<br />
* 09:00 Intro/welcome, Dan Brickley (chair, schema.org CG, SWIG)<br />
* 09:20 - The W3C perspective for the day, Phil Archer<br />
* 09:30 - Brief Introductions (30 seconds max each) <br />
* 09:45-10:30 - Lightning Talks (5 or 10 mins depending on how many proposed in Wiki below(*).<br />
* 10:30-10:35 - Agenda hacking (collecting suggestions from intros, lightning talks etc.).<br />
* 10:35-11:15 - Morning break (noting that coffee etc stops at 11) - Hall 4, First floor<br />
* 11:15-12:00 - Topical Discuss session no.1. (*)<br />
* 12:00-12:45 - Schema.org, W3C CGs and Github: discussion on the schema.org approach (Dan Brickley session lead)<br />
* 12:45-2:00 - LUNCH - Restaurant, First floor<br />
* 2:00-3:00 - Timeslot to be allocated. (2nd lightning talk session?)<br />
* 3:00-3:45 - Afternoon break - Hall 4, First floor<br />
* 3:45-4:45 - Timeslot to be allocated<br />
* 17:00 Wrap up <br />
<br />
== Lightning Talk and Unallocated Timeslot topics==<br />
<br />
(*) Short talks / presentation /demos are encouraged. Please propose here (or link to [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/ mailing list suggestions]) and we can integrate into the agenda during TPAC and in the morning 'agenda hacking' session.<br />
<br />
* Topic: I18N/L18N, [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/0024.html usecases and designs for language-varying content] from Alexandre Bertails<br />
* Short discussion topic(?): JSON-LD - context files (their role and impact) - Dan Brickley<br />
* Linked Data Fragments, Property Graphs, Linked Data API - how come these aren't W3C standards but POWDER is? - Phil Archer on how W3C decides what to do next.<br />
* Presentation of the [https://doremus-anr.github.io/schema-visualizer/ schema.org visualizer] tool ([https://github.com/DOREMUS-ANR/schema-visualizer/ code]) for visualizing Event and CreativeWork ... and general use of schema.org in the [http://doremus.org/ DOREMUS project] where we have translated the FRBRoo model in schema.org - Raphael Troncy<br />
* Presentation of the [http://nice.3cixty.com/ 3cixty platform] that consumes and produces schema.org metadata in the domain of culture and tourism, return of experience and advertisement for the [http://www.meetup.com/fr-FR/paris-web-of-data/events/232635663/?eventId=232635663 SEO - schema.org meetup] organized in Google Paris - Raphael Troncy<br />
* Your session idea here.<br />
<br />
==Location==<br />
Room 1.06, First floor<br />
<br />
==Registration==<br />
The meeting is '''public''' in that anyone may join it, but you need to be [https://www.w3.org/2002/09/wbs/35125/TPAC2016 registered for TPAC] itself. The room capacity is limited to 20 people which we think means it might be a tight squeeze.<br />
<br />
See also [https://www.w3.org/2002/09/wbs/35125/TPAC2016/registrants#SWDSCG registered attendees list], based on form filled out during TPAC registration.</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structured_Data_Schemas&diff=99639Semantic Web Structured Data Schemas2016-09-08T13:00:09Z<p>Danbri: /* Registration */</p>
<hr />
<div>This page provides a rough agenda and other info for the face to face meeting of Community Groups working in fields related to vocabularies, Semantic Web and related technologies at [https://www.w3.org/2016/09/TPAC/ TPAC 2016]. This was initiated by members of [https://www.w3.org/community/schemaorg/ schema.org]-related groups and the Semantic Web Interest Group to take advantage of the opportunity to meet face to face during TPAC. While all interested parties are welcome the formal room size is small (20), we encourage observers to join in discussions or consider giving up seats for more active participants if needed.<br />
<br />
<br />
==Topics==<br />
<br />
The goal of the meeting is to encourage cross-group discussion about approaches to the collaborative creation, maintainance and evolution of structured data schemas, particularly those designed for wide-scale adoption and iterative development.<br />
<br />
The general topics for discussion will be:<br />
<br />
* Vocabulary development - how can W3C better support vocab development and maintenance, allowing for flexibility and agility without diluting stability.<br />
* Possible future standardization work.<br />
* Potentially discussion of specific topical schemas, if sufficient parties express interest.<br />
<br />
==Agenda==<br />
<br />
As the meeting occurs on TPAC's final day (see [https://www.w3.org/2016/09/TPAC/schedule.html schedule]), we can assume that some participants will have to leave early. Rather than arrange a rigid agenda we have built in scope for self-organization and ad-hoc presentations that draw upon the prior week's TPAC discussions. As a W3C TPAC event we must also assume that many relevant parties will have been unable to travel to the event, and that some very interested parties will be overcommitted and needed in other TPAC events happening simultaneously. <br />
<br />
* 09:00 Intro/welcome, Dan Brickley (chair, schema.org CG, SWIG)<br />
* 09:20 - The W3C perspective for the day, Phil Archer<br />
* 09:30 - Brief Introductions (30 seconds max each) <br />
* 09:45-10:30 - Lightning Talks (5 or 10 mins depending on how many proposed in Wiki below(*).<br />
* 10:30-10:35 - Agenda hacking (collecting suggestions from intros, lightning talks etc.).<br />
* 10:35-11:15 - Morning break (noting that coffee etc stops at 11) - Hall 4, First floor<br />
* 11:15-12:00 - Topical Discuss session no.1. (*)<br />
* 12:00-12:45 - Schema.org, W3C CGs and Github: discussion on the schema.org approach (Dan Brickley session lead)<br />
* 12:45-2:00 - LUNCH - Restaurant, First floor<br />
* 2:00-3:00 - Timeslot to be allocated. (2nd lightning talk session?)<br />
* 3:00-3:45 - Afternoon break - Hall 4, First floor<br />
* 3:45-4:45 - Timeslot to be allocated<br />
* 17:00 Wrap up <br />
<br />
== Lightning Talk and Unallocated Timeslot topics==<br />
<br />
(*) Short talks / presentation /demos are encouraged. Please propose here (or link to [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/ mailing list suggestions]) and we can integrate into the agenda during TPAC and in the morning 'agenda hacking' session.<br />
<br />
* Topic: I18N/L18N, [usecases and designs for language-varying content](https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/0024.html|Alexandre Bertails)<br />
* Short discussion topic(?): JSON-LD - context files (their role and impact) - Dan Brickley<br />
* Linked Data Fragments, Property Graphs, Linked Data API - how come these aren't W3C standards but POWDER is? - Phil Archer on how W3C decides what to do next.<br />
* Presentation of the [https://doremus-anr.github.io/schema-visualizer/ schema.org visualizer] tool ([https://github.com/DOREMUS-ANR/schema-visualizer/ code]) for visualizing Event and CreativeWork ... and general use of schema.org in the [http://doremus.org/ DOREMUS project] where we have translated the FRBRoo model in schema.org - Raphael Troncy<br />
* Presentation of the [http://nice.3cixty.com/ 3cixty platform] that consumes and produces schema.org metadata in the domain of culture and tourism, return of experience and advertisement for the [http://www.meetup.com/fr-FR/paris-web-of-data/events/232635663/?eventId=232635663 SEO - schema.org meetup] organized in Google Paris - Raphael Troncy<br />
* Your session idea here.<br />
<br />
==Location==<br />
Room 1.06, First floor<br />
<br />
==Registration==<br />
The meeting is '''public''' in that anyone may join it, but you need to be [https://www.w3.org/2002/09/wbs/35125/TPAC2016 registered for TPAC] itself. The room capacity is limited to 20 people which we think means it might be a tight squeeze.<br />
<br />
See also [https://www.w3.org/2002/09/wbs/35125/TPAC2016/registrants#SWDSCG registered attendees list], based on form filled out during TPAC registration.</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structured_Data_Schemas&diff=99637Semantic Web Structured Data Schemas2016-09-08T12:59:37Z<p>Danbri: added attendee rgistration</p>
<hr />
<div>This page provides a rough agenda and other info for the face to face meeting of Community Groups working in fields related to vocabularies, Semantic Web and related technologies at [https://www.w3.org/2016/09/TPAC/ TPAC 2016]. This was initiated by members of [https://www.w3.org/community/schemaorg/ schema.org]-related groups and the Semantic Web Interest Group to take advantage of the opportunity to meet face to face during TPAC. While all interested parties are welcome the formal room size is small (20), we encourage observers to join in discussions or consider giving up seats for more active participants if needed.<br />
<br />
<br />
==Topics==<br />
<br />
The goal of the meeting is to encourage cross-group discussion about approaches to the collaborative creation, maintainance and evolution of structured data schemas, particularly those designed for wide-scale adoption and iterative development.<br />
<br />
The general topics for discussion will be:<br />
<br />
* Vocabulary development - how can W3C better support vocab development and maintenance, allowing for flexibility and agility without diluting stability.<br />
* Possible future standardization work.<br />
* Potentially discussion of specific topical schemas, if sufficient parties express interest.<br />
<br />
==Agenda==<br />
<br />
As the meeting occurs on TPAC's final day (see [https://www.w3.org/2016/09/TPAC/schedule.html schedule]), we can assume that some participants will have to leave early. Rather than arrange a rigid agenda we have built in scope for self-organization and ad-hoc presentations that draw upon the prior week's TPAC discussions. As a W3C TPAC event we must also assume that many relevant parties will have been unable to travel to the event, and that some very interested parties will be overcommitted and needed in other TPAC events happening simultaneously. <br />
<br />
* 09:00 Intro/welcome, Dan Brickley (chair, schema.org CG, SWIG)<br />
* 09:20 - The W3C perspective for the day, Phil Archer<br />
* 09:30 - Brief Introductions (30 seconds max each) <br />
* 09:45-10:30 - Lightning Talks (5 or 10 mins depending on how many proposed in Wiki below(*).<br />
* 10:30-10:35 - Agenda hacking (collecting suggestions from intros, lightning talks etc.).<br />
* 10:35-11:15 - Morning break (noting that coffee etc stops at 11) - Hall 4, First floor<br />
* 11:15-12:00 - Topical Discuss session no.1. (*)<br />
* 12:00-12:45 - Schema.org, W3C CGs and Github: discussion on the schema.org approach (Dan Brickley session lead)<br />
* 12:45-2:00 - LUNCH - Restaurant, First floor<br />
* 2:00-3:00 - Timeslot to be allocated. (2nd lightning talk session?)<br />
* 3:00-3:45 - Afternoon break - Hall 4, First floor<br />
* 3:45-4:45 - Timeslot to be allocated<br />
* 17:00 Wrap up <br />
<br />
== Lightning Talk and Unallocated Timeslot topics==<br />
<br />
(*) Short talks / presentation /demos are encouraged. Please propose here (or link to [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/ mailing list suggestions]) and we can integrate into the agenda during TPAC and in the morning 'agenda hacking' session.<br />
<br />
* Topic: I18N/L18N, [usecases and designs for language-varying content](https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/0024.html|Alexandre Bertails)<br />
* Short discussion topic(?): JSON-LD - context files (their role and impact) - Dan Brickley<br />
* Linked Data Fragments, Property Graphs, Linked Data API - how come these aren't W3C standards but POWDER is? - Phil Archer on how W3C decides what to do next.<br />
* Presentation of the [https://doremus-anr.github.io/schema-visualizer/ schema.org visualizer] tool ([https://github.com/DOREMUS-ANR/schema-visualizer/ code]) for visualizing Event and CreativeWork ... and general use of schema.org in the [http://doremus.org/ DOREMUS project] where we have translated the FRBRoo model in schema.org - Raphael Troncy<br />
* Your session idea here.<br />
<br />
==Location==<br />
Room 1.06, First floor<br />
<br />
==Registration==<br />
The meeting is '''public''' in that anyone may join it, but you need to be [https://www.w3.org/2002/09/wbs/35125/TPAC2016 registered for TPAC] itself. The room capacity is limited to 20 people which we think means it might be a tight squeeze.<br />
<br />
See also [registered attendees list](https://www.w3.org/2002/09/wbs/35125/TPAC2016/registrants#SWDSCG), based on form filled out during TPAC registration.</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structured_Data_Schemas&diff=99633Semantic Web Structured Data Schemas2016-09-08T12:39:53Z<p>Danbri: </p>
<hr />
<div>This page provides a rough agenda and other info for the face to face meeting of Community Groups working in fields related to vocabularies, Semantic Web and related technologies at [https://www.w3.org/2016/09/TPAC/ TPAC 2016]. This was initiated by members of [https://www.w3.org/community/schemaorg/ schema.org]-related groups and the Semantic Web Interest Group to take advantage of the opportunity to meet face to face during TPAC. While all interested parties are welcome the formal room size is small (20), we encourage observers to join in discussions or consider giving up seats for more active participants if needed.<br />
<br />
<br />
==Topics==<br />
<br />
The goal of the meeting is to encourage cross-group discussion about approaches to the collaborative creation, maintainance and evolution of structured data schemas, particularly those designed for wide-scale adoption and iterative development.<br />
<br />
The general topics for discussion will be:<br />
<br />
* Vocabulary development - how can W3C better support vocab development and maintenance, allowing for flexibility and agility without diluting stability.<br />
* Possible future standardization work.<br />
* Potentially discussion of specific topical schemas, if sufficient parties express interest.<br />
<br />
==Agenda==<br />
<br />
As the meeting occurs on TPAC's final day (see [https://www.w3.org/2016/09/TPAC/schedule.html schedule]), we can assume that some participants will have to leave early. Rather than arrange a rigid agenda we have built in scope for self-organization and ad-hoc presentations that draw upon the prior week's TPAC discussions. As a W3C TPAC event we must also assume that many relevant parties will have been unable to travel to the event, and that some very interested parties will be overcommitted and needed in other TPAC events happening simultaneously. <br />
<br />
* 09:00 Intro/welcome, Dan Brickley (chair, schema.org CG, SWIG)<br />
* 09:20 - The W3C perspective for the day, Phil Archer<br />
* 09:30 - Brief Introductions (30 seconds max each) <br />
* 09:45-10:30 - Lightning Talks (5 or 10 mins depending on how many proposed in Wiki below(*).<br />
* 10:30-10:35 - Agenda hacking (collecting suggestions from intros, lightning talks etc.).<br />
* 10:35-11:15 - Morning break (noting that coffee etc stops at 11) - Hall 4, First floor<br />
* 11:15-12:00 - Topical Discuss session no.1. (*)<br />
* 12:00-12:45 - Schema.org, W3C CGs and Github: discussion on the schema.org approach (Dan Brickley session lead)<br />
* 12:45-2:00 - LUNCH - Restaurant, First floor<br />
* 2:00-3:00 - Timeslot to be allocated. (2nd lightning talk session?)<br />
* 3:00-3:45 - Afternoon break - Hall 4, First floor<br />
* 3:45-4:45 - Timeslot to be allocated<br />
* 17:00 Wrap up <br />
<br />
== Lightning Talk and Unallocated Timeslot topics==<br />
<br />
(*) Short talks / presentation /demos are encouraged. Please propose here (or link to [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/ mailing list suggestions]) and we can integrate into the agenda during TPAC and in the morning 'agenda hacking' session.<br />
<br />
* Topic: I18N/L18N, [usecases and designs for language-varying content](https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/0024.html|Alexandre Bertails)<br />
* Short discussion topic(?): JSON-LD - context files (their role and impact) - Dan Brickley<br />
* Your session idea here.<br />
<br />
==Location==<br />
Room 1.06, First floor<br />
<br />
==Registration==<br />
The meeting is '''public''' in that anyone may join it, but you need to be [https://www.w3.org/2002/09/wbs/35125/TPAC2016 registered for TPAC] itself. The room capacity is limited to 20 people which we think means it might be a tight squeeze.</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structured_Data_Schemas&diff=99631Semantic Web Structured Data Schemas2016-09-08T12:15:53Z<p>Danbri: </p>
<hr />
<div>This page provides a rough agenda and other info for the face to face meeting of Community Groups working in fields related to vocabularies, Semantic Web and related technologies at [https://www.w3.org/2016/09/TPAC/ TPAC 2016]. Primarily this was initiated by members of [https://www.w3.org/community/schemaorg/ schema.org]-related groups and the Semantic Web Interest Group. While all interested parties are welcome the formal room size is small (20), we encourage observers to join in discussions or consider giving up seats for more active participants if needed.<br />
<br />
<br />
==Topics==<br />
<br />
The goal of the meeting is to encourage cross-group discussion about approaches to the collaborative creation of structured data schemas, particularly those designed for wide-scale adoption and iterative development.<br />
<br />
The general topics for discussion will be:<br />
<br />
* Vocabulary development - how can W3C better support vocab development and maintenance, allowing for flexibility and agility without diluting stability.<br />
* Possible future standardization work.<br />
* Potentially discussion of specific topical schemas, if sufficient parties express interest.<br />
<br />
==Agenda==<br />
<br />
As the meeting occurs on TPAC's final day (see [https://www.w3.org/2016/09/TPAC/schedule.html schedule]), we can assume that some participants will have to leave early. Rather than arrange a rigid agenda we have built in scope for self-organization and ad-hoc presentations that draw upon the prior week's TPAC discussions. As a W3C TPAC event we must also assume that many relevant parties will have been unable to travel to the event, and that some very interested parties will be overcommitted and needed in other TPAC events happening simultaneously. <br />
<br />
* 09:00 Intro/welcome, Dan Brickley (chair, schema.org CG, SWIG)<br />
* 09:20 - The W3C perspective for the day, Phil Archer<br />
* 09:30 - Brief Introductions (30 seconds max each) <br />
* 09:45-10:30 - Lightning Talks (5 or 10 mins depending on how many proposed in Wiki below(*).<br />
* 10:30-10:35 - Agenda hacking (collecting suggestions from intros, lightning talks etc.).<br />
* 10:35-11:15 - Morning break (noting that coffee etc stops at 11) - Hall 4, First floor<br />
* 11:15-12:00 - Topical Discuss session no.1. (*)<br />
* 12:00-12:45 - Schema.org, W3C CGs and Github: discussion on the schema.org approach (Dan Brickley session lead)<br />
* 12:45-2:00 - LUNCH - Restaurant, First floor<br />
* 2:00-3:00 - Timeslot to be allocated. (2nd lightning talk session?)<br />
* 3:00-3:45 - Afternoon break - Hall 4, First floor<br />
* 3:45-4:45 - Timeslot to be allocated<br />
* 17:00 Wrap up <br />
<br />
== Lightning Talk and Unallocated Timeslot topics==<br />
<br />
(*) Short talks / presentation /demos are encouraged. Please propose here (or link to [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/ mailing list suggestions]) and we can integrate into the agenda during TPAC and in the morning 'agenda hacking' session.<br />
<br />
* Topic: I18N/L18N, [usecases and designs for language-varying content](https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/0024.html|Alexandre Bertails)<br />
* Short discussion topic(?): JSON-LD - context files (their role and impact) - Dan Brickley<br />
* Your session idea here.<br />
<br />
==Location==<br />
Room 1.06, First floor<br />
<br />
==Registration==<br />
The meeting is '''public''' in that anyone may join it, but you need to be [https://www.w3.org/2002/09/wbs/35125/TPAC2016 registered for TPAC] itself. The room capacity is limited to 20 people which we think means it might be a tight squeeze.</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structure_Data_Schemas&diff=99630Semantic Web Structure Data Schemas2016-09-08T12:14:10Z<p>Danbri: Danbri moved page Semantic Web Structure Data Schemas to Semantic Web Structured Data Schemas: typo</p>
<hr />
<div>#REDIRECT [[Semantic Web Structured Data Schemas]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structured_Data_Schemas&diff=99629Semantic Web Structured Data Schemas2016-09-08T12:14:10Z<p>Danbri: Danbri moved page Semantic Web Structure Data Schemas to Semantic Web Structured Data Schemas: typo</p>
<hr />
<div>This page provides a rough agenda and other info for the face to face meeting of Community Groups working in fields related to vocabularies, Semantic Web and related technologies at [https://www.w3.org/2016/09/TPAC/ TPAC 2016]. Primarily this was initiated by members of [https://www.w3.org/community/schemaorg/ schema.org]-related groups and the Semantic Web Interest Group. While all interested parties are welcome the formal room size is small (20), we encourage observers to join in discussions or consider giving up seats for more active participants if needed.<br />
<br />
<br />
==Topics==<br />
<br />
The goal of the meeting is to encourage cross-group discussion about approaches to the collaborative creation of structured data schemas, particularly those designed for wide-scale adoption and iterative development.<br />
<br />
The general topics for discussion will be:<br />
<br />
* Vocabulary development - how can W3C better support vocab development and maintenance, allowing for flexibility and agility without diluting stability.<br />
* Possible future standardization work.<br />
* Potentially discussion of specific topical schemas, if sufficient parties express interest.<br />
<br />
==Agenda==<br />
<br />
As the meeting occurs on TPAC's final day (see [https://www.w3.org/2016/09/TPAC/schedule.html schedule]), we can assume that some participants will have to leave early. Rather than arrange a rigid agenda we have built in scope for self-organization and ad-hoc presentations that draw upon the prior week's TPAC discussions. As a W3C TPAC event we must also assume that many relevant parties will have been unable to travel to the event, and that some very interested parties will be overcommitted and needed in other TPAC events happening simultaneously. <br />
<br />
* 09:00 Intro/welcome, Dan Brickley (chair, schema.org CG, SWIG)<br />
* 09:20 - The W3C perspective for the day, Phil Archer<br />
* 09:30 - Brief Introductions (30 seconds max each) <br />
* 09:45-10:30 - Lightning Talks (5 or 10 mins depending on how many proposed in Wiki below(*).<br />
* 10:30-10:35 - Agenda hacking (collecting suggestions from intros, lightning talks etc.).<br />
* 10:35-11:15 - Morning break (noting that coffee etc stops at 11) - Hall 4, First floor<br />
* 11:15-12:00 - Topical Discuss session no.1. (*)<br />
* 12:00-12:45 - Schema.org, W3C CGs and Github: discussion on the schema.org approach (Dan Brickley session lead)<br />
* 12:45-2:00 - LUNCH - Restaurant, First floor<br />
* 2:00-3:00 - Timeslot to be allocated. (2nd lightning talk session?)<br />
* 3:00-3:45 - Afternoon break - Hall 4, First floor<br />
* 3:45-4:45 - Timeslot to be allocated<br />
* 17:00 Wrap up <br />
<br />
== Lightning Talk and Unallocated Timeslot topics==<br />
<br />
(*) Short talks / presentation /demos are encouraged. Please propose here (or link to [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/ mailing list suggestions]) and we can integrate into the agenda during TPAC and in the morning 'agenda hacking' session.<br />
<br />
* Topic: I18N/L18N, usecases and designs for language-varying content ([[ https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/0024.html|Alexandre Bertails]])<br />
* Your session idea here.<br />
<br />
==Location==<br />
Room 1.06, First floor<br />
<br />
==Registration==<br />
The meeting is '''public''' in that anyone may join it, but you need to be [https://www.w3.org/2002/09/wbs/35125/TPAC2016 registered for TPAC] itself. The room capacity is limited to 20 people which we think means it might be a tight squeeze.</div>Danbrihttps://www.w3.org/wiki/index.php?title=Semantic_Web_Structured_Data_Schemas&diff=99628Semantic Web Structured Data Schemas2016-09-08T12:13:08Z<p>Danbri: Added skeleton with lots of gaps</p>
<hr />
<div>This page provides a rough agenda and other info for the face to face meeting of Community Groups working in fields related to vocabularies, Semantic Web and related technologies at [https://www.w3.org/2016/09/TPAC/ TPAC 2016]. Primarily this was initiated by members of [https://www.w3.org/community/schemaorg/ schema.org]-related groups and the Semantic Web Interest Group. While all interested parties are welcome the formal room size is small (20), we encourage observers to join in discussions or consider giving up seats for more active participants if needed.<br />
<br />
<br />
==Topics==<br />
<br />
The goal of the meeting is to encourage cross-group discussion about approaches to the collaborative creation of structured data schemas, particularly those designed for wide-scale adoption and iterative development.<br />
<br />
The general topics for discussion will be:<br />
<br />
* Vocabulary development - how can W3C better support vocab development and maintenance, allowing for flexibility and agility without diluting stability.<br />
* Possible future standardization work.<br />
* Potentially discussion of specific topical schemas, if sufficient parties express interest.<br />
<br />
==Agenda==<br />
<br />
As the meeting occurs on TPAC's final day (see [https://www.w3.org/2016/09/TPAC/schedule.html schedule]), we can assume that some participants will have to leave early. Rather than arrange a rigid agenda we have built in scope for self-organization and ad-hoc presentations that draw upon the prior week's TPAC discussions. As a W3C TPAC event we must also assume that many relevant parties will have been unable to travel to the event, and that some very interested parties will be overcommitted and needed in other TPAC events happening simultaneously. <br />
<br />
* 09:00 Intro/welcome, Dan Brickley (chair, schema.org CG, SWIG)<br />
* 09:20 - The W3C perspective for the day, Phil Archer<br />
* 09:30 - Brief Introductions (30 seconds max each) <br />
* 09:45-10:30 - Lightning Talks (5 or 10 mins depending on how many proposed in Wiki below(*).<br />
* 10:30-10:35 - Agenda hacking (collecting suggestions from intros, lightning talks etc.).<br />
* 10:35-11:15 - Morning break (noting that coffee etc stops at 11) - Hall 4, First floor<br />
* 11:15-12:00 - Topical Discuss session no.1. (*)<br />
* 12:00-12:45 - Schema.org, W3C CGs and Github: discussion on the schema.org approach (Dan Brickley session lead)<br />
* 12:45-2:00 - LUNCH - Restaurant, First floor<br />
* 2:00-3:00 - Timeslot to be allocated. (2nd lightning talk session?)<br />
* 3:00-3:45 - Afternoon break - Hall 4, First floor<br />
* 3:45-4:45 - Timeslot to be allocated<br />
* 17:00 Wrap up <br />
<br />
== Lightning Talk and Unallocated Timeslot topics==<br />
<br />
(*) Short talks / presentation /demos are encouraged. Please propose here (or link to [https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/ mailing list suggestions]) and we can integrate into the agenda during TPAC and in the morning 'agenda hacking' session.<br />
<br />
* Topic: I18N/L18N, usecases and designs for language-varying content ([[ https://lists.w3.org/Archives/Public/public-schemaorg/2016Sep/0024.html|Alexandre Bertails]])<br />
* Your session idea here.<br />
<br />
==Location==<br />
Room 1.06, First floor<br />
<br />
==Registration==<br />
The meeting is '''public''' in that anyone may join it, but you need to be [https://www.w3.org/2002/09/wbs/35125/TPAC2016 registered for TPAC] itself. The room capacity is limited to 20 people which we think means it might be a tight squeeze.</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas&diff=98063WebSchemas2016-04-14T15:33:06Z<p>Danbri: updated to point to CG</p>
<hr />
<div>=Web Schemas=<br />
<br />
* For [http://schema.org schema.org]'s proposals tracker, see [[WebSchemas/SchemaDotOrgProposals|Extension proposals]] ([https://www.w3.org/2000/09/dbwg/details?group=49967 W3C database entry])<br />
* Web Schemas was a [http://lists.w3.org/Archives/Public/public-html-data-tf/ W3C group] used by the [http://schema.org/ schema.org] project to collaborate with the wider community.<br />
* The group is not just for schema.org; however there is more traffic here about schema.org because it is the only schema.org mailing lists. ''Other projects/vocabularies are very welcome also''!<br />
* Since 2014 schema.org uses [https://github.com/schemaorg/schemaorg/issues Github] for active development (like many other W3C communities).<br />
* Schema.org now has a dedicated [http://www.w3.org/community/schemaorg W3C Community Group] including a public-schemaorg@w3.org [https://lists.w3.org/Archives/Public/public-schemaorg mailing list] <br />
* This Wiki is left primarily for historical record...<br />
<br />
==Introduction==<br />
<br />
This is the main Wiki page for W3C's [http://www.w3.org/2001/sw/interest/ Semantic Web Interest Group] ''Web Schemas'' task force. Amongst other roles, it serves as a public discussion forum for [http://schema.org/ Schema.org], including [[WebSchemas/SchemaDotOrgProposals|Extension proposals]].<br />
<br />
The taskforce chairs are R.V.Guha (Google) and [http://www.w3.org/wiki/User:Danbri Dan Brickley] (Google)<br />
<br />
In scope include collaborations on mappings, tools, extensibility and cross-syntax interoperability. An [http://www.w3.org/wiki/Html-data-tf HTML Data] group is nearby (see also [http://lists.w3.org/Archives/Public/public-html-data-tf/ public-html-data-tf list]); detailed discussion about Web data syntax belongs there.<br />
<br />
See the [http://www.w3.org/2001/sw/interest/webschema.html charter] for more details. <br />
<br />
The group uses the '''public-vocabs@w3.org''' mailing list<br />
<br />
* See [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs@w3.org archives]<br />
* [http://www.w3.org/2011/webschema/track/ Issue Tracker] (organized into "Feedback on X" products/categories, where Xs are Schemas we're discussing)<br />
* To subscribe, send a message to public-vocabs-request@w3.org with Subject: subscribe (see [http://lists.w3.org/ lists.w3.org] for more details). To unsubscribe, do the same but use 'unsubscribe' in the title.<br />
* If you are new to the W3C community, you will need to go through the [http://www.w3.org/2002/09/aa/ archive approval] process before your posts show up in the archives.<br />
* To edit this wiki, you'll need a W3C account; these are [http://www.w3.org/Help/Account/Request/Public available to all]<br />
* To search just this WebSchemas wiki, the issue tracker and schema.org-related mailing lists, try a [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek a custom search].<br />
<br />
Groups who maintain Web Schemas are welcome to use this forum as a feedback channel, in additional to whatever independent mechanisms they also offer.<br />
<br />
In particular, the Schema.org initiative has [http://blog.schema.org/2011/10/w3c-web-schemas-group-is-our-new-public.html adopted] this group as its primary public feedback forum. Others are invited to do likewise.<br />
<br />
Any W3C-related questions, ask Dan Brickley (SWIG chair), c/o danbri@danbri.org<br />
<br />
==Discussion Elsewhere==<br />
<br />
For background discussion on this group, Schema.org and W3C's SWIG, the Oct 2011 [http://semanticweb.com/the-semantic-link-%E2%80%93-episode-11-october-2011_b23961 Semantic Link] podcast may be of interest.<br />
<br />
The Dublin Core Metadata Initiative has a related task group working on [http://wiki.dublincore.org/index.php/Schema.org_Alignment Schema.org Alignment], alongside existing vocabulary collaboration work [http://dublincore.org/documents/dcmi-foaf/ with FOAF].<br />
<br />
For schema.org there are discussions on various sites (unofficial; this group is the only place monitored by Schema.org team) :<br />
<br />
* [https://twitter.com/#!/search/schema.org on Twitter]<br />
* [https://plus.google.com/s/schema.org on G+]<br />
* [http://stackoverflow.com/questions/tagged/schema.org schema.org tag on Stack Overflow]<br />
* [http://answers.semanticweb.com/search/?q=schema.org&Submit=search&t=question answers.semanticweb.com]<br />
* [http://www.quora.com/Schema-org Schema.org on Quora]<br />
<br />
Talks and slides:<br />
<br />
* [http://www.slideshare.net/rvguha/sem-tech2014c Guha's] and [https://docs.google.com/presentation/d/1f-2asymXOCCYHa75OkOnlqc0SExvD44V5D6buyKHfII/edit?usp=sharing Dan Brickley's] SemTech 2014 slides.<br />
<br />
==Proposals from and for Schema.org==<br />
<br />
The main table for managing/tracking schema.org proposals is maintained here: [[WebSchemas/SchemaDotOrgProposals|Schema.org Proposals]]<br />
<br />
A separate entry discussed [http://www.w3.org/wiki/SchemaDotOrgProcess Schema.org Process] as it relates to this group.<br />
<br />
Possible future discussions for Schema.org extensions (proposals welcomed; this list is free-form...):<br />
<br />
* Points of Interest (POIs), collab with OGC group. See [http://opengeospatial.github.io/poi/spec/graphics/poi_model.svg data model], [http://opengeospatial.github.io/poi/spec/poi-core.html latest spec draft].<br />
* Journals / scholarly publishing<br />
* Magazines<br />
* Cultural heritage - libraries, museums, archives. See [http://www.w3.org/2005/Incubator/lld/ Linked Library W3C group], [http://www.europeana.eu/portal/ Europeana], [http://cyber.law.harvard.edu/dpla/Main_Page DPLA], [http://lod-lam.net/summit/ LOD-LAM] etc.<br />
* Bibliographic [http://www.w3.org/community/schemabibex/ Schema Bib Extend]<br />
* Integration of constructs based on Good Relations, FOAF, Dublin Core, ...<br />
* [http://www.w3.org/2011/gld/wiki/Main_Page Linked Govt data]<br />
* Software / Apps<br />
* Health/Medicine<br />
* Cars and Vehicles<br />
* ''the relationships between all of these''<br />
<br />
Some discussions are in fact targeted at the underlying syntaxes used for exposing schema.org markup:<br />
*[[WebSchemas/InverseProperties|Inverse Properties for Microdata]]<br />
<br />
==Tools and Statistics==<br />
<br />
* Statistics<br />
** [http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/0018.html Metadata statistics from Yahoo! Search]<br />
** [http://webdatacommons.org/structureddata/2012-08/stats/stats.html RDFa, Microdata and Microformat deployment statistics from WebDataCommons.org (August 2012)]<br />
** [http://webdatacommons.org/structureddata/2013-11/stats/stats.html RDFa, Microdata and Microformat deployment statistics from WebDataCommons.org (November 2013)]<br />
** [http://sindice.com/stats/basic-stats/# Sindice stats] ([http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/0020.html announcement])<br />
** [http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/ General stats discussion] incl. Bizer et al.'s CommonCrawl extraction ([http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/0029.html announcement]); there is some [http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/0016.html debate about shortcomings of this analysis and the proper interpretation of these].<br />
* Validators<br />
** [http://www.google.com/webmasters/tools/richsnippets Google richsnippets tool]<br />
** [http://www.bing.com/toolbox/EntityExtraction Microsoft Bing Markup Validator] (entity extractor)<br />
** [http://webmaster.yandex.ru/microtest.xml Yandex checker]<br />
** [http://linter.structured-data.org/ Structured Data Linter]<br />
* Search Tools<br />
** [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek Google custom search] of schema.org/webschema-related sites. ([http://www.google.com/search?start=0&num=10&q=MediaObject&client=google-csbe&output=xml_no_dtd&cx=003736913799082383568:c44bi0_xxek XML results] are also [https://developers.google.com/custom-search/docs/xml_results?hl=en#WebSearch_Request_Format available])<br />
** [http://www.raymondcamden.com/index.cfm/2012/11/26/Reading-Microdata-Elements-in-Chrome reading microdata in Chrome]<br />
* Authoring Tools<br />
** [http://rdface.aksw.org RDFaCE]<br />
** [http://schema-creator.org/ Schema Creator]<br />
** [http://www.microdatagenerator.com/ Schema.org Generator | Microdata Generator ]<br />
** [http://www.schemaapp.com Schema App | Schema.org Creator]<br />
* Vocabulary QA<br />
** Sandro Hawke made a [https://gist.github.com/sandhawke/5691972 list of 'overloaded' schema.org properties] that expect sometimes a Thing, sometimes a Text value.<br />
<br />
==Mappings==<br />
<br />
Mappings between various vocabularies of interest on the Web Schemas list. The following are mostly using schema.org as a hub, but others would be great to collect too.<br />
<br />
* [http://www.mkbergman.com/999/new-umbel-release-gains-schema-org-geonames-capabilities/ UMBEL] schema.org mappings (data is in [https://github.com/structureddynamics/UMBEL/blob/master/External%20Ontologies/schema.org.n3 github])<br />
* [http://wiki.dublincore.org/index.php/Schema.org_Alignment Dublin Core / Schema.org Allignment taskforce].<br />
* [http://schema.rdfs.org/mappings.html schema.rdfs.org mapping page].<br />
** [http://schema.rdfs.org/mappings/sioc SIOC mappings]<br />
** [http://mappings.dbpedia.org/server/ontology/export DBpedia mappings file] (download; includes schema.org)<br />
** [http://schema.rdfs.org/mappings/bibo bibo]<br />
** [[GoodRelations]] integration is underway<br />
** [http://schema.rdfs.org/mappings/schemaorg_wn.owl Wordnet]<br />
* A discussion note on [[WebSchemas/SchemaDotOrgOData|schema.org and OData]] is available.<br />
<br />
==Markup examples==<br />
<br />
This group is about vocabulary (schemas) rather than specific markup syntax details. However since syntax specs are evolving in parallel, there are often discussions that need to mix syntax and vocabulary issues.<br />
<br />
* from structured-data.org, some [http://linter.structured-data.org/examples/ examples] showing RDFa 1.1 lite versions of Schema.org's Microdata samples<br />
<br />
<br />
Schema.org example sites - the following list give concrete examples of Schema.org sites (testable with [http://www.google.com/webmasters/tools/richsnippets Google richsnippets tool]):<br />
* TV series - http://www.imdb.com/title/tt0813715/ ([http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Fwww.imdb.com%2Ftitle%2Ftt0813715%2F&view= Google checker])<br />
* Product - http://www.ebay.com/ctg/Logitech-Revue-/97019743<br />
* Movie - http://www.imdb.com/title/tt1375666/ http://www.rottentomatoes.com/m/inception/<br />
* Music - http://www.myspace.com/awilolongombaofficiel/music/playlists/awilo-longomba-officiel-s-playlist-243959?_escaped_fragment_=<br />
* Events - www.ticketmaster.com/Foo-Fighters-tickets/artist/776005?_escaped_fragment_=<br />
* [http://schema.org/Recipe Recipe] - http://www.isaveurs.com/recette/recette_tarte_tatin.php</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/PropertyValuePairs&diff=98040WebSchemas/PropertyValuePairs2016-04-07T07:49:53Z<p>Danbri: </p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=for Property-Value Pairs in Schema.org|status=Published}}<br />
<br />
== Outcome: Published as PropertyValue ==<br />
<br />
http://schema.org/PropertyValue was added in release 2.0 in 2015, see http://schema.org/docs/releases.html<br />
<br />
= Proposal for Property-Value Pairs =<br />
'''Status:''' Prepared by [http://www.heppnetz.de Martin Hepp], mheppATcomputerDOTorg<br />
<br />
== Overview == <br />
This proposal defines a lightweight, generic pattern for exposing arbitrary property value pairs to schema.org. Such is often needed for exposing <br />
*product features, <br />
*EXIF image meta-data, and <br />
*additional features of places. <br />
<br />
In the future, it could also serve as a generic extension mechanism for properties.<br />
The proposal mirrors a feature that will be added to the [http://purl.org/goodrelations/ GoodRelations vocabulary for e-commerce information], which has already been added to schema.org.<br />
<br />
== Motivating Examples ==<br />
Many Web sites contain additional, granular information about characteristics of the entities described in the respective pages that cannot be directly mapped to schema.org properties. In some cases, we can simply define additional properties for the respective schema.org types, but in many other cases, this is unfeasible. For instance, the [http://www.eclass.de/eclasscontent/standard/overview.html.en eCl@ss standard] defines more than 16,000 precise product properties for commodities. It is not possible nor desirable to add 16,000 properties to http://schema.org/Product nor to create tens of thousands of subclasses of http://schema.org/Product.<br />
<br />
Respective information is frequently rendered tabular form, but the underlying data structure is that of a property-value pair, often augmented by unit of measurement information, and sometimes characterized by value references.<br />
<br />
It would be very valuable to be able to expose as much of such '''property-value-type information''', in particular for product features, by a respective lightweight mechanism in schema.org.<br />
<br />
We all agree in here that standards for product types and properties and values are easier to process and in general better. However, the development and use of such standards is orthogonal to the proposed extension. <br />
<br />
In a nutshell, the extension allows sites to expose product feature data if any of the following condition is met:<br />
<br />
#There is no standardized property for the product characteristic (e.g. number of birds per cuckoo clock).<br />
#There is no URI / Web vocabulary for the standardized property (as is the case for eClass properties, UNSPSC classes, and was to my knowledge for GPC).<br />
#The site is not able to add the URI of the property to the data (e.g. because the back-end systems just provide property-value pairs to the Web application).<br />
#The data available to the site is not sufficiently granular or incomplete and thus insufficient for populating the target data structure as specified in the product ontology (e.g. the ontology defines a product weight including batteries and the site data is weight excluding batteries).<br />
<br />
With the proposed extension, sites can publish a wealth or product data even in such cases, which are very, very common.<br />
<br />
===Manufacturers of Commodities and Retailers ===<br />
<br />
Most product detail pages of e-commerce sites, like BestBuy.com, and most product detail pages of manufacturers of products, like cars, consumer electronics, etc. contain a "Specifications" tab or section that lists quantitative and quantitative product features. <br /><br />
'''Examples:''' <br />
* http://www.bestbuy.com/site/apple-iphone-5c-16gb-cell-phone-white-at-t/1722018.p (go to "Specifications")<br />
* http://www.nikonusa.com/en/Nikon-Products/Product/Digital-slr-Cameras/25492/D3200.html (go to "Tech Spec")<br />
* http://www.bose.com/controller?url=/shop_online/digital_music_systems/bluetooth_speakers/soundlink_mini/index.jsp (go to "Details")<br />
* http://www.crutchfield.com/S-i7yrghfFMjg/p_158ZSH10CP/Sony-ZS-H10CP.html#Specifications<br />
* http://www.philips.co.uk/c-p/OST690_10/bluetooth-usb-12-w/specifications<br />
* http://www.firebird-systems.com/graphics/dct210/digital-tv-tuner-hdmi-dct210.shtml<br />
* http://www.cisco.com/c/en/us/products/wireless/small-business-500-series-wireless-access-points/index.html<br />
* http://www.bhphotovideo.com/c/product/598513-REG/ART_PRO_MPA_II_ProMPA_II_Microphone.html<br />
* http://www.rane.com/ms1s.html (this is a very nice one, since it also has conditions / context information for the properties)<br />
* http://www.guitarcenter.com/ART-Tube-MP-Studio-Mic-Preamp-105798490-i1171932.gc<br />
* http://www.philips.co.in/c/haircare/hairdryer-hp8100_00/prd/?t=specifications<br />
* http://energizerpower.com/inverters/EN180.php<br />
* http://eu.audio-technica.com/en/products/product.asp?catID=6&subID=42&prodID=4064<br />
* http://netgear.com/business/products/wireless/business-wireless/wndap660.aspx#tab-techspecs<br />
* http://www.newegg.com/Product/Product.aspx?Item=N82E16822236404<br />
* http://www.office.xerox.com/multifunction-printer/multifunction-under-30ppm/workcentre-5300-series/spec-enus.html#yscroll_0<br />
* http://www.officedepot.com/a/products/197453/HP-Deskjet-1010-Inkjet-Printer-Color/<br />
* http://www.seagate.com/external-hard-drives/network-storage/business/blackarmor-nas-400/<br />
* http://www.tripplite.com/sku/APSINT2012/<br />
* http://uk.jbl.com/jbl_product_detail_uk/studio-580.html<br />
* http://usa.canon.com/cusa/consumer/products/copiers_fax_machines/multifunction_copiers/imageclass_mf7470/#Specifications<br />
* http://www.buffalotech.com/products/network-storage<br />
* http://www.engeniustech.com/business-networking/outdoor-access-points-client-bridges/16454-enh700ext<br />
* http://www.ricoh-usa.com/products/product_details.aspx?cid=8&scid=5&pid=2602&ptm=specifications#pdtfeatures<br />
<br />
{| class="wikitable" style="text-align:center"<br />
|+iPhone 5 Specifications<br />
!Spec!!Value!!Description<br />
|-<br />
| LTE Band and Mode||4G LTE ||<br />
|-<br />
| Battery Type||lithium-ion|| <br />
|-<br />
| Built-In GPS||Yes ||<br />
|-<br />
| Touch Screen||Yes ||<br />
|-<br />
| Operating System||Apple iOS 7||<br />
|-<br />
| Screen Size ||4"||Size of the screen, in inches, measured diagonally from corner to corner.<br />
|-<br />
| Bluetooth Version||4.0|| <br />
|-<br />
| Keyboard Type||Virtual QWERTY|| <br />
|-<br />
| Front Facing Camera MP Rating|| 1.2|| <br />
|-<br />
| Rear Facing Camera MP Rating|| 8|| <br />
|}<br />
<br />
'''Remarks:'''<br />
# The total number of properties is potentially huge. <br />
# Often, there is no global standard that precisely defines how the value of the property is measured.<br />
# Even if there are such standards (like eCl@ss), many site owners are unable to map all of their local properties and values to such a standard.<br />
<br />
=== EXIF Image Meta-data ===<br />
Another area of application for this proposal is picture meta-data from the [http://en.wikipedia.org/wiki/Exchangeable_image_file_format Exchangeable Image File Format (EXIF)] and other meta-data formats for creative works ([http://www.cipa.jp/std/documents/e/DC-008-2012_E.pdf PDF of version 2.3 of the EXIF Standard]). EXIF and proprietary extensions allow digital cameras and other devices to capture a lot of valuable meta-data about images that could be valuable for a Web site to expose. While some of the properties defined in EXIF can be mapped to existing or future properties defined in schema.org, there is a general need for a loosely-coupled mechanism for such meta-data, because<br />
# the number of EXIF properties properties is large in comparison to the properties of [http://schema.org/ImageObject http://schema.org/ImageObject],<br />
# the current [http://schema.org/exifData exifData] property causes a loss of structural information about the property-values, <br />
# the EXIF standard can evolve independently from schema.org and will thus create a constant need for alignment, and<br />
# there are domain- or vendor-specific extensions of EXIF.<br />
<br />
This has also been [http://lists.w3.org/Archives/Public/public-vocabs/2014Sep/0274.html discussed on the public-vocabs mailing list] on September 22/23, 2014.<br />
<br />
===Current Coding Practices ===<br />
Current Web page markup typically uses simple lists, tables, or nested div structures for representing property-value information.<br />
<br />
<syntaxhighlight lang="html5"><br />
<h5>Size and Weight</h5><br />
<ul><br />
<li>Desktop Form Factor</li><br />
<li>Width: 5.9 in (150.3 mm)</li><br />
<li>Height: 7.3 in (185.4 mm)</li><br />
<li>Depth: 10.3 in (262.3 mm)</li><br />
<li>Weight: 8.5 lb (3.9 kg) without hard drives, power supply, or packaging</li><br />
</ul><br />
<h5>Power and Cooling</h5><br />
<ul><br />
<li>External Power Supply:<br />
<ul><br />
<li>AC Input – 100-240VAC~2A, 50-60Hz</li><br />
<li>DC Output – 12V, 12.5A, 150W max</li><br />
</ul><br />
</li><br />
<li>Dual, fixed, variable speed cooling fans</li><br />
</ul><br />
</syntaxhighlight><br />
<br />
There is hope that the the property name, the unit information and the value, and the contextual information either come from multiple variables in the original templates, e.g. that the line<br />
<br />
<syntaxhighlight lang="html5"><br />
<li>Width: 5.9 in</li><br />
</syntaxhighlight><br />
<br />
actually comes from a template pattern like<br />
<br />
<syntaxhighlight lang="html5"><br />
<li>{{property}}: {{value}} {{unit}}</li><br />
</syntaxhighlight><br />
<br />
or that sites would be able to use local patterns to split the whole string into these components using regular expression assumed they have a reason to do so.<br />
<br />
At least the split between property name and value is frequently already materialized at the level of HTML, e.g. by emphasizing the property name using <code>&lt;strong&gt;</code> or <code>&lt;span&gt;</code>.<br />
<br />
<syntaxhighlight lang="html5"><br />
<ul><br />
<li><strong>Type: </strong> 3-speed, fully manual operation </li><br />
<li><strong>Motor: </strong> DC motor </li><br />
<li><strong>Drive Method Direct Drive: </strong> Direct drive </li><br />
<li><strong>Speeds: </strong> 33-1/3 RPM, 45 RPM, 78 RPM</li> <br />
</ul><br />
</syntaxhighlight><br />
<br />
== Design Principles ==<br />
# '''Keep Data Structure and Semantics:''' Allow site owners to expose as much granularity and data semantics as locally available.<br />
#* Example: If the back-end database holds value and unit code in two fields, the extension should allow to preserve that granularity.<br />
#* Example: If the back-end database uses standard codes, like UN/CEFACT Common Codes, for units, it should be possible to publish those.<br />
# '''No Lifting and Cleansing Barrier:''' Do not force site owners to lift or cleanse existing data.<br />
#* Example: If the source data is not able to map a local property definition to a global standard, do not force them to. It is better to allow site owners to publish what they have than to create barriers.<br />
<br />
== Requirements ==<br />
* Support for <br />
**quantitative (e.g. "number of USB ports: 5") i.e. [http://schema.org/QuantitativeValue schema:QuantitativeValue], <br />
**qualitative (e.g. "type of interface: USB"), and <br />
**boolean values ("USB interface: yes")<br />
* Support for '''point values''' (e.g. "diameter: 5 cm") and '''ranges''' (e.g. "input voltage: 3 - 9 volts").<br />
* Support for units of measurement information, in one of the following forms:<br />
** natural language / text / unit symbol (e.g. volts or V)<br />
** standard unit codes, like UN/CEFACT Common Codes, from multiple standards (e.g. "VLT" for volts from UN/CEFACT or )<br />
** URIs for a unit of measurement, like http://qudt.org/vocab/unit#Volt<br />
** Custom Enumerations (e.g. "Cellular type: GSM / EDGE / 3G / HSPA / LTE") i.e. [http://schema.org/Enumeration schema:Enumeration]<br />
* Be able to preserve contextual information and conditions (e.g. "measured at 20 degrees Celsius", "at 8 Ohm", ...)<br />
<br />
== Extension Proposal ==<br />
===Git Repository===<br />
The specification of the proposal is available via the 'property-value-and-cars' branch of the following Git repository:<br />
* https://github.com/mfhepp/schemaorg/tree/property-value-and-cars<br />
<br />
'''Note 1:''' The Git repository combines the specification for this proposal with the [https://www.w3.org/wiki/WebSchemas/Vehicles vehicles/automotive extension proposal] due to the inherent dependencies. <br /><br />
'''Note 2:''' All older repositories like https://github.com/mfhepp/sdo-property-value and https://bitbucket.org/mfhepp/property-value-pairs-for-schema.org are no longer valid and have been closed or deleted to avoid confusion.<br />
<br />
=== Live Demo on Appengine ===<br />
<br />
*See: http://sdo-property-value.appspot.com/PropertyValue<br />
<br />
=== Changes to Existing Elements ===<br />
<br />
Extend domain / range of <br />
*http://schema.org/unitCode<br />
** additional domain: http://schema.org/PropertyValue<br />
** additional range: http://schema.org/URL<br />
<br />
*http://schema.org/minValue and http://schema.org/maxValue<br />
** additional domain: http://schema.org/PropertyValue<br />
<br />
*http://schema.org/value<br />
** additional domain: http://schema.org/PropertyValue<br />
** additional ranges: http://schema.org/Text and http://schema.org/Boolean and http://schema.org/StructuredValue (the latter allows for multi-dimensional values; changed 2014-02-05 from PropertyValue to StructuredValue)<br />
<br />
*http://schema.org/valueReference<br />
** additional domain: http://schema.org/PropertyValue<br />
** additional range: http://schema.org/StructuredValue (changed 2014-02-05 from PropertyValue to StructuredValue)<br />
<br />
*http://schema.org/exifData<br />
** additional range: http://schema.org/PropertyValue (added 2014-12-09)<br />
<br />
Also, the textual description of these elements will be expanded to include the additional usages of the elements.<br />
<br />
=== New Elements ===<br />
==== New Class ====<br />
*'''http://schema.org/PropertyValue''' (Subclass of http://schema.org/StructuredValue)<br />
**A property-value pair, e.g. representing a feature of a <code>Product</code> or <code>Place</code> or <code>ImageObject</code>.<br />
<br />
==== New Properties ====<br />
*'''http://schema.org/additionalProperty'''<br />
**A property-value pair representing an additional characteristics of the entitity, e.g. a product feature or another characteristic for which there is no matching property in schema.org.<br />
**Domain: http://schema.org/Product or http://schema.org/Place<br />
**Range: http://schema.org/PropertyValue<br />
*'''http://schema.org/unitText'''<br />
**A string or text indicating the unit of measurement. Useful if you cannot provide a standard unit code for <code>unitCode</code>.<br />
**Domain: http://schema.org/PropertyValue<br />
**Range: http://schema.org/Text<br />
**'''Note:''' It will make improve schema.org to also include http://schema.org/QuantitativeValue, http://schema.org/TypeAndQuantityNode, and http://schema.org/UnitPriceSpecification in the domain of this property. The RDFa already implements that.<br />
*'''http://schema.org/propertyID'''<br />
**A commonly used identifier for the characteristic represented by the property, e.g. a manufacturer or a standard code for a property. Standards bodies (e.g. eCl@ss, GS1, ...) should define a standard prefix or base URI for their property identifiers.<br />
**Domain: http://schema.org/PropertyValue<br />
**Range: http://schema.org/Text or http://schema.org/URL<br />
<br />
'''Notes:'''<br />
*The textual name of a property shall go into http://schema.org/name<br />
*Unstructured textual properties, a human-readable version, and contextual information should go into http://schema.org/description<br />
<br />
'''Issues:'''<br />
I have thought long about the name for <code>additionalProperty</code>. For pure product features, "feature" would be a better keyword, but the application area of this proposal reaches further. "property" is catchy, but since we already have the class http://schema.org/Property, this is a potential cause of errors. Also, the new mechanism is not at the same level as the core schema.org meta-model. A nice aspect of <code>additionalProperty</code> is that is complements the existing <code>additionalType</code> keyword.<br />
<br />
=== Relationship to http://schema.org/PropertyValueSpecification ===<br />
<br />
The existing element http://schema.org/PropertyValueSpecification is a mechanism for specifying input and output constraints for potential actions (for background information, see the [https://www.w3.org/wiki/images/1/10/PotentialActionsApril11.pdf final proposal]).<br />
<br />
There is no conflict with the proposed generic property-value mechanism.<br />
<br />
== Markup Examples ==<br />
<br />
=== ImageObject: EXIF Meta-data ===<br />
==== Without Mark-up ====<br />
<syntaxhighlight lang="html5"><br />
<h2>Beach in Mexico</h2><br />
<img src="mexico-beach.jpg" /><br />
By Jane Doe<br />
Photographed in Puerto Vallarta, Mexico<br />
Date uploaded: Jan 25, 2008<br />
I took this picture while on vacation last year.<br />
<!-- We assume the following EXIF meta-data is available, but currently not shown:<br />
<br />
Exposure Time: 1/659 sec.<br />
FNumber: f/4.0<br />
MaxApertureValue: 2.00<br />
Metering Mode: Pattern<br />
Flash: Flash did not fire.<br />
--><br />
</syntaxhighlight><br />
<br />
==== Microdata ====<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/ImageObject"><br />
<h2 itemprop="name">Beach in Mexico</h2><br />
<img src="mexico-beach.jpg" itemprop="contentUrl" /><br />
By <span itemprop="author">Jane Doe</span><br />
Photographed in<br />
<span itemprop="contentLocation">Puerto Vallarta, Mexico</span><br />
Date uploaded:<br />
<meta itemprop="datePublished" content="2008-01-25">Jan 25, 2008<br />
<span itemprop="description">I took this picture while on vacation last year.</span><br />
<!-- Note: We do not split value strings in unit and value information, since this the raw EXIF data <br />
does not provide this granularity. If you are able to separate the unit, you can use the unitText property --><br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="Exposure Time"><br />
<meta itemprop="value" content="1/659 sec."><br />
</div><br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="FNumber"><br />
<meta itemprop="value" content="f/4.0"><br />
</div><br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="MaxApertureValue"><br />
<meta itemprop="value" content="2.00"><br />
</div> <br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="Metering Mode"><br />
<meta itemprop="value" content="Pattern"><br />
</div><br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="Flash"><br />
<meta itemprop="value" content="Flash did not fire."><br />
</div><br />
</div><br />
</syntaxhighlight><br />
<br />
==== RDFa ====<br />
<syntaxhighlight lang="html5"><br />
<div vocab="http://schema.org/" typeof="ImageObject"><br />
<h2 property="name">Beach in Mexico</h2><br />
<img src="mexico-beach.jpg" property="contentUrl" /><br />
By <span property="author">Jane Doe</span><br />
Photographed in<br />
<span property="contentLocation">Puerto Vallarta, Mexico</span><br />
Date uploaded:<br />
<meta property="datePublished" content="2008-01-25">Jan 25, 2008<br />
<span property="description">I took this picture while on vacation last year.</span><br />
<!-- Note: We do not split value strings in unit and value information, since this the raw EXIF data <br />
does not provide this granularity. If you are able to separate the unit, you can use the unitText property --><br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="Exposure Time"><br />
<meta property="value" content="1/659 sec."><br />
</div><br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="FNumber"><br />
<meta property="value" content="f/4.0"><br />
</div><br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="MaxApertureValue"><br />
<meta property="value" content="2.00"><br />
</div> <br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="Metering Mode"><br />
<meta property="value" content="Pattern"><br />
</div><br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="Flash"><br />
<meta property="value" content="Flash did not fire."><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
==== JSON-LD ====<br />
<syntaxhighlight lang="javascript"><br />
<script type="application/ld+json"><br />
{<br />
"@context": "http://schema.org",<br />
"@type": "ImageObject",<br />
"author": "Jane Doe",<br />
"contentLocation": "Puerto Vallarta, Mexico",<br />
"contentUrl": "mexico-beach.jpg",<br />
"datePublished": "2008-01-25",<br />
"description": "I took this picture while on vacation last year.",<br />
"name": "Beach in Mexico"<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "Exposure Time",<br />
"value": "1/659 sec."<br />
}<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "FNumber",<br />
"value": "f/4.0"<br />
}<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "MaxApertureValue",<br />
"value": "2.00"<br />
}<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "Metering Mode",<br />
"value": "Pattern"<br />
}<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "Flash",<br />
"value": "Flash did not fire."<br />
} <br />
}<br />
</script><br />
</syntaxhighlight><br />
<br />
=== Product: Point Value, with unit as text ===<br />
<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Approx. Weight</span><br />
<span itemprop="value">450</span><br />
<span itemprop="unitText">gram</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Point Value, with unit as symbol ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Approx. Weight</span><br />
<span itemprop="value">450</span><br />
<span itemprop="unitText">g</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Point Value, with unit as UN/CEFACT Common Code ===<br />
<syntaxhighlight lang="html5"><br />
<div itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Approx. Weight</span><br />
<span itemprop="value">450</span><br />
<meta itemprop="unitCode" content="GRM">g<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Range, with unit as UN/CEFACT Common Code ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Operating Voltage</span><br />
<span itemprop="minValue">100</span>-<br />
<span itemprop="maxValue">250</span><br />
<meta itemprop="unitCode" content="VLT">volts<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
<br />
=== Open Interval, with unit as UN/CEFACT Common Code ===<br />
<syntaxhighlight lang="html5"><br />
<div itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Wifi range</span>: up to <br />
<span itemprop="maxValue">30</span> <br />
<!-- Note: The UN/CEFACT Common Code for foot is FOT --> <br />
<meta itemprop="unitCode" content="FOT">ft.<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Multiple Intervals ===<br />
<syntaxhighlight lang="html5"><br />
<div itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Operating voltage</span>: <br />
<span itemprop="value">9-12</span> or<br />
<span itemprop="value">100-250</span><br />
<meta itemprop="unitCode" content="VLT">volts<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Range and Enumerated Values ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">ISO Sensitivity</span>: <br />
<span itemprop="value">100-6400</span>/<br />
<span itemprop="value">12,800</span> (Hi-1)<br />
<span itemprop="unitText">ISO</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Boolean Value ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">USB interface</span>:<br />
<meta itemprop="value" content="True">Yes<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Qualitative Value ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Interface</span>:<br />
<span itemprop="value">USB</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Qualitative Value (multiple) ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Interfaces</span>:<br />
<span itemprop="value">USB</span>, <br />
<span itemprop="value">Ethernet</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
'''Notes:''' <br />
# The <code>value</code> property should be used ''multiple times'' only for qualitative values, not for quantitative ones. <br />
# If the site is unable to represent the individual values of a list of values as distinct HTML elements (e.g. span or div), one can also use delimiters like commas or slashes in the content:<br />
<syntaxhighlight lang="html5"><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Interfaces</span>:<br />
<span itemprop="value">USB, Ethernet</span><br />
</div> <br />
</syntaxhighlight><br />
<br />
=== Property ID for clarifying the meaning of a property: URI from external vocabulary ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Car"><br />
<img itemprop="image" src="station_waggon123.jpg" /><br />
<span itemprop="name">Station Waggon 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Luggage Capacity (seats folded)</span>:<br />
<span itemprop="value">500</span><br />
<meta itemprop="unitCode" content="LTR">liter<br />
<link itemprop="propertyID" href="http://purl.org/vvo/ns#luggageCapacitySeatsFolded" /><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Property ID for clarifying the meaning of a property: Code from eCl@ss Standard ===<br />
<syntaxhighlight lang="html5"><br />
<!-- The Property code 02-AAM226 is for "USB interface present" in eCl@ss 8.1 --><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">USB Interface</span>:<br />
<meta itemprop="value" content="True">Yes<br />
<meta itemprop="propertyID" content="eclass81:02-AAM226"><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Ratios ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Car"><br />
<img itemprop="image" src="station_waggon123.jpg" /><br />
<span itemprop="name">Station Waggon 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Fuel consumption</span>:<br />
<span itemprop="value">5</span><br />
<meta itemprop="unitCode" content="LTR">liter /<br />
<div itemprop="valueReference" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="value">100</span><br />
<span itemprop="unitText">km</span><br />
</div><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Value References ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Operating Voltage</span><br />
<span itemprop="minValue">100</span>-<br />
<span itemprop="maxValue">250</span><br />
<meta itemprop="unitCode" content="VLT">volts<br />
at<br />
<div itemprop="valueReference" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="value">50</span><br />
<span itemprop="unitText">Hz</span><br />
</div> <br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Multi-dimensional Values ===<br />
'''Note:''' The domain of the <code>value</code> property has been changed to include PropertyValue recursively. This allows preserving the structure of multi-dimensional values (like 50 mm x 75 mm).<br />
<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Sensor Size</span><br />
<div itemprop="value" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="value">23.2</span><br />
<span itemprop="unitText">mm</span> <br />
</div> x<br />
<div itemprop="value" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="value">15.4</span><br />
<span itemprop="unitText">mm</span> <br />
</div><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Grouping and Hierarchical Order of Properties ===<br />
<br />
Note: A nice example of this in real Web pages is http://www.samsung.com/ae/consumer/tv-audio-video/dvd/dvd-player/DVD-D530/ZN-spec.<br />
<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<strong itemprop="name">Focus/Autofocus</strong><br />
<div itemprop="value" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Picture Control</span> <br />
<span itemprop="value">Landscape</span><br />
<span itemprop="value">Monochrome</span><br />
<span itemprop="value">Portrait</span><br />
</div><br />
<div itemprop="value" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Single-point AF Mode</span>:<br />
<meta itemprop="value" content="True">Yes<br />
</div> <br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
== Comments and Feedback ==<br />
Please post to the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs@w3.org mailing list].<br />
<br />
=== Issues ===<br />
* <del>Naming:</del><br />
**<del>Maybe rename PropertyValue to NamedValue? (MH: Unconvinced)</del><br />
**<del>Maybe rename additionalProperty to feature (MH: Unconvinced because it limits a future broader use without need)</del><br />
* <del>Maybe define a new property schema:propertyName instead of reusing schema:name </del> ''Kept the original''<br />
* <del>The naming of additionalProperty should be discussed. (some positive feedback already for keeping additionalProperty) </del> ''Kept the original''<br />
* <del>One could extend the range of value to include PropertyValue itself, which would allow modeling properties that have multi-dimensional values.</del> ''Implemented''<br />
* <del>Multiple qualitative values could be handled either via delimiters in the value or by allowing multiple values for the value property (MH: I am inclined to the latter).</del> ''Implemented''<br />
* <del>Maybe allow value references (MH: I would allow that).</del> ''Implemented''<br />
* <del>Maybe allow hierarchical structures / grouping of properties.</del> ''Implemented''<br />
<br />
[[Category:WebSchemas]]<br />
[[Category:WebSchemaProposals]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/PropertyValuePairs&diff=98039WebSchemas/PropertyValuePairs2016-04-07T07:49:10Z<p>Danbri: updated to point to release</p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=for Property-Value Pairs in Schema.org|status=Published}}<br />
<br />
= Result<br />
<br />
http://schema.org/PropertyValue was added in release 2.0 in 2015, see http://schema.org/docs/releases.html<br />
<br />
= Proposal for Property-Value Pairs =<br />
'''Status:''' Prepared by [http://www.heppnetz.de Martin Hepp], mheppATcomputerDOTorg<br />
<br />
== Overview == <br />
This proposal defines a lightweight, generic pattern for exposing arbitrary property value pairs to schema.org. Such is often needed for exposing <br />
*product features, <br />
*EXIF image meta-data, and <br />
*additional features of places. <br />
<br />
In the future, it could also serve as a generic extension mechanism for properties.<br />
The proposal mirrors a feature that will be added to the [http://purl.org/goodrelations/ GoodRelations vocabulary for e-commerce information], which has already been added to schema.org.<br />
<br />
== Motivating Examples ==<br />
Many Web sites contain additional, granular information about characteristics of the entities described in the respective pages that cannot be directly mapped to schema.org properties. In some cases, we can simply define additional properties for the respective schema.org types, but in many other cases, this is unfeasible. For instance, the [http://www.eclass.de/eclasscontent/standard/overview.html.en eCl@ss standard] defines more than 16,000 precise product properties for commodities. It is not possible nor desirable to add 16,000 properties to http://schema.org/Product nor to create tens of thousands of subclasses of http://schema.org/Product.<br />
<br />
Respective information is frequently rendered tabular form, but the underlying data structure is that of a property-value pair, often augmented by unit of measurement information, and sometimes characterized by value references.<br />
<br />
It would be very valuable to be able to expose as much of such '''property-value-type information''', in particular for product features, by a respective lightweight mechanism in schema.org.<br />
<br />
We all agree in here that standards for product types and properties and values are easier to process and in general better. However, the development and use of such standards is orthogonal to the proposed extension. <br />
<br />
In a nutshell, the extension allows sites to expose product feature data if any of the following condition is met:<br />
<br />
#There is no standardized property for the product characteristic (e.g. number of birds per cuckoo clock).<br />
#There is no URI / Web vocabulary for the standardized property (as is the case for eClass properties, UNSPSC classes, and was to my knowledge for GPC).<br />
#The site is not able to add the URI of the property to the data (e.g. because the back-end systems just provide property-value pairs to the Web application).<br />
#The data available to the site is not sufficiently granular or incomplete and thus insufficient for populating the target data structure as specified in the product ontology (e.g. the ontology defines a product weight including batteries and the site data is weight excluding batteries).<br />
<br />
With the proposed extension, sites can publish a wealth or product data even in such cases, which are very, very common.<br />
<br />
===Manufacturers of Commodities and Retailers ===<br />
<br />
Most product detail pages of e-commerce sites, like BestBuy.com, and most product detail pages of manufacturers of products, like cars, consumer electronics, etc. contain a "Specifications" tab or section that lists quantitative and quantitative product features. <br /><br />
'''Examples:''' <br />
* http://www.bestbuy.com/site/apple-iphone-5c-16gb-cell-phone-white-at-t/1722018.p (go to "Specifications")<br />
* http://www.nikonusa.com/en/Nikon-Products/Product/Digital-slr-Cameras/25492/D3200.html (go to "Tech Spec")<br />
* http://www.bose.com/controller?url=/shop_online/digital_music_systems/bluetooth_speakers/soundlink_mini/index.jsp (go to "Details")<br />
* http://www.crutchfield.com/S-i7yrghfFMjg/p_158ZSH10CP/Sony-ZS-H10CP.html#Specifications<br />
* http://www.philips.co.uk/c-p/OST690_10/bluetooth-usb-12-w/specifications<br />
* http://www.firebird-systems.com/graphics/dct210/digital-tv-tuner-hdmi-dct210.shtml<br />
* http://www.cisco.com/c/en/us/products/wireless/small-business-500-series-wireless-access-points/index.html<br />
* http://www.bhphotovideo.com/c/product/598513-REG/ART_PRO_MPA_II_ProMPA_II_Microphone.html<br />
* http://www.rane.com/ms1s.html (this is a very nice one, since it also has conditions / context information for the properties)<br />
* http://www.guitarcenter.com/ART-Tube-MP-Studio-Mic-Preamp-105798490-i1171932.gc<br />
* http://www.philips.co.in/c/haircare/hairdryer-hp8100_00/prd/?t=specifications<br />
* http://energizerpower.com/inverters/EN180.php<br />
* http://eu.audio-technica.com/en/products/product.asp?catID=6&subID=42&prodID=4064<br />
* http://netgear.com/business/products/wireless/business-wireless/wndap660.aspx#tab-techspecs<br />
* http://www.newegg.com/Product/Product.aspx?Item=N82E16822236404<br />
* http://www.office.xerox.com/multifunction-printer/multifunction-under-30ppm/workcentre-5300-series/spec-enus.html#yscroll_0<br />
* http://www.officedepot.com/a/products/197453/HP-Deskjet-1010-Inkjet-Printer-Color/<br />
* http://www.seagate.com/external-hard-drives/network-storage/business/blackarmor-nas-400/<br />
* http://www.tripplite.com/sku/APSINT2012/<br />
* http://uk.jbl.com/jbl_product_detail_uk/studio-580.html<br />
* http://usa.canon.com/cusa/consumer/products/copiers_fax_machines/multifunction_copiers/imageclass_mf7470/#Specifications<br />
* http://www.buffalotech.com/products/network-storage<br />
* http://www.engeniustech.com/business-networking/outdoor-access-points-client-bridges/16454-enh700ext<br />
* http://www.ricoh-usa.com/products/product_details.aspx?cid=8&scid=5&pid=2602&ptm=specifications#pdtfeatures<br />
<br />
{| class="wikitable" style="text-align:center"<br />
|+iPhone 5 Specifications<br />
!Spec!!Value!!Description<br />
|-<br />
| LTE Band and Mode||4G LTE ||<br />
|-<br />
| Battery Type||lithium-ion|| <br />
|-<br />
| Built-In GPS||Yes ||<br />
|-<br />
| Touch Screen||Yes ||<br />
|-<br />
| Operating System||Apple iOS 7||<br />
|-<br />
| Screen Size ||4"||Size of the screen, in inches, measured diagonally from corner to corner.<br />
|-<br />
| Bluetooth Version||4.0|| <br />
|-<br />
| Keyboard Type||Virtual QWERTY|| <br />
|-<br />
| Front Facing Camera MP Rating|| 1.2|| <br />
|-<br />
| Rear Facing Camera MP Rating|| 8|| <br />
|}<br />
<br />
'''Remarks:'''<br />
# The total number of properties is potentially huge. <br />
# Often, there is no global standard that precisely defines how the value of the property is measured.<br />
# Even if there are such standards (like eCl@ss), many site owners are unable to map all of their local properties and values to such a standard.<br />
<br />
=== EXIF Image Meta-data ===<br />
Another area of application for this proposal is picture meta-data from the [http://en.wikipedia.org/wiki/Exchangeable_image_file_format Exchangeable Image File Format (EXIF)] and other meta-data formats for creative works ([http://www.cipa.jp/std/documents/e/DC-008-2012_E.pdf PDF of version 2.3 of the EXIF Standard]). EXIF and proprietary extensions allow digital cameras and other devices to capture a lot of valuable meta-data about images that could be valuable for a Web site to expose. While some of the properties defined in EXIF can be mapped to existing or future properties defined in schema.org, there is a general need for a loosely-coupled mechanism for such meta-data, because<br />
# the number of EXIF properties properties is large in comparison to the properties of [http://schema.org/ImageObject http://schema.org/ImageObject],<br />
# the current [http://schema.org/exifData exifData] property causes a loss of structural information about the property-values, <br />
# the EXIF standard can evolve independently from schema.org and will thus create a constant need for alignment, and<br />
# there are domain- or vendor-specific extensions of EXIF.<br />
<br />
This has also been [http://lists.w3.org/Archives/Public/public-vocabs/2014Sep/0274.html discussed on the public-vocabs mailing list] on September 22/23, 2014.<br />
<br />
===Current Coding Practices ===<br />
Current Web page markup typically uses simple lists, tables, or nested div structures for representing property-value information.<br />
<br />
<syntaxhighlight lang="html5"><br />
<h5>Size and Weight</h5><br />
<ul><br />
<li>Desktop Form Factor</li><br />
<li>Width: 5.9 in (150.3 mm)</li><br />
<li>Height: 7.3 in (185.4 mm)</li><br />
<li>Depth: 10.3 in (262.3 mm)</li><br />
<li>Weight: 8.5 lb (3.9 kg) without hard drives, power supply, or packaging</li><br />
</ul><br />
<h5>Power and Cooling</h5><br />
<ul><br />
<li>External Power Supply:<br />
<ul><br />
<li>AC Input – 100-240VAC~2A, 50-60Hz</li><br />
<li>DC Output – 12V, 12.5A, 150W max</li><br />
</ul><br />
</li><br />
<li>Dual, fixed, variable speed cooling fans</li><br />
</ul><br />
</syntaxhighlight><br />
<br />
There is hope that the the property name, the unit information and the value, and the contextual information either come from multiple variables in the original templates, e.g. that the line<br />
<br />
<syntaxhighlight lang="html5"><br />
<li>Width: 5.9 in</li><br />
</syntaxhighlight><br />
<br />
actually comes from a template pattern like<br />
<br />
<syntaxhighlight lang="html5"><br />
<li>{{property}}: {{value}} {{unit}}</li><br />
</syntaxhighlight><br />
<br />
or that sites would be able to use local patterns to split the whole string into these components using regular expression assumed they have a reason to do so.<br />
<br />
At least the split between property name and value is frequently already materialized at the level of HTML, e.g. by emphasizing the property name using <code>&lt;strong&gt;</code> or <code>&lt;span&gt;</code>.<br />
<br />
<syntaxhighlight lang="html5"><br />
<ul><br />
<li><strong>Type: </strong> 3-speed, fully manual operation </li><br />
<li><strong>Motor: </strong> DC motor </li><br />
<li><strong>Drive Method Direct Drive: </strong> Direct drive </li><br />
<li><strong>Speeds: </strong> 33-1/3 RPM, 45 RPM, 78 RPM</li> <br />
</ul><br />
</syntaxhighlight><br />
<br />
== Design Principles ==<br />
# '''Keep Data Structure and Semantics:''' Allow site owners to expose as much granularity and data semantics as locally available.<br />
#* Example: If the back-end database holds value and unit code in two fields, the extension should allow to preserve that granularity.<br />
#* Example: If the back-end database uses standard codes, like UN/CEFACT Common Codes, for units, it should be possible to publish those.<br />
# '''No Lifting and Cleansing Barrier:''' Do not force site owners to lift or cleanse existing data.<br />
#* Example: If the source data is not able to map a local property definition to a global standard, do not force them to. It is better to allow site owners to publish what they have than to create barriers.<br />
<br />
== Requirements ==<br />
* Support for <br />
**quantitative (e.g. "number of USB ports: 5") i.e. [http://schema.org/QuantitativeValue schema:QuantitativeValue], <br />
**qualitative (e.g. "type of interface: USB"), and <br />
**boolean values ("USB interface: yes")<br />
* Support for '''point values''' (e.g. "diameter: 5 cm") and '''ranges''' (e.g. "input voltage: 3 - 9 volts").<br />
* Support for units of measurement information, in one of the following forms:<br />
** natural language / text / unit symbol (e.g. volts or V)<br />
** standard unit codes, like UN/CEFACT Common Codes, from multiple standards (e.g. "VLT" for volts from UN/CEFACT or )<br />
** URIs for a unit of measurement, like http://qudt.org/vocab/unit#Volt<br />
** Custom Enumerations (e.g. "Cellular type: GSM / EDGE / 3G / HSPA / LTE") i.e. [http://schema.org/Enumeration schema:Enumeration]<br />
* Be able to preserve contextual information and conditions (e.g. "measured at 20 degrees Celsius", "at 8 Ohm", ...)<br />
<br />
== Extension Proposal ==<br />
===Git Repository===<br />
The specification of the proposal is available via the 'property-value-and-cars' branch of the following Git repository:<br />
* https://github.com/mfhepp/schemaorg/tree/property-value-and-cars<br />
<br />
'''Note 1:''' The Git repository combines the specification for this proposal with the [https://www.w3.org/wiki/WebSchemas/Vehicles vehicles/automotive extension proposal] due to the inherent dependencies. <br /><br />
'''Note 2:''' All older repositories like https://github.com/mfhepp/sdo-property-value and https://bitbucket.org/mfhepp/property-value-pairs-for-schema.org are no longer valid and have been closed or deleted to avoid confusion.<br />
<br />
=== Live Demo on Appengine ===<br />
<br />
*See: http://sdo-property-value.appspot.com/PropertyValue<br />
<br />
=== Changes to Existing Elements ===<br />
<br />
Extend domain / range of <br />
*http://schema.org/unitCode<br />
** additional domain: http://schema.org/PropertyValue<br />
** additional range: http://schema.org/URL<br />
<br />
*http://schema.org/minValue and http://schema.org/maxValue<br />
** additional domain: http://schema.org/PropertyValue<br />
<br />
*http://schema.org/value<br />
** additional domain: http://schema.org/PropertyValue<br />
** additional ranges: http://schema.org/Text and http://schema.org/Boolean and http://schema.org/StructuredValue (the latter allows for multi-dimensional values; changed 2014-02-05 from PropertyValue to StructuredValue)<br />
<br />
*http://schema.org/valueReference<br />
** additional domain: http://schema.org/PropertyValue<br />
** additional range: http://schema.org/StructuredValue (changed 2014-02-05 from PropertyValue to StructuredValue)<br />
<br />
*http://schema.org/exifData<br />
** additional range: http://schema.org/PropertyValue (added 2014-12-09)<br />
<br />
Also, the textual description of these elements will be expanded to include the additional usages of the elements.<br />
<br />
=== New Elements ===<br />
==== New Class ====<br />
*'''http://schema.org/PropertyValue''' (Subclass of http://schema.org/StructuredValue)<br />
**A property-value pair, e.g. representing a feature of a <code>Product</code> or <code>Place</code> or <code>ImageObject</code>.<br />
<br />
==== New Properties ====<br />
*'''http://schema.org/additionalProperty'''<br />
**A property-value pair representing an additional characteristics of the entitity, e.g. a product feature or another characteristic for which there is no matching property in schema.org.<br />
**Domain: http://schema.org/Product or http://schema.org/Place<br />
**Range: http://schema.org/PropertyValue<br />
*'''http://schema.org/unitText'''<br />
**A string or text indicating the unit of measurement. Useful if you cannot provide a standard unit code for <code>unitCode</code>.<br />
**Domain: http://schema.org/PropertyValue<br />
**Range: http://schema.org/Text<br />
**'''Note:''' It will make improve schema.org to also include http://schema.org/QuantitativeValue, http://schema.org/TypeAndQuantityNode, and http://schema.org/UnitPriceSpecification in the domain of this property. The RDFa already implements that.<br />
*'''http://schema.org/propertyID'''<br />
**A commonly used identifier for the characteristic represented by the property, e.g. a manufacturer or a standard code for a property. Standards bodies (e.g. eCl@ss, GS1, ...) should define a standard prefix or base URI for their property identifiers.<br />
**Domain: http://schema.org/PropertyValue<br />
**Range: http://schema.org/Text or http://schema.org/URL<br />
<br />
'''Notes:'''<br />
*The textual name of a property shall go into http://schema.org/name<br />
*Unstructured textual properties, a human-readable version, and contextual information should go into http://schema.org/description<br />
<br />
'''Issues:'''<br />
I have thought long about the name for <code>additionalProperty</code>. For pure product features, "feature" would be a better keyword, but the application area of this proposal reaches further. "property" is catchy, but since we already have the class http://schema.org/Property, this is a potential cause of errors. Also, the new mechanism is not at the same level as the core schema.org meta-model. A nice aspect of <code>additionalProperty</code> is that is complements the existing <code>additionalType</code> keyword.<br />
<br />
=== Relationship to http://schema.org/PropertyValueSpecification ===<br />
<br />
The existing element http://schema.org/PropertyValueSpecification is a mechanism for specifying input and output constraints for potential actions (for background information, see the [https://www.w3.org/wiki/images/1/10/PotentialActionsApril11.pdf final proposal]).<br />
<br />
There is no conflict with the proposed generic property-value mechanism.<br />
<br />
== Markup Examples ==<br />
<br />
=== ImageObject: EXIF Meta-data ===<br />
==== Without Mark-up ====<br />
<syntaxhighlight lang="html5"><br />
<h2>Beach in Mexico</h2><br />
<img src="mexico-beach.jpg" /><br />
By Jane Doe<br />
Photographed in Puerto Vallarta, Mexico<br />
Date uploaded: Jan 25, 2008<br />
I took this picture while on vacation last year.<br />
<!-- We assume the following EXIF meta-data is available, but currently not shown:<br />
<br />
Exposure Time: 1/659 sec.<br />
FNumber: f/4.0<br />
MaxApertureValue: 2.00<br />
Metering Mode: Pattern<br />
Flash: Flash did not fire.<br />
--><br />
</syntaxhighlight><br />
<br />
==== Microdata ====<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/ImageObject"><br />
<h2 itemprop="name">Beach in Mexico</h2><br />
<img src="mexico-beach.jpg" itemprop="contentUrl" /><br />
By <span itemprop="author">Jane Doe</span><br />
Photographed in<br />
<span itemprop="contentLocation">Puerto Vallarta, Mexico</span><br />
Date uploaded:<br />
<meta itemprop="datePublished" content="2008-01-25">Jan 25, 2008<br />
<span itemprop="description">I took this picture while on vacation last year.</span><br />
<!-- Note: We do not split value strings in unit and value information, since this the raw EXIF data <br />
does not provide this granularity. If you are able to separate the unit, you can use the unitText property --><br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="Exposure Time"><br />
<meta itemprop="value" content="1/659 sec."><br />
</div><br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="FNumber"><br />
<meta itemprop="value" content="f/4.0"><br />
</div><br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="MaxApertureValue"><br />
<meta itemprop="value" content="2.00"><br />
</div> <br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="Metering Mode"><br />
<meta itemprop="value" content="Pattern"><br />
</div><br />
<div itemprop="exifData" itemscope itemtype="http://schema.org/PropertyValue"><br />
<meta itemprop="name" content="Flash"><br />
<meta itemprop="value" content="Flash did not fire."><br />
</div><br />
</div><br />
</syntaxhighlight><br />
<br />
==== RDFa ====<br />
<syntaxhighlight lang="html5"><br />
<div vocab="http://schema.org/" typeof="ImageObject"><br />
<h2 property="name">Beach in Mexico</h2><br />
<img src="mexico-beach.jpg" property="contentUrl" /><br />
By <span property="author">Jane Doe</span><br />
Photographed in<br />
<span property="contentLocation">Puerto Vallarta, Mexico</span><br />
Date uploaded:<br />
<meta property="datePublished" content="2008-01-25">Jan 25, 2008<br />
<span property="description">I took this picture while on vacation last year.</span><br />
<!-- Note: We do not split value strings in unit and value information, since this the raw EXIF data <br />
does not provide this granularity. If you are able to separate the unit, you can use the unitText property --><br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="Exposure Time"><br />
<meta property="value" content="1/659 sec."><br />
</div><br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="FNumber"><br />
<meta property="value" content="f/4.0"><br />
</div><br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="MaxApertureValue"><br />
<meta property="value" content="2.00"><br />
</div> <br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="Metering Mode"><br />
<meta property="value" content="Pattern"><br />
</div><br />
<div property="exifData" typeOf="PropertyValue"><br />
<meta property="name" content="Flash"><br />
<meta property="value" content="Flash did not fire."><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
==== JSON-LD ====<br />
<syntaxhighlight lang="javascript"><br />
<script type="application/ld+json"><br />
{<br />
"@context": "http://schema.org",<br />
"@type": "ImageObject",<br />
"author": "Jane Doe",<br />
"contentLocation": "Puerto Vallarta, Mexico",<br />
"contentUrl": "mexico-beach.jpg",<br />
"datePublished": "2008-01-25",<br />
"description": "I took this picture while on vacation last year.",<br />
"name": "Beach in Mexico"<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "Exposure Time",<br />
"value": "1/659 sec."<br />
}<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "FNumber",<br />
"value": "f/4.0"<br />
}<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "MaxApertureValue",<br />
"value": "2.00"<br />
}<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "Metering Mode",<br />
"value": "Pattern"<br />
}<br />
"exifData": {<br />
"@type": "PropertyValue",<br />
"name": "Flash",<br />
"value": "Flash did not fire."<br />
} <br />
}<br />
</script><br />
</syntaxhighlight><br />
<br />
=== Product: Point Value, with unit as text ===<br />
<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Approx. Weight</span><br />
<span itemprop="value">450</span><br />
<span itemprop="unitText">gram</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Point Value, with unit as symbol ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Approx. Weight</span><br />
<span itemprop="value">450</span><br />
<span itemprop="unitText">g</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Point Value, with unit as UN/CEFACT Common Code ===<br />
<syntaxhighlight lang="html5"><br />
<div itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Approx. Weight</span><br />
<span itemprop="value">450</span><br />
<meta itemprop="unitCode" content="GRM">g<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Range, with unit as UN/CEFACT Common Code ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Operating Voltage</span><br />
<span itemprop="minValue">100</span>-<br />
<span itemprop="maxValue">250</span><br />
<meta itemprop="unitCode" content="VLT">volts<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
<br />
=== Open Interval, with unit as UN/CEFACT Common Code ===<br />
<syntaxhighlight lang="html5"><br />
<div itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Wifi range</span>: up to <br />
<span itemprop="maxValue">30</span> <br />
<!-- Note: The UN/CEFACT Common Code for foot is FOT --> <br />
<meta itemprop="unitCode" content="FOT">ft.<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Multiple Intervals ===<br />
<syntaxhighlight lang="html5"><br />
<div itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Operating voltage</span>: <br />
<span itemprop="value">9-12</span> or<br />
<span itemprop="value">100-250</span><br />
<meta itemprop="unitCode" content="VLT">volts<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Range and Enumerated Values ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">ISO Sensitivity</span>: <br />
<span itemprop="value">100-6400</span>/<br />
<span itemprop="value">12,800</span> (Hi-1)<br />
<span itemprop="unitText">ISO</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Boolean Value ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">USB interface</span>:<br />
<meta itemprop="value" content="True">Yes<br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Qualitative Value ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Interface</span>:<br />
<span itemprop="value">USB</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Qualitative Value (multiple) ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Interfaces</span>:<br />
<span itemprop="value">USB</span>, <br />
<span itemprop="value">Ethernet</span><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
'''Notes:''' <br />
# The <code>value</code> property should be used ''multiple times'' only for qualitative values, not for quantitative ones. <br />
# If the site is unable to represent the individual values of a list of values as distinct HTML elements (e.g. span or div), one can also use delimiters like commas or slashes in the content:<br />
<syntaxhighlight lang="html5"><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Interfaces</span>:<br />
<span itemprop="value">USB, Ethernet</span><br />
</div> <br />
</syntaxhighlight><br />
<br />
=== Property ID for clarifying the meaning of a property: URI from external vocabulary ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Car"><br />
<img itemprop="image" src="station_waggon123.jpg" /><br />
<span itemprop="name">Station Waggon 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Luggage Capacity (seats folded)</span>:<br />
<span itemprop="value">500</span><br />
<meta itemprop="unitCode" content="LTR">liter<br />
<link itemprop="propertyID" href="http://purl.org/vvo/ns#luggageCapacitySeatsFolded" /><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Property ID for clarifying the meaning of a property: Code from eCl@ss Standard ===<br />
<syntaxhighlight lang="html5"><br />
<!-- The Property code 02-AAM226 is for "USB interface present" in eCl@ss 8.1 --><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">USB Interface</span>:<br />
<meta itemprop="value" content="True">Yes<br />
<meta itemprop="propertyID" content="eclass81:02-AAM226"><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Ratios ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Car"><br />
<img itemprop="image" src="station_waggon123.jpg" /><br />
<span itemprop="name">Station Waggon 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Fuel consumption</span>:<br />
<span itemprop="value">5</span><br />
<meta itemprop="unitCode" content="LTR">liter /<br />
<div itemprop="valueReference" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="value">100</span><br />
<span itemprop="unitText">km</span><br />
</div><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Value References ===<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Operating Voltage</span><br />
<span itemprop="minValue">100</span>-<br />
<span itemprop="maxValue">250</span><br />
<meta itemprop="unitCode" content="VLT">volts<br />
at<br />
<div itemprop="valueReference" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="value">50</span><br />
<span itemprop="unitText">Hz</span><br />
</div> <br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Multi-dimensional Values ===<br />
'''Note:''' The domain of the <code>value</code> property has been changed to include PropertyValue recursively. This allows preserving the structure of multi-dimensional values (like 50 mm x 75 mm).<br />
<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Sensor Size</span><br />
<div itemprop="value" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="value">23.2</span><br />
<span itemprop="unitText">mm</span> <br />
</div> x<br />
<div itemprop="value" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="value">15.4</span><br />
<span itemprop="unitText">mm</span> <br />
</div><br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Grouping and Hierarchical Order of Properties ===<br />
<br />
Note: A nice example of this in real Web pages is http://www.samsung.com/ae/consumer/tv-audio-video/dvd/dvd-player/DVD-D530/ZN-spec.<br />
<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Product"><br />
<img itemprop="image" src="camera123.jpg" /><br />
<span itemprop="name">Digital Camera 123</span><br />
<div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue"><br />
<strong itemprop="name">Focus/Autofocus</strong><br />
<div itemprop="value" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Picture Control</span> <br />
<span itemprop="value">Landscape</span><br />
<span itemprop="value">Monochrome</span><br />
<span itemprop="value">Portrait</span><br />
</div><br />
<div itemprop="value" itemscope itemtype="http://schema.org/PropertyValue"><br />
<span itemprop="name">Single-point AF Mode</span>:<br />
<meta itemprop="value" content="True">Yes<br />
</div> <br />
</div> <br />
</div><br />
</syntaxhighlight><br />
<br />
== Comments and Feedback ==<br />
Please post to the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs@w3.org mailing list].<br />
<br />
=== Issues ===<br />
* <del>Naming:</del><br />
**<del>Maybe rename PropertyValue to NamedValue? (MH: Unconvinced)</del><br />
**<del>Maybe rename additionalProperty to feature (MH: Unconvinced because it limits a future broader use without need)</del><br />
* <del>Maybe define a new property schema:propertyName instead of reusing schema:name </del> ''Kept the original''<br />
* <del>The naming of additionalProperty should be discussed. (some positive feedback already for keeping additionalProperty) </del> ''Kept the original''<br />
* <del>One could extend the range of value to include PropertyValue itself, which would allow modeling properties that have multi-dimensional values.</del> ''Implemented''<br />
* <del>Multiple qualitative values could be handled either via delimiters in the value or by allowing multiple values for the value property (MH: I am inclined to the latter).</del> ''Implemented''<br />
* <del>Maybe allow value references (MH: I would allow that).</del> ''Implemented''<br />
* <del>Maybe allow hierarchical structures / grouping of properties.</del> ''Implemented''<br />
<br />
[[Category:WebSchemas]]<br />
[[Category:WebSchemaProposals]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposals&diff=84088WebSchemas/SchemaDotOrgProposals2015-05-12T14:51:29Z<p>Danbri: updated for May 2015</p>
<hr />
<div><br />
== Proposals for Schema.org ==<br />
<br />
* Since 2014 schema.org uses [https://github.com/schemaorg/schemaorg/issues Github] for active development (like many other W3C communities).<br />
* Email discussion remains in the WebSchemas public-vocabs list here at W3C.<br />
* Archived proposals 2011-2015 are [https://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposalsArchive#2011-2014_Proposals_for_Schema.org archived here].<br />
* We now have a dedicated [http://www.w3.org/community/schemaorg W3C Schema.org Community Group] including a public-schemaorg@w3.org [https://lists.w3.org/Archives/Public/public-schemaorg mailing list]<br />
For lots more detail please visit https://github.com/schemaorg/schemaorg/issues<br />
<br />
<br />
<br />
From 2011-2014 this page collected public proposals for [http://schema.org/docs/full.html schema.org vocabulary] extensions and improvements. <br />
<br />
Until 2015, schema.org public discussions happened via the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs]@w3.org W3C mailing list for discussions. <br />
<br />
[[Category:WebSchemas]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=Main_Page&diff=82885Main Page2015-03-15T21:58:53Z<p>Danbri: Reverted edits by Tmichel (talk) to last revision by Amalhotr</p>
<hr />
<div>This wiki is for connecting the W3C communities (Web developers, implementers, people who make the W3C specifications).<br />
The [http://www.w3.org/ W3C] has a formal track for making [http://www.w3.org/TR/ standards specifications]. The specs answer a lot of questions, but not all of them. The wiki is used by many communities such as the [[Open Web Platform]] and the [[Semantic Web]]. You might want [[How To Contribute|to contribute to W3C work]].<br />
<br />
Pages here have no formal status but may have [[WikiConsensus]]. Questions & answers here may be misleading, or just plain wrong. Or, they may be useful. You are welcome to add, fix, develop and rearrange topics. <br />
<br />
__NOTOC__<br />
{| cellpadding="5" cellspacing="5" style="width:100%; border:1px solid #ddcef2; margin-bottom:0.5em; vertical-align:top; background-color:#fefede;padding:1em;"<br />
| W3C invites the public to edit this wiki. W3C Membership is not required but you must have an account. Request a [https://www.w3.org/accounts/request W3C Account] to get started. Note that you must log in with your account in order to edit the wiki.<br />
|} <br />
<br />
== Application Foundations ==<br />
See [[AppFoundations]]. <br />
<br />
== CSS ==<br />
See [[CSS]]. <br />
<br />
== [[Open Web Platform]] ==<br />
* You might be interested in [[HTML/Training|learning HTML]] or have a reference about [[HTML/Elements|HTML elements]].<br />
* The W3C [[Quality Assurance]] was a dedicated W3C activity from 2001 to 2005. It included work on the [[MarkupValidator|Markup validator]], but also touched upon topics such as [[TrackingIssues|tracking issues]] and [[UriTesting|URI testing]] among others. The W3C maintains a [[IetfW3cLiaison|liaison with IETF]] to coordinate on technologies and specification related to the [[Open Web Platform]].<br />
<br />
==Specifications==<br />
See [http://w3.org/TR current specs]. Work being done to improve specs in general:<br />
* [[SpecProd]] - an effort to [[restyle]] spec content design.<br />
* [[Spec Advancement]] - proposals for accelerating spec advancement.<br />
<br />
== [[Evolution]] ==<br />
An attempt to round up discussions about extensibility, versioning, naming, identifiers, registries, standards process.<br />
<br />
== [[Encouraging-Participation | Encouraging Participation]] ==<br />
<br />
Please help us identify barriers to participation in W3C activities, discussions, teams, etc. More importantly, contribute ideas on how to get around those barriers! Open to all! Click the title and join in!<br />
<br />
== [[SocialWeb]] ==<br />
* [[SocialIG]]<br />
* [[SocialWG]] (including [[Activity Streams]])<br />
* [[SocialWebHeadlightsTaskForce]]<br />
<br />
== [[SemanticWeb|Semantic Web]] ==<br />
* [[GoodURIs]], [[OpenFormats]], [[HCLSIG BioRDF Subgroup/Tasks/URI Best Practices]]<br />
* [[Semantic Web FAQs]], [[SemanticWebTools]], [[SPARQL]], [[:Category:Grddl]], [[OwlAuthoringTools]]<br />
** Emerging topics: [[LinkedData]], [[RdfAndSql]], [[EmbeddingRDFinHTML]], [[RDFa]]<br />
** RESTful thoughts: [[Semantic Annotations for RESTful Services]], [[WoDo|Web of Data Objects]], [[SemanticInbox]], [[foaf+ssl]]<br />
* [[SweoIG | Semantic Web Education and Outreach Interest Group]]<br />
* [[Semantic Bioinformatics]]<br />
* [[Semantic Web Job Mart]] - looking for work in the field? Looking for employees?<br />
<br />
== Security and Privacy ==<br />
* [[Security]], starting around March 2006, for discussion on W3C Security-related specifications and enhancements to [[XML-Dsig]].<br />
* Using Web technologies implies traceability, logs, identification, therefore [[Privacy]] is becoming a growing concern from the community and need to be addressed at the technical level.<br />
<br />
== Identity ==<br />
* [[IdentityBrowser]], a wiki page for notes relating to the [http://www.w3.org/2011/identity-ws/ W3C Identity in the Browser Workshop].<br />
* [[IdentityCharter]], a wiki page for the draft charter which may include Crypto API and Identity API.<br />
<br />
== XML ==<br />
* [[SchemaComposition]] and topics related to [[XML Schema]], prompted by the [http://www.w3.org/2005/03/xml-schema-user-cfp W3C Workshop on XML Schema 1.0 User Experiences].<br />
* [[XprocVnext]] for candidate requirements discussion by the XML Processing Model WG.<br />
<br />
== Multimodal Interaction (MMI) ==<br />
* See the [[MMI]] wiki.<br />
* Visit the [http://www.w3.org/2002/mmi/ group's Web page] as well.<br />
<br />
== W3C Organization ==<br />
* [[Events]]<br />
* [[PWE | Positive Work Environment]]<br />
* [[MailingLists]], [[InternetRelayChat]], [[JabberChickenEgg]], [[ConnectingAudiences]], [[ScheduledTopicChat]], [[AdvancedDevelopment]], [[StaffBooks]]<br />
* '''Local communities''' See: [[:Category:Gatherings|Category Gatherings]].<br />
<br />
Traditional Wiki starting points:<br />
* [[Special:Recentchanges|RecentChanges]]: see where people are currently working (see also [[MailingLists]]).<br />
* [http://www.mediawiki.org/wiki/Help:Contents Help pages]: to get you going.<br />
* [[WikiSandBox]]: feel free to change this page and experiment with editing.<br />
* [[Special:Search|FindPage]]: search or browse the database in various ways.<br />
<br />
We also keep notes [[AboutThisService]], like [[WikiUpgrade]].<br />
<br />
== To be classified ==<br />
<br />
Stuff to move to [[SemanticWebTools]]:<br />
* '''Compendium about RDF''': [http://planetrdf.com/guide/ Dave Beckett's RDF Resource Guide]<br />
* '''Semantic Web Tools''' (see [[SemanticWebTools]] for a more comprehensive listing):<br />
** [http://www-sop.inria.fr/acacia/soft/corese/ Corese] (RDF, RDFS, SPARQL)<br />
** [http://www.1980.hk/javadoc/ hk1980.rdf] (interface only)<br />
** [http://jena.sourceforge.net/ Jena] (RDF, RDFS, OWL)<br />
** [http://www.ontotext.com/owlim/ OWLIM] (RDF, RDFS, OWL)<br />
** [http://librdf.org/ Redland]<br />
** [http://www.openrdf.org/ Sesame]<br />
** [http://tap.stanford.edu/ TAP]<br />
* '''Semantic Web Authoring Tools''':<br />
** [[IdeaGraph]]<br />
** [[IsaViz]] (RDF editing GUIs)<br />
** [[Morla]]<br />
* '''Converters to and from RDF''':<br />
** [[ConverterToRdf]]<br />
** [[ConverterFromRdf]]<br />
** another clump, perhaps for [[RDFApplicationsAndProjects]] — or two separate clumps: [[RDFApplications]] and [[RDFProjects]]<br />
* '''Semantic Web Applications''':<br />
** [[ConceptualApplications]]<br />
** [[DmozRdf]]<br />
** [[GeoInfo]]<br />
** [[ImageDescription]]<br />
** [http://lsdis.cs.uga.edu/projects/asdoc/ Large Scale Distributed Information Systems Lab], University of Georgia<br />
** [[LodLive]] Visual SPARQL browser<br />
** [[LodView]] RDF browser and IRI dereferencer<br />
** [[MozillaRdf]]<br />
** [[MultiLingual]]<br />
** [[RdfCalendar]]<br />
** [[RdfThesaurus]]<br />
** [[RestaurantRecommendation]]<br />
** [[SkosDev]]<br />
** [[SeedApplications]]<br />
** [[SemanticWebUseCases]]<br />
** [[ServiceDescription]]<br />
** [[SPARQL Box]]<br />
** [[VocabularyMarket]]<br />
* '''Project Incubators''': [[HCLSIG/Terminology/PathRadCorrelation|Path-Rad Correlation]]<br />
* '''Usability and HCI''': [[SemanticWebUsability]] state of the art in HCI/Usability<br />
* '''RDF vocabularies''':<br />
** [[Ontology Dowsing]] (old topic of ontology discovery)<br />
** [[RdfSchema]]<br />
** [[VocabularyMarket]]<br />
* '''Design Patterns''':<br />
** [[ConfigurationManagement]]<br />
** [[Contexts]]<br />
** [[DeltaView]]<br />
** [[GermanTranslations]]<br />
** [[InterpretationProperties]]<br />
** [[LargeTripleStores]] and [[RdfStoreBenchmarking]]<br />
** [[NaturalLanguageInterfaces]]<br />
** [[PartWhole]]<br />
** [[RDFa]]<br />
** [[RdfSmushing]]<br />
** [[RoleNoun]]<br />
** [[SemanticWebArchitecture]]<br />
** [[SocialMeaning]]<br />
** [[TextValues]] and [[RdfCoreXmlLiteral]]<br />
* '''FAQs''':<br />
** [[:Category:Faq]]<br />
** [[FaqIdeas]] (desperately needs refactoring!)<br />
** [http://www.semanticwebfaq.com/ Semantic Web FAQ]<br />
* '''[[RdfSyntax|Serializations of RDF]]''':<br />
** [http://www.intertwingly.net/wiki/pie/ExtensibilityFramework ExtensibilityFramework]<br />
** [[NotationThree]]<br />
** [[PieNt]]<br />
** [[SimpleRdfXml]]<br />
** [[SpotOfDrama]] (Atom/SOAP/RDF)<br />
* '''Recent Experiments''':<br />
** [[EdmProofing]]<br />
** [[SemanticWebEnablingConferences]]<br />
** [[SemWebSpain]]<br />
** [http://simile-widgets.org/ SIMILE (Semantic Interoperability of Metadata and Information in unLike Environments)], Massachusetts Institute of Technology<br />
** SWAD-Europe work packages: [[EswWp2]], [[EswWp7]] and [[EswWp10]]<br />
* '''New overview''': [[OpenDataCorporations]]<br />
* [[:Category:Breadcrumbs]]<br />
<br />
----<br />
Issues for HTML Working Group: [http://www.w3.org/html/wg/wiki/ HTML]<br />
<br />
----<br />
[[Open Media Web: Standardization Roadmap]]<br />
<br />
----<br />
[[Xsl-fo]]<br />
<br />
----<br />
Ebook:<br />
<br />
* [[ebook-Workshop]]<br />
* [[ebook-Workshop-slides]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/VisualArtwork&diff=82589WebSchemas/VisualArtwork2015-03-02T20:19:14Z<p>Danbri: linked the release</p>
<hr />
<div>== Overview ==<br />
<br />
This was a proposal for a new Type: Thing > CreativeWork > VisualArtwork ... successfully added Feb 2015: http://schema.org/docs/releases.html#v1.93<br />
<br />
'''This page is preserved for historical reasons in its original form.<br />
'''<br />
I am aware that there are already sub-Types for "Painting", "Sculpture", and "Photograph", but this doesn't seem like a viable way forward. There are many other types of artwork (printmaking, drawing, collage, assemblage, digital art, etc.) and it seems illogical to create new Types for each artform.<br />
<br />
So my proposal is for the 'VisualArtwork' Type to be used instead of "Painting" or "Sculpture", and instead of "Photograph" where the photograph in question is being presented in context as an artwork as opposed to forensic photography, etc.<br />
<br />
A number of additional properties would enable a wider range of visual artwork media to use this type, and provide more information about the artwork being described.<br />
<br />
== Status ==<br />
<br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/visualartwork.html machine-readable schema] - first draft RDFS<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0173.html august 2014 update] (ported to github/appengine, added examples)<br />
* 2014-08-19: Added JSON-LD, Microdata version of examples<br />
* TODO: Figure out what to do about artEdition --- is it a concept that generalizes to other CreativeWork types?<br />
<br />
== Vocabulary ==<br />
<br />
<br />
Thing > CreativeWork > VisualArtwork<br />
<br />
All properties inherited from Thing and CreativeWork, plus these additional properties<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#E3E6ED; font-family: "Lucida Grande" , "Lucida Sans Unicode" , Verdana, Tahoma, Arial, sans-serif;" align="left" cellpadding="5" cellspacing="0" border="1" <br />
!Property!!Expected Type!!Description<br />
|-<br />
|style="background-color:#E3E6ED;"|Properties from VisualArtwork||style="background-color:#E3E6ED;"| ||style="background-color:#E3E6ED;"|<br />
|-<br />
|artform||Text, URL, Intangible||e.g. Painting, Drawing, Scupture, Print, Photograph, Assemblage, Collage, etc.<br />
|-<br />
|material||Text, URL, Intangible||A material/medium which which the artwork is made e.g. Oil, Watercolour, Acrylic, Linoprint, Marble, Cyanotype, Digital, Lithograph, DryPoint, Intaglio, Pastel, Woodcut, Pencil, etc. A mixed media piece of artwork can have multiple materials. <br />
|-<br />
|surface||Text, URL, Intangible||the surface or support on which the artwork is made e.g. Canvas, Paper, Wood, Board, etc.<br />
|-<br />
|width||Distance||width of the artwork<br />
|-<br />
|height||Distance||height of the artwork<br />
|-<br />
|depth||Distance||depth of the artwork<br />
|-<br />
|artEdition||Number||The number of copies when multiple copies of a piece of artwork are produced - e.g. for a limited edition of 20 prints, 'artEdition' refers to the total number of copies (in this example "20").<br />
|-<br />
|colorPalette||colorPalette||Color Palette for the artwork '''NOTE: Consensus was not reached on the colorPalette property so it has been dropped, at least from the initial version'''<br />
|}<br />
<br/><br />
<br />
Some examples:<br />
<br />
== Example Markup ==<br />
<br />
=== A Painting ===<br />
<br />
Fairly straightforward painting<br />
<br />
==== Without Markup ====<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<br />
<div><br />
<h1 lang="fr">La trahison des images </h1><br />
<p><br />
A painting also known as The Treason of Images or <br />
The Treachery of Images.<br />
</p> <br />
<img src="http://http://upload.wikimedia.org/wikipedia/en/b/b9/MagrittePipe.jpg" /><br />
<div><br />
<p><br />
The painting shows a pipe. Below it, Magritte painted, <br />
<q lang="fr">Ceci n'est pas une pipe.</q>, French for <br />
"This is not a pipe."<br />
</p><br />
<p><br />
His statement is taken to mean that the painting itself is not a pipe. <br />
The painting is merely an image of a pipe. Hence, the description, <br />
"this is not a pipe."<br />
</p><br />
<p><br />
Similarly, the image shown above is neither a pipe nor even a painting, <br />
but rather a digital photograph.<br />
</p><br />
<p><br />
The painting is sometimes given as an example of meta message conveyed <br />
by paralanguage. Compare with Korzybski's <q>The word is not the thing</q> <br />
and <q>The map is not the territory</q>.<br />
</div><br />
<ul><br />
<li>Artist: <a href="https://www.freebase.com/m/06h88">René Magritte</a></li><br />
<li>Dimensions: 940 mm × 635 mm</li><br />
<li>Materials: oil on canvas</li><br />
</ul><br />
</div><br />
<br />
</syntaxhighlight><br />
<br />
==== Microdata ====<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<br />
<div itemscope itemtype="http://schema.org/VisualArtwork"><br />
<link itemprop="sameAs" href="http://rdf.freebase.com/rdf/m.0439_q" /><br />
<h1 itemprop="name" lang="fr">La trahison des images </h1><br />
<p><br />
A <span itemprop="artform">painting</span> also known as <br />
<span>The Treason of Images</span> or <br />
<span itemprop="alternateName">The Treachery of Images</span>.<br />
</p> <br />
<img itemprop="image" src="http://http://upload.wikimedia.org/wikipedia/en/b/b9/MagrittePipe.jpg" /><br />
<div itemprop="description"><br />
<p><br />
The painting shows a pipe. Below it, Magritte painted, <br />
<q lang="fr">Ceci n'est pas une pipe.</q>, French for <br />
"This is not a pipe."<br />
</p><br />
<p><br />
His statement is taken to mean that the painting itself is not a pipe. <br />
The painting is merely an image of a pipe. Hence, the description, <br />
"this is not a pipe."<br />
</p><br />
<p><br />
Similarly, the image shown above is neither a pipe nor even a painting, <br />
but rather a digital photograph.<br />
</p><br />
<p><br />
The painting is sometimes given as an example of meta message conveyed <br />
by paralanguage. Compare with Korzybski's <q>The word is not the thing</q> <br />
and <q>The map is not the territory</q>.<br />
</div><br />
<ul><br />
<li>Artist: <br />
<span itemprop="creator" itemscope itemtype="http://schema.org/Person"><br />
<a itemprop="sameAs" href="https://www.freebase.com/m/06h88"><br />
<span itemprop="name">René Magritte</span><br />
</a><br />
</span><br />
</li><br />
<li>Dimensions:<br />
<span itemprop="width" itemscope itemtype="http://schema.org/Distance">940 mm</span> × <br />
<span itemprop="height" itemscope itemtype="http://schema.org/Distance">635 mm</span><br />
</li><br />
<li>Materials:<br />
<span itemprop="material">oil</span> on <span itemprop="surface">canvas</span><br />
</li><br />
</ul><br />
</div><br />
<br />
</syntaxhighlight><br />
<br />
==== RDFa ====<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://rdf.freebase.com/rdf/m.0439_q" /><br />
<h1 property="name" lang="fr">La trahison des images </h1><br />
<p><br />
A <span property="artform">painting</span> also known as <br />
<span>The Treason of Images</span> or <br />
<span property="alternateName">The Treachery of Images</span>.<br />
</p> <br />
<img property="image" src="http://http://upload.wikimedia.org/wikipedia/en/b/b9/MagrittePipe.jpg" /><br />
<div property="description"><br />
<p><br />
The painting shows a pipe. Below it, Magritte painted, <br />
<q lang="fr">Ceci n'est pas une pipe.</q>, French for <br />
"This is not a pipe."<br />
</p><br />
<p><br />
His statement is taken to mean that the painting itself is not a pipe. <br />
The painting is merely an image of a pipe. Hence, the description, <br />
"this is not a pipe."<br />
</p><br />
<p><br />
Similarly, the image shown above is neither a pipe nor even a painting, <br />
but rather a digital photograph.<br />
</p><br />
<p><br />
The painting is sometimes given as an example of meta message conveyed <br />
by paralanguage. Compare with Korzybski's <q>The word is not the thing</q> <br />
and <q>The map is not the territory</q>.<br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/06h88"><br />
<span property="name">René Magritte</span><br />
</a><br />
</span><br />
</li><br />
<li>Dimensions:<br />
<span property="width" typeof="Distance">940 mm</span> × <br />
<span property="height" typeof="Distance">635 mm</span><br />
</li><br />
<li>Materials:<br />
<span property="material">oil</span> on <span property="surface">canvas</span><br />
</li><br />
</ul><br />
</div><br />
<br />
</syntaxhighlight><br />
<br />
==== JSON-LD ====<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<br />
<script type="application/ld+json"><br />
{<br />
"@context": "http://schema.org",<br />
"@type": "VisualArtwork",<br />
"name": "La trahison des images",<br />
"alternateName": "The Treachery of Images",<br />
"image": "http://upload.wikimedia.org/wikipedia/en/b/b9/MagrittePipe.jpg",<br />
"description": "The painting shows a pipe. Below it, Magritte...",<br />
"creator": [<br />
{<br />
"@type": "Person",<br />
"name": "René Magritte",<br />
"sameAs": "https://www.freebase.com/m/06h88"<br />
}<br />
],<br />
"width": [<br />
{<br />
"@type": "Distance",<br />
"name": "940 mm"<br />
}<br />
],<br />
"height": [<br />
{<br />
"@type": "Distance",<br />
"name": "635 mm"<br />
}<br />
],<br />
"material": "oil",<br />
"surface": "canvas"<br />
}<br />
</script><br />
<br />
</syntaxhighlight><br />
<br />
==== VRA 4.0 XML using Getty AAT structured vocabulary ====<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<br />
<vra xmlns="http://www.vraweb.org/vracore4.htm" <br />
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:schemaLocation="http://www.vraweb.org/vracore4.htm <br />
http://gort.ucsd.edu/escowles/vracore4/vra-4.0-restricted.xsd"><br />
<br />
<work id="work_id_1234"><br />
<agentSet><br />
<agent><br />
<name>Magritte, René</name><br />
</agent><br />
</agentSet><br />
<dateSet><br />
<date><br />
<earliestDate>1928</earliestDate><br />
<latestDate>1929</latestDate><br />
</date><br />
</dateSet><br />
<descriptionSet><br />
<description>The painting shows a pipe. Below it, Magritte...</description><br />
</descriptionSet><br />
<materialSet><br />
<material type="medium" vocab="AAT" refid="300015050">oil paint</material><br />
<material type="support" vocab="AAT" refid="300014078">canvas</material><br />
</materialSet><br />
<measurementSet><br />
<measurements type="height" unit="mm" extent="overall">635</measurements><br />
<measurements type="width" unit="mm" extent="overall">940</measurements><br />
</measurementSet><br />
<titleSet><br />
<title>La trahison des images</title><br />
</titleSet><br />
<worktypeSet><br />
<worktype vocab="AAT" refid="300033799">oil painting</worktype><br />
</worktypeSet><br />
</work><br />
<br />
<image><br />
<relationSet><br />
<relation type="imageOf" relids="work_id_1234">La trahison des images</relation><br />
</relationSet><br />
<sourceSet><br />
<source><br />
<refid type="URI">http://upload.wikimedia.org/wikipedia/en/b/b9/MagrittePipe.jpg</refid><br />
</source><br />
</sourceSet><br />
<worktypeSet><br />
<worktype vocab="AAT" refid="300215302">digital image</worktype><br />
</worktypeSet><br />
</image><br />
<br />
</vra><br />
</syntaxhighlight><br />
<br />
=== Multiple materials ===<br />
<br />
A piece of Installation Art which uses multiple instances of the material property<br />
<br />
==== Without Markup ====<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div><br />
<h1>My Bed</h1><br />
<p><br />
My Bed, first created in <time datetime="1998">1998</time>, <br />
is an installation by the British artist Tracey Emin.<br />
</p> <br />
<br />
<img src="http://upload.wikimedia.org/wikipedia/en/9/9d/Emin-My-Bed.jpg" /><br />
<div><br />
<p><br />
<cite>My Bed</cite> was exhibited at the Tate Gallery in <br />
<time datetime="1998">1999</time> as one <br />
of the shortlisted works for the Turner Prize. It consisted of her <br />
bed with bedroom objects in an abject state, and gained much media <br />
attention. Although it did not win the prize, its notoriety has <br />
persisted.<br />
</div><br />
<ul><br />
<li>Artist: <a href="https://www.freebase.com/m/015sxw">Tracey Emin</li><br />
</ul><br />
<p><br />
The artwork generated considerable media furore, particularly over the <br />
fact that the bedsheets were stained with bodily secretions and the floor <br />
had items from the artist's room (such as condoms, a pair of knickers with <br />
menstrual period stains, other detritus, and functional, everyday objects, <br />
including a pair of slippers). The bed was presented in the state that <br />
Emin claimed it had been when she said she had not got up from it for <br />
several days due to suicidal depression brought on by relationship <br />
difficulties.<br />
</p><br />
</div><br />
</syntaxhighlight><br />
<br />
==== Microdata ====<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div itemscope itemtype="http://schema.org/VisualArtwork"><br />
<link itemprop="sameAs" href="http://rdf.freebase.com/rdf/m.0dbwsn" /><br />
<h1 itemprop="name">My Bed</h1><br />
<p><br />
My Bed, first created in <time itemprop="dateCreated" datetime="1998">1998</time>, <br />
is an <span itemprop="artform">installation</span> by the British artist Tracey Emin.<br />
</p> <br />
<br />
<br />
<img itemprop="image" src="http://upload.wikimedia.org/wikipedia/en/9/9d/Emin-My-Bed.jpg" /><br />
<div itemprop="description"><br />
<p><br />
<cite>My Bed</cite> was exhibited at the Tate Gallery in <br />
<time datetime="1998">1999</time> as one <br />
of the shortlisted works for the Turner Prize. It consisted of her <br />
bed with bedroom objects in an abject state, and gained much media <br />
attention. Although it did not win the prize, its notoriety has <br />
persisted.<br />
</div><br />
<ul><br />
<li>Artist: <br />
<span itemprop="creator" itemscope itemtype="http://schema.org/Person"><br />
<a itemprop="sameAs" href="https://www.freebase.com/m/015sxw"><br />
<span itemprop="name">Tracey Emin</span><br />
</a><br />
</span><br />
</li><br />
</ul><br />
<p><br />
The artwork generated considerable media furore, particularly over the <br />
fact that the <span itemprop="material">bedsheets</span> were stained <br />
with bodily secretions and the floor had items from the artist's room <br />
(such as <span itemprop="material">condoms</span>, <br />
<span itemprop="material">a pair of knickers</span> with menstrual <br />
period stains, other detritus, and functional, everyday objects, <br />
including a <span itemprop="material">pair of slippers</span>). The <br />
<span itemprop="material">bed</span> was presented in the state that <br />
Emin claimed it had been when she said she had not got up from it for <br />
several days due to suicidal depression brought on by relationship <br />
difficulties.<br />
</p><br />
</div><br />
</syntaxhighlight><br />
<br />
==== RDFa ====<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://rdf.freebase.com/rdf/m.0dbwsn" /><br />
<h1 property="name">My Bed</h1><br />
<p><br />
My Bed, first created in <time property="dateCreated" datetime="1998">1998</time>, <br />
is an <span property="artform">installation</span> by the British artist Tracey Emin.<br />
</p> <br />
<br />
<br />
<img property="image" src="http://upload.wikimedia.org/wikipedia/en/9/9d/Emin-My-Bed.jpg" /><br />
<div property="description"><br />
<p><br />
<cite>My Bed</cite> was exhibited at the Tate Gallery in <br />
<time datetime="1998">1999</time> as one <br />
of the shortlisted works for the Turner Prize. It consisted of her <br />
bed with bedroom objects in an abject state, and gained much media <br />
attention. Although it did not win the prize, its notoriety has <br />
persisted.<br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/015sxw"><br />
<span property="name">Tracey Emin</span><br />
</a><br />
</span><br />
</li><br />
</ul><br />
<p><br />
The artwork generated considerable media furore, particularly over the <br />
fact that the <span property="material">bedsheets</span> were stained <br />
with bodily secretions and the floor had items from the artist's room <br />
(such as <span property="material">condoms</span>, <br />
<span property="material">a pair of knickers</span> with menstrual <br />
period stains, other detritus, and functional, everyday objects, <br />
including a <span property="material">pair of slippers</span>). The <br />
<span property="material">bed</span> was presented in the state that <br />
Emin claimed it had been when she said she had not got up from it for <br />
several days due to suicidal depression brought on by relationship <br />
difficulties.<br />
</p><br />
</div><br />
</syntaxhighlight><br />
<br />
==== JSON-LD ====<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<br />
<script type="application/ld+json"><br />
{<br />
"@context": "http://schema.org",<br />
"@type": "VisualArtwork",<br />
"sameAs": "http://rdf.freebase.com/rdf/m.0dbwsn",<br />
"name": "My Bed",<br />
"dateCreated": "1998",<br />
"artform": "installation",<br />
"image": "http://upload.wikimedia.org/wikipedia/en/9/9d/Emin-My-Bed.jpg",<br />
"description": "My Bed was exhibited at the Tate Gallery in...",<br />
"creator": [<br />
{<br />
"@type": "Person",<br />
"name": "Tracey Emin",<br />
"sameAs": "https://www.freebase.com/m/015sxw"<br />
}<br />
],<br />
"material": "bedsheets",<br />
"material": "condoms",<br />
"material": "a pair of knickers",<br />
"material": "pair of slippers",<br />
"material": "bed"<br />
}<br />
</script><br />
<br />
</syntaxhighlight><br />
<br />
=== artEdition ===<br />
<br />
Example showing artEdition property in use for a piece of artwork that was created as a series of multiple identical items<br />
<br />
==== Without Markup ====<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div><br />
<h1>Still Life under the Lamp</h1><br />
<p><br />
Print from <time datetime="1962">1962</time><br />
by Pablo Picasso. Numbered from the edition of 50, <br />
each signed by the artist in pencil, lower right: Picasso.<br />
</p> <br />
<img src="http://www.pada.net/Photos/38/Full/picasso.lamp.jpg" /><br />
<div><br />
<p><br />
<cite>Still Life under the Lamp</cite>, from 1962, made when the artist <br />
was eighty years old, are counted among Picasso’s most important works <br />
in linocut, a technique that he explored in the late 1950s and early <br />
1960s. The progressive proofs show the step by step sequence by which <br />
Picasso created his linocut images showing the development of the <br />
image into its final form.<br />
</p><br />
</div><br />
<ul><br />
<li>Artist: <a href="https://www.freebase.com/m/07pj7mx">Pablo Picasso</li><br />
<li>Dimensions: 25 3/16 inches × 20 3/4 inches</li><br />
<li>Materials: linoprint on paper</li><br />
<li><br />
See also <a href="http://www.pada.net/members/memPicFull.php/38/367">here</a><br />
and <a href="http://www.britishmuseum.org/about_us/news_and_press/press_releases/2014/picasso_linocuts.aspx">here</a>.<br />
</ul><br />
</div><br />
</syntaxhighlight><br />
<br />
==== Microdata ====<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div itemscope itemtype="http://schema.org/VisualArtwork"><br />
<link itemprop="sameAs" href="http://www.pada.net/members/memPicFull.php/38/367" /><br />
<h1 itemprop="name">Still Life under the Lamp</h1><br />
<p><br />
<span itemprop="artform">Print</span> from <time itemprop="dateCreated" datetime="1962">1962</time><br />
by Pablo Picasso. Numbered from the edition of <span itemprop="artEdition">50</span>, <br />
each signed by the artist in pencil, lower right: Picasso.<br />
</p> <br />
<img itemprop="image" src="http://www.pada.net/Photos/38/Full/picasso.lamp.jpg" /><br />
<div itemprop="description"><br />
<p><br />
<cite>Still Life under the Lamp</cite>, from 1962, made when the artist <br />
was eighty years old, are counted among Picasso’s most important works <br />
in linocut, a technique that he explored in the late 1950s and early <br />
1960s. The progressive proofs show the step by step sequence by which <br />
Picasso created his linocut images showing the development of the <br />
image into its final form.<br />
</p><br />
</div><br />
<ul><br />
<li>Artist: <br />
<span itemprop="creator" itemscope itemtype="http://schema.org/Person"><br />
<a itemprop="sameAs" href="https://www.freebase.com/m/07pj7mx"><br />
<span itemprop="name">Pablo Picasso</span><br />
</a><br />
</span><br />
</li><br />
<li>Dimensions:<br />
<span itemprop="width" itemscope itemtype="http://schema.org/Distance">25 3/16 inches</span> × <br />
<span itemprop="height" itemscope itemtype="http://schema.org/Distance">20 3/4 inches</span><br />
</li><br />
<li>Materials:<br />
<span itemprop="material">linoprint</span> on <span itemprop="surface">paper</span><br />
</li><br />
<li><br />
See also <a href="http://www.pada.net/members/memPicFull.php/38/367">here</a><br />
and <a href="http://www.britishmuseum.org/about_us/news_and_press/press_releases/2014/picasso_linocuts.aspx">here</a>.<br />
</ul><br />
</div><br />
</syntaxhighlight><br />
<br />
==== RDFa ====<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://www.pada.net/members/memPicFull.php/38/367" /><br />
<h1 property="name">Still Life under the Lamp</h1><br />
<p><br />
<span property="artform">Print</span> from <time property="dateCreated" datetime="1962">1962</time><br />
by Pablo Picasso. Numbered from the edition of <span property="artEdition">50</span>, <br />
each signed by the artist in pencil, lower right: Picasso.<br />
</p> <br />
<img property="image" src="http://www.pada.net/Photos/38/Full/picasso.lamp.jpg" /><br />
<div property="description"><br />
<p><br />
<cite>Still Life under the Lamp</cite>, from 1962, made when the artist <br />
was eighty years old, are counted among Picasso’s most important works <br />
in linocut, a technique that he explored in the late 1950s and early <br />
1960s. The progressive proofs show the step by step sequence by which <br />
Picasso created his linocut images showing the development of the <br />
image into its final form.<br />
</p><br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/07pj7mx"><br />
<span property="name">Pablo Picasso</span><br />
</a><br />
</span><br />
</li><br />
<li>Dimensions:<br />
<span property="width" typeof="Distance">25 3/16 inches</span> × <br />
<span property="height" typeof="Distance">20 3/4 inches</span><br />
</li><br />
<li>Materials:<br />
<span property="material">linoprint</span> on <span property="surface">paper</span><br />
</li><br />
<li><br />
See also <a href="http://www.pada.net/members/memPicFull.php/38/367">here</a><br />
and <a href="http://www.britishmuseum.org/about_us/news_and_press/press_releases/2014/picasso_linocuts.aspx">here</a>.<br />
</ul><br />
</div><br />
</syntaxhighlight><br />
<br />
==== JSON-LD ====<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<br />
<script type="application/ld+json"><br />
{<br />
"@context": "http://schema.org",<br />
"@type": "VisualArtwork",<br />
"sameAs": "http://www.pada.net/members/memPicFull.php/38/367",<br />
"name": "Still Life under the Lamp",<br />
"dateCreated": "1962",<br />
"artform": "print",<br />
"artEdition": "50",<br />
"image": "http://www.pada.net/Photos/38/Full/picasso.lamp.jpg",<br />
"description": "Still Life under the Lamp, from 1962, made when...",<br />
"creator": [<br />
{<br />
"@type": "Person",<br />
"name": "Pablo Picasso",<br />
"sameAs": "https://www.freebase.com/m/07pj7mx"<br />
}<br />
],<br />
"width": [<br />
{<br />
"@type": "Distance",<br />
"name": "25 3/16 inches"<br />
}<br />
],<br />
"height": [<br />
{<br />
"@type": "Distance",<br />
"name": "20 3/4 inches"<br />
}<br />
],<br />
"material": "linoprint",<br />
"surface": "paper"<br />
}<br />
</script><br />
<br />
</syntaxhighlight><br />
<br />
== Early Color Palette proposal ==<br />
<br />
'''NOTE: Consensus was not reached on the colorPalette property so it has been dropped, at least from the initial version'''<br />
<br />
The color palette information would be very useful to classify, categorize and index artwork by colors. I have provided an example of how this structure could look:<br />
<br />
<span itemscope itemtype="http://schema.org/ColorPalette"<http://schema.org/ColorPalette>><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#3366FF</span><br />
<span itemprop="name">Sky Blue</span><br />
<span itemprop="percentage">30%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F5B800</span><br />
<span itemprop="name">Gold</span><br />
<span itemprop="percentage">25%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F5003D</span><br />
<span itemprop="name">Crimson Red</span><br />
<span itemprop="percentage">20%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#B8F500</span><br />
<span itemprop="name">Lime</span><br />
<span itemprop="percentage">15%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F500B8</span><br />
<span itemprop="name">Fuschia</span><br />
<span itemprop="percentage">10%</span><br />
</div><br />
</span><br />
<br />
== Discussion ==<br />
<br />
Posted to public-vocabs on May 7, 2013: http://lists.w3.org/Archives/Public/public-vocabs/2013May/0024.html<br />
Discussion on colorpalette property added to VisualArtwork: http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/0084.html</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/WorkersUnionSchema&diff=80636WebSchemas/WorkersUnionSchema2015-01-22T17:44:16Z<p>Danbri: </p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=WorkersUnion type for Schema.org|status=Accepted}}<br />
<br />
* A simple proposal to add a WorkersUnion type, addressing [http://www.w3.org/2011/webschema/track/issues/17 issue 17]<br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/workersunion.html draft schema]<br />
* tracked: https://github.com/schemaorg/schemaorg/issues/243</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/Vehicles&diff=80635WebSchemas/Vehicles2015-01-22T17:29:01Z<p>Danbri: added github link</p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=for Vehicles (Cars, Bikes, Boats, etc.) Sales and Rental in Schema.org|status=Proposal}}<br />
== Proposal for Vehicles - Cars, Bikes, Boats - Rental and Sales ==<br />
<br />
Tracked at https://github.com/schemaorg/schemaorg/issues/262<br />
<br />
Authors: <br />
*[http://www.heppnetz.de Martin Hepp], mheppATcomputerDOTorg<br />
*[http://makolab.com Karol Szczepański] karolDOTszczepanskiATmakolabDOTpl<br />
*[http://makolab.com Mirek Sopek] sopekATmakolabDOTcom<br />
<br />
This proposal defines a small set of additional types and properties for schema.org that will cover typical scenarios related to the sales and rental of vehicles of typical kinds, like new and used cars, bikes, and boats, and related services.<br />
<br />
It is a first contribution of the [http://www.automotive-ontology.org/ Automotive Ontology Working Group].<br />
<br />
== Overview == <br />
This proposal builds on the following vehicle-related extensions for [http://purl.org/goodrelations/ GoodRelations], the e-commerce model of schema.org:<br />
<br />
*'''Vehicle Sales Ontology (VSO),''' http://purl.org/vso/ns<br />
*'''Volkswagen Vehicles Ontology (VVO),''' http://purl.org/vvo/ns<br />
*'''Used Cars Ontology (UCO),''' http://purl.org/uco/ns<br />
<br />
It adds the core classes, properties and enumerated values for describing cars, trucks, busses, bikes, and boats and their features. For describing commercial aspects of related offers, http://schema.org/Offer already provides the necessary level of detail. Thus, this proposal does not add new elements for commercial features.<br />
<br />
=== Relationship to Configuration Information for Vehicles ===<br />
Cars and other vehicles are often highly configurable products, for which the number of possible combinations can be as much as 10 to the power of 20 for a single vendor. Many manufacturers of cars offer cars in a built-to-order fashion, i.e. they market options spaces of possible cars to customers. <br />
<br />
The space of actually available cars is a subset of the theoretically possible combinations, because <br />
#technical constraints (a configuration would not work well or not at all), <br />
#legal constraints (a configuration would not meet regulatory requirements for a target market), <br />
#production constraints (a configuration will be logistically difficult or expensive to build), and <br />
#marketing considerations (the manufacturer does not want to offer a certain configuration)<br />
<br />
rule our certain configurations.<br />
<br />
This proposal focuses on modeling fully-specified cars, like actual new or used cars, or enumerated sets of car configurations.<br />
<br />
The modeling of configuration rules (e.g. which alternative options are available and how they can be combined) is outside the scope of this proposal. We plan a second proposal for the non-trivial problem of vehicle configuration and vehicle range information, which will complement this proposal.<br />
<br />
The reasons for this staged approach are as follows:<br />
<br />
#Configurable products are not yet supported by schema.org and the underlying GoodRelations product model. An extension for configurable vehicles should include a generic extension for configurable products, which requires additional time to develop.<br />
#The number of Web sites that publish information about actual cars is by orders of magnitude bigger than then number of sites that publish or are able to publish configuration rules. Every dealer listing used and new car inventory and every car listing site will benefit from support for the proposed extension. Configuration rules will mainly be relevant for a manufacturer sites.<br />
#The proposal is based on the existing product model of schema.org. A future extension for configurable products must be designed in a way compatible with the existing product model anyway, so there is no risk starting with actual vehicles.<br />
<br />
=== Financing ===<br />
Also not included in this proposal are elements for financing as additional payment option information. Such should be added by another industry-neutral extension proposal. The [http://purl.org/vvo/ns Volkswagen Vehicles Ontology (VVO)] may serve as useful input for that, because it is based on the GoodRelations core model of payment. We may submit a respective extension proposal for financing in the future.<br />
<br />
== Motivating Examples ==<br />
* A site with used car offers wants to mark-up its individual car offers using schema.org.<br />
* A car manufacturer wants to mark up its product model information.<br />
* A rental car company wants to mark-up its fleet, rental offers, and conditions.<br />
<br />
While the original intention was support for the automotive industry, basic support for bikes and boats has already been included, too.<br />
<br />
Support for aircraft information could be added with moderate effort but is left out for the moment, because we think this should be a separate extension proposal based on additional domain expertise.<br />
<br />
'''Examples of Web Sites:'''<br />
*http://www.cars.com/vehicledetail/detail/612273235/overview/<br />
*http://www.parkers.co.uk/cars/for-sale/search/used/<br />
*http://www.autotrader.co.uk/<br />
<br />
== Design Principles ==<br />
# '''Reuse commercial properties from http://schema.org/Offer and the underlying GoodRelations conceptual model.''' Don't mix modeling vehicles with modeling offers to buy, rent, or service vehicles.<br />
# '''Standardize objective vehicle characteristics and defer consensus for diverse and vendor-specific vehicle characteristics:''' Vehicles, and in particular cars, can have a hundred features and more. Some are very objective (e.g. fuel consumption under lab conditions, dimensions); some are best handled as text (e.g. interior colors), and some are very vendor-specific, e.g. engine types, safety features, etc.<br />
# '''Balance between mark-up effort and usefulness of data:''' The data should be as useful as possible for search engines and other consumers, but the effort for Web developers must be also kept at a minimum.<br />
<br />
These design principles are implemented as follows:<br />
<br />
#Quantitative properties that do not require a unit of measurement can be modeled as either a plain numeric literal (http://schema.org/Number) or a http://schema.org/QuantitativeValue. Typical cases are the number of seats or doors. For a single value, a literal is sufficient. For a range, a http://schema.org/QuantitativeValue is more appropriate.<br />
#Qualitative properties, like fuel types or body styles can be modeled either using a Freebase URI, site-specific URI, or plain text. If a site is able to provide the URI of a authoritative definition for a value or characteristic, this is more useful, but if the site can provide only a string, this is better than nothing.<br />
#Limit the number of standardized properties and use the complementing [http://www.w3.org/wiki/WebSchemas/PropertyValuePairs property-values proposal for schema.org] for vendor-specific vehicle features.<br />
<br />
== Extension Proposal ==<br />
===Git Repository===<br />
The latest version of the proposal is now in a Git repository at github.com at: https://github.com/mfhepp/sdo-vehicles.<br />
The earlier Mercurial repository and the Git repository on bitbucket has been deprecated and set to private in order to avoid confusion.<br />
<br />
=== Development Version on Google App Engine ===<br />
<br />
A '''development version''' of the proposal is available at: http://sdo-property-value-and-cars.appspot.com.<br />
See e.g.<br />
* http://sdo-property-value-and-cars.appspot.com/Car<br />
* http://sdo-property-value-and-cars.appspot.com/Van<br />
* http://sdo-property-value-and-cars.appspot.com/Motorcycle<br />
<br />
In the following, we list the elements in the proposal. '''The authoritative proposal is the version in the ''property-values-and-cars'' branch of the Git repository at: https://github.com/mfhepp/schemaorg/tree/property-value-and-cars.'''<br />
<br />
=== Changes to Existing Elements ===<br />
* The textual definitions for Car and Vehicle will be augmented.<br />
* Car will be a superclass of the new MotorizedRoadVehicle class instead of Vehicle.<br />
=== New Terms ===<br />
The following terms will be added:<br />
==== New Classes ====<br />
*MotorizedRoadVehicle<br />
**A motorized road vehicle is a wheeled land vehicle whose main propulsion is provided by an engine or motor.<br />
*Truck<br />
**A lorry (British English) or truck (American English) is a motor vehicle designed to transport cargo.<br />
*Van<br />
**A van is a kind of vehicle used for transporting goods or groups of people. It is usually a box-shaped vehicle on four wheels, about the same width and length as a large automobile, but taller and usually higher off the ground, also referred to as a light commercial vehicle or LCV.<br />
*MotorizedBicycle<br />
**A motorized bicycle is a bicycle with an attached motor used to power the vehicle, or to assist with pedaling.<br />
*BusOrCoach<br />
**A bus (also omnibus or autobus) is a road vehicle designed to carry passengers. Buses have a capacity as high as 300 passengers and are widely used for public transportation. Coaches are luxury busses, usually in service for long distance travel.<br />
*Motorcycle<br />
**A motorcycle or motorbike is a single-track, two-wheeled motor vehicle.<br />
*<del>Bike</del>Bicycle<br />
**A bicycle or bike is a pedal-driven, human-powered, single-track vehicle, having two wheels attached to a frame, one behind the other. Some bicycles have a small combustion or electric engine that assists with the pedaling.<br />
*Watercraft<br />
**A watercraft is a vehicle, vessel or craft designed to move across or through water.<br />
*Boat<br />
**A boat is a watercraft of modest size designed to float or plane, to provide passage across water.<br />
*MotorBoat<br />
**A motorboat is a boat which is powered by an engine.<br />
*SailingBoat<br />
**A sailboat or sailing boat is a boat propelled partly or entirely by sails.<br />
*SteeringPositionValue<br />
**A value indicating a steering position.<br />
*EmissionStandardValue<br />
**A value indicating the an emission standard.<br />
*TransmissionTypeValue<br />
**A value indicating a type of transmission. <br />
*DriveWheelConfigurationValue<br />
**A value indicating which roadwheels will receive torque.<br />
*EngineTypeValue<br />
**A value indicating an engine type. <br />
*FuelTypeValue<br />
**A value indicating a type of fuel. <br />
*BodyTypeValue<br />
**A value indicating the body type or style of a vehicle.<br />
*CarUsageType<br />
**A value indicating a special usage of a car, e.g. commercial rental, driving school, or as a taxi.<br />
<br />
==== New Properties ====<br />
*steeringPosition<br />
*fuelCapacity<br />
*numberOfOwners<br />
*roofLoad<br />
*fuelConsumption<br />
*cargoVolume<br />
*configurationName (added 2014-12-09)<br />
*driveWheelConfiguration<br />
*wheelbase<br />
*payload<br />
*weightTotal<br />
*transmission<br />
*fuelType<br />
*engineDisplacement<br />
*mileageFromOdometer<br />
*bodyType (renamed from bodyStyle 2014-12-09)<br />
*tongueWeight<br />
*doors<br />
*speed<br />
*meetsEmissionStandard<br />
*fuelEfficiency<br />
*gears<br />
*axles<br />
*engineType<br />
*seatingCapacity<br />
*trailerWeight<br />
*acceleration<br />
*enginePower<br />
*productionDate<br />
*purchasingDate (added 2014-12-09)<br />
*specialUsage<br />
*damages<br />
*firstRegistration<br />
*engineName<br />
*ACRISSCode<br />
*VIN<br />
*modelDate<br />
*colorInterior<br />
*interiorType<br />
*airbags<br />
*torque<br />
*emissionsCO2<br />
<br />
==== New Individuals ====<br />
*'''SteeringPositionValue:''' RightHandDriving and LeftHandDriving<br />
*'''FuelTypeValue:''' TwoStrokeMixture (other fuel types are readily available from DBPedia or Freebase)<br />
*'''DriveWheelConfigurationValue:''' 4WD, AWD, FWD, RWD<br />
*'''CarUsageType:''' RentalUsage, DrivingSchoolUsage, TaxiUsage<br />
<br />
=== Relationship to Other Proposals ===<br />
The proposal does not critically depend on, but '''will greatly benefit from the [[WebSchemas/PropertyValuePairs|property-value pairs]] proposal''' for the many vehicle feature details that are difficult to standardize in a global, vendor-independent form.<br />
<br />
== Markup Example ==<br />
<br />
=== HTML without RDFa or Microdata ===<br />
<syntaxhighlight lang="html5"><br />
<div ><br />
<strong>Contact Name: </strong> <span>Brent</span><br />
<div>$18,000</div><br />
<!-- Car Details --><br />
<div id="product"><br />
<strong>2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p>2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)</p><br />
<img href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong>Black</p><br />
<p><strong>Interior Color: </strong>Black</p><br />
<p><strong>Interior Type: </strong>Leather upholstery, wood paneling</p><br />
<p><strong>Model Year: </strong><time>2009</time></p> <br />
<p><strong>Transmission: </strong>6 speed Sports Automatic Dual Clutch</p> <br />
<p><strong>VIN: </strong>WVWZZZ1KZ9U######</p> <br />
<p><strong>Number of gears: </strong>6</p> <br />
<p><strong>Body: </strong>Hatchback</p><br />
<p><strong>Number of doors: </strong>3</p><br />
<p><strong>Number of seats: </strong>5</p><br />
<p><strong>Drive Type: </strong>Front Wheel Drive</p><br />
<p><strong>Engine: </strong>4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</p><br />
<p><strong>Engine Power: </strong>147 kw at 5100 rpm</p><br />
<p><strong>Fuel type: </strong>Petrol - Premium ULP</p><br />
<p><strong>Engine Size: </strong>1984 ccm</p><br />
<p><strong>Mileage: </strong>53100 km</p><br />
<p><strong>Number of airbags: </strong>6</p><br />
<p><strong>CO2 Emission Combined: </strong>192 g/km</p><br />
</div><br />
</syntaxhighlight><br />
<br />
=== Microdata ===<br />
<syntaxhighlight lang="html5"><br />
<!-- Seller Details --><br />
<div itemscope itemtype="http://schema.org/Person"><br />
<strong>Contact Name: </strong> <span itemprop="name givenName">Brent</span><br />
<div itemprop="makesOffer" itemscope itemtype="http://schema.org/Offer" itemref="product"><br />
<span itemprop="priceSpecification" itemscope <br />
itemtype="http://schema.org/UnitPriceSpecification"><br />
<meta itemprop="priceCurrency" content="USD">$<br />
<meta itemprop="price" content="18000">18,000<br />
</span><br />
</div><br />
</div><br />
<!-- Car Details --><br />
<div id="product" itemprop="itemOffered" itemscope itemtype="http://schema.org/Car"><br />
<strong itemprop="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p itemprop="description">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)</p><br />
<img itemprop="image" href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong><span itemprop="color">Black</span></p><br />
<p><strong>Interior Color: </strong><span itemprop="colorInterior">Black</span></p><br />
<p><strong>Interior Type: </strong><span itemprop="interiorType">Leather upholstery, <br />
wood paneling</span></p><br />
<p><strong>Model Year: </strong><time itemprop="modelDate">2009</time></p> <br />
<p><strong>Transmission: </strong><br />
<span itemprop="transmission">6 speed Sports Automatic Dual Clutch</span><br />
</p> <br />
<p><strong>VIN: </strong><span itemprop="VIN">WVWZZZ1KZ9U######</span></p> <br />
<p><strong>Number of gears: </strong><span itemprop="gears">6</span></p> <br />
<p><strong>Body: </strong><br />
<span itemprop="bodyType">Hatchback</span><br />
</p><br />
<p><strong>Number of doors: </strong><span itemprop="doors">3</span></p><br />
<p><strong>Number of seats: </strong><span itemprop="seatingCapacity">5</span></p><br />
<p><strong>Drive Type: </strong><br />
<link itemprop="driveWheelConfiguration" href="http://schema.org/FWD" /><br />
Front Wheel Drive<br />
</p><br />
<p><strong>Engine: </strong><br />
<span itemprop="engineName">4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</span><br />
</p><br />
<p><strong>Engine Power: </strong><br />
<span itemprop="enginePower" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">147</span> <br />
<meta itemprop="unitCode" content="KWT">kw<br />
at <span itemprop="valueReference" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<meta itemprop="name" content="referenceRPM"> <br />
<span itemprop="value">5100</span> <br />
<meta itemprop="unitCode" content="RPM">rpm<br />
</span><br />
</span><br />
</p><br />
<p><strong>Fuel type: </strong><br />
<span itemprop="fuelType">Petrol - Premium ULP</span> <br />
</p><br />
<p><strong>Engine Size: </strong><br />
<span itemprop="engineDisplacement" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">1984</span> <br />
<meta itemprop="unitCode" content="CMQ">ccm<br />
</span><br />
</p><br />
<p><strong>Mileage: </strong><br />
<span itemprop="mileageFromOdometer" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">53100</span> <br />
<meta itemprop="unitCode" content="KMT">km<br />
</span><br />
</p><br />
<p><strong>Number of airbags: </strong><span itemprop="airbags">6</span></p><br />
<p><strong>CO2 Emission Combined: </strong><span itemprop="emissionCO2">192</span> g/km</p><br />
</div><br />
</syntaxhighlight><br />
<br />
=== RDFa ===<br />
<br />
<syntaxhighlight lang="html5"><br />
<!-- Seller Details --><br />
<div vocab="http://schema.org/" typeof="Person"><br />
<strong>Contact Name: </strong> <span property="name givenName">Brent</span><br />
<div property="makesOffer" typeof="Offer"><br />
<span property="priceSpecification" typeof="UnitPriceSpecification"><br />
<meta property="priceCurrency" content="USD">$<br />
<meta property="price" content="18000">18,000<br />
</span><br />
<!-- Car Details --><br />
<div id="product" property="itemOffered" typeof="Car"><br />
<strong property="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p property="description">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)<br />
</p><br />
<img property="image" href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong><span property="color">Black</span></p><br />
<p><strong>Interior Color: </strong><span property="colorInterior">Black</span></p><br />
<p><strong>Interior Type: </strong><span property="interiorType">Leather upholstery, wood paneling</span></p><br />
<p><strong>Model Year: </strong><time property="modelDate">2009</time></p> <br />
<p><strong>Transmission: </strong><br />
<span property="transmission">6 speed Sports Automatic Dual Clutch</span><br />
</p> <br />
<p><strong>VIN: </strong><span property="VIN">WVWZZZ1KZ9U######</span></p> <br />
<p><strong>Number of gears: </strong><span property="gears">6</span></p> <br />
<p><strong>Body: </strong><br />
<span property="bodyType">Hatchback</span><br />
</p><br />
<p><strong>Number of doors: </strong><span property="doors">3</span></p><br />
<p><strong>Number of seats: </strong><span property="seatingCapacity">5</span></p><br />
<p><strong>Drive Type: </strong><br />
<link property="driveWheelConfiguration" href="http://schema.org/FWD" /><br />
Front Wheel Drive<br />
</p><br />
<p><strong>Engine: </strong><br />
<span property="engineName">4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</span><br />
</p><br />
<p><strong>Engine Power: </strong><br />
<span property="enginePower" typeof="QuantitativeValue"><br />
<span property="value">147</span> <br />
<meta property="unitCode" content="KWT">kw<br />
at <span property="valueReference" typeof="QuantitativeValue"><br />
<meta property="name" content="referenceRPM"> <br />
<span property="value">5100</span> <br />
<meta property="unitCode" content="RPM">rpm<br />
</span><br />
</span><br />
</p><br />
<p><strong>Fuel type: </strong><br />
<span property="fuelType">Petrol - Premium ULP</span><br />
</p><br />
<p><strong>Engine Size: </strong><br />
<span property="engineDisplacement" typeof="QuantitativeValue"><br />
<span property="value">1984</span> <br />
<meta property="unitCode" content="CMQ">ccm<br />
</span><br />
</p><br />
<p><strong>Mileage: </strong><br />
<span property="mileageFromOdometer" typeof="QuantitativeValue"><br />
<span property="value">53100</span> <br />
<meta property="unitCode" content="KMT">km<br />
</span><br />
</p><br />
<p><strong>Number of airbags: </strong><span property="airbags">6</span></p><br />
<p><strong>CO2 Emission Combined: </strong><span property="emissionCO2">192</span> g/km</p><br />
</div><br />
</div><br />
</div><br />
</syntaxhighlight><br />
<br />
=== JSON-LD ===<br />
<br />
<syntaxhighlight lang="javascript"><br />
{<br />
"@context": "http://schema.org",<br />
"@type": "Person",<br />
"name" : "Brent",<br />
"makesOffer" : { <br />
"@type" :"Offer",<br />
"priceSpecification" : { <br />
"@type" : "UnitPriceSpecification", <br />
"priceCurrency" : "USD",<br />
"price" : "18000" },<br />
"itemOffered" : { <br />
"@type" : "Car",<br />
"name" : "2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox",<br />
"description" : "2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes every drive a fun experience. Well looked after by one owner with full service history. It drives like new and has only done 50,000kms. (...)",<br />
"image" : "2009_Volkswagen_Golf_V_GTI_MY09.png",<br />
"color" : "Black",<br />
"colorInterior" : "Black",<br />
"interiorType" : "Leather upholstery, wood paneling",<br />
"modelDate" : "2009",<br />
"transmission" : "6 speed Sports Automatic Dual Clutch",<br />
"VIN" : "WVWZZZ1KZ9U######",<br />
"gears" : "6",<br />
"bodyType" : "Hatchback",<br />
"doors" : "3",<br />
"seatingCapacity" : "5",<br />
"driveWheelConfiguration" : "http://schema.org/FWD",<br />
"engineName" : "4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)",<br />
"enginePower" : { <br />
"@type" : "QuantitativeValue",<br />
"value" : "147",<br />
"unitCode" : "KWT",<br />
"valueReference" : {<br />
"@type" : "QuantitativeValue",<br />
"name" : "referenceRPM", <br />
"value" : "5100",<br />
"unitCode" : "RPM" }<br />
},<br />
"fuelType" : "Petrol - Premium ULP",<br />
"engineDisplacement" : {<br />
"@type": "QuantitativeValue",<br />
"value" : "1984",<br />
"unitCode" : "CMQ"<br />
},<br />
"mileageFromOdometer" : {<br />
"@type" : "QuantitativeValue",<br />
"value" : "53100",<br />
"unitCode" : "KMT"<br />
},<br />
"airbags" : "6",<br />
"emissionCO2" : "192"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
== Special Cases ==<br />
=== Non-standard Vehicle Features ===<br />
<br />
For vehicle features that are do not match the properties of the extension proposal, we recommend using the [[WebSchemas/PropertyValuePairs|property-value proposal for schema.org]].<br />
<br />
For examples of this pattern, see [[WebSchemas/PropertyValuePairs#Markup_Examples|WebSchemas/PropertyValuePairs#Markup_Examples]].<br />
<br />
=== External URIs as Values ===<br />
Several properties will accept either text or entities as a value. In the later case, it could be useful if the publisher of the data can link locally defined value entities to Freebase or DBPedia entities, because this will allow consuming clients to better understand the data.<br />
This is built into the proposal, but not enforced nor directly explained in the textual definitions of the elements.<br />
<br />
== Comments and Feedback ==<br />
Please join the [https://plus.google.com/communities/104510681993581444051 Automotive Ontology Working Group] or post to the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs@w3.org mailing list] if you want to raise issues or have suggestions on how to improve the proposal.<br />
<br />
== Related Work ==<br />
See also: http://carobka.ru/cars_reviews/ford/focus/3831.html has an example of an extension Yandex have been using informally. <br /><br />
'''Note''': The Yandex proposal has been reviewed and incorporated in the current version of the proposal (mhepp, 2014-12-17)<br />
<br />
[[Category:WebSchemas]]<br />
[[Category:WebSchemaProposals]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/Measurement&diff=80634WebSchemas/Measurement2015-01-22T17:24:23Z<p>Danbri: </p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=Measurement|status=Work in progress}}<br />
<br />
See github: https://github.com/schemaorg/schemaorg/issues/264<br />
<br />
== Overview ==<br />
In order to support describing sports statistics, we need the ability to describe measurements that happen over a certain time period, where the value of the measurement can either be a quantity or a rate. Our current schema.org vocabulary is not sufficient to cover these needs but models, somewhat inconsistently, various aspects of it.<br />
This proposal aims to clean up the existing vocabulary and introduce new terminology to meet the needs of describing sports statistics.<br />
The Sports proposal is dependent upon review and approval of this proposal or similar alternative. The ItemList proposal also takes advantage of this proposal.<br />
<br />
== Proposals ==<br />
<br />
* Posted September 03 2014 - exported PDF<br />
** [[File:Schema.orgMeasurement.pdf]]<br />
** Version 1.1 - see version history at end of document<br />
<br /><br />
<br />
* Posted August 27 2014 - exported PDF<br />
** [[File:Schema.orgMeasurement.pdf]]<br />
** First Draft<br />
<br /></div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposals&diff=80633WebSchemas/SchemaDotOrgProposals2015-01-22T17:22:05Z<p>Danbri: /* Proposals for Schema.org */</p>
<hr />
<div><br />
== Proposals for Schema.org ==<br />
<br />
* Since 2014 schema.org uses [https://github.com/schemaorg/schemaorg/issues Github] for active development (like many other W3C communities).<br />
* Email discussion remains in the WebSchemas public-vocabs list here at W3C.<br />
* Archived proposals 2011-2015 are [https://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposalsArchive#2011-2014_Proposals_for_Schema.org archived here].<br />
<br />
<br />
For lots more detail please visit https://github.com/schemaorg/schemaorg/issues<br />
<br />
<br />
<br />
From 2011-2014 this page collected public proposals for [http://schema.org/docs/full.html schema.org vocabulary] extensions and improvements. <br />
<br />
Schema.org public discussions happen via the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs]@w3.org W3C mailing list for discussions. <br />
<br />
[[Category:WebSchemas]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposals&diff=80632WebSchemas/SchemaDotOrgProposals2015-01-22T17:21:40Z<p>Danbri: minimal page to avoid confusion</p>
<hr />
<div><br />
== Proposals for Schema.org ==<br />
<br />
* Since 2014 schema.org uses [https://github.com/schemaorg/schemaorg/issues Github] for active development (like many other W3C communities).<br />
* Email discussion remains in the WebSchemas public-vocabs list here at W3C.<br />
* Archived proposals 2011-2015 are [https://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposalsArchive#2011-2014_Proposals_for_Schema.org archived here].<br />
* Issues include<br />
https://github.com/schemaorg/schemaorg/issues<br />
<br />
<br />
<br />
From 2011-2014 this page collected public proposals for [http://schema.org/docs/full.html schema.org vocabulary] extensions and improvements. <br />
<br />
Schema.org public discussions happen via the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs]@w3.org W3C mailing list for discussions. <br />
<br />
[[Category:WebSchemas]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposalsArchive&diff=80631WebSchemas/SchemaDotOrgProposalsArchive2015-01-22T17:11:20Z<p>Danbri: </p>
<hr />
<div><br />
<br />
This is an archived snapshot of [https://www.w3.org/wiki/WebSchemas/SchemaDotOrgProposals WebSchemas/SchemaDotOrgProposalsArchive]. Active development has moved to Github.<br />
<br />
See also the [http://schema.org/docs/releases.html release history] page at schema.org.<br />
<br />
== 2011-2014 Proposals for Schema.org ==<br />
<br />
* Since 2014 schema.org uses [https://github.com/schemaorg/schemaorg/issues Github] for active development, although email discussion remains in the WebSchemas public-vocabs list.<br />
* History: 2012-13 draft [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext schema files] were hosted in W3C's Mercurial repository.<br />
* From 2014, schema.org runs on [https://github.com/rvguha/schemaorg opensource software], and uses Git(hub) for schema collaboration. Examples and schemas are in the [https://github.com/rvguha/schemaorg/tree/master/data data/] area of the repository.<br />
<br />
From 2011-2014 this page collected public proposals for [http://schema.org/docs/full.html schema.org vocabulary] extensions and improvements. <br />
<br />
We are winding down the [http://www.w3.org/2011/webschema/track/ W3C's issue tracker] for schema.org issues, except for matters of coordination with other vocabularies and W3C specifications.<br />
<br />
Schema.org public discussions happen via the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs]@w3.org W3C mailing list for discussions. <br />
<br />
Sometimes proposals evolve from offlist and face-to-face discussions; when possible, advance warning of 'expected' or possible proposals can be indicated here ([http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0102.html announced 24 Feb 2012]).<br />
<br />
Schema.org proposals can take any form during discussions, but ultimately they should take the form of HTML+RDFa schema definitions; some real examples are in the [https://github.com/rvguha/schemaorg/tree/master/data data/ area] of the schema.org repository. See Github pages for more details.<br />
<br />
'''Note''': When preparing a proposal, we need to know for each type and property, its name and description, alongside examples of usage. There are lots of different ways in which these can be prepared: wiki pages, text files, spreadsheets, PDFs etc. Do note that each property is considered as a global entity, ie. a property called 'foo' gets just one description - you can't give different descriptions for its use with the "Person" type, versus its use with the CreativeWork type. Ideally, develop a machine-readable proposal and test it using the software on Github.<br />
<br />
To search just these proposals, the issue tracker and schema.org-related mailing lists, try a [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek this custom search].<br />
<br />
<br />
== 2014 Proposals and Discussion ==<br />
<br />
These proposals are working towards inclusion in schema.org.<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/Measurement|Measurement]]<br />
|Proposal<br />
|Introduce the concept of a Measurement to describe the relationship between a value and a thing, as in sports statistics.<br />
|See wiki page<br />
|<br />
|-<br />
|[[WebSchemas/associatedMediaToThing|Change domain of associatedMedia to Thing]]<br />
|Proposal<br />
|Change the domain of http://schema.org/associatedMedia to http://schema.org/Thing<br />
|Enables many more types to associate contained or complementary media content, beyond CreativeWork.<br />
|Discussion at http://lists.w3.org/Archives/Public/public-vocabs/2014May/0224.html<br />
|-<br />
|[[WebSchemas/PropertyValuePairs|Property-Value Pairs]]<br />
|Proposal<br />
|Adding support for arbitrary property-value pairs. Useful for product features and proprietary features of places.<br />
|One new type http://schema.org/PropertyValue, two new properties for this type (unitText, propertyID), changes to domain and range for unitCode, value, minValue, maxValue, and valueReference properties; one new property additionalProperty for http://schema.org/Place OR http://schema.org/Product.<br />
|Mirrors an upcoming feature in [http://purl.org/goodrelations/ GoodRelations].<br />
|-<br />
|[[WebSchemas/Vehicles|Vehicles: Cars, Bikes, Boats]]<br />
|Proposal<br />
|Adding support for vehicle features for cars, bikes, boats, and other vehicles for sales and rental.<br />
|See proposal for details.<br />
|<br />
|-<br />
|[[WebSchemas/Orders_enhancement|Orders Schema update]]<br />
|Proposal<br />
|Proposal to add order line and parcel delivery support in the Orders Schema.<br />
|One new Type: OrderItem, and added properties for one existent Type: Order<br />
|<br />
|-<br />
|[[WebSchemas/SocialAccountProperty|social Account property]]<br />
|Proposal<br />
|Indicates a corresponding profile page for an account on a socially-oriented Web site.<br />
|One new property: socialAccount<br />
|<br />
|-<br />
|[[WebSchemas/Audiobook|Audiobook]]<br />
|Proposal<br />
|Proposal for new Audiobook Type and abridged property for [http://schema.org/Book Book].<br />
|Audiobook subtype of [http://schema.org/Book Book] ''and'' of [http://schema.org/AudioObject AudioObject], adds readBy property<br />
|<br />
|-<br />
|[[WebSchemas/Collection|Collection]]<br />
|Proposal<br />
|Proposal for new Collection Type and part properties for [http://schema.org/CreativeWork CreativeWork].<br />
|Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/Accessibility/ToDo|Accessibility]] (part 2)<br />
|Discussion<br />
|Extension for describing accessibility properties of a [http://schema.org/CreativeWork CreativeWork].<br />
|Additional work to add accessMode, hasAdapation, isAdaptationof that were not covered in 1.0 Accessibility work.<br />
|<br />
|-<br />
|[[WebSchemas/QuotationSchema|Add Quotation type]]<br />
|Proposal<br />
|Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties.<br />
|Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee.<br />
|Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise.<br />
|-<br />
|[[WebSchemas/WorkersUnionSchema|Workers Union type]] <br />
|Accepted<br />
|This proposal adds a single new type, WorkersUnion, addressing [http://www.w3.org/2011/webschema/track/issues/17 issue 17] in the WebSchemas tracker. <br />
|"A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying.""<br />
|One type, see [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/workersunion.html draft schema].<br />
|-<br />
|[[WebSchemas/Sports|Sports]]<br />
|Proposal<br />
|The purpose of this proposal is to introduce an expanded vocabulary for describing sports information within schema.org. Key concepts include Statistics, Roles, Ordered Events, Competitions and Competition Results.<br />
|See proposal for full set of vocabulary updates.<br />
|V3 posted 2014.05.09<br />
|-<br />
|[[WebSchemas/PeriodicalsComics|Comics and Serials]]<br />
| style="background-color:#ECC8EC;"|Discussing Proposals <br />
|Proposal from Marvel (see [[PeriodicalsComics#Code_Examples|examples]]).<br />
|Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. <br />
|Generally well received and specified, but some detailed [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0073.html discussion] re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with [http://schema.org/Book Book]/numberOfPages, or [http://schema.org/ScholarlyArticle ScholarlyArticle]? Should PeriodicalSeries be intangible?<br />
|-<br />
|[[WebSchemas/HistoricalDataSchema|Historical Data proposal]]<br />
|Proposal<br />
|The [http://historical-data.org/ historical-data.org] site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios.<br />
|Adds HistoricalRecord, HistoricalEvent (subclass of Event), ''overrides'' attendees, subEvents, superEvent to point to HistoricalEvent.<br />
|There is an associated implementation, [https://github.com/historical-data/ github repository], and [http://historical-data-schema.blogspot.com/ blog].<br />
|-<br />
|[[WebSchemas/BioDatabases|Biological Databases]]<br />
|Proposal<br />
|A schema extension for describing biological databases, [http://sagace.nibio.go.jp/schema/en/schema.html Sagace]. <br />
|Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. <br />
|Others have also mentioned interest in adding some notion of species.<br />
|-<br />
|[[WebSchemas/Breadcrumbs|Breadcrumbs]]<br />
|Proposal<br />
|A proposal resolving current problems handling breadcrumbs.<br />
|Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See [http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Nov/0026.html discussion] on using literal values.<br />
|<br />
|-<br />
|[[WebSchemas/DiscussionSchema|Discussion]] <br />
|Proposal<br />
|A proposal extending schema.org for describing online discussion forums and message boards.<br />
|Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful.<br />
|Addition candidate<br />
|-<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html Innovation] <br />
|Proposal<br />
|A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html]<br />
|Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [http://purl.org/innovation/ns] for complete list of terms.<br />
|Addition candidate<br />
|-<br />
|[[WebSchemas/dissolutionDate|dissolutionDate]]<br />
|Proposal<br />
|Add a dissolutionDate property to Organization.<br />
|<br />
|<br />
|-<br />
|[http://thematix.com/ontologies/travel/lodging/ Lodging Extensions]<br />
|Proposal<br />
|A proposal for extending LodgingBusiness. Specification is here http://thematix.com/ontologies/travel/lodging/<br />
|Adds Amenity, BusinessService, Feature, GuestRoomAmenity, LodgingBusinessAmenity, LodgingBusinessService, RentalOffer, RentalRate, Room, RoomType and Service.<br />
|In addition to the examples given in the cited website, examples can be seen at http://www.regencyhotelmiami.com/ and http://hiltonvb.com and at Super8 hotel description pages, e.g., http://www.super8.com/hotels/alberta/fort-mcmurray/super-8-fort-mcmurray/hotel-overview. <br />
|-<br />
|-<br />
|[[WebSchemas/WebObsSchema|Web Observatory]] <br />
|Proposal<br />
|Proposed extensions to schema.org for describing portals used for [[http://www.webscience.org/|Web Science]] collaboration including projects, datasets and tools used to study the Web.<br />
|Includes vocabularies for [[http://logd.tw.rpi.edu/web_observatory|Web Observatory]], [[http://logd.tw.rpi.edu/web_observatory_project|Web Observatory Project]], [[http://logd.tw.rpi.edu/web_observatory_dataset|Web Observatory Dataset]], and [[http://logd.tw.rpi.edu/web_observatory_tool|Web Observatory Tool]]<br />
|A reference implementation of a web observatory portal demonstrating the user of each Web Observatory vocabulary can be found at the [[http://tw.rpi.edu/web/web_observatory|Tetherless World Constellation Web Observatory Portal]]<br />
|-<br />
|...<br />
|<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|-<br />
|}<br />
<br />
== Brainstorming, Use Cases and Advance Notice ==<br />
<br />
The following topics are under discussion in the Web Schemas Schema.org community, but are not yet approaching specific proposed designs or broad consensus on an approach. Note that this distinction is pretty fuzzy, but some partitioning was needed here due to the number of proposals we're seeing. There is no shame in being listed here rather than as a proposal above!<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/PressReview|Ranking]]<br />
|Proposal<br />
|Proposal to add a list of items as a ranking (Top 10, Best sellers etc.)<br />
|One new type http://schema.org/ItemList/Ranking. Probably we need to specify the type, the name and the order (ascendant, descendant).<br />
|Often used in magazines.<br />
|-<br />
|[[WebSchemas/PressReview|PressReview]]<br />
|Proposal<br />
|Proposal to add a list of articles, events etc. as a Press review or Press digest<br />
|One new type http://schema.org/ItemList/PressReview<br />
|Often used in organization websites<br />
|-<br />
|[[WebSchemas/ScholarlyArticle|ScholarlyArticle]]<br />
|Early proposal from HighWire Press needs review.<br />
|Various ideas around improving [http://schema.org/ScholarlyArticle ScholarlyArticle]. <br />
|Suggestion that scholarly articles could be described in more detail.<br />
|There is a lot of related work in this area. For example [http://scholar.google.ca/intl/en/scholar/publishers.html Google Scholar publisher guidelines]; [http://academic.research.microsoft.com/ Microsoft Academic Search]. The [http://www.openarchives.org/OAI/openarchivesprotocol.html Open Archives Initiative - Protocol for Metadata Harvesting] also addresses this problem area and has broad adoption. See also earlier comments from [https://groups.google.com/forum/?fromgroups#!searchin/schemaorg-discussion/ScholarlyArticle/schemaorg-discussion/aEO56kVQoqQ/x-tGuaITitoJ HighWire Press] ([http://dl.dropbox.com/u/105439/ScholarlyArticle/ScholarlyArticle%20-%20schema.org.draft1.pdf pdf]) and following discussion (on the old mailing list).<br />
|-<br />
|[[WebSchemas/RealEstate|Real Estate]]<br />
|Discussions but no proposal yet.<br />
|Enthusiastic discussion in favour of adding RealEstate support. Tracked as [https://www.w3.org/2011/webschema/track/issues/13 issue 13]. This should likely follow along after the Good Relations work.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary, and schema.org's numerous subclasses, and [http://schema.org/Offer Offer] class.<br />
|-<br />
|Transport Data<br />
|Discussion<br />
|Initial discussion on description of transport data.<br />
|N/A<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0019.html Discussions] on whether this scenario can be covered with existing vocabulary.<br />
|-<br />
|[[WebSchemas/ActivitySchema|Activities (things you can do)]] <br />
|Proposal<br />
|Vocabulary for describing general activities not bound to any specific time or place. <br />
Unrelated to the [[WebSchemas/ActivityActions|Activities and Actions]] proposal for online user page interations that are listed above.<br />
|Examples: 'Paragliding'. 'Going to the cinema', etc. <br />
|Public draft and description available on [[WebSchemas/ActivitySchema|wiki]]. [http://lists.w3.org/Archives/Public/public-vocabs/2011Oct/0169.html Original proposal on public vocabs mailinglist].<br />
|-<br />
|[[WebSchemas/PersonBio|Person biography]]<br />
|Proposal<br />
|A proposal for supporting people's biography<br />
|Add a bibliography property to the Person type.<br />
|<br />
|-<br />
|Project<br />
|Proposal<br />
|Vocabulary for describing ''any'' kind of project<br />
|Terms (loosely) based on [http://purl.org/stuff/project this project vocabulary]<br />
|Use case gathering - [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0108.html see mailing list thread]<br />
|-<br />
|[[WebSchemas/VacationRentals|Vacation Rental Schema]]<br />
|Proposal<br />
|Creating an additional vocabulary for this hotel-alternative accommodation<br />
|Overview of new terms<br />
|Just initiated the discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/FictionalThing|Fictional Thing]]<br />
|Proposal<br />
|Providing the ability to identify a thing as being fictional<br />
|Proposal for the creation of a FictionalThing type<br />
|Supporting discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/JobMarket|JobMarket]]<br />
|Proposal<br />
|Extension for modelling job markets<br />
|Classes added: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_QuantitativeValue_.3E_Compensation Compensation], [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_StructuredValue_.3E_WorkExperience WorkExperience] + class amended: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_JobPosting JobPosting]<br />
|Draft for an extension published to elicit feedback<br />
|-<br />
|[[WebSchemas/VisualArtwork|VisualArtwork]]<br />
|Early Proposal<br />
|Extension for CreativeWork and replacement/alternative to Painting and Sculpture<br />
|Overview of Extension and new properties<br />
|Early draft for an extension published to elicit feedback.<br />
|-<br />
|[[WebSchemas/GeoJSON|GeoJSON]]<br />
|Early propsal<br />
|addition to the Geo* family of topics.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary<br />
|-<br />
|[[WebSchemas/LookInside|Looking Inside Tables]]<br />
|Early proposal<br />
|A mechanism to map the contents of tables into entities.<br />
|N/A<br />
|Draft for an extension published to elicit feedback.<br />
|-<br />
|-<br />
|[[WebSchemas/OnlinePresence|Online Presence]]<br />
|Early proposal<br />
|expressing Online Presence and current Actions<br />
|WIP<br />
|Related to [http://schema.org/Action Action] subtree and [http://online-presence.net Online Presence Ontology].<br />
|-<br />
|[[WebSchemas/SocialAccount|SocialAccount]]<br />
|Proposal<br />
| Introduce a type and a property to describe social accounts of http://schema.org/Person or http://schema.org/Organization<br />
|Add [[WebSchemas/SocialAccount| SocialAccount]] type derived from http://schema.org/Thing to capture social account. Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount| socialAccount]] expecting the type [[WebSchemas/SocialAccount| SocialAccount]]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion]<br />
|-<br />
|[[WebSchemas/socialAccount2|socialAccount]]<br />
|Proposal<br />
| Introduce a property to describe social accounts of http://schema.org/Person and http://schema.org/Organization<br />
| Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount2| socialAccount]] expecting a URL as value<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion] '''This is an alternative of the previous item'''<br />
|-<br />
|[[WebSchemas/Course|Course]]<br />
|Proposal<br />
| Introduce Course type to describe course as well as online courses (e.g. MOOCs)<br />
|Extend http://schema.org/CreativeWork to describe Course type. Proposed vocabularies are available on https://sites.google.com/site/moocontology/home]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2014Oct/0052.html discussion]<br />
|-<br />
|[[WebSchemas/VLEs|VLEs: Course, Session, Assessment]]<br />
|Proposal<br />
| Introduce additional concepts to describe Virtual Learning Environments' (VLEs) content and online courses (e.g. MOOCs)<br />
|<br />
* Extend http://schema.org/CreativeWork to describe the proposed type "Course". <br />
* Extend http://schema.org/InteractAction to describe the proposed type "Session". <br />
* Extend http://schema.org/ReviewAction to describe the proposed Assessment specific types (Assignment, Examination, Test). <br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2014Nov/0008.html discussion]<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|}<br />
<br />
== Already Accepted and Added ==<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0" <br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/providerSellerReDesign|Re-Design Provider / Seller vocabulary]]<br />
| style="background-color:#98FB98;"|[http://schema.org/docs/releases.html#v1.9 Published]<br />
|Address the issues / confusion in the relationship between provider and seller<br />
|Allows for clarity in cases like flight reservations, where you have both an airline seller and airline operator<br />
|Full details are documented [https://www.w3.org/wiki/WebSchemas/SellerVendorCleanup#Implementation_Details at W3C] and in [https://github.com/rvguha/schemaorg/issues/88 Github], alongside an [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview document]. <br />
|-<br />
|[[WebSchemas/Periodicals,_Articles_and_Multi-volume_Works|Periodicals, Articles and Multi-volume Works]]<br />
| style="background-color:#98FB98;"|[http://schema.org/docs/releases.html#v1.9 Published]<br />
|Three new Types: Periodical, PublicationVolume, PublicationIssue, and added properties for two existent Types: Article, CreativeWork<br />
|See [http://lists.w3.org/Archives/Public/public-vocabs/2014Mar/0013.html discussion] on public-vocabs.<br />
|Introduces changes proposed by the Bib Extend group for describing periodicals, alongside a 'work to work' property, 'workExample' (and an inverse).<br />
|-<br />
|[[WebSchemas/EventSchemaUpdate|Event schema update]]<br />
| style="background-color:#ECC8EC;"|Added 2013 (@@details?)<br />
|Some modifications to [http://schema.org/Event Event] based on deployment experience.<br />
|Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from [http://schema.org/Thing Thing]. <br />
|Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events.<br />
|-<br />
|[[WebSchemas/JobPostingSchema|Job Postings]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/11/schemaorg-support-for-job-postings.html Published]<br />
|A type for Job adverts.<br />
|Adds [http://schema.org/JobPosting JobPosting] class and supporting properties.<br />
|Related discussion on [[CVSchemas|CVs and resumes]]. The occupationalCategory property takes controlled values; more detail and options (e.g. EU ESCO) here would be useful.<br />
|-<br />
|IPTC/rNews integration<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/09/extended-schemaorg-news-support.html Published]<br />
|Integration of the [http://dev.iptc.org/rNews rNews] vocabulary produced by the [http://www.iptc.org/site/Home/Media_Releases/schema.org_adopts_IPTC's_rNews_for_news_markup IPTC]. <br />
|See original [http://dev.iptc.org/rNews-10-Introduction-to-rNews rNews 1.0 intro]; most of these terms are now in schema.org directly.<br />
|See New York Times' [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0040.html implementation announcement] for details and examples. <br />
|-<br />
|[[WebSchemas/Comment]]<br />
| style="background-color:#98FB98;"|Published<br />
|A fix to confusion around UserComments and lack of a Comment entity.<br />
|Add a class Comment under CreativeWork, for comments. UserComments remains a UserInteraction event, and awaits further clarification.<br />
|This addresses a need to have a representation of comments as documents, rather than merely as a user activity.<br />
|-<br />
|[[WebSchemas/SoftwareApplicationSchema|Software Application]]<br />
| style="background-color:#98FB98;"|Published<br />
|A class for Software Applications ('webapps', both installable and Web-based).<br />
|Re-uses some properties of CreativeWork; defines a subclass SoftwareApplication with 20 properties, plus two small subclasses.<br />
|This was been accepted and was sent for implementation (2012-04-15). Note that the SoftwareApplicationType enumeration may remain a Snippets-only vocabulary.<br />
|-<br />
|[[WebSchemas/Singularity|Singularity]]<br />
| style="background-color:#98FB98;"|Published<br />
|Proposes we move to singular property names, based on implementor feedback.<br />
|Adds new properties without a plural 's', aliases old ones.<br />
|This has been accepted and sent for implementation (2012-04-15)<br />
|-<br />
|[[WebSchemas/ExternalEnumerations|External Enumerations]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2012/05/schemaorg-markup-for-external-lists.html published]<br />
|Guidance on how to cite external enumerations, including constrained values for properties, and large collections of useful types.<br />
|For example, it should be possible to use lists of countries from e.g. ISO, UN. Or units and measures from systems such as [http://www.qudt.org/ QUDT]. Or community or professionally-maintained lists from Wikipedia, Library or GIS standards, etc. <br />
|Blog post covers initial/core design; further work will include lists of known authorities.<br />
|-<br />
|[[WebSchemas/MedicalHealthProposal|Medical/Health]] <br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html published]<br />
|Extended schema.org for describing key topics and their relationships in online health and medical content.<br />
|Adds MedicalEntity hierarchy including types for key medical/health topics (such as conditions, signs and symptoms, disease causes, risk factors, therapies including drugs and procedures, tests, devices, studies and trials, guidelines, diets, supplements, exercise plans, and anatomy) and supporting types. See [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html blog post] and [http://schema.org/docs/meddocs.html overview document] for details.<br />
|Published as v0.95 on 2012-06-26.<br />
|-<br />
|[[WebSchemas/additionalTypeProposal|additionalType]] <br />
| style="background-color:#98FB98;"| [http://www.w3.org/wiki/WebSchemas/additionalTypeProposal published]<br />
|Provides utility property for describing additional types.<br />
|Added 'additionalType' to [http://schema.org/Thing Thing], with detailed description discouraging use outside of Microdata syntax, since RDFa has 'typeof' built-in.<br />
|Published as v0.96 on 2012-07-17.<br />
|-<br />
|[[WebSchemas/GoodRelations|Good Relations integration]]<br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/11/good-relations-and-schemaorg.html published]<br />
| The schema.org team and Martin Hepp collaborated to integrate of a version of GR into schema.org. <br />
|See [http://www.heppnetz.de/projects/goodrelations/ Good Relations] site for background, e.g. [http://wiki.goodrelations-vocabulary.org/Quickstart quickstart] page.<br />
|Schema.org already had [http://schema.org/Offer Offer] and related terms, but benefitted from adding detail from Good Relations. Controlled values are still at purl.org GR URLs, and Good Relations continues as an independent project.<br />
|-<br />
|-<br />
|[[WebSchemas/LearningResources|Learning Resources]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013.<br />
|The Learning Resources Metadata Initiative defines a set of terms to improve schema.org's use with educational materials. <br />
|Mainly adds new properties (typically but not necc. on [http://schema.org/CreativeWork CreativeWork]): [http://wiki.creativecommons.org/LRMI/Properties/intendedEndUserRole intendedEndUserRole], [http://wiki.creativecommons.org/LRMI/Properties/educationalAlignment educationalAlignment], with values in a new class, [http://wiki.creativecommons.org/LRMI/Properties/1.0/AlignmentObject AlignmentObject]; [http://wiki.creativecommons.org/LRMI/Properties/educationalUse educationalUse] ([http://schema.org/Text Text] values), [http://wiki.creativecommons.org/LRMI/Properties/timeRequired timeRequired] (a [http://schema.org/Duration Duration]); [http://wiki.creativecommons.org/LRMI/Properties/typicalAgeRange typicalAgeRange] (Text valued); [http://wiki.creativecommons.org/LRMI/Properties/interactivityType interactivityType] (Text); [http://wiki.creativecommons.org/LRMI/Properties/learningResourceType learningResourceType], ...<br />
|Comments. see [http://wiki.creativecommons.org/LRMI/Properties/1.0 version 1.0] and [http://groups.google.com/group/lrmi discussion list]. <br />
|-<br />
|[[WebSchemas/Datasets|Datasets]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013 based on [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/dataset.html dataset.html]<br />
|A proposal extending schema.org for describing datasets and data catalogs. This may be revised to track evolution of W3C DCAT.<br />
|Adds the [http://logd.tw.rpi.edu/node/11401 Dataset], [http://logd.tw.rpi.edu/datacatalog DataCatalog], and [http://logd.tw.rpi.edu/datadownload DataDownload] types and supporting properties.<br />
|An example page with dataset microdata is available [http://logd.tw.rpi.edu/schemaorg_dataset_extension here]. For related efforts, see the [http://www.w3.org/2011/gld/wiki/Main_Page W3C Government Linked Data Working Group].<br />
|-<br />
|[[WebSchemas/TechArticleSchema|Tech Article]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html schema: techpub.html]<br />
|A proposal extending schema.org for describing technical content.<br />
|Adds dependencies, task, and technicalAudience. Adds descriptions for genre (CreativeWork) and about (CreativeWork).<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/APIReferenceSchema|API Reference]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing Application Programming Interface (API) reference content.<br />
|Derived from TechArticle; adds assembly, assemblyVersion, programmingModel, targetPlatform<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/CodeSchema|Code]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing human readable source code.<br />
|Adds codeRepository, codeSample, programmingLanguage, runtime, targetProduct.<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/Audience|Audience]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html drafted]<br />
|A proposal extending schema.org for describing audiences, building around http://schema.org/Audience type, also used by (and coordinated with) LRMI and MedicalHealth vocabulary.<br />
|Add property audience to type CreativeWork (done) and Product. Also ParentAudience, ... see [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html draft] for details.<br />
|This was added in stages; Medical/Health introduced the basic type 'Audience' first.<br />
|-<br />
|[[WebSchemas/CitationPromotion|Citation Promotion]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|To promote the 'citation' property currently on [http://schema.org/MedicalScholarlyArticle MedicalScholarlyArticle] up to [http://schema.org/CreativeWork CreativeWork].<br />
|Moved citation up to CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/sameAs|sameAs]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|Property to indicate that a single identity is being described.<br />
|Broadly same meaning as owl:sameAs.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions | Actions in Schema.org (part 1)]] <br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Aug/0008.html 1.0c, 7 August 2013].<br />
|Added a basic Action type to schema.org, as a foundation for further extension. See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|<br />
|<br />
|-<br />
|[[WebSchemas/TVRadioSchema|TV and Radio proposal]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Proposes modest changes and additions to support TV and radio (from [http://www.ebu.ch/ EBU] and [http://www.bbc.co.uk/ BBC]). <br />
|Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc.<br />
|See also [[SchemaDotOrgTV|background notes]] and [[http://www.w3.org/wiki/TVRadioSchema]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see [http://schema.org/VideoObject VideoObject], [http://schema.org/AudioObject AudioObject]; [http://schema.org/Movie Movie]. [http://schema.org/Event Event] re scheduling. See also [http://schema.org/UserPlays UserPlays], a kind of [http://schema.org/UserInteraction UserInteraction]. Comics and TV/Radio also share a concern for describing fictional characters and [http://pinboard.in/u:danbri/t:narrative/ narratives]. <br />
|-<br />
|[[WebSchemas/CivicServices|Civic Services]] <br />
| style="background-color:#98FB98;"| Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013].<br />
|Describing public civic services <br />
|A proposal extending schema.org to cover various kinds of civic services.<br />
|GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties<br />
|-<br />
|[[WebSchemas/LocalBusinessDepartment|Add Organization department property]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Added properties [http://schema.org/department department] and [http://schema.org/subOrganization subOrganizationOf] to [http://schema.org/Organization Organization], to allow local businesses to describe their depts (e.g. opening hours) in detail. <br />
|department and subOrganization properties (range and domain both Organization)<br />
|Proposal greatly simplified after WebSchemas discussion.<br />
|-<br />
|[[WebSchemas/OrdersSchema|Orders in Schema.org]] <br />
| style="background-color:#98FB98;"|Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Dec/0025.html 1.0e, 4 December 2013]<br />
|"While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)".<br />
|Adds classes OrderStatus, Order, DeliveryMethod plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/Accessibility|Accessibility]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Nov/0190.html 1.0e, 4 December 2013].<br />
|A proposal for adding accessibility metadata to all Creative Work content, done in concert with LRMI<br />
|Added four properties to CreativeWork to enable better discovery of accessible content.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions|Actions in Schema.org (part 2)]] <br />
|Added 2014<br />
|Add handlers and potential actions to Action type.<br />
|See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|-<br />
|[[WebSchemas/ReservationsSchema|Reservations in Schema.org]] <br />
|Added 2014<br />
|This proposal includes new types for describing reservations and tickets<br />
|Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/EmailMessageSchema|EmailMessage type]] <br />
|Added 2014<br />
|This proposal adds a single new type, EmailMessage<br />
|EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages.<br />
|No properties currently defined; proposals welcomed.<br />
|}<br />
<br />
<br/><br />
<br /><br />
<br /><br />
<br />
== Wiki markup ==<br />
<br />
* We have two templates for use here: [[Template:SchemaDotOrgProposal]] which takes 'name' and 'status' parameters, and which returns a one line page header for proposals; also [[Template:SchemaDotOrgTerm]], which takes a 'term' parameter and returns a simple hyperlink to that (class) term on schema.org.<br />
<br />
Nearby: <br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/drafts/alpha mercurial filetree]<br />
* [http://www.mediawiki.org/wiki/Help:Tables Help with wiki table syntax]<br />
<br />
[[Category:WebSchemas]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposalsArchive&diff=80630WebSchemas/SchemaDotOrgProposalsArchive2015-01-22T17:04:27Z<p>Danbri: </p>
<hr />
<div><br />
<br />
This is an archived snapshot of [[WebSchemas/SchemaDotOrgProposalsArchive]]. Active development has moved to Github.<br />
<br />
See also the [http://schema.org/docs/releases.html release history] page at schema.org.<br />
<br />
== 2011-2014 Proposals for Schema.org ==<br />
<br />
* Since 2014 schema.org uses [https://github.com/schemaorg/schemaorg/issues Github] for active development, although email discussion remains in the WebSchemas public-vocabs list.<br />
* History: 2012-13 draft [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext schema files] were hosted in W3C's Mercurial repository.<br />
* From 2014, schema.org runs on [https://github.com/rvguha/schemaorg opensource software], and uses Git(hub) for schema collaboration. Examples and schemas are in the [https://github.com/rvguha/schemaorg/tree/master/data data/] area of the repository.<br />
<br />
From 2011-2014 this page collected public proposals for [http://schema.org/docs/full.html schema.org vocabulary] extensions and improvements. <br />
<br />
We are winding down the [http://www.w3.org/2011/webschema/track/ W3C's issue tracker] for schema.org issues, except for matters of coordination with other vocabularies and W3C specifications.<br />
<br />
Schema.org public discussions happen via the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs]@w3.org W3C mailing list for discussions. <br />
<br />
Sometimes proposals evolve from offlist and face-to-face discussions; when possible, advance warning of 'expected' or possible proposals can be indicated here ([http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0102.html announced 24 Feb 2012]).<br />
<br />
Schema.org proposals can take any form during discussions, but ultimately they should take the form of HTML+RDFa schema definitions; some real examples are in the [https://github.com/rvguha/schemaorg/tree/master/data data/ area] of the schema.org repository. See Github pages for more details.<br />
<br />
'''Note''': When preparing a proposal, we need to know for each type and property, its name and description, alongside examples of usage. There are lots of different ways in which these can be prepared: wiki pages, text files, spreadsheets, PDFs etc. Do note that each property is considered as a global entity, ie. a property called 'foo' gets just one description - you can't give different descriptions for its use with the "Person" type, versus its use with the CreativeWork type. Ideally, develop a machine-readable proposal and test it using the software on Github.<br />
<br />
To search just these proposals, the issue tracker and schema.org-related mailing lists, try a [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek this custom search].<br />
<br />
<br />
== 2014 Proposals and Discussion ==<br />
<br />
These proposals are working towards inclusion in schema.org.<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/Measurement|Measurement]]<br />
|Proposal<br />
|Introduce the concept of a Measurement to describe the relationship between a value and a thing, as in sports statistics.<br />
|See wiki page<br />
|<br />
|-<br />
|[[WebSchemas/associatedMediaToThing|Change domain of associatedMedia to Thing]]<br />
|Proposal<br />
|Change the domain of http://schema.org/associatedMedia to http://schema.org/Thing<br />
|Enables many more types to associate contained or complementary media content, beyond CreativeWork.<br />
|Discussion at http://lists.w3.org/Archives/Public/public-vocabs/2014May/0224.html<br />
|-<br />
|[[WebSchemas/PropertyValuePairs|Property-Value Pairs]]<br />
|Proposal<br />
|Adding support for arbitrary property-value pairs. Useful for product features and proprietary features of places.<br />
|One new type http://schema.org/PropertyValue, two new properties for this type (unitText, propertyID), changes to domain and range for unitCode, value, minValue, maxValue, and valueReference properties; one new property additionalProperty for http://schema.org/Place OR http://schema.org/Product.<br />
|Mirrors an upcoming feature in [http://purl.org/goodrelations/ GoodRelations].<br />
|-<br />
|[[WebSchemas/Vehicles|Vehicles: Cars, Bikes, Boats]]<br />
|Proposal<br />
|Adding support for vehicle features for cars, bikes, boats, and other vehicles for sales and rental.<br />
|See proposal for details.<br />
|<br />
|-<br />
|[[WebSchemas/Orders_enhancement|Orders Schema update]]<br />
|Proposal<br />
|Proposal to add order line and parcel delivery support in the Orders Schema.<br />
|One new Type: OrderItem, and added properties for one existent Type: Order<br />
|<br />
|-<br />
|[[WebSchemas/SocialAccountProperty|social Account property]]<br />
|Proposal<br />
|Indicates a corresponding profile page for an account on a socially-oriented Web site.<br />
|One new property: socialAccount<br />
|<br />
|-<br />
|[[WebSchemas/Audiobook|Audiobook]]<br />
|Proposal<br />
|Proposal for new Audiobook Type and abridged property for [http://schema.org/Book Book].<br />
|Audiobook subtype of [http://schema.org/Book Book] ''and'' of [http://schema.org/AudioObject AudioObject], adds readBy property<br />
|<br />
|-<br />
|[[WebSchemas/Collection|Collection]]<br />
|Proposal<br />
|Proposal for new Collection Type and part properties for [http://schema.org/CreativeWork CreativeWork].<br />
|Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/Accessibility/ToDo|Accessibility]] (part 2)<br />
|Discussion<br />
|Extension for describing accessibility properties of a [http://schema.org/CreativeWork CreativeWork].<br />
|Additional work to add accessMode, hasAdapation, isAdaptationof that were not covered in 1.0 Accessibility work.<br />
|<br />
|-<br />
|[[WebSchemas/QuotationSchema|Add Quotation type]]<br />
|Proposal<br />
|Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties.<br />
|Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee.<br />
|Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise.<br />
|-<br />
|[[WebSchemas/WorkersUnionSchema|Workers Union type]] <br />
|Accepted<br />
|This proposal adds a single new type, WorkersUnion, addressing [http://www.w3.org/2011/webschema/track/issues/17 issue 17] in the WebSchemas tracker. <br />
|"A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying.""<br />
|One type, see [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/workersunion.html draft schema].<br />
|-<br />
|[[WebSchemas/Sports|Sports]]<br />
|Proposal<br />
|The purpose of this proposal is to introduce an expanded vocabulary for describing sports information within schema.org. Key concepts include Statistics, Roles, Ordered Events, Competitions and Competition Results.<br />
|See proposal for full set of vocabulary updates.<br />
|V3 posted 2014.05.09<br />
|-<br />
|[[WebSchemas/PeriodicalsComics|Comics and Serials]]<br />
| style="background-color:#ECC8EC;"|Discussing Proposals <br />
|Proposal from Marvel (see [[PeriodicalsComics#Code_Examples|examples]]).<br />
|Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. <br />
|Generally well received and specified, but some detailed [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0073.html discussion] re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with [http://schema.org/Book Book]/numberOfPages, or [http://schema.org/ScholarlyArticle ScholarlyArticle]? Should PeriodicalSeries be intangible?<br />
|-<br />
|[[WebSchemas/HistoricalDataSchema|Historical Data proposal]]<br />
|Proposal<br />
|The [http://historical-data.org/ historical-data.org] site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios.<br />
|Adds HistoricalRecord, HistoricalEvent (subclass of Event), ''overrides'' attendees, subEvents, superEvent to point to HistoricalEvent.<br />
|There is an associated implementation, [https://github.com/historical-data/ github repository], and [http://historical-data-schema.blogspot.com/ blog].<br />
|-<br />
|[[WebSchemas/BioDatabases|Biological Databases]]<br />
|Proposal<br />
|A schema extension for describing biological databases, [http://sagace.nibio.go.jp/schema/en/schema.html Sagace]. <br />
|Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. <br />
|Others have also mentioned interest in adding some notion of species.<br />
|-<br />
|[[WebSchemas/Breadcrumbs|Breadcrumbs]]<br />
|Proposal<br />
|A proposal resolving current problems handling breadcrumbs.<br />
|Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See [http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Nov/0026.html discussion] on using literal values.<br />
|<br />
|-<br />
|[[WebSchemas/DiscussionSchema|Discussion]] <br />
|Proposal<br />
|A proposal extending schema.org for describing online discussion forums and message boards.<br />
|Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful.<br />
|Addition candidate<br />
|-<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html Innovation] <br />
|Proposal<br />
|A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html]<br />
|Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [http://purl.org/innovation/ns] for complete list of terms.<br />
|Addition candidate<br />
|-<br />
|[[WebSchemas/dissolutionDate|dissolutionDate]]<br />
|Proposal<br />
|Add a dissolutionDate property to Organization.<br />
|<br />
|<br />
|-<br />
|[http://thematix.com/ontologies/travel/lodging/ Lodging Extensions]<br />
|Proposal<br />
|A proposal for extending LodgingBusiness. Specification is here http://thematix.com/ontologies/travel/lodging/<br />
|Adds Amenity, BusinessService, Feature, GuestRoomAmenity, LodgingBusinessAmenity, LodgingBusinessService, RentalOffer, RentalRate, Room, RoomType and Service.<br />
|In addition to the examples given in the cited website, examples can be seen at http://www.regencyhotelmiami.com/ and http://hiltonvb.com and at Super8 hotel description pages, e.g., http://www.super8.com/hotels/alberta/fort-mcmurray/super-8-fort-mcmurray/hotel-overview. <br />
|-<br />
|-<br />
|[[WebSchemas/WebObsSchema|Web Observatory]] <br />
|Proposal<br />
|Proposed extensions to schema.org for describing portals used for [[http://www.webscience.org/|Web Science]] collaboration including projects, datasets and tools used to study the Web.<br />
|Includes vocabularies for [[http://logd.tw.rpi.edu/web_observatory|Web Observatory]], [[http://logd.tw.rpi.edu/web_observatory_project|Web Observatory Project]], [[http://logd.tw.rpi.edu/web_observatory_dataset|Web Observatory Dataset]], and [[http://logd.tw.rpi.edu/web_observatory_tool|Web Observatory Tool]]<br />
|A reference implementation of a web observatory portal demonstrating the user of each Web Observatory vocabulary can be found at the [[http://tw.rpi.edu/web/web_observatory|Tetherless World Constellation Web Observatory Portal]]<br />
|-<br />
|...<br />
|<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|-<br />
|}<br />
<br />
== Brainstorming, Use Cases and Advance Notice ==<br />
<br />
The following topics are under discussion in the Web Schemas Schema.org community, but are not yet approaching specific proposed designs or broad consensus on an approach. Note that this distinction is pretty fuzzy, but some partitioning was needed here due to the number of proposals we're seeing. There is no shame in being listed here rather than as a proposal above!<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/PressReview|Ranking]]<br />
|Proposal<br />
|Proposal to add a list of items as a ranking (Top 10, Best sellers etc.)<br />
|One new type http://schema.org/ItemList/Ranking. Probably we need to specify the type, the name and the order (ascendant, descendant).<br />
|Often used in magazines.<br />
|-<br />
|[[WebSchemas/PressReview|PressReview]]<br />
|Proposal<br />
|Proposal to add a list of articles, events etc. as a Press review or Press digest<br />
|One new type http://schema.org/ItemList/PressReview<br />
|Often used in organization websites<br />
|-<br />
|[[WebSchemas/ScholarlyArticle|ScholarlyArticle]]<br />
|Early proposal from HighWire Press needs review.<br />
|Various ideas around improving [http://schema.org/ScholarlyArticle ScholarlyArticle]. <br />
|Suggestion that scholarly articles could be described in more detail.<br />
|There is a lot of related work in this area. For example [http://scholar.google.ca/intl/en/scholar/publishers.html Google Scholar publisher guidelines]; [http://academic.research.microsoft.com/ Microsoft Academic Search]. The [http://www.openarchives.org/OAI/openarchivesprotocol.html Open Archives Initiative - Protocol for Metadata Harvesting] also addresses this problem area and has broad adoption. See also earlier comments from [https://groups.google.com/forum/?fromgroups#!searchin/schemaorg-discussion/ScholarlyArticle/schemaorg-discussion/aEO56kVQoqQ/x-tGuaITitoJ HighWire Press] ([http://dl.dropbox.com/u/105439/ScholarlyArticle/ScholarlyArticle%20-%20schema.org.draft1.pdf pdf]) and following discussion (on the old mailing list).<br />
|-<br />
|[[WebSchemas/RealEstate|Real Estate]]<br />
|Discussions but no proposal yet.<br />
|Enthusiastic discussion in favour of adding RealEstate support. Tracked as [https://www.w3.org/2011/webschema/track/issues/13 issue 13]. This should likely follow along after the Good Relations work.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary, and schema.org's numerous subclasses, and [http://schema.org/Offer Offer] class.<br />
|-<br />
|Transport Data<br />
|Discussion<br />
|Initial discussion on description of transport data.<br />
|N/A<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0019.html Discussions] on whether this scenario can be covered with existing vocabulary.<br />
|-<br />
|[[WebSchemas/ActivitySchema|Activities (things you can do)]] <br />
|Proposal<br />
|Vocabulary for describing general activities not bound to any specific time or place. <br />
Unrelated to the [[WebSchemas/ActivityActions|Activities and Actions]] proposal for online user page interations that are listed above.<br />
|Examples: 'Paragliding'. 'Going to the cinema', etc. <br />
|Public draft and description available on [[WebSchemas/ActivitySchema|wiki]]. [http://lists.w3.org/Archives/Public/public-vocabs/2011Oct/0169.html Original proposal on public vocabs mailinglist].<br />
|-<br />
|[[WebSchemas/PersonBio|Person biography]]<br />
|Proposal<br />
|A proposal for supporting people's biography<br />
|Add a bibliography property to the Person type.<br />
|<br />
|-<br />
|Project<br />
|Proposal<br />
|Vocabulary for describing ''any'' kind of project<br />
|Terms (loosely) based on [http://purl.org/stuff/project this project vocabulary]<br />
|Use case gathering - [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0108.html see mailing list thread]<br />
|-<br />
|[[WebSchemas/VacationRentals|Vacation Rental Schema]]<br />
|Proposal<br />
|Creating an additional vocabulary for this hotel-alternative accommodation<br />
|Overview of new terms<br />
|Just initiated the discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/FictionalThing|Fictional Thing]]<br />
|Proposal<br />
|Providing the ability to identify a thing as being fictional<br />
|Proposal for the creation of a FictionalThing type<br />
|Supporting discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/JobMarket|JobMarket]]<br />
|Proposal<br />
|Extension for modelling job markets<br />
|Classes added: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_QuantitativeValue_.3E_Compensation Compensation], [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_StructuredValue_.3E_WorkExperience WorkExperience] + class amended: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_JobPosting JobPosting]<br />
|Draft for an extension published to elicit feedback<br />
|-<br />
|[[WebSchemas/VisualArtwork|VisualArtwork]]<br />
|Early Proposal<br />
|Extension for CreativeWork and replacement/alternative to Painting and Sculpture<br />
|Overview of Extension and new properties<br />
|Early draft for an extension published to elicit feedback.<br />
|-<br />
|[[WebSchemas/GeoJSON|GeoJSON]]<br />
|Early propsal<br />
|addition to the Geo* family of topics.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary<br />
|-<br />
|[[WebSchemas/LookInside|Looking Inside Tables]]<br />
|Early proposal<br />
|A mechanism to map the contents of tables into entities.<br />
|N/A<br />
|Draft for an extension published to elicit feedback.<br />
|-<br />
|-<br />
|[[WebSchemas/OnlinePresence|Online Presence]]<br />
|Early proposal<br />
|expressing Online Presence and current Actions<br />
|WIP<br />
|Related to [http://schema.org/Action Action] subtree and [http://online-presence.net Online Presence Ontology].<br />
|-<br />
|[[WebSchemas/SocialAccount|SocialAccount]]<br />
|Proposal<br />
| Introduce a type and a property to describe social accounts of http://schema.org/Person or http://schema.org/Organization<br />
|Add [[WebSchemas/SocialAccount| SocialAccount]] type derived from http://schema.org/Thing to capture social account. Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount| socialAccount]] expecting the type [[WebSchemas/SocialAccount| SocialAccount]]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion]<br />
|-<br />
|[[WebSchemas/socialAccount2|socialAccount]]<br />
|Proposal<br />
| Introduce a property to describe social accounts of http://schema.org/Person and http://schema.org/Organization<br />
| Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount2| socialAccount]] expecting a URL as value<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion] '''This is an alternative of the previous item'''<br />
|-<br />
|[[WebSchemas/Course|Course]]<br />
|Proposal<br />
| Introduce Course type to describe course as well as online courses (e.g. MOOCs)<br />
|Extend http://schema.org/CreativeWork to describe Course type. Proposed vocabularies are available on https://sites.google.com/site/moocontology/home]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2014Oct/0052.html discussion]<br />
|-<br />
|[[WebSchemas/VLEs|VLEs: Course, Session, Assessment]]<br />
|Proposal<br />
| Introduce additional concepts to describe Virtual Learning Environments' (VLEs) content and online courses (e.g. MOOCs)<br />
|<br />
* Extend http://schema.org/CreativeWork to describe the proposed type "Course". <br />
* Extend http://schema.org/InteractAction to describe the proposed type "Session". <br />
* Extend http://schema.org/ReviewAction to describe the proposed Assessment specific types (Assignment, Examination, Test). <br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2014Nov/0008.html discussion]<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|}<br />
<br />
== Already Accepted and Added ==<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0" <br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/providerSellerReDesign|Re-Design Provider / Seller vocabulary]]<br />
| style="background-color:#98FB98;"|[http://schema.org/docs/releases.html#v1.9 Published]<br />
|Address the issues / confusion in the relationship between provider and seller<br />
|Allows for clarity in cases like flight reservations, where you have both an airline seller and airline operator<br />
|Full details are documented [https://www.w3.org/wiki/WebSchemas/SellerVendorCleanup#Implementation_Details at W3C] and in [https://github.com/rvguha/schemaorg/issues/88 Github], alongside an [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview document]. <br />
|-<br />
|[[WebSchemas/Periodicals,_Articles_and_Multi-volume_Works|Periodicals, Articles and Multi-volume Works]]<br />
| style="background-color:#98FB98;"|[http://schema.org/docs/releases.html#v1.9 Published]<br />
|Three new Types: Periodical, PublicationVolume, PublicationIssue, and added properties for two existent Types: Article, CreativeWork<br />
|See [http://lists.w3.org/Archives/Public/public-vocabs/2014Mar/0013.html discussion] on public-vocabs.<br />
|Introduces changes proposed by the Bib Extend group for describing periodicals, alongside a 'work to work' property, 'workExample' (and an inverse).<br />
|-<br />
|[[WebSchemas/EventSchemaUpdate|Event schema update]]<br />
| style="background-color:#ECC8EC;"|Added 2013 (@@details?)<br />
|Some modifications to [http://schema.org/Event Event] based on deployment experience.<br />
|Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from [http://schema.org/Thing Thing]. <br />
|Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events.<br />
|-<br />
|[[WebSchemas/JobPostingSchema|Job Postings]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/11/schemaorg-support-for-job-postings.html Published]<br />
|A type for Job adverts.<br />
|Adds [http://schema.org/JobPosting JobPosting] class and supporting properties.<br />
|Related discussion on [[CVSchemas|CVs and resumes]]. The occupationalCategory property takes controlled values; more detail and options (e.g. EU ESCO) here would be useful.<br />
|-<br />
|IPTC/rNews integration<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/09/extended-schemaorg-news-support.html Published]<br />
|Integration of the [http://dev.iptc.org/rNews rNews] vocabulary produced by the [http://www.iptc.org/site/Home/Media_Releases/schema.org_adopts_IPTC's_rNews_for_news_markup IPTC]. <br />
|See original [http://dev.iptc.org/rNews-10-Introduction-to-rNews rNews 1.0 intro]; most of these terms are now in schema.org directly.<br />
|See New York Times' [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0040.html implementation announcement] for details and examples. <br />
|-<br />
|[[WebSchemas/Comment]]<br />
| style="background-color:#98FB98;"|Published<br />
|A fix to confusion around UserComments and lack of a Comment entity.<br />
|Add a class Comment under CreativeWork, for comments. UserComments remains a UserInteraction event, and awaits further clarification.<br />
|This addresses a need to have a representation of comments as documents, rather than merely as a user activity.<br />
|-<br />
|[[WebSchemas/SoftwareApplicationSchema|Software Application]]<br />
| style="background-color:#98FB98;"|Published<br />
|A class for Software Applications ('webapps', both installable and Web-based).<br />
|Re-uses some properties of CreativeWork; defines a subclass SoftwareApplication with 20 properties, plus two small subclasses.<br />
|This was been accepted and was sent for implementation (2012-04-15). Note that the SoftwareApplicationType enumeration may remain a Snippets-only vocabulary.<br />
|-<br />
|[[WebSchemas/Singularity|Singularity]]<br />
| style="background-color:#98FB98;"|Published<br />
|Proposes we move to singular property names, based on implementor feedback.<br />
|Adds new properties without a plural 's', aliases old ones.<br />
|This has been accepted and sent for implementation (2012-04-15)<br />
|-<br />
|[[WebSchemas/ExternalEnumerations|External Enumerations]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2012/05/schemaorg-markup-for-external-lists.html published]<br />
|Guidance on how to cite external enumerations, including constrained values for properties, and large collections of useful types.<br />
|For example, it should be possible to use lists of countries from e.g. ISO, UN. Or units and measures from systems such as [http://www.qudt.org/ QUDT]. Or community or professionally-maintained lists from Wikipedia, Library or GIS standards, etc. <br />
|Blog post covers initial/core design; further work will include lists of known authorities.<br />
|-<br />
|[[WebSchemas/MedicalHealthProposal|Medical/Health]] <br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html published]<br />
|Extended schema.org for describing key topics and their relationships in online health and medical content.<br />
|Adds MedicalEntity hierarchy including types for key medical/health topics (such as conditions, signs and symptoms, disease causes, risk factors, therapies including drugs and procedures, tests, devices, studies and trials, guidelines, diets, supplements, exercise plans, and anatomy) and supporting types. See [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html blog post] and [http://schema.org/docs/meddocs.html overview document] for details.<br />
|Published as v0.95 on 2012-06-26.<br />
|-<br />
|[[WebSchemas/additionalTypeProposal|additionalType]] <br />
| style="background-color:#98FB98;"| [http://www.w3.org/wiki/WebSchemas/additionalTypeProposal published]<br />
|Provides utility property for describing additional types.<br />
|Added 'additionalType' to [http://schema.org/Thing Thing], with detailed description discouraging use outside of Microdata syntax, since RDFa has 'typeof' built-in.<br />
|Published as v0.96 on 2012-07-17.<br />
|-<br />
|[[WebSchemas/GoodRelations|Good Relations integration]]<br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/11/good-relations-and-schemaorg.html published]<br />
| The schema.org team and Martin Hepp collaborated to integrate of a version of GR into schema.org. <br />
|See [http://www.heppnetz.de/projects/goodrelations/ Good Relations] site for background, e.g. [http://wiki.goodrelations-vocabulary.org/Quickstart quickstart] page.<br />
|Schema.org already had [http://schema.org/Offer Offer] and related terms, but benefitted from adding detail from Good Relations. Controlled values are still at purl.org GR URLs, and Good Relations continues as an independent project.<br />
|-<br />
|-<br />
|[[WebSchemas/LearningResources|Learning Resources]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013.<br />
|The Learning Resources Metadata Initiative defines a set of terms to improve schema.org's use with educational materials. <br />
|Mainly adds new properties (typically but not necc. on [http://schema.org/CreativeWork CreativeWork]): [http://wiki.creativecommons.org/LRMI/Properties/intendedEndUserRole intendedEndUserRole], [http://wiki.creativecommons.org/LRMI/Properties/educationalAlignment educationalAlignment], with values in a new class, [http://wiki.creativecommons.org/LRMI/Properties/1.0/AlignmentObject AlignmentObject]; [http://wiki.creativecommons.org/LRMI/Properties/educationalUse educationalUse] ([http://schema.org/Text Text] values), [http://wiki.creativecommons.org/LRMI/Properties/timeRequired timeRequired] (a [http://schema.org/Duration Duration]); [http://wiki.creativecommons.org/LRMI/Properties/typicalAgeRange typicalAgeRange] (Text valued); [http://wiki.creativecommons.org/LRMI/Properties/interactivityType interactivityType] (Text); [http://wiki.creativecommons.org/LRMI/Properties/learningResourceType learningResourceType], ...<br />
|Comments. see [http://wiki.creativecommons.org/LRMI/Properties/1.0 version 1.0] and [http://groups.google.com/group/lrmi discussion list]. <br />
|-<br />
|[[WebSchemas/Datasets|Datasets]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013 based on [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/dataset.html dataset.html]<br />
|A proposal extending schema.org for describing datasets and data catalogs. This may be revised to track evolution of W3C DCAT.<br />
|Adds the [http://logd.tw.rpi.edu/node/11401 Dataset], [http://logd.tw.rpi.edu/datacatalog DataCatalog], and [http://logd.tw.rpi.edu/datadownload DataDownload] types and supporting properties.<br />
|An example page with dataset microdata is available [http://logd.tw.rpi.edu/schemaorg_dataset_extension here]. For related efforts, see the [http://www.w3.org/2011/gld/wiki/Main_Page W3C Government Linked Data Working Group].<br />
|-<br />
|[[WebSchemas/TechArticleSchema|Tech Article]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html schema: techpub.html]<br />
|A proposal extending schema.org for describing technical content.<br />
|Adds dependencies, task, and technicalAudience. Adds descriptions for genre (CreativeWork) and about (CreativeWork).<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/APIReferenceSchema|API Reference]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing Application Programming Interface (API) reference content.<br />
|Derived from TechArticle; adds assembly, assemblyVersion, programmingModel, targetPlatform<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/CodeSchema|Code]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing human readable source code.<br />
|Adds codeRepository, codeSample, programmingLanguage, runtime, targetProduct.<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/Audience|Audience]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html drafted]<br />
|A proposal extending schema.org for describing audiences, building around http://schema.org/Audience type, also used by (and coordinated with) LRMI and MedicalHealth vocabulary.<br />
|Add property audience to type CreativeWork (done) and Product. Also ParentAudience, ... see [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html draft] for details.<br />
|This was added in stages; Medical/Health introduced the basic type 'Audience' first.<br />
|-<br />
|[[WebSchemas/CitationPromotion|Citation Promotion]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|To promote the 'citation' property currently on [http://schema.org/MedicalScholarlyArticle MedicalScholarlyArticle] up to [http://schema.org/CreativeWork CreativeWork].<br />
|Moved citation up to CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/sameAs|sameAs]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|Property to indicate that a single identity is being described.<br />
|Broadly same meaning as owl:sameAs.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions | Actions in Schema.org (part 1)]] <br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Aug/0008.html 1.0c, 7 August 2013].<br />
|Added a basic Action type to schema.org, as a foundation for further extension. See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|<br />
|<br />
|-<br />
|[[WebSchemas/TVRadioSchema|TV and Radio proposal]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Proposes modest changes and additions to support TV and radio (from [http://www.ebu.ch/ EBU] and [http://www.bbc.co.uk/ BBC]). <br />
|Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc.<br />
|See also [[SchemaDotOrgTV|background notes]] and [[http://www.w3.org/wiki/TVRadioSchema]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see [http://schema.org/VideoObject VideoObject], [http://schema.org/AudioObject AudioObject]; [http://schema.org/Movie Movie]. [http://schema.org/Event Event] re scheduling. See also [http://schema.org/UserPlays UserPlays], a kind of [http://schema.org/UserInteraction UserInteraction]. Comics and TV/Radio also share a concern for describing fictional characters and [http://pinboard.in/u:danbri/t:narrative/ narratives]. <br />
|-<br />
|[[WebSchemas/CivicServices|Civic Services]] <br />
| style="background-color:#98FB98;"| Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013].<br />
|Describing public civic services <br />
|A proposal extending schema.org to cover various kinds of civic services.<br />
|GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties<br />
|-<br />
|[[WebSchemas/LocalBusinessDepartment|Add Organization department property]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Added properties [http://schema.org/department department] and [http://schema.org/subOrganization subOrganizationOf] to [http://schema.org/Organization Organization], to allow local businesses to describe their depts (e.g. opening hours) in detail. <br />
|department and subOrganization properties (range and domain both Organization)<br />
|Proposal greatly simplified after WebSchemas discussion.<br />
|-<br />
|[[WebSchemas/OrdersSchema|Orders in Schema.org]] <br />
| style="background-color:#98FB98;"|Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Dec/0025.html 1.0e, 4 December 2013]<br />
|"While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)".<br />
|Adds classes OrderStatus, Order, DeliveryMethod plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/Accessibility|Accessibility]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Nov/0190.html 1.0e, 4 December 2013].<br />
|A proposal for adding accessibility metadata to all Creative Work content, done in concert with LRMI<br />
|Added four properties to CreativeWork to enable better discovery of accessible content.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions|Actions in Schema.org (part 2)]] <br />
|Added 2014<br />
|Add handlers and potential actions to Action type.<br />
|See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|-<br />
|[[WebSchemas/ReservationsSchema|Reservations in Schema.org]] <br />
|Added 2014<br />
|This proposal includes new types for describing reservations and tickets<br />
|Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/EmailMessageSchema|EmailMessage type]] <br />
|Added 2014<br />
|This proposal adds a single new type, EmailMessage<br />
|EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages.<br />
|No properties currently defined; proposals welcomed.<br />
|}<br />
<br />
<br/><br />
<br /><br />
<br /><br />
<br />
== Wiki markup ==<br />
<br />
* We have two templates for use here: [[Template:SchemaDotOrgProposal]] which takes 'name' and 'status' parameters, and which returns a one line page header for proposals; also [[Template:SchemaDotOrgTerm]], which takes a 'term' parameter and returns a simple hyperlink to that (class) term on schema.org.<br />
<br />
Nearby: <br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/drafts/alpha mercurial filetree]<br />
* [http://www.mediawiki.org/wiki/Help:Tables Help with wiki table syntax]<br />
<br />
[[Category:WebSchemas]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposalsArchive&diff=80629WebSchemas/SchemaDotOrgProposalsArchive2015-01-22T17:04:00Z<p>Danbri: saving a snapshot here so we can minimise the main page</p>
<hr />
<div><br />
<br />
This is an archived snapshot of [[SchemaDotOrgProposalsArchive]]. Active development has moved to Github.<br />
<br />
See also the [http://schema.org/docs/releases.html release history] page at schema.org.<br />
<br />
== 2011-2014 Proposals for Schema.org ==<br />
<br />
* Since 2014 schema.org uses [https://github.com/schemaorg/schemaorg/issues Github] for active development, although email discussion remains in the WebSchemas public-vocabs list.<br />
* History: 2012-13 draft [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext schema files] were hosted in W3C's Mercurial repository.<br />
* From 2014, schema.org runs on [https://github.com/rvguha/schemaorg opensource software], and uses Git(hub) for schema collaboration. Examples and schemas are in the [https://github.com/rvguha/schemaorg/tree/master/data data/] area of the repository.<br />
<br />
From 2011-2014 this page collected public proposals for [http://schema.org/docs/full.html schema.org vocabulary] extensions and improvements. <br />
<br />
We are winding down the [http://www.w3.org/2011/webschema/track/ W3C's issue tracker] for schema.org issues, except for matters of coordination with other vocabularies and W3C specifications.<br />
<br />
Schema.org public discussions happen via the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs]@w3.org W3C mailing list for discussions. <br />
<br />
Sometimes proposals evolve from offlist and face-to-face discussions; when possible, advance warning of 'expected' or possible proposals can be indicated here ([http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0102.html announced 24 Feb 2012]).<br />
<br />
Schema.org proposals can take any form during discussions, but ultimately they should take the form of HTML+RDFa schema definitions; some real examples are in the [https://github.com/rvguha/schemaorg/tree/master/data data/ area] of the schema.org repository. See Github pages for more details.<br />
<br />
'''Note''': When preparing a proposal, we need to know for each type and property, its name and description, alongside examples of usage. There are lots of different ways in which these can be prepared: wiki pages, text files, spreadsheets, PDFs etc. Do note that each property is considered as a global entity, ie. a property called 'foo' gets just one description - you can't give different descriptions for its use with the "Person" type, versus its use with the CreativeWork type. Ideally, develop a machine-readable proposal and test it using the software on Github.<br />
<br />
To search just these proposals, the issue tracker and schema.org-related mailing lists, try a [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek this custom search].<br />
<br />
<br />
== 2014 Proposals and Discussion ==<br />
<br />
These proposals are working towards inclusion in schema.org.<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/Measurement|Measurement]]<br />
|Proposal<br />
|Introduce the concept of a Measurement to describe the relationship between a value and a thing, as in sports statistics.<br />
|See wiki page<br />
|<br />
|-<br />
|[[WebSchemas/associatedMediaToThing|Change domain of associatedMedia to Thing]]<br />
|Proposal<br />
|Change the domain of http://schema.org/associatedMedia to http://schema.org/Thing<br />
|Enables many more types to associate contained or complementary media content, beyond CreativeWork.<br />
|Discussion at http://lists.w3.org/Archives/Public/public-vocabs/2014May/0224.html<br />
|-<br />
|[[WebSchemas/PropertyValuePairs|Property-Value Pairs]]<br />
|Proposal<br />
|Adding support for arbitrary property-value pairs. Useful for product features and proprietary features of places.<br />
|One new type http://schema.org/PropertyValue, two new properties for this type (unitText, propertyID), changes to domain and range for unitCode, value, minValue, maxValue, and valueReference properties; one new property additionalProperty for http://schema.org/Place OR http://schema.org/Product.<br />
|Mirrors an upcoming feature in [http://purl.org/goodrelations/ GoodRelations].<br />
|-<br />
|[[WebSchemas/Vehicles|Vehicles: Cars, Bikes, Boats]]<br />
|Proposal<br />
|Adding support for vehicle features for cars, bikes, boats, and other vehicles for sales and rental.<br />
|See proposal for details.<br />
|<br />
|-<br />
|[[WebSchemas/Orders_enhancement|Orders Schema update]]<br />
|Proposal<br />
|Proposal to add order line and parcel delivery support in the Orders Schema.<br />
|One new Type: OrderItem, and added properties for one existent Type: Order<br />
|<br />
|-<br />
|[[WebSchemas/SocialAccountProperty|social Account property]]<br />
|Proposal<br />
|Indicates a corresponding profile page for an account on a socially-oriented Web site.<br />
|One new property: socialAccount<br />
|<br />
|-<br />
|[[WebSchemas/Audiobook|Audiobook]]<br />
|Proposal<br />
|Proposal for new Audiobook Type and abridged property for [http://schema.org/Book Book].<br />
|Audiobook subtype of [http://schema.org/Book Book] ''and'' of [http://schema.org/AudioObject AudioObject], adds readBy property<br />
|<br />
|-<br />
|[[WebSchemas/Collection|Collection]]<br />
|Proposal<br />
|Proposal for new Collection Type and part properties for [http://schema.org/CreativeWork CreativeWork].<br />
|Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/Accessibility/ToDo|Accessibility]] (part 2)<br />
|Discussion<br />
|Extension for describing accessibility properties of a [http://schema.org/CreativeWork CreativeWork].<br />
|Additional work to add accessMode, hasAdapation, isAdaptationof that were not covered in 1.0 Accessibility work.<br />
|<br />
|-<br />
|[[WebSchemas/QuotationSchema|Add Quotation type]]<br />
|Proposal<br />
|Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties.<br />
|Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee.<br />
|Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise.<br />
|-<br />
|[[WebSchemas/WorkersUnionSchema|Workers Union type]] <br />
|Accepted<br />
|This proposal adds a single new type, WorkersUnion, addressing [http://www.w3.org/2011/webschema/track/issues/17 issue 17] in the WebSchemas tracker. <br />
|"A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying.""<br />
|One type, see [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/workersunion.html draft schema].<br />
|-<br />
|[[WebSchemas/Sports|Sports]]<br />
|Proposal<br />
|The purpose of this proposal is to introduce an expanded vocabulary for describing sports information within schema.org. Key concepts include Statistics, Roles, Ordered Events, Competitions and Competition Results.<br />
|See proposal for full set of vocabulary updates.<br />
|V3 posted 2014.05.09<br />
|-<br />
|[[WebSchemas/PeriodicalsComics|Comics and Serials]]<br />
| style="background-color:#ECC8EC;"|Discussing Proposals <br />
|Proposal from Marvel (see [[PeriodicalsComics#Code_Examples|examples]]).<br />
|Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. <br />
|Generally well received and specified, but some detailed [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0073.html discussion] re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with [http://schema.org/Book Book]/numberOfPages, or [http://schema.org/ScholarlyArticle ScholarlyArticle]? Should PeriodicalSeries be intangible?<br />
|-<br />
|[[WebSchemas/HistoricalDataSchema|Historical Data proposal]]<br />
|Proposal<br />
|The [http://historical-data.org/ historical-data.org] site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios.<br />
|Adds HistoricalRecord, HistoricalEvent (subclass of Event), ''overrides'' attendees, subEvents, superEvent to point to HistoricalEvent.<br />
|There is an associated implementation, [https://github.com/historical-data/ github repository], and [http://historical-data-schema.blogspot.com/ blog].<br />
|-<br />
|[[WebSchemas/BioDatabases|Biological Databases]]<br />
|Proposal<br />
|A schema extension for describing biological databases, [http://sagace.nibio.go.jp/schema/en/schema.html Sagace]. <br />
|Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. <br />
|Others have also mentioned interest in adding some notion of species.<br />
|-<br />
|[[WebSchemas/Breadcrumbs|Breadcrumbs]]<br />
|Proposal<br />
|A proposal resolving current problems handling breadcrumbs.<br />
|Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See [http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Nov/0026.html discussion] on using literal values.<br />
|<br />
|-<br />
|[[WebSchemas/DiscussionSchema|Discussion]] <br />
|Proposal<br />
|A proposal extending schema.org for describing online discussion forums and message boards.<br />
|Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful.<br />
|Addition candidate<br />
|-<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html Innovation] <br />
|Proposal<br />
|A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html]<br />
|Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [http://purl.org/innovation/ns] for complete list of terms.<br />
|Addition candidate<br />
|-<br />
|[[WebSchemas/dissolutionDate|dissolutionDate]]<br />
|Proposal<br />
|Add a dissolutionDate property to Organization.<br />
|<br />
|<br />
|-<br />
|[http://thematix.com/ontologies/travel/lodging/ Lodging Extensions]<br />
|Proposal<br />
|A proposal for extending LodgingBusiness. Specification is here http://thematix.com/ontologies/travel/lodging/<br />
|Adds Amenity, BusinessService, Feature, GuestRoomAmenity, LodgingBusinessAmenity, LodgingBusinessService, RentalOffer, RentalRate, Room, RoomType and Service.<br />
|In addition to the examples given in the cited website, examples can be seen at http://www.regencyhotelmiami.com/ and http://hiltonvb.com and at Super8 hotel description pages, e.g., http://www.super8.com/hotels/alberta/fort-mcmurray/super-8-fort-mcmurray/hotel-overview. <br />
|-<br />
|-<br />
|[[WebSchemas/WebObsSchema|Web Observatory]] <br />
|Proposal<br />
|Proposed extensions to schema.org for describing portals used for [[http://www.webscience.org/|Web Science]] collaboration including projects, datasets and tools used to study the Web.<br />
|Includes vocabularies for [[http://logd.tw.rpi.edu/web_observatory|Web Observatory]], [[http://logd.tw.rpi.edu/web_observatory_project|Web Observatory Project]], [[http://logd.tw.rpi.edu/web_observatory_dataset|Web Observatory Dataset]], and [[http://logd.tw.rpi.edu/web_observatory_tool|Web Observatory Tool]]<br />
|A reference implementation of a web observatory portal demonstrating the user of each Web Observatory vocabulary can be found at the [[http://tw.rpi.edu/web/web_observatory|Tetherless World Constellation Web Observatory Portal]]<br />
|-<br />
|...<br />
|<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|-<br />
|}<br />
<br />
== Brainstorming, Use Cases and Advance Notice ==<br />
<br />
The following topics are under discussion in the Web Schemas Schema.org community, but are not yet approaching specific proposed designs or broad consensus on an approach. Note that this distinction is pretty fuzzy, but some partitioning was needed here due to the number of proposals we're seeing. There is no shame in being listed here rather than as a proposal above!<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/PressReview|Ranking]]<br />
|Proposal<br />
|Proposal to add a list of items as a ranking (Top 10, Best sellers etc.)<br />
|One new type http://schema.org/ItemList/Ranking. Probably we need to specify the type, the name and the order (ascendant, descendant).<br />
|Often used in magazines.<br />
|-<br />
|[[WebSchemas/PressReview|PressReview]]<br />
|Proposal<br />
|Proposal to add a list of articles, events etc. as a Press review or Press digest<br />
|One new type http://schema.org/ItemList/PressReview<br />
|Often used in organization websites<br />
|-<br />
|[[WebSchemas/ScholarlyArticle|ScholarlyArticle]]<br />
|Early proposal from HighWire Press needs review.<br />
|Various ideas around improving [http://schema.org/ScholarlyArticle ScholarlyArticle]. <br />
|Suggestion that scholarly articles could be described in more detail.<br />
|There is a lot of related work in this area. For example [http://scholar.google.ca/intl/en/scholar/publishers.html Google Scholar publisher guidelines]; [http://academic.research.microsoft.com/ Microsoft Academic Search]. The [http://www.openarchives.org/OAI/openarchivesprotocol.html Open Archives Initiative - Protocol for Metadata Harvesting] also addresses this problem area and has broad adoption. See also earlier comments from [https://groups.google.com/forum/?fromgroups#!searchin/schemaorg-discussion/ScholarlyArticle/schemaorg-discussion/aEO56kVQoqQ/x-tGuaITitoJ HighWire Press] ([http://dl.dropbox.com/u/105439/ScholarlyArticle/ScholarlyArticle%20-%20schema.org.draft1.pdf pdf]) and following discussion (on the old mailing list).<br />
|-<br />
|[[WebSchemas/RealEstate|Real Estate]]<br />
|Discussions but no proposal yet.<br />
|Enthusiastic discussion in favour of adding RealEstate support. Tracked as [https://www.w3.org/2011/webschema/track/issues/13 issue 13]. This should likely follow along after the Good Relations work.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary, and schema.org's numerous subclasses, and [http://schema.org/Offer Offer] class.<br />
|-<br />
|Transport Data<br />
|Discussion<br />
|Initial discussion on description of transport data.<br />
|N/A<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0019.html Discussions] on whether this scenario can be covered with existing vocabulary.<br />
|-<br />
|[[WebSchemas/ActivitySchema|Activities (things you can do)]] <br />
|Proposal<br />
|Vocabulary for describing general activities not bound to any specific time or place. <br />
Unrelated to the [[WebSchemas/ActivityActions|Activities and Actions]] proposal for online user page interations that are listed above.<br />
|Examples: 'Paragliding'. 'Going to the cinema', etc. <br />
|Public draft and description available on [[WebSchemas/ActivitySchema|wiki]]. [http://lists.w3.org/Archives/Public/public-vocabs/2011Oct/0169.html Original proposal on public vocabs mailinglist].<br />
|-<br />
|[[WebSchemas/PersonBio|Person biography]]<br />
|Proposal<br />
|A proposal for supporting people's biography<br />
|Add a bibliography property to the Person type.<br />
|<br />
|-<br />
|Project<br />
|Proposal<br />
|Vocabulary for describing ''any'' kind of project<br />
|Terms (loosely) based on [http://purl.org/stuff/project this project vocabulary]<br />
|Use case gathering - [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0108.html see mailing list thread]<br />
|-<br />
|[[WebSchemas/VacationRentals|Vacation Rental Schema]]<br />
|Proposal<br />
|Creating an additional vocabulary for this hotel-alternative accommodation<br />
|Overview of new terms<br />
|Just initiated the discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/FictionalThing|Fictional Thing]]<br />
|Proposal<br />
|Providing the ability to identify a thing as being fictional<br />
|Proposal for the creation of a FictionalThing type<br />
|Supporting discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/JobMarket|JobMarket]]<br />
|Proposal<br />
|Extension for modelling job markets<br />
|Classes added: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_QuantitativeValue_.3E_Compensation Compensation], [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_StructuredValue_.3E_WorkExperience WorkExperience] + class amended: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_JobPosting JobPosting]<br />
|Draft for an extension published to elicit feedback<br />
|-<br />
|[[WebSchemas/VisualArtwork|VisualArtwork]]<br />
|Early Proposal<br />
|Extension for CreativeWork and replacement/alternative to Painting and Sculpture<br />
|Overview of Extension and new properties<br />
|Early draft for an extension published to elicit feedback.<br />
|-<br />
|[[WebSchemas/GeoJSON|GeoJSON]]<br />
|Early propsal<br />
|addition to the Geo* family of topics.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary<br />
|-<br />
|[[WebSchemas/LookInside|Looking Inside Tables]]<br />
|Early proposal<br />
|A mechanism to map the contents of tables into entities.<br />
|N/A<br />
|Draft for an extension published to elicit feedback.<br />
|-<br />
|-<br />
|[[WebSchemas/OnlinePresence|Online Presence]]<br />
|Early proposal<br />
|expressing Online Presence and current Actions<br />
|WIP<br />
|Related to [http://schema.org/Action Action] subtree and [http://online-presence.net Online Presence Ontology].<br />
|-<br />
|[[WebSchemas/SocialAccount|SocialAccount]]<br />
|Proposal<br />
| Introduce a type and a property to describe social accounts of http://schema.org/Person or http://schema.org/Organization<br />
|Add [[WebSchemas/SocialAccount| SocialAccount]] type derived from http://schema.org/Thing to capture social account. Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount| socialAccount]] expecting the type [[WebSchemas/SocialAccount| SocialAccount]]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion]<br />
|-<br />
|[[WebSchemas/socialAccount2|socialAccount]]<br />
|Proposal<br />
| Introduce a property to describe social accounts of http://schema.org/Person and http://schema.org/Organization<br />
| Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount2| socialAccount]] expecting a URL as value<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion] '''This is an alternative of the previous item'''<br />
|-<br />
|[[WebSchemas/Course|Course]]<br />
|Proposal<br />
| Introduce Course type to describe course as well as online courses (e.g. MOOCs)<br />
|Extend http://schema.org/CreativeWork to describe Course type. Proposed vocabularies are available on https://sites.google.com/site/moocontology/home]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2014Oct/0052.html discussion]<br />
|-<br />
|[[WebSchemas/VLEs|VLEs: Course, Session, Assessment]]<br />
|Proposal<br />
| Introduce additional concepts to describe Virtual Learning Environments' (VLEs) content and online courses (e.g. MOOCs)<br />
|<br />
* Extend http://schema.org/CreativeWork to describe the proposed type "Course". <br />
* Extend http://schema.org/InteractAction to describe the proposed type "Session". <br />
* Extend http://schema.org/ReviewAction to describe the proposed Assessment specific types (Assignment, Examination, Test). <br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2014Nov/0008.html discussion]<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|}<br />
<br />
== Already Accepted and Added ==<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0" <br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/providerSellerReDesign|Re-Design Provider / Seller vocabulary]]<br />
| style="background-color:#98FB98;"|[http://schema.org/docs/releases.html#v1.9 Published]<br />
|Address the issues / confusion in the relationship between provider and seller<br />
|Allows for clarity in cases like flight reservations, where you have both an airline seller and airline operator<br />
|Full details are documented [https://www.w3.org/wiki/WebSchemas/SellerVendorCleanup#Implementation_Details at W3C] and in [https://github.com/rvguha/schemaorg/issues/88 Github], alongside an [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview document]. <br />
|-<br />
|[[WebSchemas/Periodicals,_Articles_and_Multi-volume_Works|Periodicals, Articles and Multi-volume Works]]<br />
| style="background-color:#98FB98;"|[http://schema.org/docs/releases.html#v1.9 Published]<br />
|Three new Types: Periodical, PublicationVolume, PublicationIssue, and added properties for two existent Types: Article, CreativeWork<br />
|See [http://lists.w3.org/Archives/Public/public-vocabs/2014Mar/0013.html discussion] on public-vocabs.<br />
|Introduces changes proposed by the Bib Extend group for describing periodicals, alongside a 'work to work' property, 'workExample' (and an inverse).<br />
|-<br />
|[[WebSchemas/EventSchemaUpdate|Event schema update]]<br />
| style="background-color:#ECC8EC;"|Added 2013 (@@details?)<br />
|Some modifications to [http://schema.org/Event Event] based on deployment experience.<br />
|Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from [http://schema.org/Thing Thing]. <br />
|Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events.<br />
|-<br />
|[[WebSchemas/JobPostingSchema|Job Postings]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/11/schemaorg-support-for-job-postings.html Published]<br />
|A type for Job adverts.<br />
|Adds [http://schema.org/JobPosting JobPosting] class and supporting properties.<br />
|Related discussion on [[CVSchemas|CVs and resumes]]. The occupationalCategory property takes controlled values; more detail and options (e.g. EU ESCO) here would be useful.<br />
|-<br />
|IPTC/rNews integration<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/09/extended-schemaorg-news-support.html Published]<br />
|Integration of the [http://dev.iptc.org/rNews rNews] vocabulary produced by the [http://www.iptc.org/site/Home/Media_Releases/schema.org_adopts_IPTC's_rNews_for_news_markup IPTC]. <br />
|See original [http://dev.iptc.org/rNews-10-Introduction-to-rNews rNews 1.0 intro]; most of these terms are now in schema.org directly.<br />
|See New York Times' [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0040.html implementation announcement] for details and examples. <br />
|-<br />
|[[WebSchemas/Comment]]<br />
| style="background-color:#98FB98;"|Published<br />
|A fix to confusion around UserComments and lack of a Comment entity.<br />
|Add a class Comment under CreativeWork, for comments. UserComments remains a UserInteraction event, and awaits further clarification.<br />
|This addresses a need to have a representation of comments as documents, rather than merely as a user activity.<br />
|-<br />
|[[WebSchemas/SoftwareApplicationSchema|Software Application]]<br />
| style="background-color:#98FB98;"|Published<br />
|A class for Software Applications ('webapps', both installable and Web-based).<br />
|Re-uses some properties of CreativeWork; defines a subclass SoftwareApplication with 20 properties, plus two small subclasses.<br />
|This was been accepted and was sent for implementation (2012-04-15). Note that the SoftwareApplicationType enumeration may remain a Snippets-only vocabulary.<br />
|-<br />
|[[WebSchemas/Singularity|Singularity]]<br />
| style="background-color:#98FB98;"|Published<br />
|Proposes we move to singular property names, based on implementor feedback.<br />
|Adds new properties without a plural 's', aliases old ones.<br />
|This has been accepted and sent for implementation (2012-04-15)<br />
|-<br />
|[[WebSchemas/ExternalEnumerations|External Enumerations]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2012/05/schemaorg-markup-for-external-lists.html published]<br />
|Guidance on how to cite external enumerations, including constrained values for properties, and large collections of useful types.<br />
|For example, it should be possible to use lists of countries from e.g. ISO, UN. Or units and measures from systems such as [http://www.qudt.org/ QUDT]. Or community or professionally-maintained lists from Wikipedia, Library or GIS standards, etc. <br />
|Blog post covers initial/core design; further work will include lists of known authorities.<br />
|-<br />
|[[WebSchemas/MedicalHealthProposal|Medical/Health]] <br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html published]<br />
|Extended schema.org for describing key topics and their relationships in online health and medical content.<br />
|Adds MedicalEntity hierarchy including types for key medical/health topics (such as conditions, signs and symptoms, disease causes, risk factors, therapies including drugs and procedures, tests, devices, studies and trials, guidelines, diets, supplements, exercise plans, and anatomy) and supporting types. See [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html blog post] and [http://schema.org/docs/meddocs.html overview document] for details.<br />
|Published as v0.95 on 2012-06-26.<br />
|-<br />
|[[WebSchemas/additionalTypeProposal|additionalType]] <br />
| style="background-color:#98FB98;"| [http://www.w3.org/wiki/WebSchemas/additionalTypeProposal published]<br />
|Provides utility property for describing additional types.<br />
|Added 'additionalType' to [http://schema.org/Thing Thing], with detailed description discouraging use outside of Microdata syntax, since RDFa has 'typeof' built-in.<br />
|Published as v0.96 on 2012-07-17.<br />
|-<br />
|[[WebSchemas/GoodRelations|Good Relations integration]]<br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/11/good-relations-and-schemaorg.html published]<br />
| The schema.org team and Martin Hepp collaborated to integrate of a version of GR into schema.org. <br />
|See [http://www.heppnetz.de/projects/goodrelations/ Good Relations] site for background, e.g. [http://wiki.goodrelations-vocabulary.org/Quickstart quickstart] page.<br />
|Schema.org already had [http://schema.org/Offer Offer] and related terms, but benefitted from adding detail from Good Relations. Controlled values are still at purl.org GR URLs, and Good Relations continues as an independent project.<br />
|-<br />
|-<br />
|[[WebSchemas/LearningResources|Learning Resources]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013.<br />
|The Learning Resources Metadata Initiative defines a set of terms to improve schema.org's use with educational materials. <br />
|Mainly adds new properties (typically but not necc. on [http://schema.org/CreativeWork CreativeWork]): [http://wiki.creativecommons.org/LRMI/Properties/intendedEndUserRole intendedEndUserRole], [http://wiki.creativecommons.org/LRMI/Properties/educationalAlignment educationalAlignment], with values in a new class, [http://wiki.creativecommons.org/LRMI/Properties/1.0/AlignmentObject AlignmentObject]; [http://wiki.creativecommons.org/LRMI/Properties/educationalUse educationalUse] ([http://schema.org/Text Text] values), [http://wiki.creativecommons.org/LRMI/Properties/timeRequired timeRequired] (a [http://schema.org/Duration Duration]); [http://wiki.creativecommons.org/LRMI/Properties/typicalAgeRange typicalAgeRange] (Text valued); [http://wiki.creativecommons.org/LRMI/Properties/interactivityType interactivityType] (Text); [http://wiki.creativecommons.org/LRMI/Properties/learningResourceType learningResourceType], ...<br />
|Comments. see [http://wiki.creativecommons.org/LRMI/Properties/1.0 version 1.0] and [http://groups.google.com/group/lrmi discussion list]. <br />
|-<br />
|[[WebSchemas/Datasets|Datasets]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013 based on [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/dataset.html dataset.html]<br />
|A proposal extending schema.org for describing datasets and data catalogs. This may be revised to track evolution of W3C DCAT.<br />
|Adds the [http://logd.tw.rpi.edu/node/11401 Dataset], [http://logd.tw.rpi.edu/datacatalog DataCatalog], and [http://logd.tw.rpi.edu/datadownload DataDownload] types and supporting properties.<br />
|An example page with dataset microdata is available [http://logd.tw.rpi.edu/schemaorg_dataset_extension here]. For related efforts, see the [http://www.w3.org/2011/gld/wiki/Main_Page W3C Government Linked Data Working Group].<br />
|-<br />
|[[WebSchemas/TechArticleSchema|Tech Article]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html schema: techpub.html]<br />
|A proposal extending schema.org for describing technical content.<br />
|Adds dependencies, task, and technicalAudience. Adds descriptions for genre (CreativeWork) and about (CreativeWork).<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/APIReferenceSchema|API Reference]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing Application Programming Interface (API) reference content.<br />
|Derived from TechArticle; adds assembly, assemblyVersion, programmingModel, targetPlatform<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/CodeSchema|Code]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing human readable source code.<br />
|Adds codeRepository, codeSample, programmingLanguage, runtime, targetProduct.<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/Audience|Audience]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html drafted]<br />
|A proposal extending schema.org for describing audiences, building around http://schema.org/Audience type, also used by (and coordinated with) LRMI and MedicalHealth vocabulary.<br />
|Add property audience to type CreativeWork (done) and Product. Also ParentAudience, ... see [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html draft] for details.<br />
|This was added in stages; Medical/Health introduced the basic type 'Audience' first.<br />
|-<br />
|[[WebSchemas/CitationPromotion|Citation Promotion]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|To promote the 'citation' property currently on [http://schema.org/MedicalScholarlyArticle MedicalScholarlyArticle] up to [http://schema.org/CreativeWork CreativeWork].<br />
|Moved citation up to CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/sameAs|sameAs]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|Property to indicate that a single identity is being described.<br />
|Broadly same meaning as owl:sameAs.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions | Actions in Schema.org (part 1)]] <br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Aug/0008.html 1.0c, 7 August 2013].<br />
|Added a basic Action type to schema.org, as a foundation for further extension. See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|<br />
|<br />
|-<br />
|[[WebSchemas/TVRadioSchema|TV and Radio proposal]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Proposes modest changes and additions to support TV and radio (from [http://www.ebu.ch/ EBU] and [http://www.bbc.co.uk/ BBC]). <br />
|Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc.<br />
|See also [[SchemaDotOrgTV|background notes]] and [[http://www.w3.org/wiki/TVRadioSchema]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see [http://schema.org/VideoObject VideoObject], [http://schema.org/AudioObject AudioObject]; [http://schema.org/Movie Movie]. [http://schema.org/Event Event] re scheduling. See also [http://schema.org/UserPlays UserPlays], a kind of [http://schema.org/UserInteraction UserInteraction]. Comics and TV/Radio also share a concern for describing fictional characters and [http://pinboard.in/u:danbri/t:narrative/ narratives]. <br />
|-<br />
|[[WebSchemas/CivicServices|Civic Services]] <br />
| style="background-color:#98FB98;"| Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013].<br />
|Describing public civic services <br />
|A proposal extending schema.org to cover various kinds of civic services.<br />
|GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties<br />
|-<br />
|[[WebSchemas/LocalBusinessDepartment|Add Organization department property]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Added properties [http://schema.org/department department] and [http://schema.org/subOrganization subOrganizationOf] to [http://schema.org/Organization Organization], to allow local businesses to describe their depts (e.g. opening hours) in detail. <br />
|department and subOrganization properties (range and domain both Organization)<br />
|Proposal greatly simplified after WebSchemas discussion.<br />
|-<br />
|[[WebSchemas/OrdersSchema|Orders in Schema.org]] <br />
| style="background-color:#98FB98;"|Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Dec/0025.html 1.0e, 4 December 2013]<br />
|"While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)".<br />
|Adds classes OrderStatus, Order, DeliveryMethod plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/Accessibility|Accessibility]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Nov/0190.html 1.0e, 4 December 2013].<br />
|A proposal for adding accessibility metadata to all Creative Work content, done in concert with LRMI<br />
|Added four properties to CreativeWork to enable better discovery of accessible content.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions|Actions in Schema.org (part 2)]] <br />
|Added 2014<br />
|Add handlers and potential actions to Action type.<br />
|See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|-<br />
|[[WebSchemas/ReservationsSchema|Reservations in Schema.org]] <br />
|Added 2014<br />
|This proposal includes new types for describing reservations and tickets<br />
|Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/EmailMessageSchema|EmailMessage type]] <br />
|Added 2014<br />
|This proposal adds a single new type, EmailMessage<br />
|EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages.<br />
|No properties currently defined; proposals welcomed.<br />
|}<br />
<br />
<br/><br />
<br /><br />
<br /><br />
<br />
== Wiki markup ==<br />
<br />
* We have two templates for use here: [[Template:SchemaDotOrgProposal]] which takes 'name' and 'status' parameters, and which returns a one line page header for proposals; also [[Template:SchemaDotOrgTerm]], which takes a 'term' parameter and returns a simple hyperlink to that (class) term on schema.org.<br />
<br />
Nearby: <br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/drafts/alpha mercurial filetree]<br />
* [http://www.mediawiki.org/wiki/Help:Tables Help with wiki table syntax]<br />
<br />
[[Category:WebSchemas]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposals&diff=80608WebSchemas/SchemaDotOrgProposals2015-01-21T12:45:01Z<p>Danbri: updating to indicate more work happening on githu</p>
<hr />
<div>== Proposals for Schema.org ==<br />
<br />
* Since 2014 schema.org uses [https://github.com/schemaorg/schemaorg/issues Github] for active development, although email discussion remains in the WebSchemas public-vocabs list.<br />
* History: 2012-13 draft [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext schema files] were hosted in W3C's Mercurial repository.<br />
* From 2014, schema.org runs on [https://github.com/rvguha/schemaorg opensource software], and uses Git(hub) for schema collaboration. Examples and schemas are in the [https://github.com/rvguha/schemaorg/tree/master/data data/] area of the repository.<br />
<br />
From 2011-2014 this page collected public proposals for [http://schema.org/docs/full.html schema.org vocabulary] extensions and improvements. <br />
<br />
We are winding down the [http://www.w3.org/2011/webschema/track/ W3C's issue tracker] for schema.org issues, except for matters of coordination with other vocabularies and W3C specifications.<br />
<br />
Schema.org public discussions happen via the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs]@w3.org W3C mailing list for discussions. <br />
<br />
Sometimes proposals evolve from offlist and face-to-face discussions; when possible, advance warning of 'expected' or possible proposals can be indicated here ([http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0102.html announced 24 Feb 2012]).<br />
<br />
Schema.org proposals can take any form during discussions, but ultimately they should take the form of HTML+RDFa schema definitions; some real examples are in the [https://github.com/rvguha/schemaorg/tree/master/data data/ area] of the schema.org repository. See Github pages for more details.<br />
<br />
'''Note''': When preparing a proposal, we need to know for each type and property, its name and description, alongside examples of usage. There are lots of different ways in which these can be prepared: wiki pages, text files, spreadsheets, PDFs etc. Do note that each property is considered as a global entity, ie. a property called 'foo' gets just one description - you can't give different descriptions for its use with the "Person" type, versus its use with the CreativeWork type. Ideally, develop a machine-readable proposal and test it using the software on Github.<br />
<br />
To search just these proposals, the issue tracker and schema.org-related mailing lists, try a [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek this custom search].<br />
<br />
<br />
== Proposals and Discussion ==<br />
<br />
These proposals are working towards inclusion in schema.org.<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/Measurement|Measurement]]<br />
|Proposal<br />
|Introduce the concept of a Measurement to describe the relationship between a value and a thing, as in sports statistics.<br />
|See wiki page<br />
|<br />
|-<br />
|[[WebSchemas/associatedMediaToThing|Change domain of associatedMedia to Thing]]<br />
|Proposal<br />
|Change the domain of http://schema.org/associatedMedia to http://schema.org/Thing<br />
|Enables many more types to associate contained or complementary media content, beyond CreativeWork.<br />
|Discussion at http://lists.w3.org/Archives/Public/public-vocabs/2014May/0224.html<br />
|-<br />
|[[WebSchemas/PropertyValuePairs|Property-Value Pairs]]<br />
|Proposal<br />
|Adding support for arbitrary property-value pairs. Useful for product features and proprietary features of places.<br />
|One new type http://schema.org/PropertyValue, two new properties for this type (unitText, propertyID), changes to domain and range for unitCode, value, minValue, maxValue, and valueReference properties; one new property additionalProperty for http://schema.org/Place OR http://schema.org/Product.<br />
|Mirrors an upcoming feature in [http://purl.org/goodrelations/ GoodRelations].<br />
|-<br />
|[[WebSchemas/Vehicles|Vehicles: Cars, Bikes, Boats]]<br />
|Proposal<br />
|Adding support for vehicle features for cars, bikes, boats, and other vehicles for sales and rental.<br />
|See proposal for details.<br />
|<br />
|-<br />
|[[WebSchemas/Orders_enhancement|Orders Schema update]]<br />
|Proposal<br />
|Proposal to add order line and parcel delivery support in the Orders Schema.<br />
|One new Type: OrderItem, and added properties for one existent Type: Order<br />
|<br />
|-<br />
|[[WebSchemas/SocialAccountProperty|social Account property]]<br />
|Proposal<br />
|Indicates a corresponding profile page for an account on a socially-oriented Web site.<br />
|One new property: socialAccount<br />
|<br />
|-<br />
|[[WebSchemas/Audiobook|Audiobook]]<br />
|Proposal<br />
|Proposal for new Audiobook Type and abridged property for [http://schema.org/Book Book].<br />
|Audiobook subtype of [http://schema.org/Book Book] ''and'' of [http://schema.org/AudioObject AudioObject], adds readBy property<br />
|<br />
|-<br />
|[[WebSchemas/Collection|Collection]]<br />
|Proposal<br />
|Proposal for new Collection Type and part properties for [http://schema.org/CreativeWork CreativeWork].<br />
|Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/Accessibility/ToDo|Accessibility]] (part 2)<br />
|Discussion<br />
|Extension for describing accessibility properties of a [http://schema.org/CreativeWork CreativeWork].<br />
|Additional work to add accessMode, hasAdapation, isAdaptationof that were not covered in 1.0 Accessibility work.<br />
|<br />
|-<br />
|[[WebSchemas/QuotationSchema|Add Quotation type]]<br />
|Proposal<br />
|Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties.<br />
|Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee.<br />
|Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise.<br />
|-<br />
|[[WebSchemas/WorkersUnionSchema|Workers Union type]] <br />
|Accepted<br />
|This proposal adds a single new type, WorkersUnion, addressing [http://www.w3.org/2011/webschema/track/issues/17 issue 17] in the WebSchemas tracker. <br />
|"A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying.""<br />
|One type, see [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/workersunion.html draft schema].<br />
|-<br />
|[[WebSchemas/Sports|Sports]]<br />
|Proposal<br />
|The purpose of this proposal is to introduce an expanded vocabulary for describing sports information within schema.org. Key concepts include Statistics, Roles, Ordered Events, Competitions and Competition Results.<br />
|See proposal for full set of vocabulary updates.<br />
|V3 posted 2014.05.09<br />
|-<br />
|[[WebSchemas/PeriodicalsComics|Comics and Serials]]<br />
| style="background-color:#ECC8EC;"|Discussing Proposals <br />
|Proposal from Marvel (see [[PeriodicalsComics#Code_Examples|examples]]).<br />
|Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. <br />
|Generally well received and specified, but some detailed [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0073.html discussion] re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with [http://schema.org/Book Book]/numberOfPages, or [http://schema.org/ScholarlyArticle ScholarlyArticle]? Should PeriodicalSeries be intangible?<br />
|-<br />
|[[WebSchemas/HistoricalDataSchema|Historical Data proposal]]<br />
|Proposal<br />
|The [http://historical-data.org/ historical-data.org] site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios.<br />
|Adds HistoricalRecord, HistoricalEvent (subclass of Event), ''overrides'' attendees, subEvents, superEvent to point to HistoricalEvent.<br />
|There is an associated implementation, [https://github.com/historical-data/ github repository], and [http://historical-data-schema.blogspot.com/ blog].<br />
|-<br />
|[[WebSchemas/BioDatabases|Biological Databases]]<br />
|Proposal<br />
|A schema extension for describing biological databases, [http://sagace.nibio.go.jp/schema/en/schema.html Sagace]. <br />
|Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. <br />
|Others have also mentioned interest in adding some notion of species.<br />
|-<br />
|[[WebSchemas/Breadcrumbs|Breadcrumbs]]<br />
|Proposal<br />
|A proposal resolving current problems handling breadcrumbs.<br />
|Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See [http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Nov/0026.html discussion] on using literal values.<br />
|<br />
|-<br />
|[[WebSchemas/DiscussionSchema|Discussion]] <br />
|Proposal<br />
|A proposal extending schema.org for describing online discussion forums and message boards.<br />
|Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful.<br />
|Addition candidate<br />
|-<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html Innovation] <br />
|Proposal<br />
|A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html]<br />
|Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [http://purl.org/innovation/ns] for complete list of terms.<br />
|Addition candidate<br />
|-<br />
|[[WebSchemas/dissolutionDate|dissolutionDate]]<br />
|Proposal<br />
|Add a dissolutionDate property to Organization.<br />
|<br />
|<br />
|-<br />
|[http://thematix.com/ontologies/travel/lodging/ Lodging Extensions]<br />
|Proposal<br />
|A proposal for extending LodgingBusiness. Specification is here http://thematix.com/ontologies/travel/lodging/<br />
|Adds Amenity, BusinessService, Feature, GuestRoomAmenity, LodgingBusinessAmenity, LodgingBusinessService, RentalOffer, RentalRate, Room, RoomType and Service.<br />
|In addition to the examples given in the cited website, examples can be seen at http://www.regencyhotelmiami.com/ and http://hiltonvb.com and at Super8 hotel description pages, e.g., http://www.super8.com/hotels/alberta/fort-mcmurray/super-8-fort-mcmurray/hotel-overview. <br />
|-<br />
|-<br />
|[[WebSchemas/WebObsSchema|Web Observatory]] <br />
|Proposal<br />
|Proposed extensions to schema.org for describing portals used for [[http://www.webscience.org/|Web Science]] collaboration including projects, datasets and tools used to study the Web.<br />
|Includes vocabularies for [[http://logd.tw.rpi.edu/web_observatory|Web Observatory]], [[http://logd.tw.rpi.edu/web_observatory_project|Web Observatory Project]], [[http://logd.tw.rpi.edu/web_observatory_dataset|Web Observatory Dataset]], and [[http://logd.tw.rpi.edu/web_observatory_tool|Web Observatory Tool]]<br />
|A reference implementation of a web observatory portal demonstrating the user of each Web Observatory vocabulary can be found at the [[http://tw.rpi.edu/web/web_observatory|Tetherless World Constellation Web Observatory Portal]]<br />
|-<br />
|...<br />
|<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|-<br />
|}<br />
<br />
== Brainstorming, Use Cases and Advance Notice ==<br />
<br />
The following topics are under discussion in the Web Schemas Schema.org community, but are not yet approaching specific proposed designs or broad consensus on an approach. Note that this distinction is pretty fuzzy, but some partitioning was needed here due to the number of proposals we're seeing. There is no shame in being listed here rather than as a proposal above!<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/PressReview|Ranking]]<br />
|Proposal<br />
|Proposal to add a list of items as a ranking (Top 10, Best sellers etc.)<br />
|One new type http://schema.org/ItemList/Ranking. Probably we need to specify the type, the name and the order (ascendant, descendant).<br />
|Often used in magazines.<br />
|-<br />
|[[WebSchemas/PressReview|PressReview]]<br />
|Proposal<br />
|Proposal to add a list of articles, events etc. as a Press review or Press digest<br />
|One new type http://schema.org/ItemList/PressReview<br />
|Often used in organization websites<br />
|-<br />
|[[WebSchemas/ScholarlyArticle|ScholarlyArticle]]<br />
|Early proposal from HighWire Press needs review.<br />
|Various ideas around improving [http://schema.org/ScholarlyArticle ScholarlyArticle]. <br />
|Suggestion that scholarly articles could be described in more detail.<br />
|There is a lot of related work in this area. For example [http://scholar.google.ca/intl/en/scholar/publishers.html Google Scholar publisher guidelines]; [http://academic.research.microsoft.com/ Microsoft Academic Search]. The [http://www.openarchives.org/OAI/openarchivesprotocol.html Open Archives Initiative - Protocol for Metadata Harvesting] also addresses this problem area and has broad adoption. See also earlier comments from [https://groups.google.com/forum/?fromgroups#!searchin/schemaorg-discussion/ScholarlyArticle/schemaorg-discussion/aEO56kVQoqQ/x-tGuaITitoJ HighWire Press] ([http://dl.dropbox.com/u/105439/ScholarlyArticle/ScholarlyArticle%20-%20schema.org.draft1.pdf pdf]) and following discussion (on the old mailing list).<br />
|-<br />
|[[WebSchemas/RealEstate|Real Estate]]<br />
|Discussions but no proposal yet.<br />
|Enthusiastic discussion in favour of adding RealEstate support. Tracked as [https://www.w3.org/2011/webschema/track/issues/13 issue 13]. This should likely follow along after the Good Relations work.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary, and schema.org's numerous subclasses, and [http://schema.org/Offer Offer] class.<br />
|-<br />
|Transport Data<br />
|Discussion<br />
|Initial discussion on description of transport data.<br />
|N/A<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0019.html Discussions] on whether this scenario can be covered with existing vocabulary.<br />
|-<br />
|[[WebSchemas/ActivitySchema|Activities (things you can do)]] <br />
|Proposal<br />
|Vocabulary for describing general activities not bound to any specific time or place. <br />
Unrelated to the [[WebSchemas/ActivityActions|Activities and Actions]] proposal for online user page interations that are listed above.<br />
|Examples: 'Paragliding'. 'Going to the cinema', etc. <br />
|Public draft and description available on [[WebSchemas/ActivitySchema|wiki]]. [http://lists.w3.org/Archives/Public/public-vocabs/2011Oct/0169.html Original proposal on public vocabs mailinglist].<br />
|-<br />
|[[WebSchemas/PersonBio|Person biography]]<br />
|Proposal<br />
|A proposal for supporting people's biography<br />
|Add a bibliography property to the Person type.<br />
|<br />
|-<br />
|Project<br />
|Proposal<br />
|Vocabulary for describing ''any'' kind of project<br />
|Terms (loosely) based on [http://purl.org/stuff/project this project vocabulary]<br />
|Use case gathering - [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0108.html see mailing list thread]<br />
|-<br />
|[[WebSchemas/VacationRentals|Vacation Rental Schema]]<br />
|Proposal<br />
|Creating an additional vocabulary for this hotel-alternative accommodation<br />
|Overview of new terms<br />
|Just initiated the discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/FictionalThing|Fictional Thing]]<br />
|Proposal<br />
|Providing the ability to identify a thing as being fictional<br />
|Proposal for the creation of a FictionalThing type<br />
|Supporting discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/JobMarket|JobMarket]]<br />
|Proposal<br />
|Extension for modelling job markets<br />
|Classes added: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_QuantitativeValue_.3E_Compensation Compensation], [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_StructuredValue_.3E_WorkExperience WorkExperience] + class amended: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_JobPosting JobPosting]<br />
|Draft for an extension published to elicit feedback<br />
|-<br />
|[[WebSchemas/VisualArtwork|VisualArtwork]]<br />
|Early Proposal<br />
|Extension for CreativeWork and replacement/alternative to Painting and Sculpture<br />
|Overview of Extension and new properties<br />
|Early draft for an extension published to elicit feedback.<br />
|-<br />
|[[WebSchemas/GeoJSON|GeoJSON]]<br />
|Early propsal<br />
|addition to the Geo* family of topics.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary<br />
|-<br />
|[[WebSchemas/LookInside|Looking Inside Tables]]<br />
|Early proposal<br />
|A mechanism to map the contents of tables into entities.<br />
|N/A<br />
|Draft for an extension published to elicit feedback.<br />
|-<br />
|-<br />
|[[WebSchemas/OnlinePresence|Online Presence]]<br />
|Early proposal<br />
|expressing Online Presence and current Actions<br />
|WIP<br />
|Related to [http://schema.org/Action Action] subtree and [http://online-presence.net Online Presence Ontology].<br />
|-<br />
|[[WebSchemas/SocialAccount|SocialAccount]]<br />
|Proposal<br />
| Introduce a type and a property to describe social accounts of http://schema.org/Person or http://schema.org/Organization<br />
|Add [[WebSchemas/SocialAccount| SocialAccount]] type derived from http://schema.org/Thing to capture social account. Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount| socialAccount]] expecting the type [[WebSchemas/SocialAccount| SocialAccount]]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion]<br />
|-<br />
|[[WebSchemas/socialAccount2|socialAccount]]<br />
|Proposal<br />
| Introduce a property to describe social accounts of http://schema.org/Person and http://schema.org/Organization<br />
| Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount2| socialAccount]] expecting a URL as value<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion] '''This is an alternative of the previous item'''<br />
|-<br />
|[[WebSchemas/Course|Course]]<br />
|Proposal<br />
| Introduce Course type to describe course as well as online courses (e.g. MOOCs)<br />
|Extend http://schema.org/CreativeWork to describe Course type. Proposed vocabularies are available on https://sites.google.com/site/moocontology/home]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2014Oct/0052.html discussion]<br />
|-<br />
|[[WebSchemas/VLEs|VLEs: Course, Session, Assessment]]<br />
|Proposal<br />
| Introduce additional concepts to describe Virtual Learning Environments' (VLEs) content and online courses (e.g. MOOCs)<br />
|<br />
* Extend http://schema.org/CreativeWork to describe the proposed type "Course". <br />
* Extend http://schema.org/InteractAction to describe the proposed type "Session". <br />
* Extend http://schema.org/ReviewAction to describe the proposed Assessment specific types (Assignment, Examination, Test). <br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2014Nov/0008.html discussion]<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|}<br />
<br />
== Already Accepted and Added ==<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0" <br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/providerSellerReDesign|Re-Design Provider / Seller vocabulary]]<br />
| style="background-color:#98FB98;"|[http://schema.org/docs/releases.html#v1.9 Published]<br />
|Address the issues / confusion in the relationship between provider and seller<br />
|Allows for clarity in cases like flight reservations, where you have both an airline seller and airline operator<br />
|Full details are documented [https://www.w3.org/wiki/WebSchemas/SellerVendorCleanup#Implementation_Details at W3C] and in [https://github.com/rvguha/schemaorg/issues/88 Github], alongside an [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview document]. <br />
|-<br />
|[[WebSchemas/Periodicals,_Articles_and_Multi-volume_Works|Periodicals, Articles and Multi-volume Works]]<br />
| style="background-color:#98FB98;"|[http://schema.org/docs/releases.html#v1.9 Published]<br />
|Three new Types: Periodical, PublicationVolume, PublicationIssue, and added properties for two existent Types: Article, CreativeWork<br />
|See [http://lists.w3.org/Archives/Public/public-vocabs/2014Mar/0013.html discussion] on public-vocabs.<br />
|Introduces changes proposed by the Bib Extend group for describing periodicals, alongside a 'work to work' property, 'workExample' (and an inverse).<br />
|-<br />
|[[WebSchemas/EventSchemaUpdate|Event schema update]]<br />
| style="background-color:#ECC8EC;"|Added 2013 (@@details?)<br />
|Some modifications to [http://schema.org/Event Event] based on deployment experience.<br />
|Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from [http://schema.org/Thing Thing]. <br />
|Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events.<br />
|-<br />
|[[WebSchemas/JobPostingSchema|Job Postings]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/11/schemaorg-support-for-job-postings.html Published]<br />
|A type for Job adverts.<br />
|Adds [http://schema.org/JobPosting JobPosting] class and supporting properties.<br />
|Related discussion on [[CVSchemas|CVs and resumes]]. The occupationalCategory property takes controlled values; more detail and options (e.g. EU ESCO) here would be useful.<br />
|-<br />
|IPTC/rNews integration<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/09/extended-schemaorg-news-support.html Published]<br />
|Integration of the [http://dev.iptc.org/rNews rNews] vocabulary produced by the [http://www.iptc.org/site/Home/Media_Releases/schema.org_adopts_IPTC's_rNews_for_news_markup IPTC]. <br />
|See original [http://dev.iptc.org/rNews-10-Introduction-to-rNews rNews 1.0 intro]; most of these terms are now in schema.org directly.<br />
|See New York Times' [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0040.html implementation announcement] for details and examples. <br />
|-<br />
|[[WebSchemas/Comment]]<br />
| style="background-color:#98FB98;"|Published<br />
|A fix to confusion around UserComments and lack of a Comment entity.<br />
|Add a class Comment under CreativeWork, for comments. UserComments remains a UserInteraction event, and awaits further clarification.<br />
|This addresses a need to have a representation of comments as documents, rather than merely as a user activity.<br />
|-<br />
|[[WebSchemas/SoftwareApplicationSchema|Software Application]]<br />
| style="background-color:#98FB98;"|Published<br />
|A class for Software Applications ('webapps', both installable and Web-based).<br />
|Re-uses some properties of CreativeWork; defines a subclass SoftwareApplication with 20 properties, plus two small subclasses.<br />
|This was been accepted and was sent for implementation (2012-04-15). Note that the SoftwareApplicationType enumeration may remain a Snippets-only vocabulary.<br />
|-<br />
|[[WebSchemas/Singularity|Singularity]]<br />
| style="background-color:#98FB98;"|Published<br />
|Proposes we move to singular property names, based on implementor feedback.<br />
|Adds new properties without a plural 's', aliases old ones.<br />
|This has been accepted and sent for implementation (2012-04-15)<br />
|-<br />
|[[WebSchemas/ExternalEnumerations|External Enumerations]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2012/05/schemaorg-markup-for-external-lists.html published]<br />
|Guidance on how to cite external enumerations, including constrained values for properties, and large collections of useful types.<br />
|For example, it should be possible to use lists of countries from e.g. ISO, UN. Or units and measures from systems such as [http://www.qudt.org/ QUDT]. Or community or professionally-maintained lists from Wikipedia, Library or GIS standards, etc. <br />
|Blog post covers initial/core design; further work will include lists of known authorities.<br />
|-<br />
|[[WebSchemas/MedicalHealthProposal|Medical/Health]] <br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html published]<br />
|Extended schema.org for describing key topics and their relationships in online health and medical content.<br />
|Adds MedicalEntity hierarchy including types for key medical/health topics (such as conditions, signs and symptoms, disease causes, risk factors, therapies including drugs and procedures, tests, devices, studies and trials, guidelines, diets, supplements, exercise plans, and anatomy) and supporting types. See [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html blog post] and [http://schema.org/docs/meddocs.html overview document] for details.<br />
|Published as v0.95 on 2012-06-26.<br />
|-<br />
|[[WebSchemas/additionalTypeProposal|additionalType]] <br />
| style="background-color:#98FB98;"| [http://www.w3.org/wiki/WebSchemas/additionalTypeProposal published]<br />
|Provides utility property for describing additional types.<br />
|Added 'additionalType' to [http://schema.org/Thing Thing], with detailed description discouraging use outside of Microdata syntax, since RDFa has 'typeof' built-in.<br />
|Published as v0.96 on 2012-07-17.<br />
|-<br />
|[[WebSchemas/GoodRelations|Good Relations integration]]<br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/11/good-relations-and-schemaorg.html published]<br />
| The schema.org team and Martin Hepp collaborated to integrate of a version of GR into schema.org. <br />
|See [http://www.heppnetz.de/projects/goodrelations/ Good Relations] site for background, e.g. [http://wiki.goodrelations-vocabulary.org/Quickstart quickstart] page.<br />
|Schema.org already had [http://schema.org/Offer Offer] and related terms, but benefitted from adding detail from Good Relations. Controlled values are still at purl.org GR URLs, and Good Relations continues as an independent project.<br />
|-<br />
|-<br />
|[[WebSchemas/LearningResources|Learning Resources]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013.<br />
|The Learning Resources Metadata Initiative defines a set of terms to improve schema.org's use with educational materials. <br />
|Mainly adds new properties (typically but not necc. on [http://schema.org/CreativeWork CreativeWork]): [http://wiki.creativecommons.org/LRMI/Properties/intendedEndUserRole intendedEndUserRole], [http://wiki.creativecommons.org/LRMI/Properties/educationalAlignment educationalAlignment], with values in a new class, [http://wiki.creativecommons.org/LRMI/Properties/1.0/AlignmentObject AlignmentObject]; [http://wiki.creativecommons.org/LRMI/Properties/educationalUse educationalUse] ([http://schema.org/Text Text] values), [http://wiki.creativecommons.org/LRMI/Properties/timeRequired timeRequired] (a [http://schema.org/Duration Duration]); [http://wiki.creativecommons.org/LRMI/Properties/typicalAgeRange typicalAgeRange] (Text valued); [http://wiki.creativecommons.org/LRMI/Properties/interactivityType interactivityType] (Text); [http://wiki.creativecommons.org/LRMI/Properties/learningResourceType learningResourceType], ...<br />
|Comments. see [http://wiki.creativecommons.org/LRMI/Properties/1.0 version 1.0] and [http://groups.google.com/group/lrmi discussion list]. <br />
|-<br />
|[[WebSchemas/Datasets|Datasets]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013 based on [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/dataset.html dataset.html]<br />
|A proposal extending schema.org for describing datasets and data catalogs. This may be revised to track evolution of W3C DCAT.<br />
|Adds the [http://logd.tw.rpi.edu/node/11401 Dataset], [http://logd.tw.rpi.edu/datacatalog DataCatalog], and [http://logd.tw.rpi.edu/datadownload DataDownload] types and supporting properties.<br />
|An example page with dataset microdata is available [http://logd.tw.rpi.edu/schemaorg_dataset_extension here]. For related efforts, see the [http://www.w3.org/2011/gld/wiki/Main_Page W3C Government Linked Data Working Group].<br />
|-<br />
|[[WebSchemas/TechArticleSchema|Tech Article]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html schema: techpub.html]<br />
|A proposal extending schema.org for describing technical content.<br />
|Adds dependencies, task, and technicalAudience. Adds descriptions for genre (CreativeWork) and about (CreativeWork).<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/APIReferenceSchema|API Reference]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing Application Programming Interface (API) reference content.<br />
|Derived from TechArticle; adds assembly, assemblyVersion, programmingModel, targetPlatform<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/CodeSchema|Code]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing human readable source code.<br />
|Adds codeRepository, codeSample, programmingLanguage, runtime, targetProduct.<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/Audience|Audience]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html drafted]<br />
|A proposal extending schema.org for describing audiences, building around http://schema.org/Audience type, also used by (and coordinated with) LRMI and MedicalHealth vocabulary.<br />
|Add property audience to type CreativeWork (done) and Product. Also ParentAudience, ... see [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html draft] for details.<br />
|This was added in stages; Medical/Health introduced the basic type 'Audience' first.<br />
|-<br />
|[[WebSchemas/CitationPromotion|Citation Promotion]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|To promote the 'citation' property currently on [http://schema.org/MedicalScholarlyArticle MedicalScholarlyArticle] up to [http://schema.org/CreativeWork CreativeWork].<br />
|Moved citation up to CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/sameAs|sameAs]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|Property to indicate that a single identity is being described.<br />
|Broadly same meaning as owl:sameAs.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions | Actions in Schema.org (part 1)]] <br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Aug/0008.html 1.0c, 7 August 2013].<br />
|Added a basic Action type to schema.org, as a foundation for further extension. See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|<br />
|<br />
|-<br />
|[[WebSchemas/TVRadioSchema|TV and Radio proposal]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Proposes modest changes and additions to support TV and radio (from [http://www.ebu.ch/ EBU] and [http://www.bbc.co.uk/ BBC]). <br />
|Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc.<br />
|See also [[SchemaDotOrgTV|background notes]] and [[http://www.w3.org/wiki/TVRadioSchema]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see [http://schema.org/VideoObject VideoObject], [http://schema.org/AudioObject AudioObject]; [http://schema.org/Movie Movie]. [http://schema.org/Event Event] re scheduling. See also [http://schema.org/UserPlays UserPlays], a kind of [http://schema.org/UserInteraction UserInteraction]. Comics and TV/Radio also share a concern for describing fictional characters and [http://pinboard.in/u:danbri/t:narrative/ narratives]. <br />
|-<br />
|[[WebSchemas/CivicServices|Civic Services]] <br />
| style="background-color:#98FB98;"| Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013].<br />
|Describing public civic services <br />
|A proposal extending schema.org to cover various kinds of civic services.<br />
|GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties<br />
|-<br />
|[[WebSchemas/LocalBusinessDepartment|Add Organization department property]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Added properties [http://schema.org/department department] and [http://schema.org/subOrganization subOrganizationOf] to [http://schema.org/Organization Organization], to allow local businesses to describe their depts (e.g. opening hours) in detail. <br />
|department and subOrganization properties (range and domain both Organization)<br />
|Proposal greatly simplified after WebSchemas discussion.<br />
|-<br />
|[[WebSchemas/OrdersSchema|Orders in Schema.org]] <br />
| style="background-color:#98FB98;"|Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Dec/0025.html 1.0e, 4 December 2013]<br />
|"While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)".<br />
|Adds classes OrderStatus, Order, DeliveryMethod plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/Accessibility|Accessibility]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Nov/0190.html 1.0e, 4 December 2013].<br />
|A proposal for adding accessibility metadata to all Creative Work content, done in concert with LRMI<br />
|Added four properties to CreativeWork to enable better discovery of accessible content.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions|Actions in Schema.org (part 2)]] <br />
|Added 2014<br />
|Add handlers and potential actions to Action type.<br />
|See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|-<br />
|[[WebSchemas/ReservationsSchema|Reservations in Schema.org]] <br />
|Added 2014<br />
|This proposal includes new types for describing reservations and tickets<br />
|Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/EmailMessageSchema|EmailMessage type]] <br />
|Added 2014<br />
|This proposal adds a single new type, EmailMessage<br />
|EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages.<br />
|No properties currently defined; proposals welcomed.<br />
|}<br />
<br />
<br/><br />
<br /><br />
<br /><br />
<br />
== Wiki markup ==<br />
<br />
* We have two templates for use here: [[Template:SchemaDotOrgProposal]] which takes 'name' and 'status' parameters, and which returns a one line page header for proposals; also [[Template:SchemaDotOrgTerm]], which takes a 'term' parameter and returns a simple hyperlink to that (class) term on schema.org.<br />
<br />
Nearby: <br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/drafts/alpha mercurial filetree]<br />
* [http://www.mediawiki.org/wiki/Help:Tables Help with wiki table syntax]<br />
<br />
[[Category:WebSchemas]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=Template:SchemaDotOrgProposal&diff=80607Template:SchemaDotOrgProposal2015-01-21T12:42:43Z<p>Danbri: linking all headers to github site</p>
<hr />
<div><br />
<!-- please don't edit the template at Template:SchemaDotOrgProposal --><br />
<br />
<div style="background-color: #FADADD; color: #000; padding: 3px;">''This is an archived [[WebSchemas]] proposal {{{name}}} for [http://schema.org/ schema.org]. See [[WebSchemas/SchemaDotOrgProposals|Proposals listing]] for more. '''Note: active [http://schema.org/ schema.org] development is now based at [https://github.com/schemaorg/schemaorg/issues github]'''<br />
<br />
''</div><br />
[[Category:WebSchemas]]<br />
[[Category:WebSchemaProposals]]<br />
<br />
<br />
<br/></div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/Vehicles&diff=79372WebSchemas/Vehicles2014-11-20T13:24:13Z<p>Danbri: linked Russian example</p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=for Vehicles (Cars, Bikes, Boats, etc.) Sales and Rental in Schema.org|status=Proposal}}<br />
== Proposal for Vehicles - Cars, Bikes, Boats - Rental and Sales ==<br />
Authors: <br />
*[http://www.heppnetz.de Martin Hepp], mheppATcomputerDOTorg<br />
*[http://makolab.com Karol Szczepański] karolDOTszczepanskiATmakolabDOTpl<br />
*[http://makolab.com Mirek Sopek] sopekATmakolabDOTcom<br />
<br />
This proposal defines a small set of additional types and properties for schema.org that will cover typical scenarios related to the sales and rental of vehicles of typical kinds, like new and used cars, bikes, and boats, and related services.<br />
<br />
It is a first contribution of the [http://www.automotive-ontology.org/ Automotive Ontology Working Group].<br />
<br />
== Overview == <br />
This proposal builds on the following vehicle-related extensions for [http://purl.org/goodrelations/ GoodRelations], the e-commerce model of schema.org:<br />
<br />
*'''Vehicle Sales Ontology (VSO),''' http://purl.org/vso/ns<br />
*'''Volkswagen Vehicles Ontology (VVO),''' http://purl.org/vvo/ns<br />
*'''Used Cars Ontology (UCO),''' http://purl.org/uco/ns<br />
<br />
It adds the core classes, properties and enumerated values for describing cars, trucks, busses, bikes, and boats and their features. For describing commercial aspects of related offers, http://schema.org/Offer already provides the necessary level of detail. Thus, this proposal does not add new elements for commercial features.<br />
<br />
=== Relationship to Configuration Information for Vehicles ===<br />
Cars and other vehicles are often highly configurable products, for which the number of possible combinations can be as much as 10 to the power of 20 for a single vendor. Many manufacturers of cars offer cars in a built-to-order fashion, i.e. they market options spaces of possible cars to customers. <br />
<br />
The space of actually available cars is a subset of the theoretically possible combinations, because <br />
#technical constraints (a configuration would not work well or not at all), <br />
#legal constraints (a configuration would not meet regulatory requirements for a target market), <br />
#production constraints (a configuration will be logistically difficult or expensive to build), and <br />
#marketing considerations (the manufacturer does not want to offer a certain configuration)<br />
<br />
rule our certain configurations.<br />
<br />
This proposal focuses on modeling fully-specified cars, like actual new or used cars, or enumerated sets of car configurations.<br />
<br />
The modeling of configuration rules (e.g. which alternative options are available and how they can be combined) is outside the scope of this proposal. We plan a second proposal for the non-trivial problem of vehicle configuration and vehicle range information, which will complement this proposal.<br />
<br />
The reasons for this staged approach are as follows:<br />
<br />
#Configurable products are not yet supported by schema.org and the underlying GoodRelations product model. An extension for configurable vehicles should include a generic extension for configurable products, which requires additional time to develop.<br />
#The number of Web sites that publish information about actual cars is by orders of magnitude bigger than then number of sites that publish or are able to publish configuration rules. Every dealer listing used and new car inventory and every car listing site will benefit from support for the proposed extension. Configuration rules will mainly be relevant for a manufacturer sites.<br />
#The proposal is based on the existing product model of schema.org. A future extension for configurable products must be designed in a way compatible with the existing product model anyway, so there is no risk starting with actual vehicles.<br />
<br />
=== Financing ===<br />
Also not included in this proposal are elements for financing as additional payment option information. Such should be added by another industry-neutral extension proposal. The [http://purl.org/vvo/ns Volkswagen Vehicles Ontology (VVO)] may serve as useful input for that, because it is based on the GoodRelations core model of payment. We may submit a respective extension proposal for financing in the future.<br />
<br />
== Motivating Examples ==<br />
* A site with used car offers wants to mark-up its individual car offers using schema.org.<br />
* A car manufacturer wants to mark up its product model information.<br />
* A rental car company wants to mark-up its fleet, rental offers, and conditions.<br />
<br />
While the original intention was support for the automotive industry, basic support for bikes and boats has already been included, too.<br />
<br />
Support for aircraft information could be added with moderate effort but is left out for the moment, because we think this should be a separate extension proposal based on additional domain expertise.<br />
<br />
'''Examples of Web Sites:'''<br />
*http://www.cars.com/vehicledetail/detail/612273235/overview/<br />
* More to be added.<br />
<br />
== Design Principles ==<br />
# '''Reuse commercial properties from http://schema.org/Offer and the underlying GoodRelations conceptual model.''' Don't mix modeling vehicles with modeling offers to buy, rent, or service vehicles.<br />
# '''Standardize objective vehicle characteristics and defer consensus for diverse and vendor-specific vehicle characteristics:''' Vehicles, and in particular cars, can have a hundred features and more. Some are very objective (e.g. fuel consumption under lab conditions, dimensions); some are best handled as text (e.g. interior colors), and some are very vendor-specific, e.g. engine types, safety features, etc.<br />
# '''Balance between mark-up effort and usefulness of data:''' The data should be as useful as possible for search engines and other consumers, but the effort for Web developers must be also kept at a minimum.<br />
<br />
These design principles are implemented as follows:<br />
<br />
#Quantitative properties that do not require a unit of measurement can be modeled as either a plain numeric literal (http://schema.org/Number) or a http://schema.org/QuantitativeValue. Typical cases are the number of seats or doors. For a single value, a literal is sufficient. For a range, a http://schema.org/QuantitativeValue is more appropriate.<br />
#Qualitative properties, like fuel types or body styles can be modeled either using a Freebase URI, site-specific URI, or plain text. If a site is able to provide the URI of a authoritative definition for a value or characteristic, this is more useful, but if the site can provide only a string, this is better than nothing.<br />
#Limit the number of standardized properties and use the complementing [http://www.w3.org/wiki/WebSchemas/PropertyValuePairs property-values proposal for schema.org] for vendor-specific vehicle features.<br />
<br />
== Extension Proposal ==<br />
===Git Repository===<br />
The latest version of the proposal is now in a Git repository at github.com at: https://github.com/mfhepp/sdo-vehicles.<br />
The earlier Mercurial repository and the Git repository on bitbucket has been deprecated and set to private in order to avoid confusion.<br />
<br />
=== Development Version on GAE ===<br />
<br />
A '''development version''' of the proposal is available at: http://sdo-vehicles.appspot.com/.<br />
See e.g.<br />
* http://sdo-vehicles.appspot.com/Car<br />
* http://sdo-vehicles.appspot.com/Van<br />
* http://sdo-vehicles.appspot.com/Motorcycle<br />
<br />
In the following, we list the elements in the proposal. '''The authoritative proposal is the version in the Git repository at: https://github.com/mfhepp/sdo-vehicles.'''<br />
<br />
=== Changes to Existing Elements ===<br />
* The textual definitions for Car and Vehicle will be augmented.<br />
* Car will be a superclass of the new MotorizedRoadVehicle class instead of Vehicle.<br />
=== New Terms ===<br />
The following terms will be added:<br />
==== New Classes ====<br />
*MotorizedRoadVehicle<br />
**A motorized road vehicle is a wheeled land vehicle whose main propulsion is provided by an engine or motor.<br />
*Truck<br />
**A lorry (British English) or truck (American English) is a motor vehicle designed to transport cargo.<br />
*Van<br />
**A van is a kind of vehicle used for transporting goods or groups of people. It is usually a box-shaped vehicle on four wheels, about the same width and length as a large automobile, but taller and usually higher off the ground, also referred to as a light commercial vehicle or LCV.<br />
*MotorizedBicycle<br />
**A motorized bicycle is a bicycle with an attached motor used to power the vehicle, or to assist with pedaling.<br />
*BusOrCoach<br />
**A bus (also omnibus or autobus) is a road vehicle designed to carry passengers. Buses have a capacity as high as 300 passengers and are widely used for public transportation. Coaches are luxury busses, usually in service for long distance travel.<br />
*Motorcycle<br />
**A motorcycle or motorbike is a single-track, two-wheeled motor vehicle.<br />
*Bike<br />
**A bicycle or bike is a pedal-driven, human-powered, single-track vehicle, having two wheels attached to a frame, one behind the other. Some bicycles have a small combustion or electric engine that assists with the pedaling.<br />
*Watercraft<br />
**A watercraft is a vehicle, vessel or craft designed to move across or through water.<br />
*Boat<br />
**A boat is a watercraft of modest size designed to float or plane, to provide passage across water.<br />
*MotorBoat<br />
**A motorboat is a boat which is powered by an engine.<br />
*SailingBoat<br />
**A sailboat or sailing boat is a boat propelled partly or entirely by sails.<br />
*SteeringPositionValue<br />
**A value indicating a steering position.<br />
*EmissionStandardValue<br />
**A value indicating the an emission standard.<br />
*TransmissionTypeValue<br />
**A value indicating a type of transmission. <br />
*DriveWheelConfigurationValue<br />
**A value indicating which roadwheels will receive torque.<br />
*EngineTypeValue<br />
**A value indicating an engine type. <br />
*FuelTypeValue<br />
**A value indicating a type of fuel. <br />
*BodyStyleValue<br />
**A value indicating the body style of a vehicle.<br />
*CarUsageType<br />
**A value indicating a special usage of a car, e.g. commercial rental, driving school, or as a taxi.<br />
<br />
==== New Properties ====<br />
*steeringPosition<br />
*fuelCapacity<br />
*numberOfOwners<br />
*roofLoad<br />
*fuelConsumption<br />
*cargoVolume<br />
*driveWheelConfiguration<br />
*wheelbase<br />
*payload<br />
*weightTotal<br />
*transmission<br />
*fuelType<br />
*engineDisplacement<br />
*mileageFromOdometer<br />
*bodyStyle<br />
*tongueWeight<br />
*doors<br />
*speed<br />
*meetsEmissionStandard<br />
*fuelEfficiency<br />
*gears<br />
*axles<br />
*engineType<br />
*seatingCapacity<br />
*trailerWeight<br />
*acceleration<br />
*enginePower<br />
*productionDate<br />
*specialUsage<br />
*damages<br />
*firstRegistration<br />
*engineName<br />
*ACRISSCode<br />
*VIN<br />
*modelDate<br />
*colorInterior<br />
*interiorType<br />
*airbags<br />
*torque<br />
*emissionsCO2<br />
<br />
==== New Individuals ====<br />
*'''SteeringPositionValue:''' RightHandDriving and LeftHandDriving<br />
*'''FuelTypeValue:''' TwoStrokeMixture (other fuel types are readily available from DBPedia or Freebase)<br />
*'''DriveWheelConfigurationValue:''' 4WD, AWD, FWD, RWD<br />
*'''CarUsageType:''' RentalUsage, DrivingSchoolUsage, TaxiUsage<br />
<br />
=== Relationship to Other Proposals ===<br />
The proposal does not critically depend on, but '''will greatly benefit from the [[WebSchemas/PropertyValuePairs|property-value pairs]] proposal''' for the many vehicle feature details that are difficult to standardize in a global, vendor-independent form.<br />
<br />
== Markup Example ==<br />
<br />
=== HTML without RDFa or Microdata ===<br />
<syntaxhighlight lang="html5"><br />
<div ><br />
<strong>Contact Name: </strong> <span>Brent</span><br />
<div>$18,000</div><br />
<!-- Car Details --><br />
<div id="product"><br />
<strong>2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p>2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)</p><br />
<img href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong>Black</p><br />
<p><strong>Interior Color: </strong>Black</p><br />
<p><strong>Interior Type: </strong>Leather upholstery, wood paneling</p><br />
<p><strong>Model Year: </strong><time>2009</time></p> <br />
<p><strong>Transmission: </strong>6 speed Sports Automatic Dual Clutch</p> <br />
<p><strong>VIN: </strong>WVWZZZ1KZ9U######</p> <br />
<p><strong>Number of gears: </strong>6</p> <br />
<p><strong>Body: </strong>Hatchback</p><br />
<p><strong>Number of doors: </strong>3</p><br />
<p><strong>Number of seats: </strong>5</p><br />
<p><strong>Drive Type: </strong>Front Wheel Drive</p><br />
<p><strong>Engine: </strong>4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</p><br />
<p><strong>Engine Power: </strong>147 kw at 5100 rpm</p><br />
<p><strong>Fuel type: </strong>Petrol - Premium ULP</p><br />
<p><strong>Engine Size: </strong>1984 ccm</p><br />
<p><strong>Mileage: </strong>53100 km</p><br />
<p><strong>Number of airbags: </strong>6</p><br />
<p><strong>CO2 Emission Combined: </strong>192 g/km</p><br />
</div><br />
</syntaxhighlight><br />
<br />
=== Microdata ===<br />
<syntaxhighlight lang="html5"><br />
<!-- Seller Details --><br />
<div itemscope itemtype="http://schema.org/Person"><br />
<strong>Contact Name: </strong> <span itemprop="name givenName">Brent</span><br />
<div itemprop="makesOffer" itemscope itemtype="http://schema.org/Offer" itemref="product"><br />
<span itemprop="priceSpecification" itemscope <br />
itemtype="http://schema.org/UnitPriceSpecification"><br />
<meta itemprop="priceCurrency" content="USD">$<br />
<meta itemprop="price" content="18000">18,000<br />
</span><br />
</div><br />
</div><br />
<!-- Car Details --><br />
<div id="product" itemprop="itemOffered" itemscope itemtype="http://schema.org/Car"><br />
<strong itemprop="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p itemprop="description">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)</p><br />
<img itemprop="image" href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong><span itemprop="color">Black</span></p><br />
<p><strong>Interior Color: </strong><span itemprop="colorInterior">Black</span></p><br />
<p><strong>Interior Type: </strong><span itemprop="interiorType">Leather upholstery, <br />
wood paneling</span></p><br />
<p><strong>Model Year: </strong><time itemprop="modelDate">2009</time></p> <br />
<p><strong>Transmission: </strong><br />
<span itemprop="transmission">6 speed Sports Automatic Dual Clutch</span><br />
</p> <br />
<p><strong>VIN: </strong><span itemprop="VIN">WVWZZZ1KZ9U######</span></p> <br />
<p><strong>Number of gears: </strong><span itemprop="gears">6</span></p> <br />
<p><strong>Body: </strong><br />
<span itemprop="bodyStyle">Hatchback</span><br />
</p><br />
<p><strong>Number of doors: </strong><span itemprop="doors">3</span></p><br />
<p><strong>Number of seats: </strong><span itemprop="seatingCapacity">5</span></p><br />
<p><strong>Drive Type: </strong><br />
<link itemprop="driveWheelConfiguration" href="http://schema.org/FWD" /><br />
Front Wheel Drive<br />
</p><br />
<p><strong>Engine: </strong><br />
<span itemprop="engineName">4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</span><br />
</p><br />
<p><strong>Engine Power: </strong><br />
<span itemprop="enginePower" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">147</span> <br />
<meta itemprop="unitCode" content="KWT">kw<br />
at <span itemprop="valueReference" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<meta itemprop="name" content="referenceRPM"> <br />
<span itemprop="value">5100</span> <br />
<meta itemprop="unitCode" content="RPM">rpm<br />
</span><br />
</span><br />
</p><br />
<p><strong>Fuel type: </strong><br />
<span itemprop="fuelType">Petrol - Premium ULP</span> <br />
</p><br />
<p><strong>Engine Size: </strong><br />
<span itemprop="engineDisplacement" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">1984</span> <br />
<meta itemprop="unitCode" content="CMQ">ccm<br />
</span><br />
</p><br />
<p><strong>Mileage: </strong><br />
<span itemprop="mileageFromOdometer" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">53100</span> <br />
<meta itemprop="unitCode" content="KMT">km<br />
</span><br />
</p><br />
<p><strong>Number of airbags: </strong><span itemprop="airbags">6</span></p><br />
<p><strong>CO2 Emission Combined: </strong><span itemprop="emissionCO2">192</span> g/km</p><br />
</div><br />
</syntaxhighlight><br />
<br />
=== RDFa ===<br />
<br />
<syntaxhighlight lang="html5"><br />
<!-- Seller Details --><br />
<div vocab="http://schema.org/" typeof="Person"><br />
<strong>Contact Name: </strong> <span property="name givenName">Brent</span><br />
<div property="makesOffer" typeof="Offer"><br />
<span property="priceSpecification" typeof="UnitPriceSpecification"><br />
<meta property="priceCurrency" content="USD">$<br />
<meta property="price" content="18000">18,000<br />
</span><br />
<!-- Car Details --><br />
<div id="product" property="itemOffered" typeof="Car"><br />
<strong property="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p property="description">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)<br />
</p><br />
<img property="image" href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong><span property="color">Black</span></p><br />
<p><strong>Interior Color: </strong><span property="colorInterior">Black</span></p><br />
<p><strong>Interior Type: </strong><span property="interiorType">Leather upholstery, wood paneling</span></p><br />
<p><strong>Model Year: </strong><time property="modelDate">2009</time></p> <br />
<p><strong>Transmission: </strong><br />
<span property="transmission">6 speed Sports Automatic Dual Clutch</span><br />
</p> <br />
<p><strong>VIN: </strong><span property="VIN">WVWZZZ1KZ9U######</span></p> <br />
<p><strong>Number of gears: </strong><span property="gears">6</span></p> <br />
<p><strong>Body: </strong><br />
<span property="bodyStyle">Hatchback</span><br />
</p><br />
<p><strong>Number of doors: </strong><span property="doors">3</span></p><br />
<p><strong>Number of seats: </strong><span property="seatingCapacity">5</span></p><br />
<p><strong>Drive Type: </strong><br />
<link property="driveWheelConfiguration" href="http://schema.org/FWD" /><br />
Front Wheel Drive<br />
</p><br />
<p><strong>Engine: </strong><br />
<span property="engineName">4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</span><br />
</p><br />
<p><strong>Engine Power: </strong><br />
<span property="enginePower" typeof="QuantitativeValue"><br />
<span property="value">147</span> <br />
<meta property="unitCode" content="KWT">kw<br />
at <span property="valueReference" typeof="QuantitativeValue"><br />
<meta property="name" content="referenceRPM"> <br />
<span property="value">5100</span> <br />
<meta property="unitCode" content="RPM">rpm<br />
</span><br />
</span><br />
</p><br />
<p><strong>Fuel type: </strong><br />
<span property="fuelType">Petrol - Premium ULP</span><br />
</p><br />
<p><strong>Engine Size: </strong><br />
<span property="engineDisplacement" typeof="QuantitativeValue"><br />
<span property="value">1984</span> <br />
<meta property="unitCode" content="CMQ">ccm<br />
</span><br />
</p><br />
<p><strong>Mileage: </strong><br />
<span property="mileageFromOdometer" typeof="QuantitativeValue"><br />
<span property="value">53100</span> <br />
<meta property="unitCode" content="KMT">km<br />
</span><br />
</p><br />
<p><strong>Number of airbags: </strong><span property="airbags">6</span></p><br />
<p><strong>CO2 Emission Combined: </strong><span property="emissionCO2">192</span> g/km</p><br />
</div><br />
</div><br />
</div><br />
</syntaxhighlight><br />
<br />
== Special Cases ==<br />
=== DBPedia and Freebase URIs as Values ===<br />
Several properties will accept either text or entities as a value. In the later case, it is beneficial if the publisher of the data can link locally defined value entities to Freebase or DBPedia entities, because this will allow consuming clients to better understand the data.<br />
<br />
This is built into the proposal, but not enforced nor directly explained in the textual definitions of the elements.<br />
<br />
'''Example:'''<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Car"><br />
<strong itemprop="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p itemprop="description">2009 Volkswagen(...)</p><br />
<p><strong>Transmission: </strong><br />
<div itemprop="transmission" itemscope itemtype="http://schema.org/TransmissionTypeValue"><br />
<span itemprop="name">6 speed Sports Automatic Dual Clutch</span><br />
<link itemprop="sameAs" href="http://www.freebase.com/m/01xc2y" /> <br />
</div><br />
</p> <br />
</div><br />
</syntaxhighlight><br />
<br />
It is also possible to directly use an authoritative URI as a value, but this will be more difficult to understand for some clients:<br />
<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Car"><br />
<strong itemprop="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p itemprop="description">2009 Volkswagen(...)</p><br />
<p><strong>Transmission: </strong><br />
<link itemprop="transmission" href="http://www.freebase.com/m/01xc2y" /> 6 speed Sports Automatic Dual Clutch <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Non-standard Vehicle Features ===<br />
<br />
For vehicle features that are do not match the properties of the extension proposal, we recommend using the [[WebSchemas/PropertyValuePairs|property-value proposal for schema.org]].<br />
<br />
For examples of this pattern, see [[WebSchemas/PropertyValuePairs#Markup_Examples|WebSchemas/PropertyValuePairs#Markup_Examples]].<br />
<br />
== Comments and Feedback ==<br />
Please join the [https://plus.google.com/communities/104510681993581444051 Automotive Ontology Working Group] or post to the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs@w3.org mailing list] if you want to raise issues or have suggestions on how to improve the proposal.<br />
<br />
=== Pending Issues ===<br />
==== schema:feature ====<br />
*Shall we add a property schema:feature as subproperty of schema:additionalProperty (from the parallel property-values proposal) in order to point developers to the fact that they should use this pattern for all non-<br />
standardized car features (like audio, power windows, cup holder, sunroof, ...)? Or will it be enough to document that properly in the examples?<br />
<br />
==== Remove Types for Value Groups ====<br />
* Shall we remove the eight types that are just there for grouping values <br />
**SteeringPositionValue - A value indicating a steering position.<br />
**EmissionStandardValue - A value indicating the an emission standard.<br />
**TransmissionTypeValue - A value indicating a type of transmission.<br />
**DriveWheelConfigurationValue - A value indicating which roadwheels will receive torque.<br />
**EngineTypeValue - A value indicating an engine type.<br />
**FuelTypeValue - A value indicating a type of fuel.<br />
**BodyStyleValue - A value indicating the body style of a vehicle.<br />
**CarUsageType - A value indicating a special usage of a car, e.g. commercial rental, driving school, or as a taxi.<br />
<br />
* Or at least those that do not have individuals in schema.org, like<br />
<br />
**SteeringPositionValue: RightHandDriving and LeftHandDriving<br />
**FuelTypeValue: TwoStrokeMixture (other fuel types are readily available from DBPedia or Freebase)<br />
**DriveWheelConfigurationValue: 4WD, AWD, FWD, RWD<br />
**CarUsageType: RentalUsage, DrivingSchoolUsage, TaxiUsage<br />
<br />
We could omit all of them or at least<br />
<br />
*EmissionStandardValue <br />
*TransmissionTypeValue<br />
*EngineTypeValue<br />
*BodyStyleValue<br />
<br />
With a range of Text OR QualitativeValue, we would have all we need and trim down the number of new classes from 19 to 15 (modest trim) or 11 (if we remove all types for groups of values).<br />
<br />
A counterargument against removing them is that in other branches of schema.org, we have types for groups of values, and it will make the vocabulary more manageable as it grows.<br />
<br />
==== Define more Fuel Types ====<br />
<br />
In addition to TwoStrokeMixture, we could add individuals for all common fuel types, e.g. those from the [https://rawgit.com/w3c/automotive-bg/master/snapshots/data_spec_snapshot_latest.html#fuelconfiguration-interface Vehicle Data Specification] from the [http://www.w3.org/community/autowebplatform/ W3C Automotive and Web Platform Business Group]:<br />
<br />
*Gasoline<br />
*Methanol<br />
*Ethanol<br />
*Diesel<br />
*LPG<br />
*CNG<br />
*Propane<br />
*Electric<br />
<br />
'''Counterargument:''' In general, we try to externalize enumerations from schema.org. For fuel types, strings combined with pointers to Freebase or DBPedia or Wikipedia save the same purpose and evolve with the domain with no need to update schema.org if new fuel types become relevant.<br />
<br />
== Related Work ==<br />
See also: http://carobka.ru/cars_reviews/ford/focus/3831.html has an example of an extension Yandex have been using informally.<br />
<br />
[[Category:WebSchemas]]<br />
[[Category:WebSchemaProposals]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas&diff=77177WebSchemas2014-09-23T13:01:03Z<p>Danbri: added talks</p>
<hr />
<div>=Web Schemas=<br />
<br />
* For [http://schema.org schema.org]'s proposals tracker, see [[WebSchemas/SchemaDotOrgProposals|Extension proposals]] ([https://www.w3.org/2000/09/dbwg/details?group=49967 W3C database entry])<br />
* Web Schemas is a [http://lists.w3.org/Archives/Public/public-html-data-tf/ W3C group] used by the [http://schema.org/ schema.org] project to collaborate with the wider community.<br />
* The group is not just for schema.org; however there is more traffic here about schema.org because it is the only schema.org mailing lists. ''Other projects/vocabularies are very welcome also''!<br />
<br />
==Introduction==<br />
<br />
This is the main Wiki page for W3C's [http://www.w3.org/2001/sw/interest/ Semantic Web Interest Group] ''Web Schemas'' task force. Amongst other roles, it serves as a public discussion forum for [http://schema.org/ Schema.org], including [[WebSchemas/SchemaDotOrgProposals|Extension proposals]].<br />
<br />
The taskforce chairs are R.V.Guha (Google) and [http://www.w3.org/wiki/User:Danbri Dan Brickley] (Google)<br />
<br />
In scope include collaborations on mappings, tools, extensibility and cross-syntax interoperability. An [http://www.w3.org/wiki/Html-data-tf HTML Data] group is nearby (see also [http://lists.w3.org/Archives/Public/public-html-data-tf/ public-html-data-tf list]); detailed discussion about Web data syntax belongs there.<br />
<br />
See the [http://www.w3.org/2001/sw/interest/webschema.html charter] for more details. <br />
<br />
The group uses the '''public-vocabs@w3.org''' mailing list<br />
<br />
* See [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs@w3.org archives]<br />
* [http://www.w3.org/2011/webschema/track/ Issue Tracker] (organized into "Feedback on X" products/categories, where Xs are Schemas we're discussing)<br />
* To subscribe, send a message to public-vocabs-request@w3.org with Subject: subscribe (see [http://lists.w3.org/ lists.w3.org] for more details). To unsubscribe, do the same but use 'unsubscribe' in the title.<br />
* If you are new to the W3C community, you will need to go through the [http://www.w3.org/2002/09/aa/ archive approval] process before your posts show up in the archives.<br />
* To edit this wiki, you'll need a W3C account; these are [http://www.w3.org/Help/Account/Request/Public available to all]<br />
* To search just this WebSchemas wiki, the issue tracker and schema.org-related mailing lists, try a [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek a custom search].<br />
<br />
Groups who maintain Web Schemas are welcome to use this forum as a feedback channel, in additional to whatever independent mechanisms they also offer.<br />
<br />
In particular, the Schema.org initiative has [http://blog.schema.org/2011/10/w3c-web-schemas-group-is-our-new-public.html adopted] this group as its primary public feedback forum. Others are invited to do likewise.<br />
<br />
Any W3C-related questions, ask Dan Brickley (SWIG chair), c/o danbri@danbri.org<br />
<br />
==Discussion Elsewhere==<br />
<br />
For background discussion on this group, Schema.org and W3C's SWIG, the Oct 2011 [http://semanticweb.com/the-semantic-link-%E2%80%93-episode-11-october-2011_b23961 Semantic Link] podcast may be of interest.<br />
<br />
The Dublin Core Metadata Initiative has a related task group working on [http://wiki.dublincore.org/index.php/Schema.org_Alignment Schema.org Alignment], alongside existing vocabulary collaboration work [http://dublincore.org/documents/dcmi-foaf/ with FOAF].<br />
<br />
For schema.org there are discussions on various sites (unofficial; this group is the only place monitored by Schema.org team) :<br />
<br />
* [https://twitter.com/#!/search/schema.org on Twitter]<br />
* [https://plus.google.com/s/schema.org on G+]<br />
* [http://stackoverflow.com/questions/tagged/schema.org schema.org tag on Stack Overflow]<br />
* [http://answers.semanticweb.com/search/?q=schema.org&Submit=search&t=question answers.semanticweb.com]<br />
* [http://www.quora.com/Schema-org Schema.org on Quora]<br />
<br />
Talks and slides:<br />
<br />
* [http://www.slideshare.net/rvguha/sem-tech2014c Guha's] and [https://docs.google.com/presentation/d/1f-2asymXOCCYHa75OkOnlqc0SExvD44V5D6buyKHfII/edit?usp=sharing Dan Brickley's] SemTech 2014 slides.<br />
<br />
==Proposals from and for Schema.org==<br />
<br />
The main table for managing/tracking schema.org proposals is maintained here: [[WebSchemas/SchemaDotOrgProposals|Schema.org Proposals]]<br />
<br />
A separate entry discussed [http://www.w3.org/wiki/SchemaDotOrgProcess Schema.org Process] as it relates to this group.<br />
<br />
Possible future discussions for Schema.org extensions (proposals welcomed; this list is free-form...):<br />
<br />
* Points of Interest (POIs), collab with OGC group. See [http://opengeospatial.github.io/poi/spec/graphics/poi_model.svg data model], [http://opengeospatial.github.io/poi/spec/poi-core.html latest spec draft].<br />
* Journals / scholarly publishing<br />
* Magazines<br />
* Cultural heritage - libraries, museums, archives. See [http://www.w3.org/2005/Incubator/lld/ Linked Library W3C group], [http://www.europeana.eu/portal/ Europeana], [http://cyber.law.harvard.edu/dpla/Main_Page DPLA], [http://lod-lam.net/summit/ LOD-LAM] etc.<br />
* Bibliographic [http://www.w3.org/community/schemabibex/ Schema Bib Extend]<br />
* Integration of constructs based on Good Relations, FOAF, Dublin Core, ...<br />
* [http://www.w3.org/2011/gld/wiki/Main_Page Linked Govt data]<br />
* Software / Apps<br />
* Health/Medicine<br />
* Cars and Vehicles<br />
* ''the relationships between all of these''<br />
<br />
Some discussions are in fact targeted at the underlying syntaxes used for exposing schema.org markup:<br />
*[[WebSchemas/InverseProperties|Inverse Properties for Microdata]]<br />
<br />
==Tools and Statistics==<br />
<br />
* Statistics<br />
** [http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/0018.html Metadata statistics from Yahoo! Search]<br />
** [http://webdatacommons.org/structureddata/2012-08/stats/stats.html RDFa, Microdata and Microformat deployment statistics from WebDataCommons.org (August 2012)]<br />
** [http://webdatacommons.org/structureddata/2013-11/stats/stats.html RDFa, Microdata and Microformat deployment statistics from WebDataCommons.org (November 2013)]<br />
** [http://sindice.com/stats/basic-stats/# Sindice stats] ([http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/0020.html announcement])<br />
** [http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/ General stats discussion] incl. Bizer et al.'s CommonCrawl extraction ([http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/0029.html announcement]); there is some [http://lists.w3.org/Archives/Public/public-vocabs/2012Apr/0016.html debate about shortcomings of this analysis and the proper interpretation of these].<br />
* Validators<br />
** [http://www.google.com/webmasters/tools/richsnippets Google richsnippets tool]<br />
** [http://www.bing.com/toolbox/EntityExtraction Microsoft Bing Markup Validator] (entity extractor)<br />
** [http://webmaster.yandex.ru/microtest.xml Yandex checker]<br />
** [http://linter.structured-data.org/ Structured Data Linter]<br />
* Search Tools<br />
** [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek Google custom search] of schema.org/webschema-related sites. ([http://www.google.com/search?start=0&num=10&q=MediaObject&client=google-csbe&output=xml_no_dtd&cx=003736913799082383568:c44bi0_xxek XML results] are also [https://developers.google.com/custom-search/docs/xml_results?hl=en#WebSearch_Request_Format available])<br />
** [http://www.raymondcamden.com/index.cfm/2012/11/26/Reading-Microdata-Elements-in-Chrome reading microdata in Chrome]<br />
* Authoring Tools<br />
** [http://rdface.aksw.org RDFaCE]<br />
** [http://schema-creator.org/ Schema Creator]<br />
** [http://www.microdatagenerator.com/ Schema.org Generator | Microdata Generator ]<br />
* Vocabulary QA<br />
** Sandro Hawke made a [https://gist.github.com/sandhawke/5691972 list of 'overloaded' schema.org properties] that expect sometimes a Thing, sometimes a Text value.<br />
<br />
==Mappings==<br />
<br />
Mappings between various vocabularies of interest on the Web Schemas list. The following are mostly using schema.org as a hub, but others would be great to collect too.<br />
<br />
* [http://www.mkbergman.com/999/new-umbel-release-gains-schema-org-geonames-capabilities/ UMBEL] schema.org mappings (data is in [https://github.com/structureddynamics/UMBEL/blob/master/External%20Ontologies/schema.org.n3 github])<br />
* [http://wiki.dublincore.org/index.php/Schema.org_Alignment Dublin Core / Schema.org Allignment taskforce].<br />
* [http://schema.rdfs.org/mappings.html schema.rdfs.org mapping page].<br />
** [http://schema.rdfs.org/mappings/sioc SIOC mappings]<br />
** [http://mappings.dbpedia.org/server/ontology/export DBpedia mappings file] (download; includes schema.org)<br />
** [http://schema.rdfs.org/mappings/bibo bibo]<br />
** [[GoodRelations]] integration is underway<br />
** [http://schema.rdfs.org/mappings/schemaorg_wn.owl Wordnet]<br />
* A discussion note on [[WebSchemas/SchemaDotOrgOData|schema.org and OData]] is available.<br />
<br />
==Markup examples==<br />
<br />
This group is about vocabulary (schemas) rather than specific markup syntax details. However since syntax specs are evolving in parallel, there are often discussions that need to mix syntax and vocabulary issues.<br />
<br />
* from structured-data.org, some [http://linter.structured-data.org/examples/ examples] showing RDFa 1.1 lite versions of Schema.org's Microdata samples<br />
<br />
<br />
Schema.org example sites - the following list give concrete examples of Schema.org sites (testable with [http://www.google.com/webmasters/tools/richsnippets Google richsnippets tool]):<br />
* TV series - http://www.imdb.com/title/tt0813715/ ([http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Fwww.imdb.com%2Ftitle%2Ftt0813715%2F&view= Google checker])<br />
* Product - http://www.ebay.com/ctg/Logitech-Revue-/97019743<br />
* Movie - http://www.imdb.com/title/tt1375666/ http://www.rottentomatoes.com/m/inception/<br />
* Music - http://www.myspace.com/awilolongombaofficiel/music/playlists/awilo-longomba-officiel-s-playlist-243959?_escaped_fragment_=<br />
* Events - www.ticketmaster.com/Foo-Fighters-tickets/artist/776005?_escaped_fragment_=<br />
* [http://schema.org/Recipe Recipe] - http://www.isaveurs.com/recette/recette_tarte_tatin.php</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/VisualArtwork&diff=75965WebSchemas/VisualArtwork2014-08-19T07:20:28Z<p>Danbri: /* Overview */</p>
<hr />
<div>== Overview ==<br />
<br />
This is a proposal for a new Type: Thing > CreativeWork > VisualArtwork<br />
<br />
I am aware that there are already sub-Types for "Painting", "Sculpture", and "Photograph", but this doesn't seem like a viable way forward. There are many other types of artwork (printmaking, drawing, collage, assemblage, digital art, etc.) and it seems illogical to create new Types for each artform.<br />
<br />
So my proposal is for the 'VisualArtwork' Type to be used instead of "Painting" or "Sculpture", and instead of "Photograph" where the photograph in question is being presented in context as an artwork as opposed to forensic photography, etc.<br />
<br />
A number of additional properties would enable a wider range of visual artwork media to use this type, and provide more information about the artwork being described.<br />
<br />
<br />
== Status ==<br />
<br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/visualartwork.html machine-readable schema] - first draft RDFS<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0173.html august 2014 update] (ported to github/appengine, added examples)<br />
* TODO: Add JSON-LD, Microdata version of examples<br />
* TODO: Figure out what to do about artEdition --- is it a concept that generalizes to other CreativeWork types?<br />
<br />
== Vocabulary ==<br />
<br />
<br />
Thing > CreativeWork > VisualArtwork<br />
<br />
All properties inherited from Thing and CreativeWork, plus these additional properties<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#E3E6ED; font-family: "Lucida Grande" , "Lucida Sans Unicode" , Verdana, Tahoma, Arial, sans-serif;" align="left" cellpadding="5" cellspacing="0" border="1" <br />
!Property!!Expected Type!!Description<br />
|-<br />
|style="background-color:#E3E6ED;"|Properties from VisualArtwork||style="background-color:#E3E6ED;"| ||style="background-color:#E3E6ED;"|<br />
|-<br />
|artform||Text||e.g. Painting, Drawing, Scupture, Print, Photograph, Assemblage, Collage, etc.<br />
|-<br />
|materials||Text||A material/medium which which the artwork is made e.g. Oil, Watercolour, Acrylic, Linoprint, Marble, Cyanotype, Digital, Lithograph, DryPoint, Intaglio, Pastel, Woodcut, Pencil, etc. A mixed media piece of artwork can have multiple materials. <br />
|-<br />
|surface||Text||the surface or support on which the artwork is made e.g. Canvas, Paper, Wood, Board, etc.<br />
|-<br />
|width||Distance||width of the artwork<br />
|-<br />
|height||Distance||height of the artwork<br />
|-<br />
|depth||Distance||depth of the artwork<br />
|-<br />
|artEdition||Number||The number of copies when multiple copies of a piece of artwork are produced - e.g. for a limited edition of 20 prints, 'artEdition' refers to the total number of copies (in this example "20").<br />
|-<br />
|colorPalette||colorPalette||Color Palette for the artwork<br />
|}<br />
<br/><br />
<br />
Some examples:<br />
<br />
== Example Markup ==<br />
<br />
=== A Painting ===<br />
<br />
Fairly straightforward painting<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://rdf.freebase.com/rdf/m.0439_q" /><br />
<h1 property="name" lang="fr">La trahison des images </h1><br />
<p><br />
A <span property="artform">painting</span> also known as <br />
<span>The Treason of Images</span> or <br />
<span property="alternateName">The Treachery of Images</span>.<br />
</p> <br />
<img property="image" src="http://http://upload.wikimedia.org/wikipedia/en/b/b9/MagrittePipe.jpg" /><br />
<div property="description"><br />
<p><br />
The painting shows a pipe. Below it, Magritte painted, <br />
<q lang="fr">Ceci n'est pas une pipe.</q>, French for <br />
"This is not a pipe."<br />
</p><br />
<p><br />
His statement is taken to mean that the painting itself is not a pipe. <br />
The painting is merely an image of a pipe. Hence, the description, <br />
"this is not a pipe."<br />
</p><br />
<p><br />
Similarly, the image shown above is neither a pipe nor even a painting, <br />
but rather a digital photograph.<br />
</p><br />
<p><br />
The painting is sometimes given as an example of meta message conveyed <br />
by paralanguage. Compare with Korzybski's <q>The word is not the thing</q> <br />
and <q>The map is not the territory</q>.<br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/06h88"><br />
<span property="name">René Magritte</span><br />
</a><br />
</span><br />
</li><br />
<li>Dimensions:<br />
<span property="width" typeof="Distance">940 mm</span> × <br />
<span property="height" typeof="Distance">635 mm</span><br />
</li><br />
<li>Materials:<br />
<span property="materials">oil</span> on <span property="surface">canvas</span><br />
</li><br />
</ul><br />
</div><br />
<br />
</syntaxhighlight><br />
<br />
=== Multiple materials ===<br />
<br />
A piece of Installation Art which uses multiple instances of the materials property<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://rdf.freebase.com/rdf/m.0dbwsn" /><br />
<h1 property="name">My Bed</h1><br />
<p><br />
My Bed, first created in <time property="dateCreated" datetime="1998">1998</time>, <br />
is an <span property="artform">installation</span> by the British artist Tracey Emin.<br />
</p> <br />
<br />
<br />
<img property="image" src="http://upload.wikimedia.org/wikipedia/en/9/9d/Emin-My-Bed.jpg" /><br />
<div property="description"><br />
<p><br />
<cite>My Bed</cite> was exhibited at the Tate Gallery in <br />
<time property="datePublished" datetime="1998">1999</time> as one <br />
of the shortlisted works for the Turner Prize. It consisted of her <br />
bed with bedroom objects in an abject state, and gained much media <br />
attention. Although it did not win the prize, its notoriety has <br />
persisted.<br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/015sxw"><br />
<span property="name">Tracey Emin</span><br />
</a><br />
</span><br />
</li><br />
</ul><br />
<p><br />
The artwork generated considerable media furore, particularly over the <br />
fact that the <span property="materials">bedsheets</span> were stained <br />
with bodily secretions and the floor had items from the artist's room <br />
(such as <span property="materials">condoms</span>, <br />
<span property="materials">a pair of knickers</span> with menstrual <br />
period stains, other detritus, and functional, everyday objects, <br />
including a <span property="materials">pair of slippers</span>). The <br />
<span property="materials">bed</span> was presented in the state that <br />
Emin claimed it had been when she said she had not got up from it for <br />
several days due to suicidal depression brought on by relationship <br />
difficulties.<br />
</div><br />
</syntaxhighlight><br />
<br />
=== artEdition ===<br />
<br />
Example showing artEdition property in use for a piece of artwork that was created as a series of multiple identical items<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://www.pada.net/members/memPicFull.php/38/367" /><br />
<h1 property="name">Still Life under the Lamp</h1><br />
<p><br />
<span property="artform">Print</span> from <time property="dateCreated" datetime="1962">1962</time><br />
by Pablo Picasso. Numbered from the edition of <span property="artEdition">50</span>, <br />
each signed by the artist in pencil, lower right: Picasso.<br />
</p> <br />
<img property="image" src="http://www.pada.net/Photos/38/Full/picasso.lamp.jpg" /><br />
<div property="description"><br />
<p><br />
<cite>Still Life under the Lamp</cite>, from 1962, made when the artist <br />
was eighty years old, are counted among Picasso’s most important works <br />
in linocut, a technique that he explored in the late 1950s and early <br />
1960s. The progressive proofs show the step by step sequence by which <br />
Picasso created his linocut images showing the development of the <br />
image into its final form.<br />
</p><br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/07pj7mx"><br />
<span property="name">Pablo Picasso</span><br />
</a><br />
</span><br />
</li><br />
<li>Dimensions:<br />
<span property="width" typeof="Distance">25 3/16 inches</span> × <br />
<span property="height" typeof="Distance">20 3/4 inches</span><br />
</li><br />
<li>Materials:<br />
<span property="materials">linoprint</span> on <span property="surface">paper</span><br />
</li><br />
<li><br />
See also <a href="http://www.pada.net/members/memPicFull.php/38/367">here</a><br />
and <a href="http://www.britishmuseum.org/about_us/news_and_press/press_releases/2014/picasso_linocuts.aspx">here</a>.<br />
</ul><br />
</div><br />
</syntaxhighlight><br />
<br />
== Early Color Palette proposal ==<br />
<br />
The color palette information would be very useful to classify, categorize and index artwork by colors. I have provided an example of how this structure could look:<br />
<br />
<span itemscope itemtype="http://schema.org/ColorPalette"<http://schema.org/ColorPalette>><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#3366FF</span><br />
<span itemprop="name">Sky Blue</span><br />
<span itemprop="percentage">30%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F5B800</span><br />
<span itemprop="name">Gold</span><br />
<span itemprop="percentage">25%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F5003D</span><br />
<span itemprop="name">Crimson Red</span><br />
<span itemprop="percentage">20%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#B8F500</span><br />
<span itemprop="name">Lime</span><br />
<span itemprop="percentage">15%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F500B8</span><br />
<span itemprop="name">Fuschia</span><br />
<span itemprop="percentage">10%</span><br />
</div><br />
</span><br />
<br />
== Discussion ==<br />
<br />
Posted to public-vocabs on May 7, 2013: http://lists.w3.org/Archives/Public/public-vocabs/2013May/0024.html<br />
Discussion on colorpalette property added to VisualArtwork: http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/0084.html</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/VisualArtwork&diff=75964WebSchemas/VisualArtwork2014-08-19T07:20:16Z<p>Danbri: wording. + linked aug 2014 thread</p>
<hr />
<div>== Overview ==<br />
<br />
This is a proposal for a new Type: Thing > CreativeWork > VisualArtwork<br />
<br />
I am aware that there are already sub-Types for "Painting", "Sculpture", and "Photograph", but this doesn't seem like a viable way forward. There are many other types of artwork (printmaking, drawing, collage, assemblage, digital art, etc.) and it seems illogical to create new Types for each artform.<br />
<br />
So my proposal is for the 'VisualArtwork' Type to be used instead of "Painting" or "Sculpture", and instead of "Photograph" where the photograph in question is being presented in context as an artwork as opposed to forensic photography, etc.<br />
<br />
A number of additional properties would enable a wider range of visual artwork media to use this type, and provide more information about the artwork being described.<br />
<br />
<br />
== Implementation <br />
<br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/visualartwork.html machine-readable schema] - first draft RDFS<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0173.html august 2014 update] (ported to github/appengine, added examples)<br />
* TODO: Add JSON-LD, Microdata version of examples<br />
* TODO: Figure out what to do about artEdition --- is it a concept that generalizes to other CreativeWork types?<br />
<br />
== Vocabulary ==<br />
<br />
<br />
Thing > CreativeWork > VisualArtwork<br />
<br />
All properties inherited from Thing and CreativeWork, plus these additional properties<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#E3E6ED; font-family: "Lucida Grande" , "Lucida Sans Unicode" , Verdana, Tahoma, Arial, sans-serif;" align="left" cellpadding="5" cellspacing="0" border="1" <br />
!Property!!Expected Type!!Description<br />
|-<br />
|style="background-color:#E3E6ED;"|Properties from VisualArtwork||style="background-color:#E3E6ED;"| ||style="background-color:#E3E6ED;"|<br />
|-<br />
|artform||Text||e.g. Painting, Drawing, Scupture, Print, Photograph, Assemblage, Collage, etc.<br />
|-<br />
|materials||Text||A material/medium which which the artwork is made e.g. Oil, Watercolour, Acrylic, Linoprint, Marble, Cyanotype, Digital, Lithograph, DryPoint, Intaglio, Pastel, Woodcut, Pencil, etc. A mixed media piece of artwork can have multiple materials. <br />
|-<br />
|surface||Text||the surface or support on which the artwork is made e.g. Canvas, Paper, Wood, Board, etc.<br />
|-<br />
|width||Distance||width of the artwork<br />
|-<br />
|height||Distance||height of the artwork<br />
|-<br />
|depth||Distance||depth of the artwork<br />
|-<br />
|artEdition||Number||The number of copies when multiple copies of a piece of artwork are produced - e.g. for a limited edition of 20 prints, 'artEdition' refers to the total number of copies (in this example "20").<br />
|-<br />
|colorPalette||colorPalette||Color Palette for the artwork<br />
|}<br />
<br/><br />
<br />
Some examples:<br />
<br />
== Example Markup ==<br />
<br />
=== A Painting ===<br />
<br />
Fairly straightforward painting<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://rdf.freebase.com/rdf/m.0439_q" /><br />
<h1 property="name" lang="fr">La trahison des images </h1><br />
<p><br />
A <span property="artform">painting</span> also known as <br />
<span>The Treason of Images</span> or <br />
<span property="alternateName">The Treachery of Images</span>.<br />
</p> <br />
<img property="image" src="http://http://upload.wikimedia.org/wikipedia/en/b/b9/MagrittePipe.jpg" /><br />
<div property="description"><br />
<p><br />
The painting shows a pipe. Below it, Magritte painted, <br />
<q lang="fr">Ceci n'est pas une pipe.</q>, French for <br />
"This is not a pipe."<br />
</p><br />
<p><br />
His statement is taken to mean that the painting itself is not a pipe. <br />
The painting is merely an image of a pipe. Hence, the description, <br />
"this is not a pipe."<br />
</p><br />
<p><br />
Similarly, the image shown above is neither a pipe nor even a painting, <br />
but rather a digital photograph.<br />
</p><br />
<p><br />
The painting is sometimes given as an example of meta message conveyed <br />
by paralanguage. Compare with Korzybski's <q>The word is not the thing</q> <br />
and <q>The map is not the territory</q>.<br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/06h88"><br />
<span property="name">René Magritte</span><br />
</a><br />
</span><br />
</li><br />
<li>Dimensions:<br />
<span property="width" typeof="Distance">940 mm</span> × <br />
<span property="height" typeof="Distance">635 mm</span><br />
</li><br />
<li>Materials:<br />
<span property="materials">oil</span> on <span property="surface">canvas</span><br />
</li><br />
</ul><br />
</div><br />
<br />
</syntaxhighlight><br />
<br />
=== Multiple materials ===<br />
<br />
A piece of Installation Art which uses multiple instances of the materials property<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://rdf.freebase.com/rdf/m.0dbwsn" /><br />
<h1 property="name">My Bed</h1><br />
<p><br />
My Bed, first created in <time property="dateCreated" datetime="1998">1998</time>, <br />
is an <span property="artform">installation</span> by the British artist Tracey Emin.<br />
</p> <br />
<br />
<br />
<img property="image" src="http://upload.wikimedia.org/wikipedia/en/9/9d/Emin-My-Bed.jpg" /><br />
<div property="description"><br />
<p><br />
<cite>My Bed</cite> was exhibited at the Tate Gallery in <br />
<time property="datePublished" datetime="1998">1999</time> as one <br />
of the shortlisted works for the Turner Prize. It consisted of her <br />
bed with bedroom objects in an abject state, and gained much media <br />
attention. Although it did not win the prize, its notoriety has <br />
persisted.<br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/015sxw"><br />
<span property="name">Tracey Emin</span><br />
</a><br />
</span><br />
</li><br />
</ul><br />
<p><br />
The artwork generated considerable media furore, particularly over the <br />
fact that the <span property="materials">bedsheets</span> were stained <br />
with bodily secretions and the floor had items from the artist's room <br />
(such as <span property="materials">condoms</span>, <br />
<span property="materials">a pair of knickers</span> with menstrual <br />
period stains, other detritus, and functional, everyday objects, <br />
including a <span property="materials">pair of slippers</span>). The <br />
<span property="materials">bed</span> was presented in the state that <br />
Emin claimed it had been when she said she had not got up from it for <br />
several days due to suicidal depression brought on by relationship <br />
difficulties.<br />
</div><br />
</syntaxhighlight><br />
<br />
=== artEdition ===<br />
<br />
Example showing artEdition property in use for a piece of artwork that was created as a series of multiple identical items<br />
<br />
<syntaxhighlight lang="html4strict" line start="1"><br />
<div vocab="http://schema.org/" typeof="VisualArtwork"><br />
<link property="sameAs" href="http://www.pada.net/members/memPicFull.php/38/367" /><br />
<h1 property="name">Still Life under the Lamp</h1><br />
<p><br />
<span property="artform">Print</span> from <time property="dateCreated" datetime="1962">1962</time><br />
by Pablo Picasso. Numbered from the edition of <span property="artEdition">50</span>, <br />
each signed by the artist in pencil, lower right: Picasso.<br />
</p> <br />
<img property="image" src="http://www.pada.net/Photos/38/Full/picasso.lamp.jpg" /><br />
<div property="description"><br />
<p><br />
<cite>Still Life under the Lamp</cite>, from 1962, made when the artist <br />
was eighty years old, are counted among Picasso’s most important works <br />
in linocut, a technique that he explored in the late 1950s and early <br />
1960s. The progressive proofs show the step by step sequence by which <br />
Picasso created his linocut images showing the development of the <br />
image into its final form.<br />
</p><br />
</div><br />
<ul><br />
<li>Artist: <br />
<span property="creator" typeof="Person"><br />
<a property="sameAs" href="https://www.freebase.com/m/07pj7mx"><br />
<span property="name">Pablo Picasso</span><br />
</a><br />
</span><br />
</li><br />
<li>Dimensions:<br />
<span property="width" typeof="Distance">25 3/16 inches</span> × <br />
<span property="height" typeof="Distance">20 3/4 inches</span><br />
</li><br />
<li>Materials:<br />
<span property="materials">linoprint</span> on <span property="surface">paper</span><br />
</li><br />
<li><br />
See also <a href="http://www.pada.net/members/memPicFull.php/38/367">here</a><br />
and <a href="http://www.britishmuseum.org/about_us/news_and_press/press_releases/2014/picasso_linocuts.aspx">here</a>.<br />
</ul><br />
</div><br />
</syntaxhighlight><br />
<br />
== Early Color Palette proposal ==<br />
<br />
The color palette information would be very useful to classify, categorize and index artwork by colors. I have provided an example of how this structure could look:<br />
<br />
<span itemscope itemtype="http://schema.org/ColorPalette"<http://schema.org/ColorPalette>><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#3366FF</span><br />
<span itemprop="name">Sky Blue</span><br />
<span itemprop="percentage">30%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F5B800</span><br />
<span itemprop="name">Gold</span><br />
<span itemprop="percentage">25%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F5003D</span><br />
<span itemprop="name">Crimson Red</span><br />
<span itemprop="percentage">20%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#B8F500</span><br />
<span itemprop="name">Lime</span><br />
<span itemprop="percentage">15%</span><br />
</div><br />
<div itemscope itemtype="http://schema.org/ColorSwatch"<http://schema.org/ColorSwatch>><br />
<span itemprop="hex">#F500B8</span><br />
<span itemprop="name">Fuschia</span><br />
<span itemprop="percentage">10%</span><br />
</div><br />
</span><br />
<br />
== Discussion ==<br />
<br />
Posted to public-vocabs on May 7, 2013: http://lists.w3.org/Archives/Public/public-vocabs/2013May/0024.html<br />
Discussion on colorpalette property added to VisualArtwork: http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/0084.html</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75959WebSchemas/SellerVendorCleanup2014-08-19T05:33:29Z<p>Danbri: linked schema.org release</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement schema.org proposal 'Beta', which shipped as part of the [http://schema.org/docs/releases.html#v1.9 v1.9] release.<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
=== Main points ===<br />
<br />
<br />
* Use existing 'provider' property to describe the service provider, service operator, or service performer (see provider in exchange model in PDF) and update its description to more clearly indicate this intended usage;<br />
* Use existing 'seller' property to describe the entities which sell or offer a service on behalf of the actual service provider (see seller in exchange model). In the case of flights, this would be the airline through which a flight was booked. If a 'seller' is not provided, it is assumed the 'provider' is also the 'seller'.<br />
* Introduce a ‘broker’ property to describe entities that map to the broker concept in the exchange model.<br />
* deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property<br />
* deprecate 'vendor' in favor of re-using 'seller'<br />
* deprecate ‘merchant’ in favor of re-using ‘seller’<br />
* deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described 'provider'<br />
<br />
<br />
=== Implementation Details ===<br />
<br />
''Additions (broker) and clarifications (provider, seller)''<br />
<br />
* '''broker''': <br />
** add a new broker property.<br />
** description: "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."<br />
** Expected types: domain includes Order and Reservation (needed as 'broker' supercedes 'bookingAgent'); ''anything else''?; range includes Person and Organization.<br />
* '''provider:'''<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery, due to 'carrier' being supercededBy 'provider'.<br />
* '''seller:'''<br />
** old text: "The organization or person making the offer."<br />
** new text: "An entity which offers (sells / leases / lends / loans) the services / goods. A seller may also be a provider"<br />
** earlier suggestion: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider." ([http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0164.html see discussion])<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)<br />
<br />
''supercededBy properties''<br />
<br />
* '''bookingAgent''':<br />
** bookingAgent supercededBy broker.<br />
** old text: "If the reservation was not booked directly through the provider, the third-party booking agent can be recorded through this property."<br />
** new text: "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."<br />
* '''vendor''':<br />
** vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
** 'vendor' domain was BuyAction -- added this to seller; 'vendor' was supropertyof participant; also added to seller.<br />
* '''merchant:'''<br />
** merchant supercededBy seller.<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order; added to seller.<br />
* '''carrier:'''<br />
** carrier supercededBy provider.<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** Note that Flight, ParcelDelivery values (added with these changes) are acceptable values for 'provider' property.<br />
* '''flightNumber''':<br />
** Changed recommendation to encourage inclusion of airline code, to cover cases where a Flight can be sold by one Airline and operated (provided) by a different Airline.<br />
** old text: The unique identifier for a flight, not including the airline IATA code. For example, if describing United flight 110, the flightNumber is '110'. The IATA code can be set on the Airline.<br />
** new text: The unique identifier for a flight including the airline IATA code. For example, if describing United flight 110, where the IATA code for United is 'UA', the flightNumber is 'UA110'.</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75923WebSchemas/SellerVendorCleanup2014-08-16T16:25:46Z<p>Danbri: </p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
=== Main points ===<br />
<br />
<br />
* Use existing 'provider' property to describe the service provider, service operator, or service performer (see provider in exchange model in PDF) and update its description to more clearly indicate this intended usage;<br />
* Use existing 'seller' property to describe the entities which sell or offer a service on behalf of the actual service provider (see seller in exchange model). In the case of flights, this would be the airline through which a flight was booked. If a 'seller' is not provided, it is assumed the 'provider' is also the 'seller'.<br />
* Introduce a ‘broker’ property to describe entities that map to the broker concept in the exchange model.<br />
* deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property<br />
* deprecate 'vendor' in favor of re-using 'seller'<br />
* deprecate ‘merchant’ in favor of re-using ‘seller’<br />
* deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described 'provider'<br />
<br />
<br />
=== Implementation Details ===<br />
<br />
''Additions (broker) and clarifications (provider, seller)''<br />
<br />
* '''broker''': <br />
** add a new broker property.<br />
** description: "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."<br />
** Expected types: domain includes Order and Reservation (needed as 'broker' supercedes 'bookingAgent'); ''anything else''?; range includes Person and Organization.<br />
* '''provider:'''<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery, due to 'carrier' being supercededBy 'provider'.<br />
* '''seller:'''<br />
** old text: "The organization or person making the offer."<br />
** new text: "An entity which offers (sells / leases / lends / loans) the services / goods. A seller may also be a provider"<br />
** earlier suggestion: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider." ([http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0164.html see discussion])<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)<br />
<br />
''supercededBy properties''<br />
<br />
* '''bookingAgent''':<br />
** bookingAgent supercededBy broker.<br />
** old text: "If the reservation was not booked directly through the provider, the third-party booking agent can be recorded through this property."<br />
** new text: "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."<br />
* '''vendor''':<br />
** vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
** 'vendor' domain was BuyAction -- added this to seller; 'vendor' was supropertyof participant; also added to seller.<br />
* '''merchant:'''<br />
** merchant supercededBy seller.<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order; added to seller.<br />
* '''carrier:'''<br />
** carrier supercededBy provider.<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** Note that Flight, ParcelDelivery values (added with these changes) are acceptable values for 'provider' property.<br />
* '''flightNumber''':<br />
** Changed recommendation to encourage inclusion of airline code, to cover cases where a Flight can be sold by one Airline and operated (provided) by a different Airline.<br />
** old text: The unique identifier for a flight, not including the airline IATA code. For example, if describing United flight 110, the flightNumber is '110'. The IATA code can be set on the Airline.<br />
** new text: The unique identifier for a flight including the airline IATA code. For example, if describing United flight 110, where the IATA code for United is 'UA', the flightNumber is 'UA110'.</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75922WebSchemas/SellerVendorCleanup2014-08-16T16:25:08Z<p>Danbri: Noting change to flightNumber.</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
=== Main points ===<br />
<br />
<br />
* Use existing 'provider' property to describe the service provider, service operator, or service performer (see provider in exchange model in PDF) and update its description to more clearly indicate this intended usage;<br />
* Use existing 'seller' property to describe the entities which sell or offer a service on behalf of the actual service provider (see seller in exchange model). In the case of flights, this would be the airline through which a flight was booked. If a 'seller' is not provided, it is assumed the 'provider' is also the 'seller'.<br />
* Introduce a ‘broker’ property to describe entities that map to the broker concept in the exchange model.<br />
* deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property<br />
* deprecate 'vendor' in favor of re-using 'seller'<br />
* deprecate ‘merchant’ in favor of re-using ‘seller’<br />
* deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described 'provider'<br />
<br />
<br />
=== Implementation Details ===<br />
<br />
''Additions (broker) and clarifications (provider, seller)''<br />
<br />
* '''broker''': <br />
** add a new broker property.<br />
** description: "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."<br />
** Expected types: domain includes Order and Reservation (needed as 'broker' supercedes 'bookingAgent'); ''anything else''?; range includes Person and Organization.<br />
* '''provider:'''<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery, due to 'carrier' being supercededBy 'provider'.<br />
* '''seller:'''<br />
** old text: "The organization or person making the offer."<br />
** new text: "An entity which offers (sells / leases / lends / loans) the services / goods. A seller may also be a provider"<br />
** earlier suggestion: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider." ([http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0164.html see discussion])<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)<br />
<br />
''supercededBy properties''<br />
<br />
* '''bookingAgent''':<br />
** bookingAgent supercededBy broker.<br />
** old text: "If the reservation was not booked directly through the provider, the third-party booking agent can be recorded through this property."<br />
** new text: "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."<br />
* '''vendor''':<br />
** vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
** 'vendor' domain was BuyAction -- added this to seller; 'vendor' was supropertyof participant; also added to seller.<br />
* '''merchant:'''<br />
** merchant supercededBy seller.<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order; added to seller.<br />
* '''carrier:'''<br />
** carrier supercededBy provider.<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** Note that Flight, ParcelDelivery values (added with these changes) are acceptable values for 'provider' property.<br />
* flightNumber:<br />
** Changed recommendation to encourage inclusion of airline code, to cover cases where a Flight can be sold by one Airline and operated (provided) by a different Airline.<br />
** old text: The unique identifier for a flight, not including the airline IATA code. For example, if describing United flight 110, the flightNumber is '110'. The IATA code can be set on the Airline.<br />
** new text: The unique identifier for a flight including the airline IATA code. For example, if describing United flight 110, where the IATA code for United is 'UA', the flightNumber is 'UA110'.</div>Danbrihttps://www.w3.org/wiki/index.php?title=User:Danbri&diff=75921User:Danbri2014-08-16T16:22:38Z<p>Danbri: updated w/ google affiliation</p>
<hr />
<div>User:DanBri is Dan Brickley.<br />
<br />
* I work on the Schema.org initiative for Google (where I'm now on full time staff) via W3C's [[WebSchemas]] group. There is a page documenting the relationship between [http://www.w3.org/2001/sw/interest/schema.org-collab.html Schema.org and Web Schemas TF].<br />
* I was affiliated to the Vrije Universiteit, Amsterdam (vu.nl), where I work part-time on TV/Web and Linked Data via the [http://notube.tv/ NoTube project].<br />
* I'm responsible, with Libby Miller, for the FOAF project.<br />
* At W3C, I chair the Semantic Web Interest Group (which started in 1998 as RDF-DEV, then RDF Interest Group in 1999...).<br />
* Libby and I ran the SWAD-Europe project which created SKOS, and the ancestor of this Wiki.<br />
<br />
If you have any questions about my work, or my various affiliations / hats, don't hestitate to get in touch via danbri@danbri.org.<br />
<br />
<br />
==Sandbox==<br />
<br />
Can we [http://www.mediawiki.org/wiki/Help:Templates#Named_parameters use templates]? Testing 'Template:SchemaDotOrgTerm'<br />
<br />
<br />
* TVSeries: {{Template:SchemaDotOrgTerm|term=TVSeries}}<br />
<br />
== Testing Geshi syntax highligher ==<br />
<br />
See my draft of [http://www.w3.org/2006/tools/wiki/W3CWikiNotes notes on posting examples in W3C wikis].<br />
<br />
In these examples, we try basically the same text with some variations. In each case we have 'line start 100' and a highlight set on line 5.<br />
<br />
<br />
== XML syntax highlighting ==<br />
<br />
Taken from [http://schema.org/Movie schema.org], with some XMLisation:<br />
<br />
<syntaxhighlight lang="xml" line start="100" highlight="5"><br />
<div itemscope="true" itemtype="http://schema.org/Movie"><br />
<h1 itemprop="name">Pirates of the Carribean: On Stranger Tides (2011)</h1><br />
<span itemprop="description">Jack Sparrow and Barbossa embark on a quest to<br />
find the elusive fountain of youth, only to discover that Blackbeard and<br />
his daughter are after it too.</span><br />
Director:<br />
<div itemprop="director" itemscope="true" itemtype="http://schema.org/People"><br />
<span itemprop="name">Rob Marshall</span><br />
</div><br />
</syntaxhighlight><br />
<br />
<br />
Ok, how does it deal with illformed XML? After all, that's a reasonable thing to show in an example (especially on a standards site):<br />
<br />
Result: illformed (i.e. attributes with no values) are displayed fine. This is good!<br />
<br />
<syntaxhighlight lang="xml" line start="100" highlight="5"><br />
<div itemscope itemtype="http://schema.org/Movie"><br />
<h1 itemprop="name">Pirates of the Carribean: On Stranger Tides (2011)</h1><br />
<span itemprop="description">Jack Sparrow and Barbossa embark on a quest to<br />
find the elusive fountain of youth, only to discover that Blackbeard and<br />
his daughter are after it too.</span><br />
Director:<br />
<div itemprop="director" itemscope itemtype="http://schema.org/People"><br />
<span itemprop="name">Rob Marshall</span><br />
</div><br />
</syntaxhighlight><br />
<br />
= Syntax highlighting tests=<br />
<br />
Tentative conclusion: For now, use html5strict language type for html5 examples. <br />
<br />
== HTML4 syntax highlighting ==<br />
<br />
Taken from [http://schema.org/Movie schema.org], without any XMLisation (uses 'itemscope' value-less attribute):<br />
<br />
<syntaxhighlight lang="html4strict" line start="100" highlight="5"><br />
<div itemscope itemtype="http://schema.org/Movie"><br />
<h1 itemprop="name">Pirates of the Carribean: On Stranger Tides (2011)</h1><br />
<span itemprop="description">Jack Sparrow and Barbossa embark on a quest to<br />
find the elusive fountain of youth, only to discover that Blackbeard and<br />
his daughter are after it too.</span><br />
Director:<br />
<div itemprop="director" itemscope itemtype="http://schema.org/People"><br />
<span itemprop="name">Rob Marshall</span><br />
</div><br />
</syntaxhighlight><br />
<br />
<br />
<br />
<br />
== Text syntax highlighting ==<br />
<br />
As above, with different highlighter ('text'):<br />
<br />
<syntaxhighlight lang="text" line start="100" highlight="5"><br />
<div itemscope itemtype="http://schema.org/Movie"><br />
<h1 itemprop="name">Pirates of the Carribean: On Stranger Tides (2011)</h1><br />
<span itemprop="description">Jack Sparrow and Barbossa embark on a quest to<br />
find the elusive fountain of youth, only to discover that Blackbeard and<br />
his daughter are after it too.</span><br />
Director:<br />
<div itemprop="director" itemscope itemtype="http://schema.org/People"><br />
<span itemprop="name">Rob Marshall</span><br />
</div><br />
</syntaxhighlight><br />
<br />
<br />
'''Note:''' Trying 'html' as a language does not work.</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75916WebSchemas/SellerVendorCleanup2014-08-15T09:02:54Z<p>Danbri: updated seller description after discussion</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
=== Main points ===<br />
<br />
<br />
* Use existing 'provider' property to describe the service provider, service operator, or service performer (see provider in exchange model in PDF) and update its description to more clearly indicate this intended usage;<br />
* Use existing 'seller' property to describe the entities which sell or offer a service on behalf of the actual service provider (see seller in exchange model). In the case of flights, this would be the airline through which a flight was booked. If a 'seller' is not provided, it is assumed the 'provider' is also the 'seller'.<br />
* Introduce a ‘broker’ property to describe entities that map to the broker concept in the exchange model.<br />
* deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property<br />
* deprecate 'vendor' in favor of re-using 'seller'<br />
* deprecate ‘merchant’ in favor of re-using ‘seller’<br />
* deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described 'provider'<br />
<br />
<br />
=== Implementation Details ===<br />
<br />
''Additions (broker) and clarifications (provider, seller)''<br />
<br />
* '''broker''': <br />
** add a new broker property.<br />
** description: "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."<br />
** Expected types: domain includes Order and Reservation (needed as 'broker' supercedes 'bookingAgent'); ''anything else''?; range includes Person and Organization.<br />
* '''provider:'''<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery, due to 'carrier' being supercededBy 'provider'.<br />
* '''seller:'''<br />
** old text: "The organization or person making the offer."<br />
** new text: "An entity which offers (sells / leases / lends / loans) the services / goods. A seller may also be a provider"<br />
** earlier suggestion: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider." ([http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0164.html see discussion])<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)<br />
<br />
''supercededBy properties''<br />
<br />
* '''bookingAgent''':<br />
** bookingAgent supercededBy broker.<br />
** old text: "If the reservation was not booked directly through the provider, the third-party booking agent can be recorded through this property."<br />
** new text: "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."<br />
* '''vendor''':<br />
** vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
** 'vendor' domain was BuyAction -- added this to seller; 'vendor' was supropertyof participant; also added to seller.<br />
* '''merchant:'''<br />
** merchant supercededBy seller.<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order; added to seller.<br />
* '''carrier:'''<br />
** carrier supercededBy provider.<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** Note that Flight, ParcelDelivery values (added with these changes) are acceptable values for 'provider' property.</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75907WebSchemas/SellerVendorCleanup2014-08-14T19:46:24Z<p>Danbri: Added Order to domain includes for 'broker' property.</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
=== Main points ===<br />
<br />
<br />
* Use existing 'provider' property to describe the service provider, service operator, or service performer (see provider in exchange model in PDF) and update its description to more clearly indicate this intended usage;<br />
* Use existing 'seller' property to describe the entities which sell or offer a service on behalf of the actual service provider (see seller in exchange model). In the case of flights, this would be the airline through which a flight was booked. If a 'seller' is not provided, it is assumed the 'provider' is also the 'seller'.<br />
* Introduce a ‘broker’ property to describe entities that map to the broker concept in the exchange model.<br />
* deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property<br />
* deprecate 'vendor' in favor of re-using 'seller'<br />
* deprecate ‘merchant’ in favor of re-using ‘seller’<br />
* deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described 'provider'<br />
<br />
<br />
=== Implementation Details ===<br />
<br />
''Additions (broker) and clarifications (provider, seller)''<br />
<br />
* '''broker''': <br />
** add a new broker property.<br />
** description: "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."<br />
** Expected types: domain includes Order and Reservation (needed as 'broker' supercedes 'bookingAgent'); ''anything else''?; range includes Person and Organization.<br />
* '''provider:'''<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery, due to 'carrier' being supercededBy 'provider'.<br />
* '''seller:'''<br />
** old text: "The organization or person making the offer."<br />
** new text: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider."<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)<br />
<br />
''supercededBy properties''<br />
<br />
* '''bookingAgent''':<br />
** bookingAgent supercededBy broker.<br />
** old text: "If the reservation was not booked directly through the provider, the third-party booking agent can be recorded through this property."<br />
** new text: "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."<br />
* '''vendor''':<br />
** vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
** 'vendor' domain was BuyAction -- added this to seller; 'vendor' was supropertyof participant; also added to seller.<br />
* '''merchant:'''<br />
** merchant supercededBy seller.<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order; added to seller.<br />
* '''carrier:'''<br />
** carrier supercededBy provider.<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** Note that Flight, ParcelDelivery values (added with these changes) are acceptable values for 'provider' property.</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75906WebSchemas/SellerVendorCleanup2014-08-14T19:21:41Z<p>Danbri: /* Implementation Details */</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
=== Main points ===<br />
<br />
<br />
* Use existing 'provider' property to describe the service provider, service operator, or service performer (see provider in exchange model in PDF) and update its description to more clearly indicate this intended usage;<br />
* Use existing 'seller' property to describe the entities which sell or offer a service on behalf of the actual service provider (see seller in exchange model). In the case of flights, this would be the airline through which a flight was booked. If a 'seller' is not provided, it is assumed the 'provider' is also the 'seller'.<br />
* Introduce a ‘broker’ property to describe entities that map to the broker concept in the exchange model.<br />
* deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property<br />
* deprecate 'vendor' in favor of re-using 'seller'<br />
* deprecate ‘merchant’ in favor of re-using ‘seller’<br />
* deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described 'provider'<br />
<br />
<br />
=== Implementation Details ===<br />
<br />
''Additions (broker) and clarifications (provider, seller)''<br />
<br />
* '''broker''': <br />
** add a new broker property.<br />
** description: "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."<br />
** Expected types: domain includes Reservation (needed as 'broker' supercedes 'bookingAgent'); anything else? (TODO); range includes Person and Organization.<br />
* '''provider:'''<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery, due to 'carrier' being supercededBy 'provider'.<br />
* '''seller:'''<br />
** old text: "The organization or person making the offer."<br />
** new text: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider."<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)<br />
<br />
''supercededBy properties''<br />
<br />
* '''bookingAgent''':<br />
** bookingAgent supercededBy broker.<br />
** old text: "If the reservation was not booked directly through the provider, the third-party booking agent can be recorded through this property."<br />
** new text: "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."<br />
* '''vendor''':<br />
** vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
** 'vendor' domain was BuyAction -- added this to seller; 'vendor' was supropertyof participant; also added to seller.<br />
* '''merchant:'''<br />
** merchant supercededBy seller.<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order; added to seller.<br />
* '''carrier:'''<br />
** carrier supercededBy provider.<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** Note that Flight, ParcelDelivery values (added with these changes) are acceptable values for 'provider' property.</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75905WebSchemas/SellerVendorCleanup2014-08-14T19:19:25Z<p>Danbri: /* Implementation Details */</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
=== Main points ===<br />
<br />
<br />
* Use existing 'provider' property to describe the service provider, service operator, or service performer (see provider in exchange model in PDF) and update its description to more clearly indicate this intended usage;<br />
* Use existing 'seller' property to describe the entities which sell or offer a service on behalf of the actual service provider (see seller in exchange model). In the case of flights, this would be the airline through which a flight was booked. If a 'seller' is not provided, it is assumed the 'provider' is also the 'seller'.<br />
* Introduce a ‘broker’ property to describe entities that map to the broker concept in the exchange model.<br />
* deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property<br />
* deprecate 'vendor' in favor of re-using 'seller'<br />
* deprecate ‘merchant’ in favor of re-using ‘seller’<br />
* deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described 'provider'<br />
<br />
<br />
=== Implementation Details ===<br />
<br />
''Additions (broker) and clarifications (provider, seller)''<br />
<br />
* '''broker''': <br />
** add a new broker property.<br />
** description: "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."<br />
** Expected types: domain includes Reservation (needed as 'broker' supercedes 'bookingAgent'); anything else? (TODO); range includes Person and Organization.<br />
* '''provider:'''<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery, due to 'carrier' being supercededBy 'provider'.<br />
* '''seller:'''<br />
** old text: "The organization or person making the offer."<br />
** new text: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider."<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)<br />
<br />
''supercededBy properties''<br />
<br />
* '''bookingAgent''':<br />
** bookingAgent supercededBy broker.<br />
** old text: "If the reservation was not booked directly through the provider, the third-party booking agent can be recorded through this property."<br />
** new text: "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."<br />
* '''vendor''':<br />
** vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
** 'vendor' domain was BuyAction -- added this to seller; 'vendor' was supropertyof participant; also added to seller.<br />
* '''merchant:'''<br />
** merchant supercededBy seller.<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order; added to seller.<br />
* '''carrier:'''<br />
** carrier supercededBy provider.<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** TODO: check Flight, ParcelDelivery acceptable w/ 'provider'</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75904WebSchemas/SellerVendorCleanup2014-08-14T19:17:54Z<p>Danbri: /* Changes proposed */</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
=== Main points ===<br />
<br />
<br />
* Use existing 'provider' property to describe the service provider, service operator, or service performer (see provider in exchange model in PDF) and update its description to more clearly indicate this intended usage;<br />
* Use existing 'seller' property to describe the entities which sell or offer a service on behalf of the actual service provider (see seller in exchange model). In the case of flights, this would be the airline through which a flight was booked. If a 'seller' is not provided, it is assumed the 'provider' is also the 'seller'.<br />
* Introduce a ‘broker’ property to describe entities that map to the broker concept in the exchange model.<br />
* deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property<br />
* deprecate 'vendor' in favor of re-using 'seller'<br />
* deprecate ‘merchant’ in favor of re-using ‘seller’<br />
* deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described 'provider'<br />
<br />
<br />
=== Implementation Details ===<br />
<br />
* '''broker''': <br />
** add a new broker property.<br />
** description: "An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred."<br />
** Expected types: domain includes Reservation (needed as 'broker' supercedes 'bookingAgent'); anything else? (TODO); range includes Person and Organization.<br />
* '''bookingAgent''':<br />
** bookingAgent supercededBy broker.<br />
** old text: "If the reservation was not booked directly through the provider, the third-party booking agent can be recorded through this property."<br />
** new text: "'bookingAgent' is an out-dated term indicating a 'broker' that serves as a booking agent."<br />
* '''vendor''':<br />
** vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
** 'vendor' domain was BuyAction -- added this to seller; 'vendor' was supropertyof participant; also added to seller.<br />
* '''merchant:'''<br />
** merchant supercededBy seller.<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order; added to seller.<br />
* '''carrier:'''<br />
** carrier supercededBy provider.<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** TODO: check Flight, ParcelDelivery acceptable w/ 'provider'<br />
* '''provider:'''<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery, due to 'carrier' being supercededBy 'provider'.<br />
* '''seller:'''<br />
** old text: "The organization or person making the offer."<br />
** new text: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider."<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75902WebSchemas/SellerVendorCleanup2014-08-14T18:44:20Z<p>Danbri: /* Changes proposed */</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
* Add a a new broker property.<br />
** from bookingAgent, we add domain include for Reservation; range includes Person, Organization.<br />
* bookingAgent supercededBy broker.<br />
** TODO: update text? check constraints.<br />
* vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
* vendor domain was BuyAction -- added this to seller. it was supropertyof participant; also added to seller.<br />
* merchant supercededBy seller<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
** new text: "'merchant' is an out-dated term for 'seller'."<br />
** old domain included: Order<br />
* carrier supercededBy provider<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** TODO: check Flight, ParcelDelivery acceptable w/ 'provider'<br />
* provider<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery<br />
* seller<br />
** old text: "The organization or person making the offer."<br />
** new text: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider."<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SellerVendorCleanup&diff=75901WebSchemas/SellerVendorCleanup2014-08-14T18:43:45Z<p>Danbri: Proposed changes for seller/broker etc</p>
<hr />
<div><br />
<br />
<br />
This wiki entry tracks the details needed to implement proposal 'Beta'<br />
<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html discussion on public-vocabs]<br />
* [https://github.com/rvguha/schemaorg/issues/88 github issue]<br />
* [https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf overview doc]<br />
<br />
== Changes proposed ==<br />
<br />
Exact and final details will be in github, but this gives a medium-level overview.<br />
<br />
* Add a a new broker property.<br />
** from bookingAgent, we add domain include for Reservation; range includes Person, Organization.<br />
* bookingAgent supercededBy broker.<br />
** TODO: update text? check constraints.<br />
* vendor supercededBy seller.<br />
** old text: "A sub property of participant. The seller. The participant/person/organization that sold the object."<br />
** new text: 'vendor' is an out-dated term for seller."<br />
* vendor domain was BuyAction -- added this to seller. it was supropertyof participant; also added to seller.<br />
* merchant supercededBy seller<br />
** old text: "The party taking the order (e.g. Amazon.com is a merchant for many sellers)""<br />
old domain included: Order<br />
new: 'merchant' is an out-dated term for 'seller'.<br />
* carrier supercededBy provider<br />
** old text: "The party responsible for the parcel delivery."<br />
** new text: "'carrier' is an out-dated term indicating the 'provider' for parcel delivery."<br />
** TODO: check Flight, ParcelDelivery acceptable w/ 'provider'<br />
* provider<br />
** new text: "The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller."<br />
** old text: The person or organization providing the service, reservation, or creative work. The provider may subcontract out the service.<br />
** additional domain included: ParcelDelivery<br />
* seller<br />
** old text: "The organization or person making the offer."<br />
** new text: "The entity which sells or offers services or goods. The seller may sell / offer goods and services on behalf of a provider."<br />
** new domains included: BuyAction, Order (since we're superceding 'merchant', 'vendor')<br />
** new super-property: participant (cf. vendor)</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/QuotationSchema&diff=75479WebSchemas/QuotationSchema2014-08-08T13:52:10Z<p>Danbri: githubbed</p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=Quotation|status=Proposal}}<br />
<br />
<br />
==Quotation schema for schema.org==<br />
<br />
Update (2014-08-04): schema [https://github.com/danbri/schemaorg/blob/sdo-quotation/data/sdo-quotation-schema.rdfa drafted on github] for discussion. See [http://sdo-wip1.appspot.com/Quotation test site].<br />
<br />
This is a draft proposal for a Quotation schema, as an addition to schema.org.<br />
<br />
The goal is to be able to describe excerpts from larger works, and give some key information to help contextualize - such as associated people, events, places.<br />
<br />
* Add a new type Quotation, a subtype of CreativeWork. Description "A quotation from some work, attributable to real world author and - if associated with a fictional character - to any fictional Person." This would typically use 'name', 'description', from Thing; 'author' from CreativeWork.<br />
* Some mechanism for referencing the source or origin, i.e. the place (book, film, essay, etc.) in which the quotation appeared. Note that CreativeWork has 'isBasedOnUrl' (which should perhaps be simply an isBasedOn relationship; so let's add a property with that name too)<br />
* The date the quotation was made can be expressed with 'dateCreated'or 'datePublished' from CreativeWork; probably latter is best. These take a Date value.<br />
* spokenByCharacter, a new property for Quotation. "the (e.g. fictional) character to whom the quotation is attributed within the containing CreativeWork."<br />
* To describe the subject of the quotation, for example- love, art, math, we use existing CreativeWork constructs. Broad topics can be expressed with 'keywords' from CreativeWork ... or for more precise reference to topics (related people, places, things), the 'about' property is available.<br />
* incorrectlyAttributedTo - relates a quotation to a Person that the quotation is often mistakenly attributed to.<br />
<br />
Three new utility properties that attach to CreativeWork but are particularly relevant here:<br />
<br />
* aboutEvent - Relates a CreativeWork (e.g. a Quotation) to an event it describes. e.g. The Mutiny on the Bounty<br />
* fromEvent - Relates a CreativeWork (e.g. a Quotation) to an event at which it was spoken, e.g. The Mutiny on the Bounty<br />
* addressee - Relates a CreativeWork (e.g. a Quotation) to a Person ''or Organization'' that it was addressed to. <br />
<br />
==Discussion==<br />
<br />
* It has been suggested that incorrectlyAttributedTo may not supply a lot of good data and that "sometimes people confuse mis-attribution for lack of evidence " -jg<br />
* Could an addressee be more than a Person? I am thinking of speeches, which may be delivered to an organization or some amorphous group. (Vicki Tardif Holland)<br />
** have added another expected type, "Organization"<br />
** Q: For quotations addressed to amorphous audiences (e.g. 'sermon on the mount'), can we associate an event somehow instead?<br />
* (via Quotations book), " something along the lines of source type I think e.g. from a movie, speech, radio show, etc. ?"<br />
** (can't we get this indirectly from the associated CreativeWork?)<br />
<br />
==External Links==<br />
<br />
* [https://meta.wikimedia.org/wiki/Structured_Wikiquote Structured Wikiquote] project, which aims to build on to of Wikidata<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2013May/0174.html public-vocabs thread]<br />
* Freebase Quotation [http://www.freebase.com/m/069dd entry] and [http://www.freebase.com/m/02hyl2s schema]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/QuotationSchema&diff=75478WebSchemas/QuotationSchema2014-08-08T13:41:19Z<p>Danbri: added structured wikiquote</p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=Quotation|status=Proposal}}<br />
<br />
<br />
==Quotation schema for schema.org==<br />
<br />
This is a draft proposal for a Quotation schema, as an addition to schema.org.<br />
<br />
The goal is to be able to describe excerpts from larger works, and give some key information to help contextualize - such as associated people, events, places.<br />
<br />
* Add a new type Quotation, a subtype of CreativeWork. Description "A quotation from some work, attributable to real world author and - if associated with a fictional character - to any fictional Person." This would typically use 'name', 'description', from Thing; 'author' from CreativeWork.<br />
* Some mechanism for referencing the source or origin, i.e. the place (book, film, essay, etc.) in which the quotation appeared. Note that CreativeWork has 'isBasedOnUrl' (which should perhaps be simply an isBasedOn relationship; so let's add a property with that name too)<br />
* The date the quotation was made can be expressed with 'dateCreated'or 'datePublished' from CreativeWork; probably latter is best. These take a Date value.<br />
* spokenByCharacter, a new property for Quotation. "the (e.g. fictional) character to whom the quotation is attributed within the containing CreativeWork."<br />
* To describe the subject of the quotation, for example- love, art, math, we use existing CreativeWork constructs. Broad topics can be expressed with 'keywords' from CreativeWork ... or for more precise reference to topics (related people, places, things), the 'about' property is available.<br />
* incorrectlyAttributedTo - relates a quotation to a Person that the quotation is often mistakenly attributed to.<br />
<br />
Three new utility properties that attach to CreativeWork but are particularly relevant here:<br />
<br />
* aboutEvent - Relates a CreativeWork (e.g. a Quotation) to an event it describes. e.g. The Mutiny on the Bounty<br />
* fromEvent - Relates a CreativeWork (e.g. a Quotation) to an event at which it was spoken, e.g. The Mutiny on the Bounty<br />
* addressee - Relates a CreativeWork (e.g. a Quotation) to a Person ''or Organization'' that it was addressed to. <br />
<br />
==Discussion==<br />
<br />
* It has been suggested that incorrectlyAttributedTo may not supply a lot of good data and that "sometimes people confuse mis-attribution for lack of evidence " -jg<br />
* Could an addressee be more than a Person? I am thinking of speeches, which may be delivered to an organization or some amorphous group. (Vicki Tardif Holland)<br />
** have added another expected type, "Organization"<br />
** Q: For quotations addressed to amorphous audiences (e.g. 'sermon on the mount'), can we associate an event somehow instead?<br />
* (via Quotations book), " something along the lines of source type I think e.g. from a movie, speech, radio show, etc. ?"<br />
** (can't we get this indirectly from the associated CreativeWork?)<br />
<br />
==External Links==<br />
<br />
* [https://meta.wikimedia.org/wiki/Structured_Wikiquote Structured Wikiquote] project, which aims to build on to of Wikidata<br />
* [http://lists.w3.org/Archives/Public/public-vocabs/2013May/0174.html public-vocabs thread]<br />
* Freebase Quotation [http://www.freebase.com/m/069dd entry] and [http://www.freebase.com/m/02hyl2s schema]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/Vehicles&diff=74791WebSchemas/Vehicles2014-08-01T07:07:20Z<p>Danbri: Writing 'terms' instead of 'elements', to avoid confusing XML people.</p>
<hr />
<div>{{Template:SchemaDotOrgProposal|name=for Vehicles (Cars, Bikes, Boats, etc.) Sales and Rental in Schema.org|status=Proposal}}<br />
== Proposal for Vehicles - Cars, Bikes, Boats - Rental and Sales ==<br />
Authors: <br />
*[http://www.heppnetz.de Martin Hepp], mheppATcomputerDOTorg<br />
*[http://makolab.com Karol Szczepański] karolDOTszczepanskiATmakolabDOTpl<br />
*[http://makolab.com Mirek Sopek] sopekATmakolabDOTcom<br />
<br />
This proposal defines a small set of additional types and properties for schema.org that will cover typical scenarios related to the sales and rental of vehicles of typical kinds, like new and used cars, bikes, and boats, and related services.<br />
<br />
It is a first contribution of the [http://www.automotive-ontology.org/ Automotive Ontology Working Group].<br />
<br />
== Overview == <br />
This proposal builds on the following vehicle-related extensions for [http://purl.org/goodrelations/ GoodRelations], the e-commerce model of schema.org:<br />
<br />
*'''Vehicle Sales Ontology (VSO),''' http://purl.org/vso/ns<br />
*'''Volkswagen Vehicles Ontology (VVO),''' http://purl.org/vvo/ns<br />
*'''Used Cars Ontology (UCO),''' http://purl.org/uco/ns<br />
<br />
It adds the core classes, properties and enumerated values for describing cars, trucks, busses, bikes, and boats and their features. For describing commercial aspects of related offers, http://schema.org/Offer already provides the necessary level of detail. Thus, this proposal does not add new elements for commercial features.<br />
<br />
The proposal supports the description of actual new and used vehicles as well as make and model information for vehicle data-sheets etc. However, configuration and buildability information (e.g. which alternative options are available and how they can be combined) is outside the scope of this proposal. We plan a second proposal for the non-trivial problem of vehicle configuration and vehicle range information, which will complement this proposal.<br />
<br />
Also not included in this proposal are elements for financing as additional payment option information. Such should be added by another industry-neutral extension proposal. The [http://purl.org/vvo/ns Volkswagen Vehicles Ontology (VVO)] may serve as useful input for that, because it is based on the GoodRelations core model of payment. We may submit a respective extension proposal for financing in the future.<br />
<br />
== Motivating Examples ==<br />
* A site with used car offers wants to mark-up its individual car offers using schema.org.<br />
* A car manufacturer wants to mark up its product model information.<br />
* A rental car company wants to mark-up its fleet, rental offers, and conditions.<br />
<br />
While the original intention was support for the automotive industry, basic support for bikes and boats has already been included, too.<br />
<br />
Support for aircraft information could be added with moderate effort but is left out for the moment, because we think this should be a separate extension proposal based on additional domain expertise.<br />
<br />
'''Examples of Web Sites:'''<br />
*http://www.cars.com/vehicledetail/detail/612273235/overview/<br />
* More to be added.<br />
<br />
== Design Principles ==<br />
# '''Reuse commercial properties from http://schema.org/Offer and the underlying GoodRelations conceptual model.''' Don't mix modeling vehicles with modeling offers to buy, rent, or service vehicles.<br />
# '''Standardize objective vehicle characteristics and defer consensus for diverse and vendor-specific vehicle characteristics:''' Vehicles, and in particular cars, can have a hundred features and more. Some are very objective (e.g. fuel consumption under lab conditions, dimensions); some are best handled as text (e.g. interior colors), and some are very vendor-specific, e.g. engine types, safety features, etc.<br />
# '''Balance between mark-up effort and usefulness of data:''' The data should be as useful as possible for search engines and other consumers, but the effort for Web developers must be also kept at a minimum.<br />
<br />
These design principles are implemented as follows:<br />
<br />
#Quantitative properties that do not require a unit of measurement can be modeled as either a plain numeric literal (http://schema.org/Number) or a http://schema.org/QuantitativeValue. Typical cases are the number of seats or doors. For a single value, a literal is sufficient. For a range, a http://schema.org/QuantitativeValue is more appropriate.<br />
#Qualitative properties, like fuel types or body styles can be modeled either using a Freebase URI, site-specific URI, or plain text. If a site is able to provide the URI of a authoritative definition for a value or characteristic, this is more useful, but if the site can provide only a string, this is better than nothing.<br />
#Limit the number of standardized properties and use the complementing [http://www.w3.org/wiki/WebSchemas/PropertyValuePairs property-values proposal for schema.org] for vendor-specific vehicle features.<br />
<br />
== Extension Proposal ==<br />
===Git Repository===<br />
The latest version of the proposal is now in a Git repository at: https://mfhepp@bitbucket.org/mfhepp/sdo-vehicles.git.<br />
The earlier Mercurial repository has been deprecated and set to private in order to avoid confusion.<br />
<br />
=== Development Version on GAE ===<br />
<br />
A '''development version''' of the proposal is available at: http://sdo-vehicles.appspot.com/.<br />
See e.g.<br />
* http://sdo-vehicles.appspot.com/Car<br />
* http://sdo-vehicles.appspot.com/Van<br />
* http://sdo-vehicles.appspot.com/Motorcycle<br />
<br />
In the following, we list the elements in the proposal. '''The authoritative proposal is the version in the Git repository at: https://mfhepp@bitbucket.org/mfhepp/sdo-vehicles.git.'''<br />
<br />
=== Changes to Existing Elements ===<br />
* The textual definitions for Car and Vehicle will be augmented.<br />
* Car will be a superclass of the new MotorizedRoadVehicle class instead of Vehicle.<br />
=== New Terms ===<br />
The following terms will be added:<br />
==== New Classes ====<br />
*MotorizedRoadVehicle<br />
**A motorized road vehicle is a wheeled land vehicle whose main propulsion is provided by an engine or motor.<br />
*Truck<br />
**A lorry (British English) or truck (American English) is a motor vehicle designed to transport cargo.<br />
*Van<br />
**A van is a kind of vehicle used for transporting goods or groups of people. It is usually a box-shaped vehicle on four wheels, about the same width and length as a large automobile, but taller and usually higher off the ground, also referred to as a light commercial vehicle or LCV.<br />
*MotorizedBicycle<br />
**A motorized bicycle is a bicycle with an attached motor used to power the vehicle, or to assist with pedaling.<br />
*BusOrCoach<br />
**A bus (also omnibus or autobus) is a road vehicle designed to carry passengers. Buses have a capacity as high as 300 passengers and are widely used for public transportation. Coaches are luxury busses, usually in service for long distance travel.<br />
*Motorcycle<br />
**A motorcycle or motorbike is a single-track, two-wheeled motor vehicle.<br />
*Bike<br />
**A bicycle or bike is a pedal-driven, human-powered, single-track vehicle, having two wheels attached to a frame, one behind the other. Some bicycles have a small combustion or electric engine that assists with the pedaling.<br />
*Watercraft<br />
**A watercraft is a vehicle, vessel or craft designed to move across or through water.<br />
*Boat<br />
**A boat is a watercraft of modest size designed to float or plane, to provide passage across water.<br />
*MotorBoat<br />
**A motorboat is a boat which is powered by an engine.<br />
*SailingBoat<br />
**A sailboat or sailing boat is a boat propelled partly or entirely by sails.<br />
*SteeringPositionValue<br />
**A value indicating a steering position.<br />
*EmissionStandardValue<br />
**A value indicating the an emission standard.<br />
*TransmissionTypeValue<br />
**A value indicating a type of transmission. <br />
*DriveWheelConfigurationValue<br />
**A value indicating which roadwheels will receive torque.<br />
*EngineTypeValue<br />
**A value indicating an engine type. <br />
*FuelTypeValue<br />
**A value indicating a type of fuel. <br />
*BodyStyleValue<br />
**A value indicating the body style of a vehicle.<br />
*CarUsageType<br />
**A value indicating a special usage of a car, e.g. commercial rental, driving school, or as a taxi.<br />
<br />
==== New Properties ====<br />
*steeringPosition<br />
*fuelCapacity<br />
*numberOfOwners<br />
*roofLoad<br />
*fuelConsumption<br />
*cargoVolume<br />
*driveWheelConfiguration<br />
*wheelbase<br />
*payload<br />
*weightTotal<br />
*transmission<br />
*fuelType<br />
*engineDisplacement<br />
*mileageFromOdometer<br />
*bodyStyle<br />
*tongueWeight<br />
*doors<br />
*speed<br />
*meetsEmissionStandard<br />
*fuelEfficiency<br />
*gears<br />
*axles<br />
*engineType<br />
*seatingCapacity<br />
*trailerWeight<br />
*acceleration<br />
*enginePower<br />
*productionDate<br />
*specialUsageUsage<br />
*damages<br />
*firstRegistration<br />
*engineName<br />
*ACRISSCode<br />
*VIN<br />
*modelDate<br />
*colorInterior<br />
*interiorType<br />
*airbags<br />
*torque<br />
*emissionsCO2<br />
==== New Individuals ====<br />
*'''SteeringPositionValue:''' RightHandDriving and LeftHandDriving<br />
*'''FuelTypeValue:''' TwoStrokeMixture (other fuel types are readily available from DBPedia or Freebase)<br />
*'''DriveWheelConfigurationValue:''' 4WD, AWD, FWD, RWD<br />
*'''CarUsageType:''' RentalUsage, DrivingSchoolUsage, TaxiUsage<br />
<br />
=== Relationship to Other Proposals ===<br />
The proposal does not critically depend on, but '''will greatly benefit from the [[WebSchemas/PropertyValuePairs|property-value pairs]] proposal''' for the many vehicle feature details that are difficult to standardize in a global, vendor-independent form.<br />
<br />
== Markup Example ==<br />
<br />
=== HTML without RDFa or Microdata ===<br />
<syntaxhighlight lang="html5"><br />
<div ><br />
<strong>Contact Name: </strong> <span>Brent</span><br />
<div>$18,000</div><br />
<!-- Car Details --><br />
<div id="product"><br />
<strong>2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p>2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)</p><br />
<img href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong>Black</p><br />
<p><strong>Interior Color: </strong>Black</p><br />
<p><strong>Interior Type: </strong>Leather upholstery, wood paneling</p><br />
<p><strong>Model Year: </strong><time>2009</time></p> <br />
<p><strong>Transmission: </strong>6 speed Sports Automatic Dual Clutch</p> <br />
<p><strong>VIN: </strong>WVWZZZ1KZ9U######</p> <br />
<p><strong>Number of gears: </strong>6</p> <br />
<p><strong>Body: </strong>Hatchback</p><br />
<p><strong>Number of doors: </strong>3</p><br />
<p><strong>Number of seats: </strong>5</p><br />
<p><strong>Drive Type: </strong>Front Wheel Drive</p><br />
<p><strong>Engine: </strong>4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</p><br />
<p><strong>Engine Power: </strong>147 kw at 5100 rpm</p><br />
<p><strong>Fuel type: </strong>Petrol - Premium ULP</p><br />
<p><strong>Engine Size: </strong>1984 ccm</p><br />
<p><strong>Mileage: </strong>53100 km</p><br />
<p><strong>Number of airbags: </strong>6</p><br />
<p><strong>CO2 Emission Combined: </strong>192 g/km</p><br />
</div><br />
</syntaxhighlight><br />
<br />
=== Microdata ===<br />
<syntaxhighlight lang="html5"><br />
<!-- Seller Details --><br />
<div itemscope itemtype="http://schema.org/Person"><br />
<strong>Contact Name: </strong> <span itemprop="name givenName">Brent</span><br />
<div itemprop="makesOffer" itemscope itemtype="http://schema.org/Offer" itemref="product"><br />
<span itemprop="priceSpecification" itemscope <br />
itemtype="http://schema.org/UnitPriceSpecification"><br />
<meta itemprop="priceCurrency" content="USD">$<br />
<meta itemprop="price" content="18000">18,000<br />
</span><br />
</div><br />
</div><br />
<!-- Car Details --><br />
<div id="product" itemprop="itemOffered" itemscope itemtype="http://schema.org/Car"><br />
<strong itemprop="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p itemprop="description">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)</p><br />
<img itemprop="image" href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong><span itemprop="color">Black</span></p><br />
<p><strong>Interior Color: </strong><span itemprop="colorInterior">Black</span></p><br />
<p><strong>Interior Type: </strong><span itemprop="interiorType">Leather upholstery, <br />
wood paneling</span></p><br />
<p><strong>Model Year: </strong><time itemprop="modelDate">2009</time></p> <br />
<p><strong>Transmission: </strong><br />
<span itemprop="transmission">6 speed Sports Automatic Dual Clutch</span><br />
</p> <br />
<p><strong>VIN: </strong><span itemprop="VIN">WVWZZZ1KZ9U######</span></p> <br />
<p><strong>Number of gears: </strong><span itemprop="gears">6</span></p> <br />
<p><strong>Body: </strong><br />
<span itemprop="bodyStyle">Hatchback</span><br />
</p><br />
<p><strong>Number of doors: </strong><span itemprop="doors">3</span></p><br />
<p><strong>Number of seats: </strong><span itemprop="seatingCapacity">5</span></p><br />
<p><strong>Drive Type: </strong><br />
<link itemprop="driveWheelConfiguration" href="http://schema.org/FWD" /><br />
Front Wheel Drive<br />
</p><br />
<p><strong>Engine: </strong><br />
<span itemprop="engineName">4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</span><br />
</p><br />
<p><strong>Engine Power: </strong><br />
<span itemprop="enginePower" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">147</span> <br />
<meta itemprop="unitCode" content="KWT">kw<br />
at <span itemprop="valueReference" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<meta itemprop="name" content="referenceRPM"> <br />
<span itemprop="value">5100</span> <br />
<meta itemprop="unitCode" content="RPM">rpm<br />
</span><br />
</span><br />
</p><br />
<p><strong>Fuel type: </strong><br />
<span itemprop="fuelType">Petrol - Premium ULP</span> <br />
</p><br />
<p><strong>Engine Size: </strong><br />
<span itemprop="engineDisplacement" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">1984</span> <br />
<meta itemprop="unitCode" content="CMQ">ccm<br />
</span><br />
</p><br />
<p><strong>Mileage: </strong><br />
<span itemprop="mileageFromOdometer" itemscope itemtype="http://schema.org/QuantitativeValue"><br />
<span itemprop="value">53100</span> <br />
<meta itemprop="unitCode" content="KMT">km<br />
</span><br />
</p><br />
<p><strong>Number of airbags: </strong><span itemprop="airbags">6</span></p><br />
<p><strong>CO2 Emission Combined: </strong><span itemprop="emissionCO2">192</span> g/km</p><br />
</div><br />
</syntaxhighlight><br />
<br />
=== RDFa ===<br />
<br />
<syntaxhighlight lang="html5"><br />
<!-- Seller Details --><br />
<div vocab="http://schema.org/" typeof="Person"><br />
<strong>Contact Name: </strong> <span property="name givenName">Brent</span><br />
<div property="makesOffer" typeof="Offer"><br />
<span property="priceSpecification" typeof="UnitPriceSpecification"><br />
<meta property="priceCurrency" content="USD">$<br />
<meta property="price" content="18000">18,000<br />
</span><br />
<!-- Car Details --><br />
<div id="product" property="itemOffered" typeof="Car"><br />
<strong property="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p property="description">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox in perfect <br />
mechanical condition and low kilometres. It's impressive 2.0 litre turbo engine makes <br />
every drive a fun experience. Well looked after by one owner with full service history. <br />
It drives like new and has only done 50,000kms. (...)<br />
</p><br />
<img property="image" href="2009_Volkswagen_Golf_V_GTI_MY09.png" /><br />
<p><strong>Color: </strong><span property="color">Black</span></p><br />
<p><strong>Interior Color: </strong><span property="colorInterior">Black</span></p><br />
<p><strong>Interior Type: </strong><span property="interiorType">Leather upholstery, wood paneling</span></p><br />
<p><strong>Model Year: </strong><time property="modelDate">2009</time></p> <br />
<p><strong>Transmission: </strong><br />
<span property="transmission">6 speed Sports Automatic Dual Clutch</span><br />
</p> <br />
<p><strong>VIN: </strong><span property="VIN">WVWZZZ1KZ9U######</span></p> <br />
<p><strong>Number of gears: </strong><span property="gears">6</span></p> <br />
<p><strong>Body: </strong><br />
<span property="bodyStyle">Hatchback</span><br />
</p><br />
<p><strong>Number of doors: </strong><span property="doors">3</span></p><br />
<p><strong>Number of seats: </strong><span property="seatingCapacity">5</span></p><br />
<p><strong>Drive Type: </strong><br />
<link property="driveWheelConfiguration" href="http://schema.org/FWD" /><br />
Front Wheel Drive<br />
</p><br />
<p><strong>Engine: </strong><br />
<span property="engineName">4 cylinder Petrol Turbo Intercooled 2.0 L (1984 cc)</span><br />
</p><br />
<p><strong>Engine Power: </strong><br />
<span property="enginePower" typeof="QuantitativeValue"><br />
<span property="value">147</span> <br />
<meta property="unitCode" content="KWT">kw<br />
at <span property="valueReference" typeof="QuantitativeValue"><br />
<meta property="name" content="referenceRPM"> <br />
<span property="value">5100</span> <br />
<meta property="unitCode" content="RPM">rpm<br />
</span><br />
</span><br />
</p><br />
<p><strong>Fuel type: </strong><br />
<span property="fuelType">Petrol - Premium ULP</span><br />
</p><br />
<p><strong>Engine Size: </strong><br />
<span property="engineDisplacement" typeof="QuantitativeValue"><br />
<span property="value">1984</span> <br />
<meta property="unitCode" content="CMQ">ccm<br />
</span><br />
</p><br />
<p><strong>Mileage: </strong><br />
<span property="mileageFromOdometer" typeof="QuantitativeValue"><br />
<span property="value">53100</span> <br />
<meta property="unitCode" content="KMT">km<br />
</span><br />
</p><br />
<p><strong>Number of airbags: </strong><span property="airbags">6</span></p><br />
<p><strong>CO2 Emission Combined: </strong><span property="emissionCO2">192</span> g/km</p><br />
</div><br />
</div><br />
</div><br />
</syntaxhighlight><br />
<br />
== Special Cases ==<br />
=== DBPedia and Freebase URIs as Values ===<br />
Several properties will accept either text or entities as a value. In the later case, it is beneficial if the publisher of the data can link locally defined value entities to Freebase or DBPedia entities, because this will allow consuming clients to better understand the data.<br />
<br />
This is built into the proposal, but not enforced nor directly explained in the textual definitions of the elements.<br />
<br />
'''Example:'''<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Car"><br />
<strong itemprop="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p itemprop="description">2009 Volkswagen(...)</p><br />
<p><strong>Transmission: </strong><br />
<div itemprop="transmission" itemscope itemtype="http://schema.org/TransmissionTypeValue"><br />
<span itemprop="name">6 speed Sports Automatic Dual Clutch</span><br />
<link itemprop="sameAs" href="http://www.freebase.com/m/01xc2y" /> <br />
</div><br />
</p> <br />
</div><br />
</syntaxhighlight><br />
<br />
It is also possible to directly use an authoritative URI as a value, but this will be more difficult to understand for some clients:<br />
<br />
<syntaxhighlight lang="html5"><br />
<div itemscope itemtype="http://schema.org/Car"><br />
<strong itemprop="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong><br />
<p itemprop="description">2009 Volkswagen(...)</p><br />
<p><strong>Transmission: </strong><br />
<link itemprop="transmission" href="http://www.freebase.com/m/01xc2y" /> 6 speed Sports Automatic Dual Clutch <br />
</div><br />
</syntaxhighlight><br />
<br />
=== Non-standard Vehicle Features ===<br />
<br />
For vehicle features that are do not match the properties of the extension proposal, we recommend using the [[WebSchemas/PropertyValuePairs|property-value proposal for schema.org]].<br />
<br />
For examples of this pattern, see [[WebSchemas/PropertyValuePairs#Markup_Examples|WebSchemas/PropertyValuePairs#Markup_Examples]].<br />
<br />
== Comments and Feedback ==<br />
Please join the [https://plus.google.com/communities/104510681993581444051 Automotive Ontology Working Group] or post to the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs@w3.org mailing list] if you want to raise issues or have suggestions on how to improve the proposal.<br />
<br />
[[Category:WebSchemas]]<br />
[[Category:WebSchemaProposals]]</div>Danbrihttps://www.w3.org/wiki/index.php?title=WebSchemas/SchemaDotOrgProposals&diff=74764WebSchemas/SchemaDotOrgProposals2014-07-31T13:17:45Z<p>Danbri: freshened intro section</p>
<hr />
<div>== Proposals for Schema.org ==<br />
<br />
* History: 2012-13 draft [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext schema files] were hosted in W3C's Mercurial repository.<br />
* From 2014, schema.org runs on [https://github.com/rvguha/schemaorg opensource software], and uses Git(hub) for schema collaboration. Examples and schemas are in the [https://github.com/rvguha/schemaorg/tree/master/data data/] area of the repository.<br />
<br />
This page attempts to offer a canonical list of public proposals for [http://schema.org/docs/full.html schema.org vocabulary] extensions and improvements. It is not always up to date. <br />
<br />
Schema.org issues are now tracked [https://github.com/rvguha/schemaorg/issues at github]. This will replace use of [http://www.w3.org/2011/webschema/track/ W3C's issue tracker] except for matters of coordination with other vocabularies and W3C specifications.<br />
<br />
Schema.org public discussions happen via the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs]@w3.org W3C mailing list for discussions. <br />
<br />
Sometimes proposals evolve from offlist and face-to-face discussions; when possible, advance warning of 'expected' or possible proposals can be indicated here ([http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0102.html announced 24 Feb 2012]).<br />
<br />
* Editor: Dan Brickley (danbri@danbri.org). <br />
* Status: Feel free to update the table for accuracy and detail, but discuss status-oriented changes with the editor to avoid confusion.<br />
* If you add a proposal, please also mail the [http://lists.w3.org/Archives/Public/public-vocabs/ public-vocabs@w3.org list] to start a discussion (and link it from here)<br />
<br />
Proposals should include ''markup examples'' as well as vocabulary definitions, and should point to related and prior work. It is also important to give examples of real sites that have suitable content. See [http://www.w3.org/2006/tools/wiki/W3CWikiNotes#Posting_Markup_examples Posting markup examples in W3C wikis] documentation for details on how to post examples here. <br />
<br />
Schema.org proposals can take any form during discussions, but ultimately they should take the form of HTML+RDFa schema definitions; some real examples are in the [https://github.com/rvguha/schemaorg/tree/master/data data/ area] of the schema.org repository.<br />
<br />
'''Note''': When preparing a proposal, we need to know for each type and property, its name and description, alongside examples of usage. There are lots of different ways in which these can be prepared: wiki pages, text files, spreadsheets, PDFs etc. Do note that each property is considered as a global entity, ie. a property called 'foo' gets just one description - you can't give different descriptions for its use with the "Person" type, versus its use with the CreativeWork type. Ideally, develop a machine-readable proposal and test it using the software on Github.<br />
<br />
To search just these proposals, the issue tracker and schema.org-related mailing lists, try a [http://www.google.com/cse/home?cx=003736913799082383568:c44bi0_xxek this custom search].<br />
<br />
<br />
== Proposals and Discussion ==<br />
<br />
These proposals are working towards inclusion in schema.org.<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/associatedMediaToThing|Change domain of associatedMedia to Thing]]<br />
|Proposal<br />
|Change the domain of http://schema.org/associatedMedia to http://schema.org/Thing<br />
|Enables many more types to associate contained or complementary media content, beyond CreativeWork.<br />
|Discussion at http://lists.w3.org/Archives/Public/public-vocabs/2014May/0224.html<br />
|-<br />
|[[WebSchemas/PropertyValuePairs|Property-Value Pairs]]<br />
|Proposal<br />
|Adding support for arbitrary property-value pairs. Useful for product features and proprietary features of places.<br />
|One new type http://schema.org/PropertyValue, two new properties for this type (unitText, propertyID), changes to domain and range for unitCode, value, minValue, maxValue, and valueReference properties; one new property additionalProperty for http://schema.org/Place OR http://schema.org/Product.<br />
|Mirrors an upcoming feature in [http://purl.org/goodrelations/ GoodRelations].<br />
|-<br />
|[[WebSchemas/Orders_enhancement|Orders Schema update]]<br />
|Proposal<br />
|Proposal to add order line and parcel delivery support in the Orders Schema.<br />
|One new Type: OrderItem, and added properties for one existent Type: Order<br />
|<br />
|-<br />
|[[WebSchemas/Periodicals,_Articles_and_Multi-volume_Works|Periodicals, Articles and Multi-volume Works]]<br />
|Proposal<br />
|Proposal to address the basic description of Articles within issues and/or volumes of periodicals of most types.<br />
|Three new Types: Periodical, PublicationVolume, PublicationIssue, and added properties for two existent Types: Article, CreativeWork<br />
|See [http://lists.w3.org/Archives/Public/public-vocabs/2014Mar/0013.html discussion] on public-vocabs.<br />
|-<br />
|[[WebSchemas/SocialAccountProperty|social Account property]]<br />
|Proposal<br />
|Indicates a corresponding profile page for an account on a socially-oriented Web site.<br />
|One new property: socialAccount<br />
|<br />
|-<br />
|[[WebSchemas/Audiobook|Audiobook]]<br />
|Proposal<br />
|Proposal for new Audiobook Type and abridged property for [http://schema.org/Book Book].<br />
|Audiobook subtype of [http://schema.org/Book Book] ''and'' of [http://schema.org/AudioObject AudioObject], adds readBy property<br />
|<br />
|-<br />
|[[WebSchemas/Collection|Collection]]<br />
|Proposal<br />
|Proposal for new Collection Type and part properties for [http://schema.org/CreativeWork CreativeWork].<br />
|Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/Accessibility/ToDo|Accessibility]] (part 2)<br />
|Discussion<br />
|Extension for describing accessibility properties of a [http://schema.org/CreativeWork CreativeWork].<br />
|Additional work to add accessMode, hasAdapation, isAdaptationof that were not covered in 1.0 Accessibility work.<br />
|<br />
|-<br />
|[[WebSchemas/QuotationSchema|Add Quotation type]]<br />
|Proposal<br />
|Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties.<br />
|Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee.<br />
|Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise.<br />
|-<br />
|[[WebSchemas/WorkersUnionSchema|Workers Union type]] <br />
|Accepted<br />
|This proposal adds a single new type, WorkersUnion, addressing [http://www.w3.org/2011/webschema/track/issues/17 issue 17] in the WebSchemas tracker. <br />
|"A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying.""<br />
|One type, see [https://dvcs.w3.org/hg/webschema/file/default/schema.org/ext/workersunion.html draft schema].<br />
|-<br />
|[[WebSchemas/Sports|Sports]]<br />
|Proposal<br />
|The purpose of this proposal is to introduce an expanded vocabulary for describing sports information within schema.org. Key concepts include Statistics, Roles, Ordered Events, Competitions and Competition Results.<br />
|See proposal for full set of vocabulary updates.<br />
|V3 posted 2014.05.09<br />
|-<br />
|[[WebSchemas/PeriodicalsComics|Comics and Serials]]<br />
| style="background-color:#ECC8EC;"|Discussing Proposals <br />
|Proposal from Marvel (see [[PeriodicalsComics#Code_Examples|examples]]).<br />
|Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. <br />
|Generally well received and specified, but some detailed [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0073.html discussion] re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with [http://schema.org/Book Book]/numberOfPages, or [http://schema.org/ScholarlyArticle ScholarlyArticle]? Should PeriodicalSeries be intangible?<br />
|-<br />
|[[WebSchemas/HistoricalDataSchema|Historical Data proposal]]<br />
|Proposal<br />
|The [http://historical-data.org/ historical-data.org] site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios.<br />
|Adds HistoricalRecord, HistoricalEvent (subclass of Event), ''overrides'' attendees, subEvents, superEvent to point to HistoricalEvent.<br />
|There is an associated implementation, [https://github.com/historical-data/ github repository], and [http://historical-data-schema.blogspot.com/ blog].<br />
|-<br />
|[[WebSchemas/BioDatabases|Biological Databases]]<br />
|Proposal<br />
|A schema extension for describing biological databases, [http://sagace.nibio.go.jp/schema/en/schema.html Sagace]. <br />
|Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. <br />
|Others have also mentioned interest in adding some notion of species.<br />
|-<br />
|[[WebSchemas/Breadcrumbs|Breadcrumbs]]<br />
|Proposal<br />
|A proposal resolving current problems handling breadcrumbs.<br />
|Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See [http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Nov/0026.html discussion] on using literal values.<br />
|<br />
|-<br />
|[[WebSchemas/DiscussionSchema|Discussion]] <br />
|Proposal<br />
|A proposal extending schema.org for describing online discussion forums and message boards.<br />
|Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful.<br />
|Addition candidate<br />
|-<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html Innovation] <br />
|Proposal<br />
|A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [http://lists.w3.org/Archives/Public/public-vocabs/2012Jul/0071.html]<br />
|Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [http://purl.org/innovation/ns] for complete list of terms.<br />
|Addition candidate<br />
|-<br />
|[[WebSchemas/dissolutionDate|dissolutionDate]]<br />
|Proposal<br />
|Add a dissolutionDate property to Organization.<br />
|<br />
|<br />
|-<br />
|[http://thematix.com/ontologies/travel/lodging/ Lodging Extensions]<br />
|Proposal<br />
|A proposal for extending LodgingBusiness. Specification is here http://thematix.com/ontologies/travel/lodging/<br />
|Adds Amenity, BusinessService, Feature, GuestRoomAmenity, LodgingBusinessAmenity, LodgingBusinessService, RentalOffer, RentalRate, Room, RoomType and Service.<br />
|In addition to the examples given in the cited website, examples can be seen at http://www.regencyhotelmiami.com/ and http://hiltonvb.com and at Super8 hotel description pages, e.g., http://www.super8.com/hotels/alberta/fort-mcmurray/super-8-fort-mcmurray/hotel-overview. <br />
|-<br />
|-<br />
|[[WebSchemas/WebObsSchema|Web Observatory]] <br />
|Proposal<br />
|Proposed extensions to schema.org for describing portals used for [[http://www.webscience.org/|Web Science]] collaboration including projects, datasets and tools used to study the Web.<br />
|Includes vocabularies for [[http://logd.tw.rpi.edu/web_observatory|Web Observatory]], [[http://logd.tw.rpi.edu/web_observatory_project|Web Observatory Project]], [[http://logd.tw.rpi.edu/web_observatory_dataset|Web Observatory Dataset]], and [[http://logd.tw.rpi.edu/web_observatory_tool|Web Observatory Tool]]<br />
|A reference implementation of a web observatory portal demonstrating the user of each Web Observatory vocabulary can be found at the [[http://tw.rpi.edu/web/web_observatory|Tetherless World Constellation Web Observatory Portal]]<br />
|-<br />
|...<br />
|<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|-<br />
|}<br />
<br />
== Brainstorming, Use Cases and Advance Notice ==<br />
<br />
The following topics are under discussion in the Web Schemas Schema.org community, but are not yet approaching specific proposed designs or broad consensus on an approach. Note that this distinction is pretty fuzzy, but some partitioning was needed here due to the number of proposals we're seeing. There is no shame in being listed here rather than as a proposal above!<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0"<br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/PressReview|Ranking]]<br />
|Proposal<br />
|Proposal to add a list of items as a ranking (Top 10, Best sellers etc.)<br />
|One new type http://schema.org/ItemList/Ranking. Probably we need to specify the type, the name and the order (ascendant, descendant).<br />
|Often used in magazines.<br />
|-<br />
|[[WebSchemas/PressReview|PressReview]]<br />
|Proposal<br />
|Proposal to add a list of articles, events etc. as a Press review or Press digest<br />
|One new type http://schema.org/ItemList/PressReview<br />
|Often used in organization websites<br />
|-<br />
|[[WebSchemas/ScholarlyArticle|ScholarlyArticle]]<br />
|Early proposal from HighWire Press needs review.<br />
|Various ideas around improving [http://schema.org/ScholarlyArticle ScholarlyArticle]. <br />
|Suggestion that scholarly articles could be described in more detail.<br />
|There is a lot of related work in this area. For example [http://scholar.google.ca/intl/en/scholar/publishers.html Google Scholar publisher guidelines]; [http://academic.research.microsoft.com/ Microsoft Academic Search]. The [http://www.openarchives.org/OAI/openarchivesprotocol.html Open Archives Initiative - Protocol for Metadata Harvesting] also addresses this problem area and has broad adoption. See also earlier comments from [https://groups.google.com/forum/?fromgroups#!searchin/schemaorg-discussion/ScholarlyArticle/schemaorg-discussion/aEO56kVQoqQ/x-tGuaITitoJ HighWire Press] ([http://dl.dropbox.com/u/105439/ScholarlyArticle/ScholarlyArticle%20-%20schema.org.draft1.pdf pdf]) and following discussion (on the old mailing list).<br />
|-<br />
|[[WebSchemas/RealEstate|Real Estate]]<br />
|Discussions but no proposal yet.<br />
|Enthusiastic discussion in favour of adding RealEstate support. Tracked as [https://www.w3.org/2011/webschema/track/issues/13 issue 13]. This should likely follow along after the Good Relations work.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary, and schema.org's numerous subclasses, and [http://schema.org/Offer Offer] class.<br />
|-<br />
|[[WebSchemas/Vehicles|Vehicles]]<br />
|Anticipated.<br />
|A proposal extending schema.org for describing vehicles is being prepared.<br />
| <br />
|No public draft yet.<br />
|-<br />
|Transport Data<br />
|Discussion<br />
|Initial discussion on description of transport data.<br />
|N/A<br />
|[http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0019.html Discussions] on whether this scenario can be covered with existing vocabulary.<br />
|-<br />
|[[WebSchemas/ActivitySchema|Activities (things you can do)]] <br />
|Proposal<br />
|Vocabulary for describing general activities not bound to any specific time or place. <br />
Unrelated to the [[WebSchemas/ActivityActions|Activities and Actions]] proposal for online user page interations that are listed above.<br />
|Examples: 'Paragliding'. 'Going to the cinema', etc. <br />
|Public draft and description available on [[WebSchemas/ActivitySchema|wiki]]. [http://lists.w3.org/Archives/Public/public-vocabs/2011Oct/0169.html Original proposal on public vocabs mailinglist].<br />
|-<br />
|[[WebSchemas/PersonBio|Person biography]]<br />
|Proposal<br />
|A proposal for supporting people's biography<br />
|Add a bibliography property to the Person type.<br />
|<br />
|-<br />
|Project<br />
|Proposal<br />
|Vocabulary for describing ''any'' kind of project<br />
|Terms (loosely) based on [http://purl.org/stuff/project this project vocabulary]<br />
|Use case gathering - [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0108.html see mailing list thread]<br />
|-<br />
|[[WebSchemas/VacationRentals|Vacation Rental Schema]]<br />
|Proposal<br />
|Creating an additional vocabulary for this hotel-alternative accommodation<br />
|Overview of new terms<br />
|Just initiated the discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/FictionalThing|Fictional Thing]]<br />
|Proposal<br />
|Providing the ability to identify a thing as being fictional<br />
|Proposal for the creation of a FictionalThing type<br />
|Supporting discussion around this schema. Public proposal available on the Wiki<br />
|-<br />
|[[WebSchemas/JobMarket|JobMarket]]<br />
|Proposal<br />
|Extension for modelling job markets<br />
|Classes added: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_QuantitativeValue_.3E_Compensation Compensation], [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_StructuredValue_.3E_WorkExperience WorkExperience] + class amended: [http://www.w3.org/wiki/WebSchemas/JobMarket#Thing_.3E_Intangible_.3E_JobPosting JobPosting]<br />
|Draft for an extension published to elicit feedback<br />
|-<br />
|[[WebSchemas/VisualArtwork|VisualArtwork]]<br />
|Early Proposal<br />
|Extension for CreativeWork and replacement/alternative to Painting and Sculpture<br />
|Overview of Extension and new properties<br />
|Early draft for an extension published to elicit feedback.<br />
|-<br />
|[[WebSchemas/GeoJSON|GeoJSON]]<br />
|Early propsal<br />
|addition to the Geo* family of topics.<br />
|N/A<br />
|Related to [http://schema.org/Place Place] vocabulary<br />
|-<br />
|[[WebSchemas/LookInside|Looking Inside Tables]]<br />
|Early proposal<br />
|A mechanism to map the contents of tables into entities.<br />
|N/A<br />
|Draft for an extension published to elicit feedback.<br />
|-<br />
|-<br />
|[[WebSchemas/OnlinePresence|Online Presence]]<br />
|Early proposal<br />
|expressing Online Presence and current Actions<br />
|WIP<br />
|Related to [http://schema.org/Action Action] subtree and [http://online-presence.net Online Presence Ontology].<br />
|-<br />
|[[WebSchemas/SocialAccount|SocialAccount]]<br />
|Proposal<br />
| Introduce a type and a property to describe social accounts of http://schema.org/Person or http://schema.org/Organization<br />
|Add [[WebSchemas/SocialAccount| SocialAccount]] type derived from http://schema.org/Thing to capture social account. Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount| socialAccount]] expecting the type [[WebSchemas/SocialAccount| SocialAccount]]<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion]<br />
|-<br />
|[[WebSchemas/socialAccount2|socialAccount]]<br />
|Proposal<br />
| Introduce a property to describe social accounts of http://schema.org/Person and http://schema.org/Organization<br />
| Update http://schema.org/Person and http://schema.org/Organization by adding the property [[WebSchemas/socialAccount2| socialAccount]] expecting a URL as value<br />
| See also the mailing list [http://lists.w3.org/Archives/Public/public-vocabs/2013Jun/thread.html#msg78 discussion] '''This is an alternative of the previous item'''<br />
|-<br />
|''Proposal name''<br />
|''How far along''<br />
|''Summary of contribution.''<br />
|''Overview of new terms''<br />
|''Comments on status, particularly regarding integration, overlaps and open issues.''<br />
|}<br />
<br />
== Already Accepted and Added ==<br />
<br />
{| border="1" style="text-align:left; color: #3A4956; background-color:#eeeeee; font-family: 'Lucida Grande' , 'Lucida Sans Unicode' , Verdana, Tahoma, Arial, sans-serif;" cellpadding="5" cellspacing="0" <br />
!Topic<br />
!Status<br />
!Summary<br />
!Vocab<br />
!Comments<br />
|-<br />
|[[WebSchemas/EventSchemaUpdate|Event schema update]]<br />
| style="background-color:#ECC8EC;"|Added 2013 (@@details?)<br />
|Some modifications to [http://schema.org/Event Event] based on deployment experience.<br />
|Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from [http://schema.org/Thing Thing]. <br />
|Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events.<br />
|-<br />
|[[WebSchemas/JobPostingSchema|Job Postings]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/11/schemaorg-support-for-job-postings.html Published]<br />
|A type for Job adverts.<br />
|Adds [http://schema.org/JobPosting JobPosting] class and supporting properties.<br />
|Related discussion on [[CVSchemas|CVs and resumes]]. The occupationalCategory property takes controlled values; more detail and options (e.g. EU ESCO) here would be useful.<br />
|-<br />
|IPTC/rNews integration<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2011/09/extended-schemaorg-news-support.html Published]<br />
|Integration of the [http://dev.iptc.org/rNews rNews] vocabulary produced by the [http://www.iptc.org/site/Home/Media_Releases/schema.org_adopts_IPTC's_rNews_for_news_markup IPTC]. <br />
|See original [http://dev.iptc.org/rNews-10-Introduction-to-rNews rNews 1.0 intro]; most of these terms are now in schema.org directly.<br />
|See New York Times' [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0040.html implementation announcement] for details and examples. <br />
|-<br />
|[[WebSchemas/Comment]]<br />
| style="background-color:#98FB98;"|Published<br />
|A fix to confusion around UserComments and lack of a Comment entity.<br />
|Add a class Comment under CreativeWork, for comments. UserComments remains a UserInteraction event, and awaits further clarification.<br />
|This addresses a need to have a representation of comments as documents, rather than merely as a user activity.<br />
|-<br />
|[[WebSchemas/SoftwareApplicationSchema|Software Application]]<br />
| style="background-color:#98FB98;"|Published<br />
|A class for Software Applications ('webapps', both installable and Web-based).<br />
|Re-uses some properties of CreativeWork; defines a subclass SoftwareApplication with 20 properties, plus two small subclasses.<br />
|This was been accepted and was sent for implementation (2012-04-15). Note that the SoftwareApplicationType enumeration may remain a Snippets-only vocabulary.<br />
|-<br />
|[[WebSchemas/Singularity|Singularity]]<br />
| style="background-color:#98FB98;"|Published<br />
|Proposes we move to singular property names, based on implementor feedback.<br />
|Adds new properties without a plural 's', aliases old ones.<br />
|This has been accepted and sent for implementation (2012-04-15)<br />
|-<br />
|[[WebSchemas/ExternalEnumerations|External Enumerations]]<br />
| style="background-color:#98FB98;"|[http://blog.schema.org/2012/05/schemaorg-markup-for-external-lists.html published]<br />
|Guidance on how to cite external enumerations, including constrained values for properties, and large collections of useful types.<br />
|For example, it should be possible to use lists of countries from e.g. ISO, UN. Or units and measures from systems such as [http://www.qudt.org/ QUDT]. Or community or professionally-maintained lists from Wikipedia, Library or GIS standards, etc. <br />
|Blog post covers initial/core design; further work will include lists of known authorities.<br />
|-<br />
|[[WebSchemas/MedicalHealthProposal|Medical/Health]] <br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html published]<br />
|Extended schema.org for describing key topics and their relationships in online health and medical content.<br />
|Adds MedicalEntity hierarchy including types for key medical/health topics (such as conditions, signs and symptoms, disease causes, risk factors, therapies including drugs and procedures, tests, devices, studies and trials, guidelines, diets, supplements, exercise plans, and anatomy) and supporting types. See [http://blog.schema.org/2012/06/health-and-medical-vocabulary-for.html blog post] and [http://schema.org/docs/meddocs.html overview document] for details.<br />
|Published as v0.95 on 2012-06-26.<br />
|-<br />
|[[WebSchemas/additionalTypeProposal|additionalType]] <br />
| style="background-color:#98FB98;"| [http://www.w3.org/wiki/WebSchemas/additionalTypeProposal published]<br />
|Provides utility property for describing additional types.<br />
|Added 'additionalType' to [http://schema.org/Thing Thing], with detailed description discouraging use outside of Microdata syntax, since RDFa has 'typeof' built-in.<br />
|Published as v0.96 on 2012-07-17.<br />
|-<br />
|[[WebSchemas/GoodRelations|Good Relations integration]]<br />
| style="background-color:#98FB98;"| [http://blog.schema.org/2012/11/good-relations-and-schemaorg.html published]<br />
| The schema.org team and Martin Hepp collaborated to integrate of a version of GR into schema.org. <br />
|See [http://www.heppnetz.de/projects/goodrelations/ Good Relations] site for background, e.g. [http://wiki.goodrelations-vocabulary.org/Quickstart quickstart] page.<br />
|Schema.org already had [http://schema.org/Offer Offer] and related terms, but benefitted from adding detail from Good Relations. Controlled values are still at purl.org GR URLs, and Good Relations continues as an independent project.<br />
|-<br />
|-<br />
|[[WebSchemas/LearningResources|Learning Resources]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013.<br />
|The Learning Resources Metadata Initiative defines a set of terms to improve schema.org's use with educational materials. <br />
|Mainly adds new properties (typically but not necc. on [http://schema.org/CreativeWork CreativeWork]): [http://wiki.creativecommons.org/LRMI/Properties/intendedEndUserRole intendedEndUserRole], [http://wiki.creativecommons.org/LRMI/Properties/educationalAlignment educationalAlignment], with values in a new class, [http://wiki.creativecommons.org/LRMI/Properties/1.0/AlignmentObject AlignmentObject]; [http://wiki.creativecommons.org/LRMI/Properties/educationalUse educationalUse] ([http://schema.org/Text Text] values), [http://wiki.creativecommons.org/LRMI/Properties/timeRequired timeRequired] (a [http://schema.org/Duration Duration]); [http://wiki.creativecommons.org/LRMI/Properties/typicalAgeRange typicalAgeRange] (Text valued); [http://wiki.creativecommons.org/LRMI/Properties/interactivityType interactivityType] (Text); [http://wiki.creativecommons.org/LRMI/Properties/learningResourceType learningResourceType], ...<br />
|Comments. see [http://wiki.creativecommons.org/LRMI/Properties/1.0 version 1.0] and [http://groups.google.com/group/lrmi discussion list]. <br />
|-<br />
|[[WebSchemas/Datasets|Datasets]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013 based on [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/dataset.html dataset.html]<br />
|A proposal extending schema.org for describing datasets and data catalogs. This may be revised to track evolution of W3C DCAT.<br />
|Adds the [http://logd.tw.rpi.edu/node/11401 Dataset], [http://logd.tw.rpi.edu/datacatalog DataCatalog], and [http://logd.tw.rpi.edu/datadownload DataDownload] types and supporting properties.<br />
|An example page with dataset microdata is available [http://logd.tw.rpi.edu/schemaorg_dataset_extension here]. For related efforts, see the [http://www.w3.org/2011/gld/wiki/Main_Page W3C Government Linked Data Working Group].<br />
|-<br />
|[[WebSchemas/TechArticleSchema|Tech Article]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html schema: techpub.html]<br />
|A proposal extending schema.org for describing technical content.<br />
|Adds dependencies, task, and technicalAudience. Adds descriptions for genre (CreativeWork) and about (CreativeWork).<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/APIReferenceSchema|API Reference]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing Application Programming Interface (API) reference content.<br />
|Derived from TechArticle; adds assembly, assemblyVersion, programmingModel, targetPlatform<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/CodeSchema|Code]] <br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/techpub.html drafted]<br />
|A proposal extending schema.org for describing human readable source code.<br />
|Adds codeRepository, codeSample, programmingLanguage, runtime, targetProduct.<br />
|Added as 1.0a, April 2013<br />
|-<br />
|[[WebSchemas/Audience|Audience]]<br />
| style="background-color:#98FB98;"| Added as 1.0a, April 2013. [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html drafted]<br />
|A proposal extending schema.org for describing audiences, building around http://schema.org/Audience type, also used by (and coordinated with) LRMI and MedicalHealth vocabulary.<br />
|Add property audience to type CreativeWork (done) and Product. Also ParentAudience, ... see [http://dvcs.w3.org/hg/webschema/raw-file/default/schema.org/ext/audience.html draft] for details.<br />
|This was added in stages; Medical/Health introduced the basic type 'Audience' first.<br />
|-<br />
|[[WebSchemas/CitationPromotion|Citation Promotion]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|To promote the 'citation' property currently on [http://schema.org/MedicalScholarlyArticle MedicalScholarlyArticle] up to [http://schema.org/CreativeWork CreativeWork].<br />
|Moved citation up to CreativeWork<br />
|<br />
|-<br />
|[[WebSchemas/sameAs|sameAs]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Jul/0067.html 1.0b, 24 July 2013].<br />
|Property to indicate that a single identity is being described.<br />
|Broadly same meaning as owl:sameAs.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions | Actions in Schema.org (part 1)]] <br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Aug/0008.html 1.0c, 7 August 2013].<br />
|Added a basic Action type to schema.org, as a foundation for further extension. See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|<br />
|<br />
|-<br />
|[[WebSchemas/TVRadioSchema|TV and Radio proposal]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Proposes modest changes and additions to support TV and radio (from [http://www.ebu.ch/ EBU] and [http://www.bbc.co.uk/ BBC]). <br />
|Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc.<br />
|See also [[SchemaDotOrgTV|background notes]] and [[http://www.w3.org/wiki/TVRadioSchema]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see [http://schema.org/VideoObject VideoObject], [http://schema.org/AudioObject AudioObject]; [http://schema.org/Movie Movie]. [http://schema.org/Event Event] re scheduling. See also [http://schema.org/UserPlays UserPlays], a kind of [http://schema.org/UserInteraction UserInteraction]. Comics and TV/Radio also share a concern for describing fictional characters and [http://pinboard.in/u:danbri/t:narrative/ narratives]. <br />
|-<br />
|[[WebSchemas/CivicServices|Civic Services]] <br />
| style="background-color:#98FB98;"| Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013].<br />
|Describing public civic services <br />
|A proposal extending schema.org to cover various kinds of civic services.<br />
|GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties<br />
|-<br />
|[[WebSchemas/LocalBusinessDepartment|Add Organization department property]]<br />
| style="background-color:#98FB98;"|Added as [http://blog.schema.org/2013/11/schemaorg-v10d-published-tvradio-civic.html 1.0d, 21 November 2013]<br />
|Added properties [http://schema.org/department department] and [http://schema.org/subOrganization subOrganizationOf] to [http://schema.org/Organization Organization], to allow local businesses to describe their depts (e.g. opening hours) in detail. <br />
|department and subOrganization properties (range and domain both Organization)<br />
|Proposal greatly simplified after WebSchemas discussion.<br />
|-<br />
|[[WebSchemas/OrdersSchema|Orders in Schema.org]] <br />
| style="background-color:#98FB98;"|Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Dec/0025.html 1.0e, 4 December 2013]<br />
|"While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)".<br />
|Adds classes OrderStatus, Order, DeliveryMethod plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/Accessibility|Accessibility]]<br />
| style="background-color:#98FB98;"| Added as [http://lists.w3.org/Archives/Public/public-vocabs/2013Nov/0190.html 1.0e, 4 December 2013].<br />
|A proposal for adding accessibility metadata to all Creative Work content, done in concert with LRMI<br />
|Added four properties to CreativeWork to enable better discovery of accessible content.<br />
|<br />
|-<br />
|[[WebSchemas/ActivityActions|Actions in Schema.org (part 2)]] <br />
|Added 2014<br />
|Add handlers and potential actions to Action type.<br />
|See full entry and proposal for details. <br />
|The schema.org team solicit comments on this draft via public-vocabs@w3.org.<br />
|-<br />
|[[WebSchemas/ReservationsSchema|Reservations in Schema.org]] <br />
|Added 2014<br />
|This proposal includes new types for describing reservations and tickets<br />
|Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties.<br />
|Complements Actions proposal, but independent.<br />
|-<br />
|[[WebSchemas/EmailMessageSchema|EmailMessage type]] <br />
|Added 2014<br />
|This proposal adds a single new type, EmailMessage<br />
|EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages.<br />
|No properties currently defined; proposals welcomed.<br />
|}<br />
<br />
<br/><br />
<br /><br />
<br /><br />
<br />
== Wiki markup ==<br />
<br />
* We have two templates for use here: [[Template:SchemaDotOrgProposal]] which takes 'name' and 'status' parameters, and which returns a one line page header for proposals; also [[Template:SchemaDotOrgTerm]], which takes a 'term' parameter and returns a simple hyperlink to that (class) term on schema.org.<br />
<br />
Nearby: <br />
* [https://dvcs.w3.org/hg/webschema/file/default/schema.org/drafts/alpha mercurial filetree]<br />
* [http://www.mediawiki.org/wiki/Help:Tables Help with wiki table syntax]<br />
<br />
[[Category:WebSchemas]]</div>Danbri