Hydra Community Group - Activity in 2021
No matches.
GitHub
HydraCG/Specifications
-
1 pull request opened.
-
Specification release candidate HydraCG/Specifications#243, by @alien-mcl.
-
Participants
-
2 participants joined.
-
Rajesh kumar Gupta joined.
-
Aparna Garimella (IHS Markit) joined.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Retracting operations HydraCG/Specifications#241, by @alien-mcl.
-
-
1 issue received 15 new comments.
-
Retracting operations HydraCG/Specifications#241 (15 comments by @alien-mcl, @asbjornu, @serialseb, @tpluscode)
-
-
1 pull request opened.
-
Fix JSON-LD syntax in examples HydraCG/Specifications#242, by @jaw111.
-
-
2 pull requests merged.
-
Fix JSON-LD syntax in examples HydraCG/Specifications#242.
-
#149 hydra:search with HTTP POST HydraCG/Specifications#238.
-
-
2 pull requests received 3 new comments.
-
Added support for strongly typed collections HydraCG/Specifications#240 (2 comments by @alien-mcl, @tpluscode)
-
Participants
-
1 participant left.
-
Christopher Johnson (Akademie der Wissenschaften zu Göttingen) left.
-
-
1 organization left.
-
Akademie der Wissenschaften zu Göttingen left.
-
GitHub
HydraCG/Specifications
-
1 issue closed.
-
Supported property values source HydraCG/Specifications#227.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Added support for strongly typed collections HydraCG/Specifications#240, by @alien-mcl.
-
-
1 pull request merged.
-
#227 Supported property values source HydraCG/Specifications#229.
-
-
1 pull request received 5 new comments.
Participants
-
5 participants joined.
-
Matthew Radford (Vitalwerks Internet Solutions LLC) joined.
-
Kristoffer Garcia (IHS Markit) joined.
-
R. Michael Cary (IHS Markit) joined.
-
Rishab Raj joined.
-
DELETED DELETED joined.
-
-
3 participants left.
-
Nandana Mihindukulasooriya (Universidad Politécnica de Madrid) left.
-
Rishab Raj left.
-
Benjamin Goering left.
-
-
2 organizations joined.
-
Vitalwerks Internet Solutions LLC joined.
-
IHS Markit joined.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
editorial error: double negation in § 4.4 Api versions: prevents [...] not to get broken HydraCG/Specifications#239, by @jonassmedegaard.
-
-
3 issues closed.
-
Indicate a partial collection view is ordered HydraCG/Specifications#172.
-
Using collection to create resources vs adding members HydraCG/Specifications#237.
-
Improve documentation of the hydra:entrypoint property HydraCG/Specifications#52.
-
-
5 issues received 8 new comments.
-
Using collection to create resources vs adding members HydraCG/Specifications#237 (3 comments by @alien-mcl, @tpluscode)
-
Separating GET and PUT requests (a'la CQRS) HydraCG/Specifications#234 (2 comments by @alien-mcl, @tpluscode)
-
Indicate a partial collection view is ordered HydraCG/Specifications#172 (1 comment by @pietercolpaert)
-
Strongly typed collections in API documentation HydraCG/Specifications#233 (1 comment by @tpluscode)
-
Improve documentation of the hydra:entrypoint property HydraCG/Specifications#52 (1 comment by @alien-mcl)
-
-
1 pull request opened.
-
#149 hydra:search with HTTP POST HydraCG/Specifications#238, by @alien-mcl.
-
-
1 pull request merged.
-
Minor changes in IRI Template paragraphs HydraCG/Specifications#235.
-
-
2 pull requests received 11 new comments.
Participants
-
3 participants joined.
-
Paul Alagna joined.
-
Tory Clasen joined.
-
christian veigl joined.
-
GitHub
HydraCG/Specifications
-
7 issues opened.
-
Using collection to create resources vs adding members HydraCG/Specifications#237, by @tpluscode.
-
Use of Hydra collections for W3C WoT Discovery HydraCG/Specifications#236, by @wiresio.
-
Separating GET and PUT requests (a'la CQRS) HydraCG/Specifications#234, by @tpluscode.
-
Strongly typed collections in API documentation HydraCG/Specifications#233, by @alien-mcl.
-
Explicitly assert rdfs:Resource sub class? HydraCG/Specifications#232, by @tpluscode.
-
Replace property possibleStatus by statusCode in example 27. HydraCG/Specifications#231, by @cKlee.
-
Supported property values source HydraCG/Specifications#227, by @alien-mcl.
-
-
3 issues closed.
-
Use of Hydra collections for W3C WoT Discovery HydraCG/Specifications#236.
-
Replace property possibleStatus by statusCode in example 27. HydraCG/Specifications#231.
-
Way for API to announce any extensions they use in addition to Hydra Core HydraCG/Specifications#221.
-
-
6 issues received 25 new comments.
-
Separating GET and PUT requests (a'la CQRS) HydraCG/Specifications#234 (9 comments by @alien-mcl, @asbjornu, @tpluscode)
-
Use of Hydra collections for W3C WoT Discovery HydraCG/Specifications#236 (4 comments by @AndreaCimminoArriaga, @tpluscode, @wiresio)
-
Using collection to create resources vs adding members HydraCG/Specifications#237 (3 comments by @alien-mcl, @tpluscode)
-
Replace property possibleStatus by statusCode in example 27. HydraCG/Specifications#231 (3 comments by @alien-mcl, @cKlee)
-
Way for API to announce any extensions they use in addition to Hydra Core HydraCG/Specifications#221 (1 comment by @alien-mcl)
-
-
4 pull requests opened.
-
Minor changes in IRI Template paragraphs HydraCG/Specifications#235, by @tpluscode.
-
replaced possibleStatus by statusCode in example HydraCG/Specifications#230, by @cKlee.
-
#227 Supported property values source HydraCG/Specifications#229, by @alien-mcl.
-
fix a few typos HydraCG/Specifications#228, by @oftl.
-
-
1 pull request merged.
-
replaced possibleStatus by statusCode in example HydraCG/Specifications#230.
-
-
1 pull request closed.
-
fix a few typos HydraCG/Specifications#228.
-
-
1 pull request reopened.
-
replaced possibleStatus by statusCode in example HydraCG/Specifications#230, by @alien-mcl.
-
-
2 pull requests received 3 new comments.
-
replaced possibleStatus by statusCode in example HydraCG/Specifications#230 (2 comments by @alien-mcl, @cKlee)
-
Participants
-
2 participants joined.
-
Samesh Lakhotia joined.
-
Rishav Kumar joined.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Permalink for error.jsonld context HydraCG/Specifications#225, by @tpluscode.
-
-
4 issues closed.
-
Is the term ApiDocumentation misleading HydraCG/Specifications#61.
-
Remove hydra:Resource and hydra:Class HydraCG/Specifications#90.
-
Allow returns/expects to be expressed in terms of a media type; what about multiple types? HydraCG/Specifications#22.
-
Add rdfs:isDefinedBy to all concepts and rdfs:seeAlso to vocabulary itself HydraCG/Specifications#12.
-
-
7 issues received 8 new comments.
-
Permalink for error.jsonld context HydraCG/Specifications#225 (2 comments by @lanthaler, @tpluscode)
-
Describe how hydra:apiDocumentation can be used to associate information to concepts defined in other vocabularies HydraCG/Specifications#13 (1 comment by @alien-mcl)
-
Allow returns/expects to be expressed in terms of a media type; what about multiple types? HydraCG/Specifications#22 (1 comment by @alien-mcl)
-
Add rdfs:isDefinedBy to all concepts and rdfs:seeAlso to vocabulary itself HydraCG/Specifications#12 (1 comment by @alien-mcl)
-
Should sorting of paged collections be specified (in Hydra core)? HydraCG/Specifications#6 (1 comment by @alien-mcl)
-
-
1 pull request opened.
-
Added pointed predicates to the RDF serialization of the vocab HydraCG/Specifications#226, by @alien-mcl.
-
-
4 pull requests merged.
-
Allow returns/expects to be expressed in terms of a media type HydraCG/Specifications#186.
-
Way for API to announce any extensions they use in addition to Hydra Core HydraCG/Specifications#222.
-
Added pointed predicates to the RDF serialization of the vocab HydraCG/Specifications#226.
-
Addressed issues #13, #21 and #61 HydraCG/Specifications#223.
-
-
1 pull request reopened.
-
Addressed issues #13, #21 and #61 HydraCG/Specifications#223, by @alien-mcl.
-
-
2 pull requests received 2 new comments.
-
Way for API to announce any extensions they use in addition to Hydra Core HydraCG/Specifications#222 (1 comment by @alien-mcl)
-
Allow returns/expects to be expressed in terms of a media type HydraCG/Specifications#186 (1 comment by @alien-mcl)
-
Participants
-
1 participant left.
-
Miguel Ceriani left.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Use rfc7807bis JSON-LD Context HydraCG/Specifications#224, by @asbjornu.
-
-
3 issues received 8 new comments.
-
Use rfc7807bis JSON-LD Context HydraCG/Specifications#224 (6 comments by @alien-mcl, @asbjornu, @tpluscode)
-
Improve documentation of the hydra:entrypoint property HydraCG/Specifications#52 (1 comment by @tpluscode)
-
-
2 pull requests closed.
-
API documentation limitations HydraCG/Specifications#183.
-
Detailed specification for expects/returns and strongly typed collections HydraCG/Specifications#187.
-
-
3 pull requests received 19 new comments.
-
Way for API to announce any extensions they use in addition to Hydra Core HydraCG/Specifications#222 (10 comments by @dunglas, @tpluscode)
-
Allow returns/expects to be expressed in terms of a media type HydraCG/Specifications#186 (1 comment by @tpluscode)
-
GitHub
HydraCG/Specifications
-
3 issues closed.
-
State more explicitely that hydra:return etc. are just hints HydraCG/Specifications#21.
-
Introduce something like hydra:memberTemplate HydraCG/Specifications#16.
-
Make hydra:error compatible with RFC 7807 HydraCG/Specifications#178.
-
-
5 issues received 9 new comments.
-
Describe how hydra:apiDocumentation can be used to associate information to concepts defined in other vocabularies HydraCG/Specifications#13 (4 comments by @alien-mcl, @asbjornu, @tpluscode)
-
State more explicitely that hydra:return etc. are just hints HydraCG/Specifications#21 (2 comments by @alien-mcl)
-
Improve documentation of the hydra:entrypoint property HydraCG/Specifications#52 (1 comment by @alien-mcl)
-
-
1 pull request opened.
-
Addressed issues #13, #21 and #61 HydraCG/Specifications#223, by @alien-mcl.
-
-
1 pull request merged.
-
#178 Make hydra:error compatible with RFC 7807 HydraCG/Specifications#218.
-
-
3 pull requests received 19 new comments.
-
#178 Make hydra:error compatible with RFC 7807 HydraCG/Specifications#218 (14 comments by @alien-mcl, @asbjornu, @lanthaler, @tpluscode)
-
Way for API to announce any extensions they use in addition to Hydra Core HydraCG/Specifications#222 (4 comments by @alien-mcl, @tpluscode)
-
Allow returns/expects to be expressed in terms of a media type HydraCG/Specifications#186 (1 comment by @alien-mcl)
-