New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
danbri opened this Issue Apr 3, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@danbri
Contributor

danbri commented Apr 3, 2014

This issue is 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

@danbri danbri changed the title from supercedes should work on types as well as properties to CODE: supercedes should work on types as well as properties Jun 15, 2014

@danbri danbri added the python code label Jun 16, 2014

vholland referenced this issue in vholland/schemaorg Sep 15, 2014

Merge pull request #3 from vholland/sdo-itemlist
Moved ItemList out of CreativeWork and extended the domain for CreativeW...

@danbri danbri modified the milestone: sdo-venkman release Oct 12, 2014

danbri pushed a commit that referenced this issue Dec 11, 2014

Merge pull request #3 from danbri/tilid-VideoGame
Linked github. Deleted unwanted text.

@danbri danbri closed this May 12, 2015

@danbri danbri self-assigned this May 12, 2015

@danbri danbri removed this from the sdo-gozer release milestone Sep 8, 2015

@danbri

This comment has been minimized.

Show comment
Hide comment
Contributor

danbri commented Sep 8, 2015

@danbri danbri changed the title from CODE: supercedes should work on types as well as properties to Meta bug to provide overview of all python/site tool issues Sep 8, 2015

@danbri danbri reopened this Sep 8, 2015

@danbri danbri referenced this issue Sep 8, 2015

Open

Meta: schema.org planning #1

14 of 20 tasks complete

RichardWallis added a commit that referenced this issue Sep 18, 2015

Extension navigation from (#3)
Enhancements:
  Full listing for extension only
  Type/Property counts on docs/schemas.html
  Link to extensions on docs/schemas.html
  Type/Property listings on extension home pages
@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Feb 2, 2017

Contributor

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

Contributor

danbri commented Feb 2, 2017

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

@RichardWallis

This comment has been minimized.

Show comment
Hide comment
@RichardWallis

RichardWallis Feb 2, 2017

Contributor

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.

Contributor

RichardWallis commented Feb 2, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment