danbri/gist:9962d481b1e52025387921cc531a6446

## gistfile1.txt

This file documents differences between v2.2 and v3.0 of schema.org at the level of triples in the schema definitions.

The *vast* majority of differences were from the movement of medical/health terms into an extension.

The first section was based on a study of schema assertions that were only in 2.2 but not in 3.0; the final section was based
on assertions that were found in 3.0 but not in 2.2. Medical-related vocabulary was largely ignored here (although see #1203 for dedicated
analysis, which identified 4 health-lifesci extension terms that were dropped: breastfeedingWarning, healthCondition, prescriptionStatus, secondaryPrevention).

Misc notes that arose in passing, for later investigation but which are not bugs:
* Properties 'aspect', 'availableService', 'overview' in health-lifesci could be generalized.
* Grammar fix? in schema:structuralClass a rdf:Property ; rdfs:comment "The name given to how bone physically connects to each other." (bones?)
*  The 'subtype' property in health-lifesci extension is confusingly named, consider renaming with a less general name.

Some of these are just comments on changes noted, others (flagged TODO) are bugs in v3 and need fixing asap.
Some obvious changes are not noted e.g. gtin* properties were reworded and therefore show up in the diff. Others are noted
and marked 'ok'.


0) Misc, noted elsewhere, added to top of list for completeness.

a. TODO: health-lifesci is missing definitions for breastfeedingWarning, healthCondition, prescriptionStatus, secondaryPrevention.
b. TODO: BlogPosting should have supertype SocialMediaPosting not Article.

Missing: schema:BlogPosting rdfs:subClassOf schema:SocialMediaPosting .
Added but should be removed:
schema:BlogPosting rdfs:subClassOf schema:Article .


1.) OK: schema:description rdfs:comment ... "a description" vs "a short description"

This is OK - this is from https://github.com/schemaorg/schemaorg/pull/891/files in v3 https://github.com/schemaorg/schemaorg/issues/880

2.) OK: gender
Note that we added mention of /Male, /Female and strings.

Optional TODO: mention this in conformance section re expecting unexpected in docs/datamodel.html as similar issues
cropped up with opening hours and Monday-Friday URLs vs strings.

3.) TODO: genre
We lost URL as values,
schema:genre schema:rangeIncludes schema:URL . was removed in v3.
See http://schema.org/docs/releases.html#g346 from v2.1. Should be restored.

4.) ingredients - this was already restored.

Addressed as a quick fix in http://schema.org/docs/releases.html#g1174

schema:ingredients a rdf:Property ;
    rdfs:label "ingredients" ;
    schema:domainIncludes schema:Recipe ;
    schema:rangeIncludes schema:Text ;
    schema:supersededBy schema:recipeIngredient ;
    rdfs:comment "A single ingredient used in the recipe, e.g. sugar, flour or garlic." .

... has this gone? seems to be in v3 too.

5.) OK: schema:mainEntityOfPage --- whitespace changed <br>  - assume this is OK, markdown related.

6.) TODO: check status of manufacturer ... we restored this as a quick fix too, looking at diff of data/schema.org vs data/releases/3.0/schema.rdfa

7.) TODO: netWorth - reversion see 60.) below

8.) OK: openingHours text changed:

Looks ok as uses language of "general" (vs special) which was introduced for v3.0.

2.2: schema:openingHours rdfs:comment "The opening hours for a business. Opening hours can be specified as a weekly time range, starting with days, then times per day. Multiple days can be listed with commas ',' separating each day. Day or time ranges are specified using a hyphen '-'.<br />- Days are specified using the following two-letter combinations: <code>Mo</code>, <code>Tu</code>, <code>We</code>, <code>Th</code>, <code>Fr</code>, <code>Sa</code>, <code>Su</code>.<br />- Times are specified using 24:00 time. For example, 3pm is specified as <code>15:00</code>. <br />- Here is an example: <code>&lt;time itemprop=&quot;openingHours&quot; datetime=&quot;Tu,Th 16:00-20:00&quot;&gt;Tuesdays and Thursdays 4-8pm&lt;/time&gt;</code>. <br />- If a business is open 7 days a week, then it can be specified as <code>&lt;time itemprop=&quot;openingHours&quot; datetime=&quot;Mo-Su&quot;&gt;Monday through Sunday, all day&lt;/time&gt;</code>." .
3.0: schema:openingHours rdfs:comment "The general opening hours for a business. Opening hours can be specified as a weekly time range, starting with days, then times per day. Multiple days can be listed with commas ',' separating each day. Day or time ranges are specified using a hyphen '-'.<br />- Days are specified using the following two-letter combinations: <code>Mo</code>, <code>Tu</code>, <code>We</code>, <code>Th</code>, <code>Fr</code>, <code>Sa</code>, <code>Su</code>.<br />- Times are specified using 24:00 time. For example, 3pm is specified as <code>15:00</code>. <br />- Here is an example: <code>&lt;span itemprop=&quot;openingHours&quot; content=&quot;Tu,Th 16:00-20:00&quot;&gt;Tuesdays and Thursdays 4-8pm&lt;/span&gt;</code>. <br />- If a business is open 7 days a week, then it can be specified as <code>&lt;span itemprop=&quot;openingHours&quot; content=&quot;Mo-Su&quot;&gt;Monday through Sunday, all day&lt;/span&gt;</code>." .


9.) TODO: affiliation was subpropertyOf memberOf

Established in 2.1 via http://schema.org/docs/releases.html#g596 (Documented that affiliation is a sub-property of memberOf.)

1212 Removed: schema:affiliation rdfs:subPropertyOf schema:memberOf .

2.2: schema:affiliation rdfs:subPropertyOf schema:memberOf .
3.0: MISSING

TODO: confirm and restore.

10.) prepTime - TODO: link ISO

2.2: schema:prepTime rdfs:comment "The length of time it takes to prepare the recipe, in <a href='http://en.wikipedia.org/wiki/ISO_8601'>ISO 8601 duration format</a>." .
3.0: schema:prepTime rdfs:comment "The length of time it takes to prepare the recipe, in ISO 8601 duration format." .

11.) TODO: restore schema:publisher schema:rangeIncludes schema:Person .

schema:publisher schema:rangeIncludes schema:Person . has gone. - noted in #1198.

12.) recipeCategory - ok

2.2: schema:recipeCategory rdfs:comment "The category of the recipe&#x2014;for example, appetizer, entree, etc." .
3.0: schema:recipeCategory rdfs:comment "The category of the recipe—for example, appetizer, entree, etc." .

13.) schemaVersion - ok

2.2: schema:schemaVersion rdfs:comment "Indicates (by URL or string) a particular version of a schema used in some CreativeWork. For example, a document could declare a schemaVersion using a URL such as http://schema.org/version/2.0/ if precise indication of schema version was required by some application. " .
3.0: schema:schemaVersion rdfs:comment "Indicates (by URL or string) a particular version of a schema used in some CreativeWork. For example, a document could declare a schemaVersion using an URL such as http://schema.org/version/2.0/ if precise indication of schema version was required by some application. " .

14.) sponsor domainIncludes - ok

2.2: schema:sponsor schema:domainIncludes schema:MedicalStudy ;
    rdfs:comment "Sponsor of the study." .

3.0: schema:sponsor schema:domainIncludes schema:Event,
        schema:Organization,
        schema:Person ;
    schema:rangeIncludes schema:Person ;
    rdfs:comment "A person or organization that supports a thing through a pledge, promise, or financial contribution. e.g. a sponsor of a Medical Study or a corporate sponsor of an event." .


15.) totalTime - TODO link ISO

2.2: schema:totalTime rdfs:comment "The total time it takes to prepare and cook the recipe, in <a href='http://en.wikipedia.org/wiki/ISO_8601'>ISO 8601 duration format</a>." .
3.0: schema:totalTime rdfs:comment "The total time it takes to prepare and cook the recipe, in ISO 8601 duration format." .

16.) translator - ok

2.2: schema:translator rdfs:comment "Organization or person who adapts a creative work to different languages, regional differences and technical requirements of a target market." .
3.0: schema:translator schema:domainIncludes schema:Event ;
    rdfs:comment "Organization or person who adapts a creative work to different languages, regional differences and technical requirements of a target market, or that translates during some event." .

17.) urlTemplate - ok

2.2: schema:urlTemplate rdfs:comment "A url template (RFC6570) that will be used to construct the target of the execution of the action." .
3.0: schema:urlTemplate rdfs:comment "An url template (RFC6570) that will be used to construct the target of the execution of the action." .

18.) validThrough - ok

Fibo.

2.2: schema:validThrough rdfs:comment "The end of the validity of offer, price specification, or opening hours data." .
3.0: schema:validThrough schema:domainIncludes schema:JobPosting,
        schema:MonetaryAmount ;
    rdfs:comment "The date after when the item is not valid. For example the end of an offer, salary period, or a period of opening hours." .

19.) value - ok

Fibo.

2.2: schema:value rdfs:comment "The value of the quantitative value or property value node. For QuantitativeValue, the recommended type for values is 'Number'. For PropertyValue, it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'." .
3.0: schema:value schema:domainIncludes schema:MonetaryAmount ;
    rdfs:comment """The value of the quantitative value or property value node.<br/>
	For QuantitativeValue and MonetaryValue, the recommended type for values is 'Number'. <br/>
	For PropertyValue, it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'.""" .


20.) vehicleSeatedCapacity - ok

We added a '.'.

2.2: schema:vehicleSeatingCapacity rdfs:comment """The number of passengers that can be seated in the vehicle, both in terms of the physical space available, and in terms of limitations set by law.<br />
Typical unit code(s): C62 for persons """ .
3.0: schema:vehicleSeatingCapacity rdfs:comment """The number of passengers that can be seated in the vehicle, both in terms of the physical space available, and in terms of limitations set by law.<br />
Typical unit code(s): C62 for persons.""" .

21.) videoFormat TODO: restore #577 http://schema.org/docs/releases.html#g577

In 2.1 we had http://schema.org/docs/releases.html#g577 "Amended videoFormat to indicate that it is expected on BroadcastEvent and ScreeningEvent, rather than TelevisionStation."

TODO: Restore per 2.2.

2.2: schema:videoFormat schema:domainIncludes schema:BroadcastEvent,
        schema:BroadcastService .
3.0: schema:videoFormat schema:domainIncludes schema:TelevisionStation .

22.) Language - ok

As intended - http://schema.org/docs/releases.html#g341

2.2: schema:Language rdfs:comment "Natural languages such as Spanish, Tamil, Hindi, English, etc. and programming languages such as Scheme and Lisp." .
3.0: schema:Language rdfs:comment "Natural languages such as Spanish, Tamil, Hindi, English, etc. Formal language code tags expressed in [BCP 47](https://en.wikipedia.org/wiki/IETF_language_tag) can be used via the [[alternateName]] property. The Language type previously also covered programming languages such as Scheme and Lisp, which are now best represented using [[ComputerLanguage]]." .

23.) GR credits - ok

e.g. in 2.2 we had schema:Product ns1:source <http://www.w3.org/wiki/WebSchemas/SchemaDotOrgSources#source_GoodRelationsProperties> .
...we now have schema:Product ns1:source <http://www.w3.org/wiki/WebSchemas/SchemaDotOrgSources#source_GoodRelationsTerms> .
This is as intended, since per-property pages were added, and we moved to a generic piece of acknowledgement text for types and properties.


24.) Recipe - ok

2.2: schema:Recipe rdfs:comment "A recipe." .
3.0: schema:Recipe rdfs:comment """A recipe. For dietary restrictions covered by the recipe,
    a few common restrictions are enumerated via <a href="/suitableForDiet">suitableForDiet</a>.
    The <a href="/keywords">keywords</a> property can also be used to add more detail.""" .

As intended.

25.) containsPlace inverseOf ... - ok

It was inverseOf itself previously.

2.2: schema:containsPlace schema:inverseOf schema:containsPlace .
3.0: schema:containsPlace schema:inverseOf schema:containedInPlace .

26.) includedDataCatalog - ok

As intended.

2.2: schema:includedDataCatalog rdfs:comment "A data catalog contained in the dataset." .
3.0: schema:includedDataCatalog schema:supersededBy schema:includedInDataCatalog ;
    rdfs:comment "A data catalog which contains this dataset (this property was previously 'catalog', preferred name is now 'includedInDataCatalog')." .

We now have

schema:includedInDataCatalog a rdf:Property ;
    rdfs:label "includedInDataCatalog" ;
    schema:domainIncludes schema:Dataset ;
    schema:inverseOf schema:dataset ;
    schema:rangeIncludes schema:DataCatalog ;
    rdfs:comment "A data catalog which contains this dataset." .


27.) parentOrganization - TODO repair and restore.

To be restored.

Unwanted rollback of http://schema.org/docs/releases.html#g535 ("Broadened domain of parentOrganization to allow any Organization, rather than only LocalBusiness. Noted parentOrganization and subOrganization as inverses.")

2.2: schema:parentOrganization schema:inverseOf schema:subOrganization ;
    rdfs:comment "The larger organization that this organization is a branch of, if any." .
3.0: schema:parentOrganization rdfs:comment "The larger organization that this local business is a branch of, if any." .

schema:subOrganization schema:inverseOf schema:parentOrganization . ...was also dropped in v3.0.

28.) Enumeration - html entity - ok

schema:Enumeration rdfs:comment ... removed HTML entity markup in v3. This is ok.


...


29.) CheckInAction - ok

Change is just markdown.

2.2: schema:CheckInAction rdfs:comment "The act of an agent communicating (service provider, social media, etc) their arrival by registering/confirming for a previously reserved service (e.g. flight check in) or at a place (e.g. hotel), possibly resulting in a result (boarding pass, etc).<p>Related actions:</p><ul><li><a href=\"http://schema.org/CheckOutAction\">CheckOutAction</a>: The antonym of CheckInAction.</li><li><a href=\"http://schema.org/ArriveAction\">ArriveAction</a>: Unlike ArriveAction, CheckInAction implies that the agent is informing/confirming the start of a previously reserved service.</li><li><a href=\"http://schema.org/ConfirmAction\">ConfirmAction</a>: Unlike ConfirmAction, CheckInAction implies that the agent is informing/confirming the *start* of a previously reserved service rather than its validity/existence</li></ul>." .
3.0: schema:CheckInAction rdfs:comment "The act of an agent communicating (service provider, social media, etc) their arrival by registering/confirming for a previously reserved service (e.g. flight check in) or at a place (e.g. hotel), possibly resulting in a result (boarding pass, etc).\\n\\nRelated actions:\\n\\n* [[CheckOutAction]]: The antonym of CheckInAction.\\n* [[ArriveAction]]: Unlike ArriveAction, CheckInAction implies that the agent is informing/confirming the start of a previously reserved service.\\n* [[ConfirmAction]]: Unlike ConfirmAction, CheckInAction implies that the agent is informing/confirming the *start* of a previously reserved service rather than its validity/existence." .

30.) schema:EmailMessage - ok

OK, added as http://schema.org/docs/releases.html#g1020

2.2: schema:EmailMessage rdfs:subClassOf schema:CreativeWork .
3.0: schema:EmailMessage rdfs:subClassOf schema:Message .


31.) Game - ok (removed explicit link to openissues list)

2.2: schema:Game rdfs:comment "The Game type represents things which are games. These are typically rule-governed recreational activities, e.g. role-playing games in which players assume the role of characters in a fictional setting. See also <a href=\"https://github.com/rvguha/schemaorg/issues/169\">open issues list</a>." .
3.0: schema:Game rdfs:comment "The Game type represents things which are games. These are typically rule-governed recreational activities, e.g. role-playing games in which players assume the role of characters in a fictional setting." .

32.) PreOrder - ok reworded.

2.2: schema:PreOrder rdfs:comment "Indicates that the item is available for pre-order." .
3.0: schema:PreOrder rdfs:comment "Indicates that the item is available for pre-order, but will be delivered when generally available." .

33.) PriceSpecification - ok, tweaked when MonetaryAmount was added.

2.2: schema:PriceSpecification rdfs:comment "A structured value representing a monetary amount. Typically, only the subclasses of this type are used for markup." .
3.0: schema:PriceSpecification rdfs:comment "A structured value representing a price or price range. Typically, only the subclasses of this type are used for markup. It is recommended to use [[MonetaryAmount]] to describe independent amounts of money such as a salary, credit card limits, etc." .


34.) Series - ok, superseded statement backed out due to addition of EventSeries.

2.2: schema:Series schema:supersededBy schema:CreativeWorkSeries .
3.0: No comment on this.

35.) Whitespace - ok - both of these had whitespace trimmed

schema:TaxiReservation rdfs:label " TaxiReservation" .
schema:TrainReservation rdfs:label " TrainReservation" .

36.) acceptsReservations - ok, s/a/an/

2.2: schema:acceptsReservations rdfs:comment "Indicates whether a FoodEstablishment accepts reservations. Values can be Boolean, a URL at which reservations can be made or (for backwards compatibility) the strings <code>Yes</code> or <code>No</code>." .
3.0: schema:acceptsReservations rdfs:comment "Indicates whether a FoodEstablishment accepts reservations. Values can be Boolean, an URL at which reservations can be made or (for backwards compatibility) the strings <code>Yes</code> or <code>No</code>." .

37.)  action - ok

2.2: schema:action a rdf:Property ;
    rdfs:label "action" ;
    schema:domainIncludes schema:Muscle ;
    schema:rangeIncludes schema:Text ;
    schema:supersededBy schema:muscleAction ;
    rdfs:comment "The movement the muscle generates." .

3.0: moved to extension - http://health-lifesci.schema.org/action - and indicated obsolete for muscleAction.

38.) actor - ok, allowed on events too now.

2.2: schema:actor rdfs:comment "An actor, e.g. in tv, radio, movie, video games etc. Actors can be associated with individual items or with a series, episode, clip." .
3.0: schema:actor schema:domainIncludes schema:Event ;
    rdfs:comment "An actor, e.g. in tv, radio, movie, video games etc., or in an event. Actors can be associated with individual items or with a series, episode, clip." .

39.) branchCode TODO

2.2: schema:branchCode schema:domainIncludes schema:LocalBusiness,
        schema:Store .
3.0: MISSING: RESTORE.

40.) branchOf - ok, clarified

2.2: schema:branchOf rdfs:comment "The larger organization that this local business is a branch of, if any." .
3.0: schema:branchOf rdfs:comment "The larger organization that this local business is a branch of, if any. Not to be confused with (anatomical)[[branch]]." .

41.) catalog - ok

2.2: schema:catalog schema:supersededBy schema:includedDataCatalog ;
    rdfs:comment "A data catalog which contains a dataset." .
3.0: schema:catalog schema:supersededBy schema:includedInDataCatalog ;
    rdfs:comment "A data catalog which contains this dataset." .

42.) category - ok

2.2: schema:category schema:domainIncludes schema:PhysicalActivity ;
    schema:rangeIncludes schema:PhysicalActivityCategory .

3.0: these triples moved to extension. base definition still in core.

43.) composer - ok, added Event

2.2: schema:composer rdfs:comment "The person or organization who wrote the composition." .
3.0: schema:composer schema:domainIncludes schema:Event ;
    rdfs:comment "The person or organization who wrote a composition, or who is the composer of a work performed at some event." .

44.) contributor - ok, added Event

2.2: schema:contributor rdfs:comment "A secondary contributor to the CreativeWork." .
3.0: schema:contributor schema:domainIncludes schema:Event ;
    rdfs:comment "A secondary contributor to the CreativeWork or Event." .

45.) cookTime - TODO, restore hyperlink

2.2: schema:cookTime rdfs:comment "The time it takes to actually cook the dish, in <a href='http://en.wikipedia.org/wiki/ISO_8601'>ISO 8601 duration format</a>." .
3.0: schema:cookTime rdfs:comment "The time it takes to actually cook the dish, in ISO 8601 duration format." .

46.) dataset - ok

2.2: schema:dataset rdfs:comment "A dataset contained in a catalog." .
3.0: schema:dataset schema:inverseOf schema:includedInDataCatalog ;
    rdfs:comment "A dataset contained in this catalog." .

47.) director - ok, added Event

2.2: schema:director rdfs:comment "A director of e.g. tv, radio, movie, video games etc. content. Directors can be associated with individual items or with a series, episode, clip." .
3.0: schema:director schema:domainIncludes schema:Event ;
    rdfs:comment "A director of e.g. tv, radio, movie, video gaming etc. content, or of an event. Directors can be associated with individual items or with a series, episode, clip." .


##### CHANGES relating to additions in 3.0 (triples that were not in 2.2)

48.) ok: Additions for FIBO

BankAccount, CompoundPriceSpecification, FinancialProduct, DepositAccount, CurrencyConversionService,
InvestmentOrDeposit, LoanOrCredit, MonetaryAmount, CreditCard, DatedMoneySpecification,

49.) ok: other additions

Added types (ok):
ComputerLanguage, Conversation, DigitalDocument, DigitalDocumentPermission,
DigitalDocumentPermissionType, GenderType, Message, NoteDigitalDocument, PresentationDigitalDocument,
RestrictedDiet, SpreadsheetDigitalDocument, TextDigitalDocument, AudiobookFormat,
CommentPermission,DiabeticDiet, Female, Friday, GlutenFreeDiet, HalalDiet,
HinduDiet, KosherDiet, LowCalorieDiet, LowFatDiet, LowLactoseDiet, LowSaltDiet,
Male, Monday, PreSale, PublicHolidays, ReadPermission, Saturday, Sunday,
Thursday,
Tuesday, VeganDiet, VegetarianDiet, Wednesday, WritePermission,

added assertions (ok):

schema:acceptedPaymentMethod schema:rangeIncludes schema:LoanOrCredit .

schema:audience schema:domainIncludes schema:Service . (#1005)

schema:programmingLanguage schema:rangeIncludes schema:ComputerLanguage,
        schema:Text .
schema:recipient schema:domainIncludes schema:Message .
schema:validFrom schema:domainIncludes schema:MonetaryAmount .

schema:validThrough schema:domainIncludes schema:JobPosting,
        schema:MonetaryAmount ;
    rdfs:comment "The date after when the item is not valid. For example the end of an offer, salary period, or a period of opening hours." .

    schema:subEvent schema:inverseOf schema:superEvent .
    schema:superEvent schema:inverseOf schema:subEvent .


(and similar - not listing all here.)


added properties (ok):
dateRead, dateReceived, dateSent, disambiguatingDescription,
grantee, hasDigitalDocumentPermission, messageAttachment,
minimumPaymentDue, permissionType, suitableForDiet, isBasedOn,


FIBO-related properties (ok): feesAndCommissionsSpecification,
interestRate, leiCode, loanTerm, priceComponent,
referenceQuantity, requiredCollateral,

Other misc changes (ok):

* gtin12 etc updated URLs to fix broken links.
* typo in icaoCode fixed.
* inLanguage now cites bcp-47
* mainEntityOfPage - linked datamodel.html entry
* netWorth tweaked

50.) TODOs


Dentist?
In 3.0, added:
schema:Dentist rdfs:label " Dentist" ;
    rdfs:subClassOf schema:ProfessionalService .
removed (to extension - check):
schema:Dentist rdfs:label "Dentist" .
schema:Dentistry a schema:MedicalSpecialty ;
    rdfs:label "Dentistry" ;
    rdfs:comment "Dentistry." .

doublecheck addition/edit:
schema:MedicalOrganization rdfs:comment "A medical organization (physical or not), such as hospital, institution or clinic." ;
    rdfs:subClassOf schema:Organization .

51.) schema:CheckInAction  - trivial change - ok

...

52.) Language - ok
schema:Language rdfs:comment "Natural languages such as Spanish, Tamil, Hindi, English, etc. Formal language code tags expressed in [BCP 47](https://en.wikipedia.org/wiki/IETF_language_tag) can be used via the [[alternateName]] property. The Language type previously also covered programming languages such as Scheme and Lisp, which are now best represented using [[ComputerLanguage]]." .

53.) Periodical - added link to blog post - ok

2.2: schema:Periodical rdfs:comment """A publication in any medium issued in successive parts bearing numerical or chronological designations and intended, such as a magazine, scholarly journal, or newspaper to continue indefinitely.
3.0: schema:Periodical rdfs:comment "A publication in any medium issued in successive parts bearing numerical or chronological designations and intended, such as a magazine, scholarly journal, or newspaper to continue indefinitely.\\n\\nSee also [blog post](http://blog.schema.org/2014/09/schemaorg-support-for-bibliographic_2.html)." .

54.)  PreSale - ok - added for #888

55.) availableLanguage -ok

2.2: schema:availableLanguage rdfs:comment "A language someone may use with the item.
TODO: We should restore this edit, https://github.com/schemaorg/schemaorg/pull/513/files

2.2: schema:codeSampleType rdfs:comment "What type of code sample: full (compile ready) solution, code snippet, inline code, scripts, template." .
3.0: schema:codeSampleType rdfs:comment "Full (compile ready) solution, code snippet, inline code, scripts, template." .

TODO: Also fix sampleType (the superseded version).

57.) colleague expects URL now - ok

Added for JSON-LD, https://github.com/schemaorg/schemaorg/issues/929

58.) isBasedOnUrl - ok  - #950

schema:isBasedOnUrl schema:rangeIncludes schema:CreativeWork,
        schema:Product ;
    schema:supersededBy schema:isBasedOn .

59.) isRelatedTo, isSimilarTo , logo - added for Service #1005 - ok

60.) TODO: netWorth - rollback of https://github.com/schemaorg/schemaorg/issues/585

We chose to exclude "organization" from the text. This was rolled back in schema.rdfa and should be re-excluded,
pending input from FIBO et al.


61.) trivial change to schemaVersion (s/a/an/) - ok

2.2: schema:schemaVersion rdfs:comment "Indicates (by URL or string) a particular version of a schema used in some CreativeWork. For example, a document could declare a schemaVersion using a URL such as http://schema.org/version/2.0/ if precise indication of schema version was required by some application. " .
3.0: schema:schemaVersion rdfs:comment "Indicates (by URL or string) a particular version of a schema used in some CreativeWork. For example, a document could declare a schemaVersion using an URL such as http://schema.org/version/2.0/ if precise indication of schema version was required by some application. " .

62.) trivial (a/an) - urlTemplate - ok

2.2: schema:urlTemplate rdfs:comment "A url template (RFC6570) that will be used to construct the target of the execution of the action." .
3.0: schema:urlTemplate rdfs:comment "An url template (RFC6570) that will be used to construct the target of the execution of the action." .

63.) value - added MonetaryAmount - ok

2.2: schema:value rdfs:comment "The value of the quantitative value or property value node. For QuantitativeValue, the recommended type for values is 'Number'. For PropertyValue, it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'." .
3.0: schema:value schema:domainIncludes schema:MonetaryAmount ;
    rdfs:comment """The value of the quantitative value or property value node.<br/>
	For QuantitativeValue and MonetaryValue, the recommended type for values is 'Number'. <br/>
	For PropertyValue, it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'.""" .

64.) PriceSpecification - added MonetaryAmount mention - ok

2.2: schema:PriceSpecification rdfs:comment "A structured value representing a monetary amount. Typically, only the subclasses of this type are used for markup." .
3.0: schema:PriceSpecification rdfs:comment "A structured value representing a price or price range. Typically, only the subclasses of this type are used for markup. It is recommended to use [[MonetaryAmount]] to describe independent amounts of money such as a salary, credit card limits, etc." .

...