profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/angelo-v/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Angelo Veltens angelo-v @codecentric Hamburg https://angelo.veltens.org/profile/card#me Software developer & IT consultant at codecentric.

angelo-v/docker-solid-server 18

Containerized version of node-solid-server

angelo-v/groovyrdf 12

Library for building and processing RDF data with Groovy

angelo-v/docker-testinfra 2

Testing docker images via testinfra

angelo-v/GroovySparql 1

Groovy Sparql

angelo-v/admin 0

A beautiful and fully-featured administration interface builder for hypermedia APIs

angelo-v/api-doc-parser 0

Transforms a Hydra API doc in an intermediate representation that can be used for various tasks such as creating smart API clients, scaffolding code or building administration interfaces.

angelo-v/docker 0

Docker - the open-source application container engine

angelo-v/docker-create-react-app 0

Dockerized create-react-app

PR opened solid/solid-ui

feat(buttons): created a renderdiv to render a person in a div

Overview This PR adds a new function renderAsDiv which will render a person (image, name, and link) in a div.

  1. includes renderAsDiv function
  2. a bit of a refactor.
  3. Tests
  4. And a storybook example

No breaking changes.

+25042 -76

0 comment

11 changed files

pr created time in 6 minutes

create barnchsolid/solid-ui

branch : person-div

created branch time in 8 minutes

push eventsolid/node-solid-server

bourgeoa

commit sha f95745ee4161d62c54d545b74c7003af1a633c61

getOwner(req)

view details

push time in 19 hours

startedrust-cloud-native/rust-cloud-native.github.io

started time in 19 hours

startedmelvincarvalho/aam

started time in 2 days

created repositorymelvincarvalho/aam

autonomous agent manager

created time in 2 days

startedcodesome/prometheus-slo

started time in 2 days

pull request commentsolid/web-access-control-spec

Initial Editor’s Draft of the WAC specification

I don't have the rights to review this. But here is my take:

  1. a lot of work went it it, and it is a big improvement over what was there previously. so +1 to let it through
  2. there is a huge amount more to do. As it stands it is not really useable for building decentralised hyper-apps because the only apps that can see the ACL document are those with control access: so either an app knows how to access a resource or it has to guess, or someone has to invent a complicated protocol to get around it. My fear is that because this is not addressed people are trying to build complicated protocols to get around it.
csarven

comment created time in 2 days

startedmoov-io/watchman

started time in 3 days

push eventsolid/web-access-control-spec

Sarven Capadisli

commit sha 74cbbdc298c462daa2fcb84fc80472ea5ba3dabd

Reinclude rdf-schema in namespaces

view details

Sarven Capadisli

commit sha 0b9b32ddfd40285bef3547c7166c8114fe9ea8a0

Wrap prefixes with code

view details

Sarven Capadisli

commit sha 9437c922cb3870b106525b33376643e2ea91f80c

List only MUST and MUST NOT in Conformance

view details

Sarven Capadisli

commit sha 42bbf5a7994d416c2adb461a2cbd3e05c577347a

Clarify parsing algorithm for field-value

view details

Sarven Capadisli

commit sha 510a5f16a4dcfb5415f576bbc3a4ac0ede1e5ebd

Clarify Control operation including view

view details

Sarven Capadisli

commit sha 09aa7dbc67370ff916bdf6622afbc965a0101f49

Link to effective-acl-resource

view details

Sarven Capadisli

commit sha c970116c15751faf51d1b892b7b58302982dc875

Remove 'see '

view details

Sarven Capadisli

commit sha d0c072a611f1d006145013c343bbb3784bd56796

Minor

view details

push time in 3 days

push eventsolid/web-access-control-spec

Sarven Capadisli

commit sha 2bef8a1cfb840f2e56b89f749dbeac9c9742ff04

Minor

view details

Sarven Capadisli

commit sha db1dc81f3efed5bc1c1f4ae5214c85f04858d4a5

Fix nav numbering

view details

push time in 3 days

fork deduktion/clojure

The Clojure programming language

https://clojure.org

fork in 3 days

push eventsolid/web-access-control-spec

Sarven Capadisli

commit sha 666308a60e956accb5b1e9d5ae4b7ba7685d1fb3

Fix example query

view details

push time in 3 days

release AKASHAorg/secure-webstore

v.1.3.5

released time in 3 days

release AKASHAorg/easy-web-crypto

v1.2.8

released time in 3 days

starteddoyensec/electronegativity

started time in 3 days

pull request commentw3c/EasierRDF

Changes "average developers" to "most developers" (drops 'mainstream')

Tagline still needs updating

Fixed, thanks.

dbooth-boston

comment created time in 3 days

pull request commentw3c/EasierRDF

Changes "average developers" to "most developers" (drops 'mainstream')

Tagline still needs updating

dbooth-boston

comment created time in 4 days

issue closedw3c/EasierRDF

Average developers (middle 33% of ability)

What does the following mean:

average developers (middle 33% of ability)

closed time in 4 days

amirouche

issue commentw3c/EasierRDF

Average developers (middle 33% of ability)

It seems we've reached consensus on this, so I've merged PR #86, and I'm closing this issue. Thanks all, for helping to reach this improvement!

amirouche

comment created time in 4 days

PR merged w3c/EasierRDF

s/average/most mainstream developers/g

Inspired by @afs 's suggestion , in response to issue #79.

+3 -3

0 comment

1 changed file

dbooth-boston

pr closed time in 4 days

push eventw3c/EasierRDF

David Booth

commit sha 406015d86701f0cfd2b22bc4e42558104006031e

most mainstream developers

view details

David Booth

commit sha 9b43c07dbe8ddd2ace4392f1a733abc06b12e31e

Deleted 'mainstream'

view details

David Booth

commit sha 539f9dfbf8109bfa88d260d1a67fc60a673cd1cf

Merge pull request #86 from w3c/most2 Changes "average developers" to "most developers" (drops 'mainstream')

view details

push time in 4 days

startedjquense/yup

started time in 4 days

startedcolinhacks/zod

started time in 4 days

Pull request review commentHydraCG/Specifications

Added support for strongly typed collections

 <h4>Member assertions</h4>     <p class="note">It's important to point out that the <code>subject</code>, <code>property</code>       and <code>object</code> predicates are defined within the Hydra namespace and are not       <a href="https://www.w3.org/TR/rdf-schema/"><code>rdf</code></a> terms.</p>++    <p>It is also possible to use <i>memberAssertion</i> predicate on the API documentation level,+      by attaching this predicate to subclasses of the <i>Collection</i>, like in the example below:</p>++    <pre class="example nohighlight"+         data-transform="updateExample"+         title="Member assertion block describes strongly typed collection">+      <!--+      {+        "@context": "http://www.w3.org/ns/hydra/context.jsonld",

Adding this so that we can have a valid api: prefix as used below

        "@context": [
          "http://www.w3.org/ns/hydra/context.jsonld",
          {
            "api": "http://api.example.com/api/documentation#"
          }
        ],
alien-mcl

comment created time in 4 days

Pull request review commentHydraCG/Specifications

Added support for strongly typed collections

 <h4>Member assertions</h4>     <p class="note">It's important to point out that the <code>subject</code>, <code>property</code>       and <code>object</code> predicates are defined within the Hydra namespace and are not       <a href="https://www.w3.org/TR/rdf-schema/"><code>rdf</code></a> terms.</p>++    <p>It is also possible to use <i>memberAssertion</i> predicate on the API documentation level,+      by attaching this predicate to subclasses of the <i>Collection</i>, like in the example below:</p>++    <pre class="example nohighlight"+         data-transform="updateExample"+         title="Member assertion block describes strongly typed collection">+      <!--+      {+        "@context": "http://www.w3.org/ns/hydra/context.jsonld",+        "@id": "http://api.example.com/api/documentation",+        "@type": "ApiDocumentation",+        "supportedClass": [api:User, api:UserCollection],+        "api:UserCollection": {+          "subClassOf": "Collection",+          ****"memberAssertion": {+            "property": "rdf:type",+            "object": "http://api.example.com/api/documentation#User"
            "object": "api:User"
alien-mcl

comment created time in 4 days

Pull request review commentHydraCG/Specifications

Added support for strongly typed collections

 <h4>Member assertions</h4>     <p class="note">It's important to point out that the <code>subject</code>, <code>property</code>       and <code>object</code> predicates are defined within the Hydra namespace and are not       <a href="https://www.w3.org/TR/rdf-schema/"><code>rdf</code></a> terms.</p>++    <p>It is also possible to use <i>memberAssertion</i> predicate on the API documentation level,+      by attaching this predicate to subclasses of the <i>Collection</i>, like in the example below:</p>
      by attaching this predicate to subclasses of the <i>Collection</i>, like in the example below.
      Clients would understand that all members of collections which are instances of <i>api:UserCollection</i>`
      would in fact have <i>rdf:type api:User</i></p>
alien-mcl

comment created time in 4 days

Pull request review commentHydraCG/Specifications

Added support for strongly typed collections

 <h4>Member assertions</h4>      <pre class="example nohighlight"          data-transform="updateExample"-         title="Manages block describes relation with another resource">+         title="Member assertion block describes relation with another resource">
         title="Member assertion describes relation with another resource">
alien-mcl

comment created time in 4 days