Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / w3c/rdf-dir-literal issues and pull requests

#24 - Acknowledge `zxx` in BCP47 section

Issue - State: open - Opened by marrus-sh over 4 years ago - 1 comment

#23 - Added compound literals

Pull Request - State: closed - Opened by iherman almost 5 years ago - 4 comments

#22 - Evolution approach to compound literals.

Issue - State: open - Opened by afs almost 5 years ago - 4 comments

#21 - Security considerations should stay

Issue - State: open - Opened by jyasskin almost 5 years ago - 1 comment
Labels: charter draft

#20 - Draft charter changes, related to issues #18 and #19

Pull Request - State: closed - Opened by iherman almost 5 years ago

#19 - direction agnostic querying

Issue - State: closed - Opened by joernhees about 5 years ago - 2 comments
Labels: charter draft, change on charter t.b.d.

#18 - Scope of "editorial errata"

Issue - State: closed - Opened by afs about 5 years ago - 4 comments
Labels: charter draft, change on charter t.b.d.

#17 - Advance notice draft

Pull Request - State: closed - Opened by iherman about 5 years ago

#16 - Update core doc

Pull Request - State: closed - Opened by iherman about 5 years ago

#15 - Timeline changes

Pull Request - State: closed - Opened by iherman about 5 years ago

#14 - Hybrid solution documented in the charter

Pull Request - State: closed - Opened by iherman about 5 years ago
Labels: charter draft

#13 - Proposal: find a transitional solution before updating langString

Issue - State: closed - Opened by pchampin about 5 years ago - 20 comments
Labels: charter draft

#12 - What about RDB2RDF?

Issue - State: closed - Opened by pchampin about 5 years ago - 3 comments
Labels: charter draft

#11 - Change timeline?

Issue - State: closed - Opened by iherman about 5 years ago - 1 comment
Labels: charter draft

#10 - Feasibility of the charter

Issue - State: open - Opened by iherman about 5 years ago - 5 comments
Labels: charter draft

#9 - fixed 2 broken links

Pull Request - State: closed - Opened by pchampin about 5 years ago - 1 comment

#8 - After first round

Pull Request - State: closed - Opened by iherman about 5 years ago - 2 comments

#7 - Do we need directional metadata in the first place ?

Issue - State: open - Opened by iherman about 5 years ago - 38 comments
Labels: preliminary discussions

#6 - Use cases for separate language and direction metadata

Issue - State: closed - Opened by aphillips about 5 years ago - 1 comment

#6 - Use cases for separate language and direction metadata

Issue - State: closed - Opened by aphillips about 5 years ago - 1 comment

#5 - Added a first draft for the introduction

Pull Request - State: closed - Opened by iherman about 5 years ago

#5 - Added a first draft for the introduction

Pull Request - State: closed - Opened by iherman about 5 years ago

#4 - Should 'auto' be part of the value space or only the lexical space?

Issue - State: open - Opened by iherman about 5 years ago
Labels: define localizableString, extend langString, preliminary discussions

#3 - In defense of extending language tags

Issue - State: open - Opened by pchampin about 5 years ago - 65 comments
Labels: extend bcp47, preliminary discussions

#2 - A point against `LocalizableString`: redundancy

Issue - State: open - Opened by pchampin about 5 years ago - 2 comments
Labels: define localizableString, preliminary discussions

#1 - Literal equality, and examples in appendix

Issue - State: open - Opened by chaals about 5 years ago - 9 comments
Labels: define localizableString, extend langString, preliminary discussions