Hydra Community Group - Activity in 2017
No matches.
Participants
-
1 participant left.
-
Eduardo Vital Alencar Cunha left.
-
-
1 organization joined.
-
Culture Creates Inc joined.
-
-
1 organization left.
-
Stockholm University left.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
i18n support HydraCG/Specifications#153, by @binhle410.
-
-
1 issue received 2 new comments.
Participants
-
1 participant joined.
-
Jose Montoya joined.
-
-
1 participant left.
-
Alexander Surinov left.
-
GitHub
HydraCG/Specifications
-
7 issues opened.
-
Usage of IriTemplate HydraCG/Specifications#152, by @tpluscode.
-
Rename manages to memberAssertion HydraCG/Specifications#150, by @asbjornu.
-
hydra:search with HTTP POST HydraCG/Specifications#149, by @elf-pavlik.
-
Extend PartialCollectionView with template variables' values HydraCG/Specifications#148, by @tpluscode.
-
Start a Hydra gitbook HydraCG/Specifications#147, by @tpluscode.
-
External operations HydraCG/Specifications#146, by @asbjornu.
-
IriTemplate should have a way to describe variable as UUID etc. HydraCG/Specifications#145, by @elf-pavlik.
-
-
2 issues closed.
-
CreateAction with HTTP PUT HydraCG/Specifications#141.
-
Specifying operations on TemplatedLink objects HydraCG/Specifications#118.
-
-
14 issues received 80 new comments.
-
IriTemplate should have a way to describe variable as UUID etc. HydraCG/Specifications#145 (14 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
External operations HydraCG/Specifications#146 (12 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode, @vasilakisfil)
-
Introduce something like hydra:memberTemplate HydraCG/Specifications#16 (11 comments by @alien-mcl, @elf-pavlik, @lanthaler, @tpluscode)
-
Start a Hydra gitbook HydraCG/Specifications#147 (9 comments by @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
POST/PUT requests in use cases shouldn't use relative URLs to reference the context HydraCG/Specifications#144 (8 comments by @asbjornu, @elf-pavlik, @lanthaler)
-
hydra:search with HTTP POST HydraCG/Specifications#149 (8 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
Extend PartialCollectionView with template variables' values HydraCG/Specifications#148 (6 comments by @alien-mcl, @elf-pavlik, @lanthaler, @tpluscode)
-
Rename manages to memberAssertion HydraCG/Specifications#150 (2 comments by @elf-pavlik, @tpluscode)
-
collections with manages block & Triple Pattern Fragments HydraCG/Specifications#142 (1 comment by @elf-pavlik)
-
Describe/specify how the target IRI for an hydra:operation is resolved HydraCG/Specifications#100 (1 comment by @tpluscode)
-
-
1 pull request opened.
-
Remove hydra: prefix from use cases HydraCG/Specifications#151, by @tpluscode.
-
-
2 pull requests merged.
-
Remove hydra: prefix from use cases HydraCG/Specifications#151.
-
Add Use Case: Creating events indirectly (ie. with PUT) HydraCG/Specifications#143.
-
-
1 pull request closed.
-
Recommend to use cache revalidation HydraCG/Specifications#94.
-
-
3 pull requests received 25 new comments.
-
Add Use Case: Creating events indirectly (ie. with PUT) HydraCG/Specifications#143 (14 comments by @alien-mcl, @elf-pavlik, @lanthaler, @tpluscode)
-
Remove hydra: prefix from use cases HydraCG/Specifications#151 (9 comments by @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
Recommend to use cache revalidation HydraCG/Specifications#94 (2 comments by @elf-pavlik, @lanthaler)
-
Participants
-
1 participant joined.
-
Roman Evstifeev joined.
-
GitHub
HydraCG/Specifications
-
3 issues opened.
-
POST/PUT requests in use cases shouldn't use relative URLs to reference the context HydraCG/Specifications#144, by @lanthaler.
-
collections with manages block & Triple Pattern Fragments HydraCG/Specifications#142, by @elf-pavlik.
-
CreateAction with HTTP PUT HydraCG/Specifications#141, by @elf-pavlik.
-
-
1 issue closed.
-
Should spec mandate on server removing membership triple for deleted resources HydraCG/Specifications#137.
-
-
6 issues received 84 new comments.
-
Adding already existing resources as collection members HydraCG/Specifications#134 (37 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
CreateAction with HTTP PUT HydraCG/Specifications#141 (29 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
Should we introduce a property to associate operations and their target directly to an entity? HydraCG/Specifications#3 (11 comments by @alien-mcl, @asbjornu, @elf-pavlik, @tpluscode)
-
Should spec mandate on server removing membership triple for deleted resources HydraCG/Specifications#137 (5 comments by @alien-mcl, @elf-pavlik, @RubenVerborgh)
-
POST/PUT requests in use cases shouldn't use relative URLs to reference the context HydraCG/Specifications#144 (1 comment by @tpluscode)
-
-
1 pull request opened.
-
Add Use Case: Creating events indirectly (ie. with PUT) HydraCG/Specifications#143, by @tpluscode.
-
-
1 pull request merged.
-
Explicitly mention namespace in Core Vocabulary document HydraCG/Specifications#97.
-
-
3 pull requests received 30 new comments.
-
Add Use Case: Creating events indirectly (ie. with PUT) HydraCG/Specifications#143 (24 comments by @alien-mcl, @elf-pavlik, @lanthaler, @tpluscode)
-
Recommend to use cache revalidation HydraCG/Specifications#94 (4 comments by @elf-pavlik, @lanthaler)
-
Explicitly mention namespace in Core Vocabulary document HydraCG/Specifications#97 (2 comments by @elf-pavlik, @lanthaler)
-
Participants
-
1 organization joined.
-
Viacom inc. joined.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Are we considering semantics for partial querying of objects HydraCG/Specifications#139, by @Mec-iS.
-
-
3 issues received 16 new comments.
-
Adding already existing resources as collection members HydraCG/Specifications#134 (7 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
Are we considering semantics for partial querying of objects HydraCG/Specifications#139 (7 comments by @asbjornu, @elf-pavlik, @tpluscode)
-
Should spec mandate on server removing membership triple for deleted resources HydraCG/Specifications#137 (2 comments by @elf-pavlik, @lanthaler)
-
-
1 pull request opened.
-
initial draft of attendance use case (adding existing resources to collections) HydraCG/Specifications#140, by @elf-pavlik.
-
-
2 pull requests merged.
-
initial draft of attendance use case (adding existing resources to collections) HydraCG/Specifications#140.
-
add two more collections: people & venues HydraCG/Specifications#136.
-
-
1 pull request closed.
-
Proof of concept for authoring spec in markdown HydraCG/Specifications#110.
-
-
2 pull requests received 7 new comments.
-
add two more collections: people & venues HydraCG/Specifications#136 (4 comments by @elf-pavlik, @lanthaler)
-
initial draft of attendance use case (adding existing resources to collections) HydraCG/Specifications#140 (3 comments by @elf-pavlik, @lanthaler, @tpluscode)
-
Participants
-
3 participants joined.
-
Eduardo Vital Alencar Cunha joined.
-
Kabul Kurniawan joined.
-
Ardalan Saeidi joined.
-
-
3 organizations joined.
-
Adaptive, Inc joined.
-
Virtual Organization Management Institute joined.
-
virtual earth Gesellschaft für Wissens re/prä sentation mbH joined.
-
GitHub
HydraCG/Specifications
-
5 issues opened.
-
Callback based handling of responses HydraCG/Specifications#138, by @asbjornu.
-
Should spec mandate on server removing membership triple for deleted resources HydraCG/Specifications#137, by @elf-pavlik.
-
Why reviewable.io for code reviews? HydraCG/Specifications#135, by @asbjornu.
-
Adding already existing resources as collection members HydraCG/Specifications#134, by @elf-pavlik.
-
Class and Property should not have same name with just different capitalization HydraCG/Specifications#133, by @elf-pavlik.
-
-
3 issues closed.
-
Callback based handling of responses HydraCG/Specifications#138.
-
Why reviewable.io for code reviews? HydraCG/Specifications#135.
-
Class and Property should not have same name with just different capitalization HydraCG/Specifications#133.
-
-
6 issues received 28 new comments.
-
Adding already existing resources as collection members HydraCG/Specifications#134 (10 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
Why reviewable.io for code reviews? HydraCG/Specifications#135 (6 comments by @akuckartz, @asbjornu, @lanthaler, @tpluscode)
-
Callback based handling of responses HydraCG/Specifications#138 (5 comments by @asbjornu, @elf-pavlik, @RubenVerborgh)
-
Class and Property should not have same name with just different capitalization HydraCG/Specifications#133 (3 comments by @akuckartz, @lanthaler, @tpluscode)
-
Should spec mandate on server removing membership triple for deleted resources HydraCG/Specifications#137 (2 comments by @elf-pavlik, @tpluscode)
-
Simplify discovery of collections that contain resources of a certain type HydraCG/Specifications#126 (2 comments by @elf-pavlik)
-
-
2 pull requests opened.
-
add two more collections: people & venues HydraCG/Specifications#136, by @elf-pavlik.
-
Use manages block to advertise type of collection members HydraCG/Specifications#132, by @elf-pavlik.
-
-
1 pull request merged.
-
Use manages block to advertise type of collection members HydraCG/Specifications#132.
-
-
2 pull requests received 25 new comments.
-
Use manages block to advertise type of collection members HydraCG/Specifications#132 (24 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @RubenVerborgh, @tpluscode)
-
Participants
-
2 participants joined.
-
Damian Martinez Gelabert joined.
-
Sebastian Bader joined.
-
-
1 participant left.
-
Dhruvan Ganesh left.
-
-
2 organizations joined.
-
Southern Cross Medical Care Society joined.
-
Austrian Academy of Sciences joined.
-
GitHub
HydraCG/Specifications
-
1 issue closed.
-
Hydra api demo, question about Collections HydraCG/Specifications#119.
-
-
2 issues received 14 new comments.
-
Simplify discovery of collections that contain resources of a certain type HydraCG/Specifications#126 (13 comments by @alien-mcl, @asbjornu, @dunglas, @elf-pavlik, @lanthaler, @RubenVerborgh)
-
-
3 pull requests opened.
-
fix iri template expansion in filter use case HydraCG/Specifications#131, by @elf-pavlik.
-
Fix GitHub pages update script HydraCG/Specifications#130, by @lanthaler.
-
Reference the automatically created diagram HydraCG/Specifications#129, by @lanthaler.
-
-
5 pull requests merged.
-
fix iri template expansion in filter use case HydraCG/Specifications#131.
-
Fix GitHub pages update script HydraCG/Specifications#130.
-
Reference the automatically created diagram HydraCG/Specifications#129.
-
Add architectural diagram to main repository HydraCG/Specifications#128.
-
Update specification document HydraCG/Specifications#127.
-
-
5 pull requests received 13 new comments.
-
Fix GitHub pages update script HydraCG/Specifications#130 (5 comments by @lanthaler, @RubenVerborgh)
-
Reference the automatically created diagram HydraCG/Specifications#129 (4 comments by @lanthaler, @RubenVerborgh)
-
Participants
-
1 participant joined.
-
Akshay xadahiya joined.
-
-
2 organizations left.
-
Ministério do Planejamento left.
-
Cornell University Library left.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Simplify discovery of collections that contain resources of a certain type HydraCG/Specifications#126, by @elf-pavlik.
-
-
1 issue received 7 new comments.
-
Simplify discovery of collections that contain resources of a certain type HydraCG/Specifications#126 (7 comments by @alien-mcl, @asbjornu, @dunglas, @elf-pavlik, @lanthaler, @tpluscode)
-
-
3 pull requests opened.
-
Add architectural diagram to main repository HydraCG/Specifications#128, by @RubenVerborgh.
-
Update specification document HydraCG/Specifications#127, by @kartikadur.
-
use schema.org actions HydraCG/Specifications#125, by @elf-pavlik.
-
-
1 pull request merged.
-
use schema.org actions HydraCG/Specifications#125.
-
-
2 pull requests received 60 new comments.
-
use schema.org actions HydraCG/Specifications#125 (48 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
Add architectural diagram to main repository HydraCG/Specifications#128 (12 comments by @asbjornu, @lanthaler, @RubenVerborgh)
-
Participants
-
1 participant joined.
-
kartik adur joined.
-
-
1 participant left.
-
Cedric Dumont left.
-
GitHub
HydraCG/Specifications
-
1 issue received 5 new comments.
-
Interoperability with Linked Data Platform (especially regarding collections and paging) HydraCG/Specifications#36 (5 comments by @asbjornu, @elf-pavlik, @RubenVerborgh)
-
-
5 pull requests opened.
-
Add use case: Filter resources HydraCG/Specifications#124, by @alien-mcl.
-
Add use case: Search resources HydraCG/Specifications#123, by @alien-mcl.
-
Add use case: Update resource HydraCG/Specifications#122, by @alien-mcl.
-
Same IRI must not denote both - the operation and the api resource which supports that operation HydraCG/Specifications#121, by @elf-pavlik.
-
"@type": "@id" in JSON-LD context of use cases HydraCG/Specifications#120, by @elf-pavlik.
-
-
10 pull requests merged.
-
Same IRI must not denote both - the operation and the api resource which supports that operation HydraCG/Specifications#121.
-
Add use case: Filter resources HydraCG/Specifications#124.
-
Add use case: Search resources HydraCG/Specifications#123.
-
Add use case: Update resource HydraCG/Specifications#122.
-
Add use case: Create resource HydraCG/Specifications#117.
-
Add use case: Retrieve resource HydraCG/Specifications#116.
-
"@type": "@id" in JSON-LD context of use cases HydraCG/Specifications#120.
-
Let's consider a use case when a Hydra client obtains events. HydraCG/Specifications#115.
-
Let's consider an API documentation fetch use case for the Hydra client. HydraCG/Specifications#114.
-
Let's consider first an entry-point use case of the Hydra client. HydraCG/Specifications#113.
-
-
8 pull requests received 84 new comments.
-
Add use case: Create resource HydraCG/Specifications#117 (21 comments by @alien-mcl, @elf-pavlik, @lanthaler, @tpluscode)
-
Same IRI must not denote both - the operation and the api resource which supports that operation HydraCG/Specifications#121 (19 comments by @alien-mcl, @elf-pavlik, @lanthaler, @tpluscode)
-
"@type": "@id" in JSON-LD context of use cases HydraCG/Specifications#120 (10 comments by @alien-mcl, @elf-pavlik, @lanthaler, @tpluscode)
-
Add use case: Retrieve resource HydraCG/Specifications#116 (7 comments by @alien-mcl, @elf-pavlik, @lanthaler)
-
Add use case: Filter resources HydraCG/Specifications#124 (6 comments by @alien-mcl, @asbjornu, @lanthaler, @RubenVerborgh, @tpluscode)
-
Add use case: Update resource HydraCG/Specifications#122 (5 comments by @alien-mcl, @elf-pavlik, @lanthaler)
-
Let's consider first an entry-point use case of the Hydra client. HydraCG/Specifications#113 (4 comments by @elf-pavlik, @lanthaler)
-
Participants
-
1 participant joined.
-
Douglas Fils joined.
-
GitHub
HydraCG/Specifications
-
2 issues opened.
-
Hydra api demo, question about Collections HydraCG/Specifications#119, by @cr3a7ure.
-
Specifying operations on TemplatedLink objects HydraCG/Specifications#118, by @tpluscode.
-
-
2 issues received 6 new comments.
-
Specifying operations on TemplatedLink objects HydraCG/Specifications#118 (4 comments by @cr3a7ure, @tpluscode)
-
Describe/specify how the target IRI for an hydra:operation is resolved HydraCG/Specifications#100 (2 comments by @cr3a7ure, @RubenVerborgh)
-
-
5 pull requests opened.
-
Add use case: Create resource HydraCG/Specifications#117, by @alien-mcl.
-
Add use case: Retrieve resource HydraCG/Specifications#116, by @alien-mcl.
-
Let's consider a use case when a Hydra client obtains events. HydraCG/Specifications#115, by @alien-mcl.
-
Let's consider an API documentation fetch use case for the Hydra client. HydraCG/Specifications#114, by @alien-mcl.
-
Let's consider first an entry-point use case of the Hydra client. HydraCG/Specifications#113, by @alien-mcl.
-
-
1 pull request merged.
-
[client-interface] Suggestion for browser-like client API HydraCG/Specifications#111.
-
-
4 pull requests received 103 new comments.
-
Let's consider first an entry-point use case of the Hydra client. HydraCG/Specifications#113 (44 comments by @alien-mcl, @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
Let's consider an API documentation fetch use case for the Hydra client. HydraCG/Specifications#114 (35 comments by @alien-mcl, @asbjornu, @lanthaler, @tpluscode)
-
Let's consider a use case when a Hydra client obtains events. HydraCG/Specifications#115 (22 comments by @alien-mcl, @asbjornu, @lanthaler, @RubenVerborgh, @tpluscode)
-
[client-interface] Suggestion for browser-like client API HydraCG/Specifications#111 (2 comments by @dschulten, @lanthaler)
-
Participants
-
3 participants joined.
-
Bojan Suzic joined.
-
Chris Andrew joined.
-
Alexandre Nicastro joined.
-
-
1 participant left.
-
Alexandre Nicastro left.
-
-
2 organizations joined.
-
Intel Corporation joined.
-
FPT Software joined.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Linking to multiple PartialCollectionView from Collection HydraCG/Specifications#112, by @literarymachine.
-
-
1 issue closed.
-
Linking to multiple PartialCollectionView from Collection HydraCG/Specifications#112.
-
-
1 issue received 6 new comments.
-
Linking to multiple PartialCollectionView from Collection HydraCG/Specifications#112 (6 comments by @lanthaler, @literarymachine, @RubenVerborgh, @tpluscode)
-
-
1 pull request opened.
-
[client-interface] Suggestion for browser-like client API HydraCG/Specifications#111, by @dschulten.
-
-
1 pull request received 38 new comments.
-
[client-interface] Suggestion for browser-like client API HydraCG/Specifications#111 (38 comments by @asbjornu, @dschulten, @dunglas, @lanthaler, @RubenVerborgh, @tpluscode)
-
Participants
-
4 participants joined.
-
Manos Batsis joined.
-
Cong Peng joined.
-
Upendra Kumar joined.
-
Alexander Surinov joined.
-
-
1 organization left.
-
PT Bina Media Terpadu left.
-
Participants
-
1 participant joined.
-
Kalin Maldzhanski joined.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Use W3C HTTP RDF vocabulary HydraCG/Specifications#109, by @asbjornu.
-
-
2 issues closed.
-
Remove predefined operations from the core vocabulary. HydraCG/Specifications#11.
-
Update context at w3.org HydraCG/Specifications#104.
-
-
3 issues received 14 new comments.
-
Use W3C HTTP RDF vocabulary HydraCG/Specifications#109 (10 comments by @asbjornu, @elf-pavlik, @lanthaler, @tpluscode)
-
Use the term Action instead of Operation HydraCG/Specifications#2 (3 comments by @asbjornu, @lanthaler, @tpluscode)
-
-
1 pull request opened.
-
Proof of concept for authoring spec in markdown HydraCG/Specifications#110, by @tpluscode.
-
-
1 pull request merged.
-
Implement “remove predefined operations” HydraCG/Specifications#86.
-
-
2 pull requests received 17 new comments.
-
Proof of concept for authoring spec in markdown HydraCG/Specifications#110 (15 comments by @asbjornu, @lanthaler, @RubenVerborgh, @tpluscode)
-
Implement “remove predefined operations” HydraCG/Specifications#86 (2 comments by @asbjornu, @lanthaler)
-