Meta bug to provide overview of all python/site tool issues

[danbri]

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 (CODE: RDFa in per-term pages should include inverseOf, subPropertyOf #67) RDFa in per term pages should include inverseOf & subPropertyOf
  • Issue (The rdfs:subClassOf links in RDFa markup have room for improvement #217) The rdfs:subClassOf links in RDFa markup have room for improvement
  • Issue (Add Turtle dumps on per-term views #317) Add Turtle dumps on per-term views
  • Issue (Populate meta description with item description #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 (RDFa on Term page - subClassOf in odd place #1217) RDFa on Term page - subClassOf in odd place
• Example txt files
  • Issue (Automate comparison of examples with schema #54) Automate comparison of examples with Schema
  • Issue (Every example should have a unique ID #177) Every example should have a unique ID
  • Issue (Generate a list of terms that do not appear in examples e.g. AlignmentObject #499) Generate a list of terms that do not appear in examples
  • Issue (Schema.org workflow needs syntax-checkers integrated for all examples #1104) Workflow needs syntax-checkers integrated for all examples
  • Issue (Clean up .txt files #1145) Clean up .txt files
• Tests
  • Issue (tests/test_graphs.py should test supercededBy and inverseOf don't point to same thing #156) Test supercededBy & inverseOf don't point to same thing
  • Issue (Add a unit test ensuring sentences end in '.'. #250) Test ensuring sentences end on '.'
  • Issue (Add a SPARQL testcase to catch case where a property points to an enum that we forgot to enumerate #485) Testcase to catch case where a property points to an enum that we forgot to enumerate
  • Issue (Add a scripts/ utility for QA of Web-served functionality #782) Add a scripts/ utility for QA of Web-served functionality
  • Issue (Add a unit test warning if a property is inverseOf itself #1205) Unit test warning if a property is inverseOf itself
  • Issue (Need python API telling us which examples exist in < 3 formats #1280) Need python API telling us which examples exist in < 3 formats
  • Issue (Test to catch terms that are subtype/property of an attic term #1329) Test to catch terms that are subtype/property of an attic term
• Export formats / files
  • Issue (ENH: Always generate updated RDF, OWL, JSON-LD #197) Always generate updated RDF, OWL, JSON-LD
  • Issue (Add more export formats (e.g. as offered but obsolete at schema.rdfs.org) #208) Add more export formats
  • Issue (Content Negotiation for Turtle file #703) Content Negotiation for Turtle file
  • Issue (Add Turtle dumps on per-term views #317 ) Add Turtle dumps on per-term views
  • Issue (Representation of schema_org_rdfa in "canonized" Polyglot HTML5 #360) Representation of schema_org_rdfa in "canonized" Polyglot HTML5
  • Issue (CSV download of all terms #390) CSV download of all terms
  • Issue (Release snapshot format improvements #484) Release snapshot format improvements
  • Issue (Should the version history of the schema.org JSON-LD context file be archived? #1101) Should the version history of the schema.org JSONLD context file be archived.
• JSON-LD / Context
  • Issue (JSON-LD context problem for properties that can take both URL or Text #51) JSON-LD context problem for properties that can take both URL or Text
  • Issue (JSON-LD emerging best practice is to alias @type, @id (and other keywords) #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 (Add the chinese translations #491) Add the chinese translations
  • Issue (data/* schema files should have consistent language tagging #1282) data/*schema files should have consistent language tagging
• Meta vocabulary & display thereof
  • Issue (Add to RDFS conventions for see-also-issue-tracker, or see-also-documentation link #182) Add to RDFS Conventions for see-also-issue-tracker, or see-also-documentation link
  • Issues (schema:purpose is poorly defined #233) (#255) Add domainHint & rangeHints for properties
  • Issue (rdfs:comment encoding... Need quotation rules? #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 (Create process/UI/etc for terms that graduate from Pending (or get archived/abandoned) #1318) Create process/UI/etc for terms that graduate from Pending (or get archived/abandoned) - "attic"
• Site functionality
  • Issue (Site HTML should be responsive to people using tiny pocket computers #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

[danbri]

/cc @RichardWallis

[danbri]

@RichardWallis ... are any of these closed but not indicated as done here?

[RichardWallis]

I think #208 should be closed. Any remaining comments (eg. https) are covered elsewhere or probably not on the agenda for fixing now. I believe closing this, with the 3.2 release, will draw a line under this area so that any remaining suggestions and/or concerns can be built from a clean foundation.

I have marked #1282 as done because @en tags have come out of bib files but I can't track down when it happened- so left the issue still open.