profile
viewpoint
Shigeya Suzuki shigeya Project Professor, Keio University, @keio-bcl, @Auto-ID-Labs, @Auto-ID-Lab-Japan Tokyo, Japan http://member.wide.ad.jp/~shigeya/ Researcher, Professor, Software Developer, Engineer.

shigeya/jekyll-category-archive-plugin 79

Jekyll plugin for category archive

shigeya/distribute2 3

Nearly 20 years old Classic distribute mailing list sequencer. Version 2 series. This is the first of this sort which introduced mailing list sequences. Not maintained well (till now)

shigeya/IT-terminologies-en-ja 3

IT Terminologies Translation List in English-Japanese

shigeya/capybara-webkit 1

A capybara driver that uses WebKit via QtWebKit.

shigeya/fetch-parse-jws 1

Fetch and Parse Journalist Wall of Shame

shigeya/HBscripts 1

Utility scripts to parse output of HandBrake CLI for analyze disc parameters

shigeya/jekyll 1

Jekyll is a blog-aware, static site generator in Ruby

shigeya/bitcoin 0

Bitcoin Core integration/staging tree

shigeya/BubbleWrap 0

Cocoa wrappers and helpers for RubyMotion (Ruby for iOS) - Making Cocoa APIs more Ruby like, one API at a time. Fork away and send your pull requests.

PullRequestReviewEvent

startedmerlos/iOS-Open-GPX-Tracker

started time in 18 days

fork shigeya/vc-wg-charter

Developing a new charter for the VC WG.

https://w3c.github.io/vc-wg-charter/

fork in 19 days

issue commentw3c/vc-wg-charter

Standardization of Multilingual Support

I forgot to mention that I (of course) want to contribute. I'm thinking about how this work fits into the charter and looking forward to having discussions/comments.

shigeya

comment created time in 19 days

startedw3c/vc-wg-charter

started time in 19 days

issue openedw3c/vc-wg-charter

Standardization of Multilingual Support

As I mentioned during the TPAC 2022 VC meeting two weeks ago, we need multilingual support, especially for Asian countries.

While some examples (even the first example) in the Verifiable Credential 1.1 spec show how you can encode multinational strings into a property value, there is a lack of discussion about this scheme.

Since these strings need to be content-integrity protected, externalizing translation mapping is not an option; multilingual support must be part of the Verifiable Credentials Data Model.

In Japan, we already observe difficulty in vaccination certificates since we need to use English for overseas purposes and Japanese for domestic purposes. Both the data model and the software support are in need. Thus, standardizing support in the Verifiable Credentials Data Model is necessary.

We understand this is a challenging topic, especially when looking at the data representation syntax point of view. But for the more general, international adoption, we need multilingual support without affecting single-lingual syntax.

I think including this work as part of Verifiable Credential 2.0 work is essential.

created time in 19 days

PR closed w3c/did-spec-registries

Reviewers
Registering did:dnssec method

<!-- This comment and the below content is programatically generated. You may add a comma-separated list of anchors you'd like a direct link to below (e.g. #idl-serializers, #idl-sequence):

Don't remove this comment or modify anything below this line.
If you don't want a preview generated for this pull request,
just replace the whole of this comment's content by "no preview"
and remove what's below.

-->


<a href="https://pr-preview.s3.amazonaws.com/shigeya/did-spec-registries/pull/336.html" title="Last updated on Sep 3, 2021, 12:26 AM UTC (46777fe)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/did-spec-registries/336/55da218...shigeya:46777fe.html" title="Last updated on Sep 3, 2021, 12:26 AM UTC (46777fe)">Diff</a>

+17 -0

7 comments

1 changed file

shigeya

pr closed time in 21 days

pull request commentw3c/did-spec-registries

Registering did:dnssec method

Withdrawing this PR. Will be back...

shigeya

comment created time in 21 days

pull request commentw3c/did-spec-registries

Registering did:dnssec method

@OR13 I had no time working on this last October. I will try to address this.

If you prefer not having this kind of PR (not ready and staying as PR for a while) I'm ok to withdraw until it's ready.

shigeya

comment created time in 21 days

startedw3c/w3process

started time in a month

startedw3c/vc-wg-charter

started time in a month

startedcopy/v86

started time in a month

startedctc-selmid/wallet

started time in a month

startedmattrglobal/jsonld-signatures-bbs

started time in 2 months

startedyamdan/jsonld-signatures-bbs

started time in 2 months

startedyamdan/zkp-ld-playground

started time in 2 months

push eventbase-alliance/base-alliance

jaykishigami

commit sha dee8defddc0c0a3f4faff096d705cec90d983bed

Update 2021_10_08-basing_blockchain_4_materials.ja.md base-alliance/base-web@197235d3d59ebe6fa47b0071c00062e8a4b7a40b

view details

push time in 2 months

push eventbase-alliance/base-alliance

jaykishigami

commit sha 7f92f1ba80e656e06a3d14aad171fc52f7c07b03

Update 2021_10_08-basing_blockchain_4_materials.en.md base-alliance/base-web@ffff45d209bc2261e4d7bf0954b3cf149f20dc9d

view details

push time in 2 months

push eventbase-alliance/base-alliance

jaykishigami

commit sha 80a29021c03762036184ce075fa10a5f1222722f

Update 2021_10_08-basing_blockchain_4_materials.ja.md plus Prof.Yamasaki file base-alliance/base-web@9ae5a12b50aec42045eec2750eb261c91479a6e2

view details

push time in 2 months

push eventbase-alliance/base-alliance

jaykishigami

commit sha 13b94d3f69cea106c5da8e8d86fe4227dbeb029a

Add files via upload base-alliance/base-web@cbb0519dbfdfe70fa1c2f0774db5bce16c4d8cc0

view details

push time in 2 months

startedopenssl/openssl

started time in 2 months

push eventbase-alliance/base-alliance

shigeya

commit sha afddf109ade3a999cd03ea0683ea6222ae7197cc

More minor fixes base-alliance/base-web@0eb75c4f01e25abc4749071b756fa7517d9f75df

view details

push time in 2 months

push eventbase-alliance/base-alliance

shigeya

commit sha 0cd0726996d86727b4896addef867bcc2e816a3f

More space fixes base-alliance/base-web@ff0befca276cd727a71e5a202cf325d0ad041fda

view details

push time in 2 months

push eventbase-alliance/base-alliance

shigeya

commit sha 1e3d190935c6527e660c34acd5f6759299917ae7

Changing erroneous zenkaku-space to hankaku base-alliance/base-web@ab4e538ddcb2f985014f74cb7ebebf7d0c3b9db1

view details

push time in 2 months

push eventbase-alliance/base-alliance

shigeya

commit sha fbb6fd21dab0cafdf70e1cfc42c5a8d9ec400e01

Updating themes (2) base-alliance/base-web@117fdf134f92eba25e286d0761da618de5cc60e4

view details

push time in 2 months

push eventbase-alliance/base-alliance

shigeya

commit sha 94e981be03d4eb454593d1548da1d145d7d65ec1

Presentation materials for Matsuura-san and Shigeya base-alliance/base-web@2e85ffc0f186ae6ef7b2e7dcb40bd7bcf50032cc

view details

push time in 2 months

push eventbase-alliance/base-alliance

shigeya

commit sha 98b81a909880340363221c0ab70f56984e65082f

Cancellation Update on 4th base-alliance/base-web@c9c3bf9eec29d497bdba839d5c26e90e46a84ed2

view details

push time in 2 months

push eventshigeya/oo2md2tex

dependabot[bot]

commit sha 7b1d0c648125abe38ccac41e2946ce93d72a677b

Bump nokogiri from 1.11.4 to 1.12.5 in /sample/v3 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.11.4 to 1.12.5. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.11.4...v1.12.5) --- updated-dependencies: - dependency-name: nokogiri dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

view details

Shigeya Suzuki

commit sha edface160fd0d473b51aa1e62294e82b0ccc0e22

Merge pull request #6 from shigeya/dependabot/bundler/sample/v3/nokogiri-1.12.5 Bump nokogiri from 1.11.4 to 1.12.5 in /sample/v3

view details

push time in 2 months

PR merged shigeya/oo2md2tex

Bump nokogiri from 1.11.4 to 1.12.5 in /sample/v3 dependencies

Bumps nokogiri from 1.11.4 to 1.12.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sparklemotion/nokogiri/releases">nokogiri's releases</a>.</em></p> <blockquote> <h2>1.12.5 / 2021-09-27</h2> <h3>Security</h3> <p>[JRuby] Address CVE-2021-41098 (<a href="https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-2rr5-8q37-2w7h">GHSA-2rr5-8q37-2w7h</a>).</p> <p>In Nokogiri v1.12.4 and earlier, on JRuby only, the SAX parsers resolve external entities (XXE) by default. This fix turns off entity-resolution-by-default in the JRuby SAX parsers to match the CRuby SAX parsers' behavior.</p> <p>CRuby users are not affected by this CVE.</p> <h3>Fixed</h3> <ul> <li>[CRuby] <code>Document#to_xhtml</code> properly serializes self-closing tags in libxml > 2.9.10. A behavior change introduced in libxml 2.9.11 resulted in emitting start and and tags (e.g., <code><br></br></code>) instead of a self-closing tag (e.g., <code><br/></code>) in previous Nokogiri versions. [<a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/2324">#2324</a>]</li> </ul> <hr /> <p>SHA256 checksums:</p> <pre><code>36bfa3a07aced069b3f3c9b39d9fb62cb0728d284d02b079404cd55780beaeff nokogiri-1.12.5-arm64-darwin.gem 16b1a9ddbb70a9c998462912a5972097cbc79c3e01eb373906886ef8a469f589 nokogiri-1.12.5-java.gem 218dcc6edd1b49cc6244b5f88afb978739bb2f3f166c271557fe5f51e4bc713c nokogiri-1.12.5-x64-mingw32.gem e33bb919d64c16d931a5f26dc880969e587d225cfa97e6b56e790fb52179f527 nokogiri-1.12.5-x86-linux.gem e13c2ed011b8346fbd589e96fe3542d763158bc2c7ad0f4f55f6d801afd1d9ff nokogiri-1.12.5-x86-mingw32.gem 1ed64f7db7c1414b87fce28029f2a10128611d2037e0871ba298d00f9a00edd6 nokogiri-1.12.5-x86_64-darwin.gem 0868c8d0a147904d4dedaaa05af5f06656f2d3c67e4432601718559bf69d6cea nokogiri-1.12.5-x86_64-linux.gem 2b20905942acc580697c8c496d0d1672ab617facb9d30d156b3c7676e67902ec nokogiri-1.12.5.gem </code></pre> <h2>1.12.4 / 2021-08-29</h2> <h3>Notable fix: Namespace inheritance</h3> <p>Namespace behavior when reparenting nodes has historically been poorly specified and the behavior diverged between CRuby and JRuby. As a result, making this behavior consistent in v1.12.0 introduced a breaking change.</p> <p>This patch release reverts the Builder behavior present in v1.12.0..v1.12.3 but keeps the Document behavior. This release also introduces a Document attribute to allow affected users to easily change this behavior for their legacy code without invasive changes.</p> <h4>Compensating Feature in XML::Document</h4> <p>This release of Nokogiri introduces a new <code>Document</code> boolean attribute, <code>namespace_inheritance</code>, which controls whether children should inherit a namespace when they are reparented. <code>Nokogiri::XML:Document</code> defaults this attribute to <code>false</code> meaning "do not inherit," thereby making explicit the behavior change introduced in v1.12.0.</p> <p>CRuby users who desire the pre-v1.12.0 behavior may set <code>document.namespace_inheritance = true</code> before reparenting nodes.</p> <p>See <a href="https://nokogiri.org/rdoc/Nokogiri/XML/Document.html#namespace_inheritance-instance_method">https://nokogiri.org/rdoc/Nokogiri/XML/Document.html#namespace_inheritance-instance_method</a> for example usage.</p> <h4>Fix for XML::Builder</h4> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md">nokogiri's changelog</a>.</em></p> <blockquote> <h2>1.12.5 / 2021-09-27</h2> <h3>Security</h3> <p>[JRuby] Address CVE-2021-41098 (<a href="https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-2rr5-8q37-2w7h">GHSA-2rr5-8q37-2w7h</a>).</p> <p>In Nokogiri v1.12.4 and earlier, on JRuby only, the SAX parsers resolve external entities (XXE) by default. This fix turns off entity-resolution-by-default in the JRuby SAX parsers to match the CRuby SAX parsers' behavior.</p> <p>CRuby users are not affected by this CVE.</p> <h3>Fixed</h3> <ul> <li>[CRuby] <code>Document#to_xhtml</code> properly serializes self-closing tags in libxml > 2.9.10. A behavior change introduced in libxml 2.9.11 resulted in emitting start and and tags (e.g., <code><br></br></code>) instead of a self-closing tag (e.g., <code><br/></code>) in previous Nokogiri versions. [<a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/2324">#2324</a>]</li> </ul> <h2>1.12.4 / 2021-08-29</h2> <h3>Notable fix: Namespace inheritance</h3> <p>Namespace behavior when reparenting nodes has historically been poorly specified and the behavior diverged between CRuby and JRuby. As a result, making this behavior consistent in v1.12.0 introduced a breaking change.</p> <p>This patch release reverts the Builder behavior present in v1.12.0..v1.12.3 but keeps the Document behavior. This release also introduces a Document attribute to allow affected users to easily change this behavior for their legacy code without invasive changes.</p> <h4>Compensating Feature in XML::Document</h4> <p>This release of Nokogiri introduces a new <code>Document</code> boolean attribute, <code>namespace_inheritance</code>, which controls whether children should inherit a namespace when they are reparented. <code>Nokogiri::XML:Document</code> defaults this attribute to <code>false</code> meaning "do not inherit," thereby making explicit the behavior change introduced in v1.12.0.</p> <p>CRuby users who desire the pre-v1.12.0 behavior may set <code>document.namespace_inheritance = true</code> before reparenting nodes.</p> <p>See <a href="https://nokogiri.org/rdoc/Nokogiri/XML/Document.html#namespace_inheritance-instance_method">https://nokogiri.org/rdoc/Nokogiri/XML/Document.html#namespace_inheritance-instance_method</a> for example usage.</p> <h4>Fix for XML::Builder</h4> <p>However, recognizing that we want <code>Builder</code>-created children to inherit namespaces, Builder now will set <code>namespace_inheritance=true</code> on the underlying document for both JRuby and CRuby. This means that, on CRuby, the pre-v1.12.0 behavior is restored.</p> <p>Users who want to turn this behavior off may pass a keyword argument to the Builder constructor like so:</p> <pre lang="ruby"><code>Nokogiri::XML::Builder.new(namespace_inheritance: false) </code></pre> <p>See <a href="https://nokogiri.org/rdoc/Nokogiri/XML/Builder.html#label-Namespace+inheritance">https://nokogiri.org/rdoc/Nokogiri/XML/Builder.html#label-Namespace+inheritance</a> for example usage.</p> <h4>Downstream gem maintainers</h4> <p>Note that any downstream gems may want to specifically omit Nokogiri v1.12.0--v1.12.3 from their dependency specification if they rely on child namespace inheritance:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sparklemotion/nokogiri/commit/47f6a461fdc3e375b30522259e48569fb578dece"><code>47f6a46</code></a> version bump to v1.12.5</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/2a0ac88518fdd1509d14c4cbdb9784c73dd8a839"><code>2a0ac88</code></a> update CHANGELOG</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/6b6063782cefc42e527dc967c6119125cae0042d"><code>6b60637</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/2329">#2329</a> from sparklemotion/flavorjones-GHSA-2rr5-8q37-2w7h_1...</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/4bd943cae3039c51c3f54de9cd76abbfb647666b"><code>4bd943c</code></a> fix(jruby): SAX parser uses an entity resolver</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/f943ee4108b007d225e00c3ac7da00df17b81b1a"><code>f943ee4</code></a> refactor(jruby): handle errors more consistently</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/27901227488ea7e439777cfc907e52c68622e6a3"><code>2790122</code></a> format: test files</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/01e1618f7551ae3c32c1a5790c1004c18a46b316"><code>01e1618</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/2327">#2327</a> from sparklemotion/2324-xhtml-self-closing-tags_v1.12.x</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/a0180c72c55c44b8e0db3a98040bd5f115742817"><code>a0180c7</code></a> fix: HTML4::Document.to_xhtml self-closing tags</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/564ac1787303332e0b2b92311ff6f1b30a893eae"><code>564ac17</code></a> release v1.12.4</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/4d5754baede4fc98cd4f12754f479bd228b6b55b"><code>4d5754b</code></a> backport <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/2320">#2320</a></li> <li>Additional commits viewable in <a href="https://github.com/sparklemotion/nokogiri/compare/v1.11.4...v1.12.5">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+2 -2

0 comment

1 changed file

dependabot[bot]

pr closed time in 2 months

push eventshigeya/oo2md2tex

dependabot[bot]

commit sha f822c3de7f12cba6b319e54753fc7791a68b2d8f

Bump nokogiri from 1.11.4 to 1.12.5 in /sample/v5 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.11.4 to 1.12.5. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.11.4...v1.12.5) --- updated-dependencies: - dependency-name: nokogiri dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

view details

Shigeya Suzuki

commit sha 3bf460e3a80c9488d73714de9b4e5fe3d2b5324a

Merge pull request #7 from shigeya/dependabot/bundler/sample/v5/nokogiri-1.12.5 Bump nokogiri from 1.11.4 to 1.12.5 in /sample/v5

view details

push time in 2 months

more