Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / tdwg/vocab issues and pull requests
#53 - Two dead resource links
Issue -
State: closed - Opened by rowan-ardc over 3 years ago
- 1 comment
#52 - https://www.tdwg.org/standards/147 > 404 Not Found error
Issue -
State: closed - Opened by PacoPando about 6 years ago
- 2 comments
#51 - Added spaces after Markdown headers for correct render
Pull Request -
State: closed - Opened by gaurav over 7 years ago
#50 - Minor typographical issues documentation-specification.md
Pull Request -
State: closed - Opened by dagendresen over 7 years ago
- 1 comment
#49 - SKOS and other demands of descriptors with unique values
Issue -
State: closed - Opened by ramorrismorris over 7 years ago
- 1 comment
#48 - RFC 2119 notation text
Issue -
State: closed - Opened by dagendresen over 7 years ago
- 1 comment
#47 - Response to expert review
Issue -
State: closed - Opened by baskaufs almost 8 years ago
- 3 comments
#46 - Decision history for vocabulary changes
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 1 comment
Labels: documentation, maintenance
#45 - Enabling "semantically enhanced" vocabularies through vocabulary extension term lists
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 4 comments
#44 - terms by inclusion
Issue -
State: closed - Opened by ramorrismorris over 8 years ago
- 1 comment
#43 - Term Labels
Issue -
State: closed - Opened by tucotuco over 8 years ago
- 4 comments
#42 - Inconsistent English language tags
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 4 comments
Labels: documentation
#41 - Documenting the date of death for terms in a vocabulary
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 4 comments
Labels: documentation, maintenance
#40 - What's a version?
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 10 comments
Labels: maintenance
#39 - Default serialization for RDF
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 11 comments
Labels: documentation
#38 - Licensing for vocabularies
Issue -
State: open - Opened by baskaufs over 8 years ago
- 4 comments
Labels: documentation
#37 - Acknowledging contributors to documents and standards
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 2 comments
Labels: documentation
#36 - Conventions for separating highly mutable components related to a standard
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 2 comments
#35 - What parts of term definitions are normative?
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 6 comments
Labels: documentation
#34 - Convention for presenting the namespace abbreviation as part of the term name
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 5 comments
Labels: documentation
#33 - Rules about IRI construction
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 11 comments
Labels: documentation
#32 - Does TDWG have a web page that contains copyright, licensing, and disclamer statements?
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 6 comments
Labels: documentation
#31 - Specification of Introduction, Motivation, and Rationale sections
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 5 comments
Labels: documentation
#30 - Should navigation methods be specified in the documentation spec?
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 5 comments
Labels: documentation
#29 - Investigate the standard practice for reporting names
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 4 comments
Labels: documentation
#28 - Use of "Supersedes" vs. "Previous version"
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 5 comments
Labels: documentation
#27 - Revise draft documentation specification and initiate review process
Issue -
State: closed - Opened by baskaufs over 8 years ago
- 17 comments
Labels: documentation
#26 - DwC class hierarchy
Issue -
State: closed - Opened by ramorrismorris over 9 years ago
- 7 comments
#25 - Should specific formats be required or specified for human-readable documents?
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 1 comment
Labels: documentation
#24 - vocabulary document citations
Issue -
State: closed - Opened by ramorrismorris over 9 years ago
- 1 comment
Labels: documentation
#23 - At what point (if any) should implementation reports be required for vocabulary additions?
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 1 comment
Labels: maintenance
#22 - How in RDF do we link "imported" terms to TDWG vocabularies that adopt them?
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 2 comments
#21 - Include controlled vocabularies among the types of vocabularies that are maintained
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 1 comment
Labels: maintenance
#20 - Describe how controlled vocabularies should be documented
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 7 comments
Labels: documentation
#19 - Under what circumstances (if any) should the terms defined in RFC 2119 be used in TDWG Standards documentation?
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 3 comments
Labels: documentation
#18 - Determine whether specifying practices related to controlled vocabularies is in scope
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 4 comments
Labels: documentation, maintenance
#17 - Specify a model for deprecating vocabularies
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 3 comments
Labels: documentation, maintenance
#16 - Discussion
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 28 comments
#15 - Examine workflows for managing vocabularies used by other organizations
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 2 comments
Labels: documentation, maintenance
#14 - Establish best practices for asserting relationships within RDF documents
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 8 comments
Labels: documentation
#13 - Criterion for assessing the need for a change to a vocabulary
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 3 comments
Labels: maintenance
#12 - Clarify the communication mechanisms that should be used during the change process
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 1 comment
Labels: maintenance
#11 - Establish a timeframe for addressing proposed changes to vocabularies
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 3 comments
Labels: maintenance
#10 - Review migrated Standards Documentation Specification
Issue -
State: closed - Opened by peterdesmet over 9 years ago
- 10 comments
#9 - Where do we keep documents, how do people find them, and how do people look at them?
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 11 comments
Labels: documentation, maintenance
#8 - Clarify roles of task groups, interest groups, the TAG in maintenance of vocabularies
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 9 comments
Labels: maintenance
#7 - Create a process to govern how non-term changes should be made to vocabulary standards
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 1 comment
Labels: maintenance
#6 - Revise Darwin Core Namespace Policy to make it applicable across TDWG vocabulary standards
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 5 comments
Labels: maintenance
#5 - Should the normative document be RDF, human-readable, or either?
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 4 comments
Labels: documentation
#4 - How is the normative part of a standard designated?
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 4 comments
Labels: documentation
#3 - Implications of vocabulary changes on interaction between applications and archived data
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 3 comments
Labels: documentation, maintenance
#2 - Complete draft Vocabulary Maintenance Specification
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 11 comments
Labels: maintenance
#1 - Complete draft Standards Documentation Standard
Issue -
State: closed - Opened by baskaufs over 9 years ago
- 6 comments
Labels: block, documentation