The RDFa definition for schema:Event claims that it has an owl:equivalentClass of dc:Event (actually, using @href, this is dc:event, use @resource to get http://purl.org/dc/terms/Event).

As it happens, DCMI does not define Event in that namespace; however, it does define http://purl.org/dc/dcmitype/Event. See http://dublincore.org/documents/dcmi-terms/#dcmitype-Event.

Before I realized that types can have several parents, I was really confused why LocalBusiness shows me sometimes the breadcrumb "Thing > Place > LocalBusiness" and sometimes "Thing > Organization > LocalBusiness".

I think it would be nice to represent this fact also in the breadcrumb on top of the page (and not only indirectly in the property table).

A simple solution: Show one breadcrumb line per parent, sorted alphabetically.

This (or a more beautiful solution) has also the benefit that the tbody elements won’t change their order (depending on which breadcrumb you happen to get).

i needed it as an example for my suggestion in http://lists.w3.org/Archives/Public/public-vocabs/2014Sep/0182.html

Additions to Actions

AuthoooAr: Vicki Tardif Holland ([email protected])
Last Edited: 20140909

Background

As schema.org Actions are adopted by the community for everything from reserving a flight to listening to music, we are finding a need to describe new Actions and conditions on when and where a provider is available for a user to complete an Action. The following new types and properties are proposed to help with describing these conditions.

Thing > Action > OperateAction

The new OperateAction allows users to operate a device or application. It's subtypes
are ActivateAction, DeactivateAction, SuspendAction, and ResumeAction. OperateAction has no unique properties.

Thing > Action > OperateAction > ActivateAction

An action which allows a user to start a device or application (e.g. starting a timer or turning on a flashlight).

Thing > Action > OperateAction > DeactivateAction

Stop a device or application (e.g. stop a timer or turn off a flashlight).

Thing > Action > OperateAction > SuspendAction

Momentarily pause a device or application (e.g. pause music or pause a timer).

Thing > Action > OperateAction > ResumeAction

Resume an action which was formerly paused (e.g. resume playing music or resume the timer).

ConsumeAction

The ConsumeAction type already exists in schema.org. To date, we have primarily discussed conditions on the entity performing the action, but we want to have conditions on the object of the action as well. The proposed new properties are:

Offer

The following property will be added to the existing Offer type.

Examples

Available in the US-only

{
  "@context": "http://schema.org",
  "@type": "WatchAction",
  "target": "http://www.hulu.com/thedailyshowwithjonstewart",
  "contingentOnOffer": {
    "@type": "Offer",
    "availableAtOrFrom": {
      "@type": "Country",
      "name": "USA"
    }
  }
}

Not Available in China

{
  "@context": "http://schema.org",
  "@type": "WatchAction",
  "target": "http://www.hulu.com/thedailyshowwithjonstewart",
  "contingentOnOffer": {
    "@type": "Offer",
    "notAvailableAtOrFrom": {
      "@type": "Country",
      "name": "CHN"
    }
  }
}

Available in US and Later in Canada

{
  "@context": "http://schema.org",
  "@type": "WatchAction",
  "target": "http://www.hulu.com/thedailyshowwithjonstewart",
  "contingentOnOffer": [
  {
    "@type": "Offer",
    "availabilityStarts": "20140701",
    "availableAtOrFrom": {
      "@type": "Country",
      "name": "USA"
    }
  },
  {
    "@type": "Offer",
    "availabilityStarts": "20140801",
    "availableAtOrFrom": {
      "@type": "Country",
      "name": "CAN"
    }
  }
]}

Per http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0008.html the rough consensus of discussion leads us to proposal 'Beta' in https://www.w3.org/wiki/images/7/7e/ProviderSellerVocabularyRe-DesignProposal.pdf

"Proposal Beta
This alternative proposal attempts ... to use only the existing vocabulary. The changes instead would be
in the descriptions associated with existing terms and intended usage model.
● Leverage the existing 'provider' property to describe the service provider, service operator, or
service performer (see provider in exchange model) and update its description to more clearly
indicate this intended usage;
● Leverage the 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'.
● Introduce a ‘broker’ property to describe entities that map to the broker concept in the
exchange model.
● deprecate ‘bookingAgent’ in favor of the more generic, newly proposed ‘broker’ property
● deprecate 'vendor' in favor of re-using 'seller'
● deprecate ‘merchant’ in favor of re-using ‘seller’
● deprecate 'carrier' within Flight and ParcelDelivery in favor of using the newly described
'provider'"

Issue #1 tracks high-level plans for schema.org. It gives entry points for release-level issues as well as broader goals that correspond to rough milestones over the next year. In practice, these goals are pretty hit-and-miss w.r.t. people actually doing the necessary work, but they are reported here as aspirations and for discussion.

See also release history and draft next release.

Release plans

• 14.0 #3017 [2022-01-xx]
• 13.0 #2884 [2021-07-07]
• 12.0 #2813 [2021-02-12]
• 11.0 #2768 [released 2020-11-30]
• 10.0 #2648 [released 2020-09-08]
• 9.0 #2634 [released 2020-07-21]
• 8.0 #2528 [released 2020-05-01]
• 7.0 #2453 [rapid releases of 7.0, 7.01 ... 7.04]
• 6.0 #2376 [expected 2019-12-01]
• 5.0 #2370 [expected 2019-11-07]
• 4.0 #2363 [release 2019-10-15]
• 3.9 #2306 [release 2019-08-01]
• 3.8 #2272 [release 2019-07-01]
• 3.7 #2239 [release 2019-06-01]
• 3.6 #2193 [release 2019-05-01]
• 3.5 #2052 [release 2019-04-01]
• 3.4 #1891 [release 2018-06-15]
• 3.3 #1569
• 3.2 sdo-callisto - detailed in #1292 - [release 2017-03-23]
• 3.1 sdo-makemake - detailed in #1212 - release 2016-08-09
• 3.0 sdo-deimos - detailed in #911 - release 2016-05-04
• 2.2 sdo-phobos - detailed in #827 - released 2015-11-05
• 2.1 sdo-ganymede - detailed in #510 - released 2015-08-07 (mail thread)
• 2.0 sdo-gozer - detailed in #418 released 2015-05-12

Issues Overview

We label issues by topic, workflow status. The most concrete milestone is the next upcoming release, which since April 2019 are monthly, officially on (and named for) the 1st of the month, but in practice released on the first working day following. Work in progress edits can be found on webschemas.org.

We try to avoid unlabelled issues. The most important labels and entry points are:

• Vocabulary issues - additions, cleanup, clarification and integration; there are various supporting labels to distinguish enhancements from bugs, cleanup and clarification, tricky problems, rough ideas etc.
  • Sometimes we have enough discussion on related issues to require a shared label, e.g. the date/time, events and opening hours cluster.
• New or improved site features - software work. Mainly python coding, appengine, site navigation (css/js) etc.: all under the site tools and python code label.
• Content fixes - primarily bad examples.: we use the guidelines, docs and examples label. This covers all general and specific documentation beyond the actual term definitions.
• Workflow and documentation for Extensions - the extension model, and/or specific extension areas: all filed under extension tracking
• There are also various workflow-related issues e.g. needs review for topics where community discussion is particularly invited; for steering group attention for areas where careful oversight is most needed; standards and organizations linking schema.org to related efforts elsewhere; implementing, which is used when an issue is decided but not fully implemented.

Historical Meeting agenda and notes

• #587 2015-05-28
• #588 2015-06-11
• (July/August email only)
• #775 2015-09-03
• In Nov 2015 we agreed to stop our regular audio calls and operate in public email/github primarily.

Steering Group background

Elaborating on http://schema.org/docs/about.html -

The day to day operations of Schema.org, including decisions regarding the schema, are handled by a steering group, which includes representatives of the sponsor companies and a small number of individuals who have contributed substantially to Schema.org and related standards. The steering group typically makes decisions by consensus. All members of the steering group have the same standing. The steering group is currently chaired by R.V.Guha, who does not represent his employer in this capacity. Discussions of the steering group are public, see https://groups.google.com/forum/#!forum/schema-org-sg (very rarely used; more often CC:'d threads with the W3C Community Group public list).

Migrating from https://www.w3.org/2011/webschema/track/issues/6

From http://groups.google.com/group/schemaorg-discussion/browse_thread/thread/62117670d187559e?pli=1

Raised as

"The concept is defined in
http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#global-identifiers-for-items
and means that you can do things like

Philip

This might seem like an academic questions, but it is what defines if
validators for schema.org should allow itemid or not. Do any of the
sponsors do anything with itemid? If not, updating the documentation
to explicitly say that it is not allowed (and ignored) would be most
welcome. "

... ensuing discussion made it clear that Schema.org does support itemid. This issue tracks the need to document that on Schema.org.

Per the discussion at http://lists.w3.org/Archives/Public/public-vocabs/2014May/0182.html it would be nice to have the RDFS for a given class or property documentation page expressed on that page itself, so that someone who points rdfpipe or the like at that page will actually extract something useful.

Searching for "itemref" returns a page where the term "itemref" doesn't exist.

Update: https://gist.github.com/danbri/c5fef76dcf89bc23bdb6 has a fresh run against 2015-01-28th snapshot of sdo-stantz branch. -- @danbri

FYI, the following are warnings produced by the Structured-Data Linter for current schema.org examples:

[ earlier results removed for readability, see link above ]

This was done through the following:

• clone http://github.com/structured-data/linter
• bundle install
• run the schema_examples rake task to generate all example files
• run `script/parse schema.org/*.html --lint --quiet

Changes to the schema.org RDFS need to be synchronized by updating the vocabulary in the RDF.rb gem, typically done after each release.

Each data/*examples.txt file currently has a bogus final entry ("FakeEntryNeeded, FixMeSomeDay"), since AddExample only gets called when a next item is encountered.

https://github.com/rvguha/schemaorg/blob/master/parsers.py#L76

Next step - let's get a failing test case for this.

http://schema.org/Blog looks wrong - not showing breadcrumbs.
(Someone kindly reported this in email which I can't find right now to acknowledge -but thanks!)

Here are the triples in the schema.rdfa file for both Blog type (which isn't working) and BlogPosting (which is) :

rdfa schema.rdfa | grep Blog

http://schema.org/BlogPosting http://www.w3.org/2000/01/rdf-schema#label "BlogPosting" .
http://schema.org/BlogPosting http://www.w3.org/2000/01/rdf-schema#comment "A blog post." .
http://schema.org/BlogPosting http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class .
http://schema.org/BlogPosting http://www.w3.org/2000/01/rdf-schema#subClassOf http://schema.org/Article .

http://schema.org/blogPosts http://schema.org/rangeIncludes http://schema.org/BlogPosting .
http://schema.org/blogPost http://schema.org/rangeIncludes http://schema.org/BlogPosting .

http://schema.org/Blog http://www.w3.org/2000/01/rdf-schema#label "Blog" .
http://schema.org/Blog http://www.w3.org/2000/01/rdf-schema#comment "A blog" .
http://schema.org/Blog http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class .
http://schema.org/blogPost http://schema.org/domainIncludes http://schema.org/Blog .
http://schema.org/blogPosts http://schema.org/domainIncludes http://schema.org/Blog .

It seems a subClassOf is missing.

Confirmed by looking at the markup:

<div typeof="rdfs:Class" resource="http://schema.org/Blog">
  <span class="h" property="rdfs:label">Blog</span>
  <span property="rdfs:comment">A blog</span>
</div>

It needs a supertype. CreativeWork?

It could make it straight forward to work in github issues and wiki pages, and then once something matures move it to http://schema.org/docs/

You can find example of schema.org documentation done with GFM in #125

I could also help here with another example and rewrite http://schema.org/docs/actions.html in GFM #123

Nice Markdown(+GFM) guide (3min claim) available at: https://guides.github.com/features/mastering-markdown/

This library for python looks quite popular: https://github.com/trentm/python-markdown2

http://schema.org/downvoteCount
http://schema.org/upvoteCount
http://schema.org/Comment

Via JasonJ: re https://schema.org/Comment "the property descriptions for downvoteCount and upvoteCount are specific to Question but the properties apparently apply to comments as well."

Also maybe "The parent of a question, answer or item in general." -> "The parent of a question, answer or comment item in general."? (http://schema.org/parentItem)

Navigating around api.py is a little disorienting as it does not include any docstrings to identify what the classes such as "Unit" represent. One can certainly work it out over time, but docstrings would help get newbies up to speed faster :)

http://schema.org/GeoShape
http://schema.org/box
http://schema.org/polygon

See discussion at geojson/geojson-ld#28

Original text: "See http://geowanking.org/pipermail/geowanking_geowanking.org/2012-June/026179.html
Schema.org's design came via rNews from GeoRSS, and there from GML. It needs a fresh look."

This is now a meta bug for improvements to schema.org's geo(spatial) vocabulary:

Geospatial 'core' terms:

• http://schema.org/latitude http://schema.org/longitude http://schema.org/elevation on http://schema.org/GeoCoordinates are vague; they don't mention e.g. wgs-84. #802
• http://schema.org/elevation has no units or base; contrast e.g. W3C basic geo which we defined (eventually) as "The WGS84 altitude of a SpatialThing (decimal meters above the local reference ellipsoid)."
• http://schema.org/box has the wrong text (copy/paste error), definition is identical to http://schema.org/polygon. Needs a definition. #8
• Suggest to also allow http://schema.org/geo on Organization (however it is on Place and therefore applicable on any LocalBusiness already)
• GeoShape and GeoCoordinates should allow a postalCode for rough positioning.
• a GeoCircle would improve upon existing simple 'circle' property of GeoShape, as publishers could define radius and (various approaches to) centre without pushing it all into textual micro-syntax.

Related schema.org vocabulary for locally oriented info:

• Physical Web e.g. via beacons such as https://github.com/google/physical-web - what kind of richer schemas are needed to support these use cases?
• Accessibility of Places - schema.org expects to do some work to support scenarios such as 'is there a wheelchair ramp?', see #254
• Opening Hours markup needs improving - #245

Links have been provided to GS1 pages on GTIN8, GTIN13 and GTIN14 in Offer and Product. It would be helpful as well to add links to GS1 information on the Global Location Number in the Organization class. These are the links to the GS1 Global Data Dictionary definition for GLN as well as the GS1 GLN Summary:

http://apps.gs1.org/GDD/glossary/Pages/Global%20Location%20Number%20(GLN).aspx
http://www.gs1.org/barcodes/technical/idkeys/gln

2020 Update

I've gone through these, closed a few, tagged others for move to the suggestions-questions-brainstorming repo. I think we can close this issue (and maybe recycle it, as #3 is a good number).

Original text

This issue was (originally) intended for high-level planning, and relates to the set of issues tagged as site tools + python

See #1 for overall plan, and #2 for vocabulary planning.

Note:

• ▶️ Being worked on
• ✋ Work paused

Issues [to be] addressed

• Site HTML
  • Issue (#67) RDFa in per term pages should include inverseOf & subPropertyOf
  • Issue (#217) The rdfs:subClassOf links in RDFa markup have room for improvement
  • Issue (#317) Add Turtle dumps on per-term views
  • Issue (#725) Description tag to include term description of sensible length, breaking on a sentence boundary. Issue extended to include same functionality for JSON-LD output also to strip out quotes and other breaking markup.
  • Issue (#1217) RDFa on Term page - subClassOf in odd place
• Example txt files
  • Issue (#54) Automate comparison of examples with Schema
  • Issue (#177) Every example should have a unique ID
  • Issue (#499) Generate a list of terms that do not appear in examples
  • Issue (#1104) Workflow needs syntax-checkers integrated for all examples
  • Issue (#1145) Clean up .txt files
• Tests
  • Issue (#156) Test supercededBy & inverseOf don't point to same thing
  • Issue (#250) Test ensuring sentences end on '.'
  • Issue (#485) Testcase to catch case where a property points to an enum that we forgot to enumerate
  • Issue (#782) Add a scripts/ utility for QA of Web-served functionality
  • Issue (#1205) Unit test warning if a property is inverseOf itself
  • Issue (#1280) Need python API telling us which examples exist in < 3 formats
  • Issue (#1329) Test to catch terms that are subtype/property of an attic term
• Export formats / files
  • Issue (#197) Always generate updated RDF, OWL, JSON-LD
  • Issue (#208) Add more export formats
  • Issue (#703) Content Negotiation for Turtle file
  • Issue (#317 ) Add Turtle dumps on per-term views
  • Issue (#360) Representation of schema_org_rdfa in "canonized" Polyglot HTML5
  • Issue (#390) CSV download of all terms
  • Issue (#484) Release snapshot format improvements
  • Issue (#1101) Should the version history of the schema.org JSONLD context file be archived.
• JSON-LD / Context
  • Issue (#51) JSON-LD context problem for properties that can take both URL or Text
  • Issue (#854) JSON-LD emerging best practice is to alias @type, @id (and other keywords)
  • Issue (#860) Add a 404 handler that detects lookupd of /id and /type (JSON-LD keywords) and explains what's up
• Language
  • Issue (#491) Add the chinese translations
  • Issue (#1282) data/*schema files should have consistent language tagging
• Meta vocabulary & display thereof
  • Issue (#182) Add to RDFS Conventions for see-also-issue-tracker, or see-also-documentation link
  • Issues (#233) (#255) Add domainHint & rangeHints for properties
  • Issue (#359) rdfs:comment ... Need quotation rules?
  • Issue (#465) Document .py API + schema config markup for deprecating (rather than marking as supersededBy) terms
  • Issue (#914) Implement a mechanism for recording context-specific term definitions (textual at least)
  • Issue (#1318) Create process/UI/etc for terms that graduate from Pending (or get archived/abandoned) - "attic"
• Site functionality
  • Issue (#490) Site HTML should be responsive to people using tiny pocket computers
  • Issue (#879) Collect some useful/interesting visualizations of the schema.org vocabularies
• Vocabulary Definition
  • Unit tests to check extension values
  • Extension vocabulary definition:
    • Define overall state of extension - Proposed / Released
    • Define state of individual terms within released extension - Proposed / Accepted
    • Include release version

Jason Johnson reports "why are the enumeration members listed here http://schema.org/EventStatusType but not here? http://schema.org/DrugCostCategory when they are defined similarly in the rdfa"

http://schema.org/DrugCostCategory does not list instances, but last year, i.e.
https://web.archive.org/web/20130308031023/http://schema.org/DrugCostCategory ... it did: i.e. links to ReimbursementCap Retail Wholesale

2020 update

This was an earlier attempt to try to triage incoming suggestions into higher level groupings. We didn't keep up, hence #2573 and the creation of the suggestions-questions-brainstorming repo. The need still exists but I'm going to close this issue for now (and then move it over to that repo). --danbri@

Original text

This issue accompanies the rolling planning issue (#1) by providing at-a-glance view into the pile of vocabulary changes collected nearby. This is where "Closed but Noted (and possible Queued)" issues should be registered by the schema.org team. Doing so allows us to have an overview of potential work, and to avoid being overwhelmed with 100s of open issues. See our github issue management page for more details.

Noted proposals

The following gives an overview of proposals that have been received.

• CreativeWork
  • #1010 Movie, TVSeries - proposed addition of cinematographer property.
  • #756 Poem
  • #749 MedicalWebPage
  • #737 keywords should allow URLs
  • #736 publications (a list of)
• Place / LocalBusiness
  • #743 Distillery
  • Dataset
    • #713 - description of dataset (and database) schemas, beyond schema.org's.
      Top level or misfit
• Product
  • IndividualProduct
    • #1289 - suggested new fields, (initially MSRP, MSRP Currency). While these can be handled via additionalProperty, also noting here.

• 746 Animal

Major cross-cutting areas:

• Events and Actions
• Food (for Recipe, MedicalEntity / Diet, menus, Reservation, GS1 / food packaging, etc etc.) - #458
• Achievements, credentials and awards. Relates to sports, JobPosting and to courses, e.g. see:
  • #1324 for sporting championship/tournament awards
  • #668 dance studio awards
  • #780 - use of starRating on hotels and food establishments; #1293 proposed EndorsementRating for critic's reviews and other non-scaled positive ratings.
  • #195 - extensive discussion of academic/scholarly, professional and vocational credentials around courses; also skills for a JobPosting: #1167

Changes / updates

• #735 - Why is DownloadAction under TransferAction instead of ConsumeAction

http://schema.org/Offer
http://schema.org/price

(originally relayed from a colleague, Matthias)

Fixed already:

• price field, can we say something clearer about localization (use of €, $ symbols, '.', ',' for decimal vs 1000s, @content?). e.g. $ is ambiguous
• we could point out '.' vs ',' are ambiguous (http://en.wikipedia.org/wiki/Decimal_mark#Hindu.E2.80.93Arabic_numeral_system).
• Maybe we should we just say "without using '.' or ',' for 1000s", and using '.' for decimals? We can also note that both Microdata and RDFa allow localised human-facing markup to say one thing, but an equivalent decimal value can be written in the @content="..." attribute.
• gtin. we should link to http://www.gs1us.org/about-gs1-us/media-center/press-releases/gtin-validation-guide.
• a way of indicating the main offer in a page ('mainEntity' use case?) would be useful. Fixed in #301"

Open...

• can we say something about whether tax is included in price?
• also consider adding examples or shortcut properties that show how to describe related products via their gtin.
• show a product example for mainEntityOfPage - the problem is that a merchant's web-site contains multiple offers, the "main" one and typically related product/offers, but also offers for the same product by different sub-sellers." e.g. http://www.walmart.com/ip/Teenage-Mutant-Ninja-Turtles-2014-Blu-ray-Gift-Set-With-Figurines-Walmart-Exclusive-Widescreen/38234327
• see also notes below...

e.g. see http://brendanscott.wordpress.com/2013/02/21/supersede-v-supercede-proof-by-google/

While "supercedes" isn't out-and-out wrong, it is significantly less conventional than "supersedes" (regardless of US vs EN English usage).

See also http://www.dailymail.co.uk/news/article-1049010/Cant-spell-Maybe-youre-clever-says-Collins-dictionary.html

"Many of us wrongly come up with ' supercede' because of our knowledge of other words including intercede or precede. The word itself comes from the Latin super-sedere, meaning to desist.

See also http://www.dailymail.co.uk/news/article-1049010/Cant-spell-Maybe-youre-clever-says-Collins-dictionary.html#ixzz3AsGjt6s4

https://twitter.com/danbri/status/501750568549761026

To change would require only local code changes - the property is unlikely to be used outside of our repo.

• http://schema.org/alumniOf already linked to alumni (its inverse)
• http://schema.org/object already links to its sub-properties.
• http://schema.org/docs/schema_org_rdfa.html already documents these in RDFa/RDFS.

For consistency it would be nice (but non-urgent) if the per-term pages also exposed this information.

Nearby:

• AttributeProperties method generates the current RDFa-less markup, https://github.com/rvguha/schemaorg/blob/master/api.py#L572
• GetExtMappingsRDFa method maps external URIs, https://github.com/rvguha/schemaorg/blob/master/api.py#L335

Hi,

I was wondering if it would make sense to consider different RDF serializations as a possible output format rather than RDFa only. This could happen via content negotiation. If you are a search bot and you would like to get some more information about the underlying schema you would ask most vocabulary pages in a way similar to the following:

curl -H "accept: application/rdf+xml" "http://schema.org/inLanguage"

Now, if the response header provides HTML rather than the suggested format, the bot could start parsing the page wrt RDFa and find out that there is indeed some useful information. Alternatively, schema.org could respond with a corresponding header that suggests that the returned entity can be parsed with a corresponding parser. From what I know, the latter option would be more in line with current best practices.

Andreas

a) example needs fixing
b) we should automate a test for such things - easy to have bad examples.

We have this triple in the schema:

<http://schema.org/attendees> <http://schema.org/supersededBy> <http://schema.org/attendees> .

See also notes in Wiki: https://github.com/schemaorg/schemaorg/wiki/JsonLd

e.g. namedPosition in Role example http://schema.org/Role
{
"@context": "http://schema.org",
"@type": "SportsTeam",
"name": "San Francisco 49ers",
"member": {
"@type": "OrganizationRole",
"member": {
"@type": "Person",
"name": "Joe Montana"
},
"startDate": "1979",
"endDate": "1992",
"namedPosition": "Quarterback"
}
}

Currently the context file (see http://schema.org/docs/jsonldcontext.json.txt) has this:
"namedPosition": { "@type": "@id" },

... because an URL is a possible value. However text is also a possible value, and currently more likely. The problem is that the JSON-LD context forces the property value to be interpreted as a (possible relative) URI reference, hence in http://json-ld.org/playground/ the value shows up relative to the site the data's on:

_:b1 http://schema.org/namedPosition http://json-ld.org/playground/Quarterback .

We could over-ride this, e.g. using:

"namedPosition": { "@value": "Quarterback" }

Or we could change the context for this property (and others?), so that literal values are the default. But then we'd need to use (something like) this notation for controlled values:

"namedPosition": { "@id": "http://sport-vocabs.example.org/Quarterback" }

From https://plus.google.com/u/0/108052676511190204011/posts/e1MTjatEP7s
"With over 300,000 companies using GTIN12 (Known by most across North America as the U.P.C.), it's important to add this property ASAP! "

Boolean is not currently declared as a subclass of anything, thus as it is neither an instance of rdfs:Class nor of rdfs:Property it is not rendered correctly (no breadcrumb header, no enumeration members).

Boolean should be declared as a subclass of DataType, which also currently is not handled correctly.

redirect http://www.schema.org/Person to http://schema.org/Person
and
redirect https://www.schema.org/Person to https://schema.org/Person
on the basis that we prefer to see the canonical 'http://schema.org/Person' in widespread use, but if someone asks for the https then let's give it to them.

work in progress, http://lists.w3.org/Archives/Public/www-archive/2014Apr/0023.html

http://schema.org/True
http://schema.org/False

"One thing, though: In the current version of schema.org, False and True are subtypes of Boolean. They should be instances / enumerated values."

Mostly recently pointed out by Martin Hepp, http://lists.w3.org/Archives/Public/public-vocabs/2014Sep/0191.html

(There's also the issue that such values very often show up as literals in data, even if they should be URIs. Could either try to fix documentation to encourage URI use, or document this as an 'expect the unexpected' pattern.)

e.g. http://schema.org/PreOrder

Investigate linking to Role into the boilerplate of per property (e.g. http://schema.org/member ) and per-type (e.g. http://schema.org/Person) navigation.

This is needed so that people know Role is an allowable type on most/all properties.

We also need to update the text of the Role type to link to the blog post. I'll file a separate bug on that since we've a few blog posts worth linking.

We should use this notation for MapCategoryType:
<div typeof="http://schema.org/BookFormatType" resource="http://schema.org/EBook">

Currently: <div typeof="MapCategoryType" resource="http://schema.org/ParkingMap">

Should be:
<div typeof="http://schema.org/MapCategoryType" resource="http://schema.org/ParkingMap">

Reported: http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0149.html ( Peter F. Patel-Schneider )

There are some address format issues in EU that make vCard a bad fit. This issue is a placeholder for investigating the situation.

See also http://www.w3.org/ns/locn
http://schema.org/PostalAddress

The example on SportsTeam uses a value of OrganizationRole for the member property. But member expects "Person or Organization", while OrganizationRole is "Intangible > Role".

The description of Role (if I understand it correctly) seems to explain that this is an intended use.

If that’s true, shouldn’t Role be listed as expected type for member?

We encourage people to use /-based extensions, so these shouldn't 404.

Possible designs include:

1. redirect to http://schema.org/Person#Xyz and have .js notice the fragment
2. make a stub page with a hyperlink back to /Person

My bad for not having done this already. --Dan

Some (?) examples use a meta element for providing a URL. Instead, a link element should be used.

Example on http://schema.org/WebSite:

<meta itemprop="url" content="http://www.example.com/"/>

<meta property="url" content="http://www.example.com/"/>

According to HTML5 (W3C WD), the meta element is only to be used for metadata

[…] that cannot be expressed using the […] link […] elements

Microdata (W3C Note) also requires:

If a property's value, as defined by the property's definition, is an absolute URL, the property must be specified using a URL property element.

In the current version of schema.org, False and True are subtypes of Boolean. They should be instances / enumerated values.

When we integrated GoodRelations, we skipped the category property for reasons I do not remember.

This should be fixed - simply add
<span>Domain: <a property="http://schema.org/domainIncludes" href="http://schema.org/Product">Product</a></span>

in the block for

<div typeof="rdf:Property" resource="http://schema.org/category">

This will also make this consistent with

http://www.heppnetz.de/ontologies/goodrelations/v1.html#category

We now reflect such mappings into per-term RDFa, and several have already been collected:

http://wiki.dublincore.org/index.php/Schema.org_Alignment/Telecon_20120514_Report

The simplest of these should be trivial to add.

Update: Dublin Core have a draft list of mappings - see github

"If you are messing around near StructuredValue, it would probably be worthwhile to fix up the comment on StructuredValue, which says that structured values are strings, but all the subclasses of StructuredValue are not strings." -- http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0205.html

http://schema.org/StructuredValue "Structured values are strings—for example, addresses—that have certain constraints on their structure."

Subtypes:

More specific Types
ContactPoint
GeoCoordinates
GeoShape
NutritionInformation
OpeningHoursSpecification
OwnershipInfo
PriceSpecification
QuantitativeValue
TypeAndQuantityNode
WarrantyPromise

This issue is a duplicate of #70

1. the RDFa syntax is wrong - href doesn't expect qualified names
2. the namespace is wrong; Event is is dc's type namespace.

http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#dcmitype-Event

The RDFa initial context file doesn't define a prefix for dcmi-type, http://www.w3.org/2011/rdfa-context/rdfa-1.1

The correct uri would be http://purl.org/dc/dcmitype/Event

We have good documentation in the blog that can't be found easily from the actual site.

As the top of docs/full.html says:

Note: as of 2014-04-04 this tree is not entirely up to date. Additional types have been
added: see EmailMessage, Reservation, Question and Answer, added in version 1.1.
Version 1.2 added the Potential Actions vocabulary, see potentialAction, EntryPoint,
target, actionStatus, ActionStatusType, ActiveActionStatus, CompletedActionStatus,
PotentialActionStatus.

Short term, we need to add all of these back in (and any others that we're missing).

Long term, we need to programmatically construct the list. Because maintaining it manually is insane :)

the description still reads "URL of an image of the item."
Should be "An image of the item (e.g. URL, or described inline as an ImageObject)." or similar.

/cc @dbs

This appears to have been a problem since at least the 1.0b release (the earliest to which I have access).

To avoid #49 and similar.