Hydra Community Group - Activity in 2019
No matches.
Participants
-
2 participants joined.
-
Stefan Bourlon joined.
-
Ajay Kumar Ajay joined.
-
GitHub
HydraCG/Specifications
-
2 issues opened.
-
Clarify behaviour when ApiDocumentation resource contains more than just itself HydraCG/Specifications#202, by @tpluscode.
-
JSON-LD context missing @type HydraCG/Specifications#201, by @thewilkybarkid.
-
-
3 issues received 18 new comments.
-
Indicate a partial collection view is ordered HydraCG/Specifications#172 (14 comments by @alien-mcl, @asbjornu, @pietercolpaert, @tpluscode)
-
Clarify behaviour when ApiDocumentation resource contains more than just itself HydraCG/Specifications#202 (3 comments by @alien-mcl, @tpluscode)
-
GitHub
HydraCG/Specifications
-
1 pull request merged.
-
Enable hydra to expect and return non RDF resources HydraCG/Specifications#200.
-
Participants
-
1 participant left.
-
Tom Panier left.
-
GitHub
HydraCG/Specifications
-
1 issue received 1 new comment.
-
Stop advocating the use of the unmaintained and not dereferencable VOID vocabulary? HydraCG/Specifications#170 (1 comment by @pietercolpaert)
-
-
1 pull request opened.
-
Enable hydra to expect and return non RDF resources HydraCG/Specifications#200, by @alien-mcl.
-
-
2 pull requests received 10 new comments.
-
Enable hydra to expect and return non RDF resources HydraCG/Specifications#200 (9 comments by @alien-mcl, @asbjornu, @tpluscode)
-
TemplatedLink cannot formally have supportedOperation HydraCG/Specifications#198 (1 comment by @alien-mcl)
-
Participants
-
1 participant left.
-
Dominik Tomaszuk left.
-
GitHub
HydraCG/Specifications
-
1 issue received 1 new comment.
-
Requiring proper ranges on supported properties HydraCG/Specifications#192 (1 comment by @tpluscode)
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Another take on non-RDF payloads (aka file upload) HydraCG/Specifications#199, by @tpluscode.
-
-
2 issues received 10 new comments.
-
Another take on non-RDF payloads (aka file upload) HydraCG/Specifications#199 (7 comments by @alien-mcl, @angelo-v, @asbjornu, @tpluscode)
-
TemplatedLink cannot formally have supportedOperation HydraCG/Specifications#197 (3 comments by @alien-mcl, @angelo-v, @tpluscode)
-
-
1 pull request received 1 new comment.
Participants
-
2 organizations left.
-
trick17.media left.
-
Open Knowledge Foundation left.
-
GitHub
HydraCG/Specifications
-
1 issue reopened.
-
Rename manages to memberAssertion HydraCG/Specifications#150, by @alien-mcl.
-
-
2 issues received 3 new comments.
-
TemplatedLink cannot formally have supportedOperation HydraCG/Specifications#197 (1 comment by @angelo-v)
-
1 pull request opened.
-
TemplatedLink cannot formally have supportedOperation HydraCG/Specifications#198, by @alien-mcl.
-
Participants
-
1 participant left.
-
Tomasz Pluskiewicz (Zazuko) left.
-
-
2 organizations joined.
-
Iron Horse Software, LLC joined.
-
Zazuko joined.
-
GitHub
HydraCG/Specifications
-
6 issues opened.
-
TemplatedLink cannot formally have supportedOperation HydraCG/Specifications#197, by @alien-mcl.
-
Supported Operations on properties HydraCG/Specifications#196, by @angelo-v.
-
Manages block usage for subject vs object HydraCG/Specifications#194, by @tpluscode.
-
hydra:Link should be an ObjectProperty HydraCG/Specifications#193, by @tpluscode.
-
Requiring proper ranges on supported properties HydraCG/Specifications#192, by @tpluscode.
-
Clarify how to describe HTTP status HydraCG/Specifications#191, by @angelo-v.
-
-
6 issues closed.
-
Simplify discovery of collections that contain resources of a certain type HydraCG/Specifications#126.
-
Discuss how usage of Collections "breaks" relationships HydraCG/Specifications#41.
-
Find a better name for the "manages block" HydraCG/Specifications#60.
-
Manages block usage for subject vs object HydraCG/Specifications#194.
-
hydra:Link should be an ObjectProperty HydraCG/Specifications#193.
-
Add support for describing headers accepted in supported operations HydraCG/Specifications#99.
-
-
8 issues received 41 new comments.
-
TemplatedLink cannot formally have supportedOperation HydraCG/Specifications#197 (9 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Requiring proper ranges on supported properties HydraCG/Specifications#192 (8 comments by @alien-mcl, @angelo-v, @asbjornu, @tpluscode)
-
Clarify how to describe HTTP status HydraCG/Specifications#191 (7 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Manages block usage for subject vs object HydraCG/Specifications#194 (6 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Supported Operations on properties HydraCG/Specifications#196 (5 comments by @alien-mcl, @angelo-v, @tpluscode)
-
hydra:Link should be an ObjectProperty HydraCG/Specifications#193 (3 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Indicate a partial collection view is ordered HydraCG/Specifications#172 (2 comments by @alien-mcl, @pietercolpaert)
-
Add support for describing headers accepted in supported operations HydraCG/Specifications#99 (1 comment by @alien-mcl)
-
-
1 pull request opened.
-
add section about manages block HydraCG/Specifications#195, by @tpluscode.
-
-
2 pull requests merged.
-
add section about manages block HydraCG/Specifications#195.
-
Add support for describing headers HydraCG/Specifications#185.
-
-
2 pull requests received 10 new comments.
-
add section about manages block HydraCG/Specifications#195 (9 comments by @alien-mcl, @angelo-v, @asbjornu, @tpluscode, @vddesai1871)
-
GitHub
HydraCG/Specifications
-
2 issues opened.
-
Question about resource versioning HydraCG/Specifications#190, by @ghost.
-
Question about HATEOAS shortcuts HydraCG/Specifications#189, by @ghost.
-
-
1 issue closed.
-
Question about HATEOAS shortcuts HydraCG/Specifications#189.
-
-
1 issue reopened.
-
Question about HATEOAS shortcuts HydraCG/Specifications#189.
-
-
3 issues received 22 new comments.
-
Question about HATEOAS shortcuts HydraCG/Specifications#189 (15 comments by @alien-mcl, @dret, @ghost, @tpluscode)
-
Question about resource versioning HydraCG/Specifications#190 (5 comments by @alien-mcl, @angelo-v, @ghost)
-
Indicate a partial collection view is ordered HydraCG/Specifications#172 (2 comments by @Mec-iS, @pietercolpaert)
-
-
1 pull request closed.
-
Update UC of partial collection HydraCG/Specifications#165.
-
-
1 pull request received 1 new comment.
Participants
-
1 participant joined.
-
steve jose joined.
-
-
2 participants left.
-
Adrian Gschwend left.
-
Dan Scott left.
-
-
1 organization joined.
-
Inria joined.
-
GitHub
HydraCG/Specifications
-
1 pull request opened.
-
Collaboration templates HydraCG/Specifications#188, by @tpluscode.
-
-
2 pull requests merged.
-
Collaboration templates HydraCG/Specifications#188.
-
Define client-initiated pagination HydraCG/Specifications#184.
-
-
3 pull requests received 26 new comments.
-
Collaboration templates HydraCG/Specifications#188 (16 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Detailed specification for expects/returns and strongly typed collections HydraCG/Specifications#187 (6 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Define client-initiated pagination HydraCG/Specifications#184 (4 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Participants
-
2 participants joined.
-
Costi Dumitrescu joined.
-
Jim Smart joined.
-
-
2 participants left.
-
Costi Dumitrescu left.
-
David Bell left.
-
-
1 organization joined.
-
Fortuity Infotech Pvt Ltd joined.
-
GitHub
HydraCG/Specifications
-
8 issues closed.
-
Start a Hydra gitbook HydraCG/Specifications#147.
-
Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? HydraCG/Specifications#32.
-
Discuss versioning HydraCG/Specifications#72.
-
Add domainIncludes/rangeIncludes statements HydraCG/Specifications#48.
-
Document how "errors" can be given an identifier and be reused in responses HydraCG/Specifications#39.
-
Describe entry point -> ApiDocumentation flow HydraCG/Specifications#69.
-
Define a property to be used for untyped links? HydraCG/Specifications#15.
-
Allow SupportedProperty to overwrite a vocabulary's rdfs:label and rdfs:comment HydraCG/Specifications#1.
-
-
10 issues received 30 new comments.
-
Define client-initiated pagination HydraCG/Specifications#102 (11 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Semantics to define constraints and/or globally unique ids HydraCG/Specifications#168 (4 comments by @alien-mcl, @knakul853, @Mec-iS)
-
Simplify discovery of collections that contain resources of a certain type HydraCG/Specifications#126 (2 comments by @angelo-v, @tpluscode)
-
Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? HydraCG/Specifications#32 (1 comment by @alien-mcl)
-
-
5 pull requests opened.
-
Detailed specification for expects/returns and strongly typed collections HydraCG/Specifications#187, by @alien-mcl.
-
Allow returns/expects to be expressed in terms of a media type HydraCG/Specifications#186, by @alien-mcl.
-
Add support for describing headers HydraCG/Specifications#185, by @alien-mcl.
-
Define client-initiated pagination HydraCG/Specifications#184, by @alien-mcl.
-
API documentation limitations HydraCG/Specifications#183, by @alien-mcl.
-
-
7 pull requests merged.
-
expand on @id with `Status`/`Error` response HydraCG/Specifications#180.
-
Discuss versioning HydraCG/Specifications#179.
-
Added an example of Api response -> ApiDocumentation flow HydraCG/Specifications#177.
-
Define a property to be used for untyped links? HydraCG/Specifications#174.
-
Add domainIncludes/rangeIncludes statements HydraCG/Specifications#176.
-
Should returns and statusCodes be removed to avoid tight coupling? HydraCG/Specifications#175.
-
Allow SupportedProperty to overwrite a vocabulary's rdfs:label and rdfs:comment HydraCG/Specifications#173.
-
-
1 pull request closed.
-
Vocabulary extensions HydraCG/Specifications#182.
-
-
5 pull requests received 89 new comments.
-
Define client-initiated pagination HydraCG/Specifications#184 (20 comments by @alien-mcl, @angelo-v, @tpluscode, @vddesai1871)
-
Allow returns/expects to be expressed in terms of a media type HydraCG/Specifications#186 (16 comments by @alien-mcl, @angelo-v, @tpluscode)
-
Add support for describing headers HydraCG/Specifications#185 (14 comments by @alien-mcl, @angelo-v, @tpluscode)
-
API documentation limitations HydraCG/Specifications#183 (13 comments by @alien-mcl, @angelo-v, @tpluscode)
Participants
-
3 participants left.
-
Sebastian Bader left.
-
Andy Hagerty left.
-
Markus Mächler left.
-
-
2 organizations left.
-
NRU ITMO left.
-
Adobe left.
-
GitHub
HydraCG/Specifications
-
2 issues opened.
-
Hydra logo licensing HydraCG/Specifications#181, by @tpluscode.
-
Make hydra:error compatible with RFC 7807 HydraCG/Specifications#178, by @asbjornu.
-
-
15 issues closed.
-
Should properties and types that only differ in their capitalization be avoided? HydraCG/Specifications#28.
-
Use W3C HTTP RDF vocabulary HydraCG/Specifications#109.
-
Add picture to LDF/TPF specs HydraCG/Specifications#98.
-
Clarify the reuse of the request URL inside of the fragment HydraCG/Specifications#93.
-
How to suggest dereferenceability? HydraCG/Specifications#91.
-
Triple pattern fragments: explain how to handle blank nodes HydraCG/Specifications#77.
-
Add support for examples (Operations, IriTemplates, etc.) HydraCG/Specifications#74.
-
Description of workflows HydraCG/Specifications#70.
-
Create a test suite for servers of triple pattern fragments HydraCG/Specifications#65.
-
Improve definition of hydra:search HydraCG/Specifications#51.
-
Restructure spec to talk about application state, resource state, and API as whole HydraCG/Specifications#44.
-
Reversed SupportedProperty HydraCG/Specifications#40.
-
Define "priority of constituencies" HydraCG/Specifications#38.
-
Are Operations violating REST's uniform interface constraint? HydraCG/Specifications#31.
-
Ideas for additional features/vocabularies HydraCG/Specifications#20.
-
-
2 issues reopened.
-
Hydra logo licensing HydraCG/Specifications#181, by @alien-mcl.
-
Date ranges / intervals for LDF HydraCG/Specifications#56, by @alien-mcl.
-
-
24 issues received 68 new comments.
-
Hydra logo licensing HydraCG/Specifications#181 (18 comments by @alien-mcl, @asbjornu, @lanthaler, @tpluscode)
-
Make hydra:error compatible with RFC 7807 HydraCG/Specifications#178 (13 comments by @akuckartz, @alien-mcl, @asbjornu, @dret, @tpluscode)
-
Date ranges / intervals for LDF HydraCG/Specifications#56 (5 comments by @akuckartz, @alien-mcl, @asbjornu, @RubenVerborgh)
-
Document how "errors" can be given an identifier and be reused in responses HydraCG/Specifications#39 (4 comments by @alien-mcl, @asbjornu, @tpluscode)
-
Spec document has wrong header level for classes and properties HydraCG/Specifications#78 (4 comments by @akuckartz, @alien-mcl, @tpluscode)
-
Restructure spec to talk about application state, resource state, and API as whole HydraCG/Specifications#44 (3 comments by @akuckartz, @alien-mcl)
-
Add support for allowed literals and allowed individuals HydraCG/Specifications#82 (2 comments by @alien-mcl)
-
Introduce hydra:filter (subPropertyOf hydra:search) HydraCG/Specifications#45 (1 comment by @alien-mcl)
-
Should properties and types that only differ in their capitalization be avoided? HydraCG/Specifications#28 (1 comment by @alien-mcl)
-
Clarify the reuse of the request URL inside of the fragment HydraCG/Specifications#93 (1 comment by @alien-mcl)
-
Triple pattern fragments: explain how to handle blank nodes HydraCG/Specifications#77 (1 comment by @alien-mcl)
-
Add support for examples (Operations, IriTemplates, etc.) HydraCG/Specifications#74 (1 comment by @alien-mcl)
-
Create a test suite for servers of triple pattern fragments HydraCG/Specifications#65 (1 comment by @alien-mcl)
-
Are Operations violating REST's uniform interface constraint? HydraCG/Specifications#31 (1 comment by @alien-mcl)
-
-
8 pull requests opened.
-
Vocabulary extensions HydraCG/Specifications#182, by @alien-mcl.
-
expand on @id with `Status`/`Error` response HydraCG/Specifications#180, by @tpluscode.
-
Discuss versioning HydraCG/Specifications#179, by @alien-mcl.
-
Added an example of Api response -> ApiDocumentation flow HydraCG/Specifications#177, by @alien-mcl.
-
Add domainIncludes/rangeIncludes statements HydraCG/Specifications#176, by @alien-mcl.
-
Should returns and statusCodes be removed to avoid tight coupling? HydraCG/Specifications#175, by @alien-mcl.
-
Define a property to be used for untyped links? HydraCG/Specifications#174, by @alien-mcl.
-
Allow SupportedProperty to overwrite a vocabulary's rdfs:label and rdfs:comment HydraCG/Specifications#173, by @alien-mcl.
-
-
9 pull requests received 84 new comments.
-
Define a property to be used for untyped links? HydraCG/Specifications#174 (17 comments by @alien-mcl, @asbjornu, @tpluscode)
-
Add domainIncludes/rangeIncludes statements HydraCG/Specifications#176 (15 comments by @alien-mcl, @tpluscode, @vddesai1871)
-
Allow SupportedProperty to overwrite a vocabulary's rdfs:label and rdfs:comment HydraCG/Specifications#173 (14 comments by @alien-mcl, @tpluscode)
-
expand on @id with `Status`/`Error` response HydraCG/Specifications#180 (13 comments by @alien-mcl, @tpluscode)
-
Added an example of Api response -> ApiDocumentation flow HydraCG/Specifications#177 (11 comments by @alien-mcl, @tpluscode)
-
Should returns and statusCodes be removed to avoid tight coupling? HydraCG/Specifications#175 (6 comments by @alien-mcl, @tpluscode)
-