Hydra Community Group - Activity in 2014
No matches.
Participants
-
3 participants joined.
-
Sebastien Lambla joined.
-
Alessandro Baffa joined.
-
Andrew Hacking joined.
-
-
2 participants left.
-
Markus Lanthaler (Google LLC) left.
-
Alessandro Baffa left.
-
GitHub
HydraCG/Specifications
-
1 issue opened.
-
Spec document has wrong header level for classes and properties HydraCG/Specifications#78, by @RubenVerborgh.
-
-
1 issue closed.
-
Expansion of IRI templates should be better documented HydraCG/Specifications#30.
-
-
5 issues received 12 new comments.
-
Should sorting of paged collections be specified (in Hydra core)? HydraCG/Specifications#6 (4 comments by @akuckartz, @ceefour)
-
Spec document has wrong header level for classes and properties HydraCG/Specifications#78 (3 comments by @akuckartz, @lanthaler, @RubenVerborgh)
-
Interoperability with Linked Data Platform (especially regarding collections and paging) HydraCG/Specifications#36 (2 comments by @ceefour, @elf-pavlik)
-
-
1 pull request opened.
-
Detail IRI template expansion in vocabulary and spec. HydraCG/Specifications#79, by @RubenVerborgh.
-
-
1 pull request closed.
-
Detail IRI template expansion in vocabulary and spec. HydraCG/Specifications#79.
-
Participants
-
6 participants joined.
-
Klaas Heidstra joined.
-
Bawer Dagdeviren joined.
-
Kai Kunstmann joined.
-
Ryan Roberts joined.
-
Chunming Hu (W3C) joined.
-
Pedro Urra joined.
-
-
4 organizations joined.
-
TopQuadrant joined.
-
PT Bina Media Terpadu joined.
-
Ranyart Systems Limited joined.
-
trick17.media joined.
-
-
1 organization left.
-
E NET Production left.
-
GitHub
HydraCG/Specifications
-
1 issue received 3 new comments.
-
Add Turtle serialization of the examples HydraCG/Specifications#18 (3 comments by @elf-pavlik, @lanthaler, @RubenVerborgh)
-
Participants
-
6 participants joined.
-
yannick serra joined.
-
Luis Baquera joined.
-
Timo Stollenwerk joined.
-
Matthew Slater joined.
-
Simon Heimler joined.
-
Paul Walker joined.
-
-
1 participant left.
-
Ioseb Dzmanashvili left.
-
-
2 organizations joined.
-
Stanford University joined.
-
The Dun & Bradstreet Corporation joined.
-
GitHub
HydraCG/Specifications
-
4 issues opened.
-
Triple pattern fragments: explain how to handle blank nodes HydraCG/Specifications#77, by @RubenVerborgh.
-
Link to "complete API documentation" if it varies based on permissions HydraCG/Specifications#75, by @lanthaler.
-
Add support for examples (Operations, IriTemplates, etc.) HydraCG/Specifications#74, by @lanthaler.
-
Make it clear how supportedProperty statements work with multi-typed entities HydraCG/Specifications#73, by @lanthaler.
-
-
4 issues received 6 new comments.
-
Expansion of IRI templates should be better documented HydraCG/Specifications#30 (2 comments by @lanthaler)
-
Add support for examples (Operations, IriTemplates, etc.) HydraCG/Specifications#74 (1 comment by @akuckartz)
-
-
1 pull request opened.
-
Relax CORS requirements for TPF servers HydraCG/Specifications#76, by @lanthaler.
-
-
1 pull request merged.
-
Relax CORS requirements for TPF servers HydraCG/Specifications#76.
-
-
1 pull request received 3 new comments.
-
Relax CORS requirements for TPF servers HydraCG/Specifications#76 (3 comments by @lanthaler, @RubenVerborgh)
-
Participants
-
7 participants joined.
-
David Bell joined.
-
Kev Kirkland joined.
-
Wasin Passornpakorn joined.
-
Robert Nix joined.
-
Nathan Stites joined.
-
Andreas Prieß joined.
-
Peb Ruswono Aryan joined.
-
GitHub
HydraCG/Specifications
-
4 issues opened.
-
Discuss versioning HydraCG/Specifications#72, by @lanthaler.
-
Clarify that operations from operation and supportedOperation are merged HydraCG/Specifications#71, by @lanthaler.
-
Description of workflows HydraCG/Specifications#70, by @lanthaler.
-
Describe entry point -> ApiDocumentation flow HydraCG/Specifications#69, by @lanthaler.
-
-
5 issues received 9 new comments.
-
Having both hydra:statusCode and hydra:statusCodes should be avoided HydraCG/Specifications#27 (1 comment by @lanthaler)
-
Restructure spec to talk about application state, resource state, and API as whole HydraCG/Specifications#44 (1 comment by @elf-pavlik)
Participants
-
4 participants joined.
-
Martijn Faassen joined.
-
Cedric Dumont joined.
-
Tibor Katelbach joined.
-
Jacopo Scazzosi joined.
-
-
3 participants left.
-
Benjamin Young left.
-
Jaik Dean left.
-
Robert Best left.
-
-
2 organizations joined.
-
Mashape Inc. joined.
-
TNO joined.
-
GitHub
HydraCG/Specifications
-
2 issues opened.
-
Add an example showing how responses point to the ApiDocumentation HydraCG/Specifications#68, by @lanthaler.
-
LinkedData™ HydraCG/Specifications#66, by @dret.
-
-
2 issues closed.
-
LinkedData™ HydraCG/Specifications#66.
-
Review HTTP status codes for non-existing / empty fragments HydraCG/Specifications#64.
-
-
6 issues received 15 new comments.
-
Review HTTP status codes for non-existing / empty fragments HydraCG/Specifications#64 (3 comments by @lanthaler, @RubenVerborgh)
-
Discuss how usage of Collections "breaks" relationships HydraCG/Specifications#41 (2 comments by @jacoscaz, @lanthaler)
-
HTTP might not be the only implementation of triple pattern fragment servers HydraCG/Specifications#63 (1 comment by @RubenVerborgh)
-
1 pull request opened.
-
fixing typo HydraCG/Specifications#67, by @dret.
-
-
1 pull request merged.
-
fixing typo HydraCG/Specifications#67.
-
-
1 pull request received 1 new comment.
Participants
-
3 participants joined.
-
Dan Scott joined.
-
Matt Crellin joined.
-
Philipp Zins joined.
-
-
1 participant left.
-
Michael Härtl left.
-
-
1 organization joined.
-
Siemens AG joined.
-
GitHub
HydraCG/Specifications
-
8 issues opened.
-
Create a test suite for servers of triple pattern fragments HydraCG/Specifications#65, by @RubenVerborgh.
-
Review HTTP status codes for non-existing / empty fragments HydraCG/Specifications#64, by @RubenVerborgh.
-
HTTP might not be the only implementation of triple pattern fragment servers HydraCG/Specifications#63, by @RubenVerborgh.
-
Is the term ApiDocumentation misleading HydraCG/Specifications#61, by @lanthaler.
-
Find a better name for the "manages block" HydraCG/Specifications#60, by @lanthaler.
-
Enumerate supported/used operation types and properties in ApiDocumentation HydraCG/Specifications#59, by @lanthaler.
-
Range of required, writeonly, readonly should be boolean not "undefined" HydraCG/Specifications#58, by @akuckartz.
-
Resource both a hydra:Collection and a hydra:Link ? HydraCG/Specifications#57, by @mb21.
-
-
4 issues closed.
-
Map predefined operations to CRUD operations and name them accordingly HydraCG/Specifications#4.
-
Add RetrieveResourceOperation HydraCG/Specifications#5.
-
Range of required, writeonly, readonly should be boolean not "undefined" HydraCG/Specifications#58.
-
Resource both a hydra:Collection and a hydra:Link ? HydraCG/Specifications#57.
-
-
15 issues received 39 new comments.
-
Discuss how usage of Collections "breaks" relationships HydraCG/Specifications#41 (5 comments by @cdchapman, @gkellogg, @lanthaler)
-
Resource both a hydra:Collection and a hydra:Link ? HydraCG/Specifications#57 (5 comments by @lanthaler, @mb21)
-
Date ranges / intervals for LDF HydraCG/Specifications#56 (4 comments by @akuckartz, @lanthaler, @RubenVerborgh)
-
Review HTTP status codes for non-existing / empty fragments HydraCG/Specifications#64 (3 comments by @akuckartz, @RubenVerborgh)
-
Expansion of IRI templates should be better documented HydraCG/Specifications#30 (3 comments by @jaw111, @lanthaler, @RubenVerborgh)
-
Add Turtle serialization of the examples HydraCG/Specifications#18 (3 comments by @arnau, @elf-pavlik, @lanthaler)
-
Having both hydra:statusCode and hydra:statusCodes should be avoided HydraCG/Specifications#27 (2 comments by @lanthaler)
-
Rename readonly/writeonly to readable/writeable HydraCG/Specifications#14 (2 comments by @lanthaler)
-
Document how "errors" can be given an identifier and be reused in responses HydraCG/Specifications#39 (2 comments by @lanthaler)
-
Map predefined operations to CRUD operations and name them accordingly HydraCG/Specifications#4 (2 comments by @lanthaler)
-
Remove predefined operations from the core vocabulary. HydraCG/Specifications#11 (2 comments by @lanthaler)
-
HTTP might not be the only implementation of triple pattern fragment servers HydraCG/Specifications#63 (2 comments by @akuckartz, @RubenVerborgh)
-
Enumerate supported/used operation types and properties in ApiDocumentation HydraCG/Specifications#59 (1 comment by @lanthaler)
-
Range of required, writeonly, readonly should be boolean not "undefined" HydraCG/Specifications#58 (1 comment by @lanthaler)
-
-
1 pull request opened.
-
The URL of the Hydra core has been changed. HydraCG/Specifications#62, by @baquiax.
-
-
2 pull requests merged.
-
The URL of the Hydra core has been changed. HydraCG/Specifications#62.
-
changed schema.org spec to use respec-w3c-common from w3.org HydraCG/Specifications#55.
-
-
2 pull requests received 3 new comments.
-
The URL of the Hydra core has been changed. HydraCG/Specifications#62 (2 comments by @baquiax, @lanthaler)
-
changed schema.org spec to use respec-w3c-common from w3.org HydraCG/Specifications#55 (1 comment by @lanthaler)
-
Participants
-
7 participants joined.
-
Claus Stadler (Universität Leipzig) joined.
-
Robert Best joined.
-
Ryan Riley joined.
-
Jaik Dean joined.
-
Benjamin Cogrel joined.
-
Sindre Njøsen joined.
-
Tomasz Pluskiewicz (Zazuko) joined.
-
-
3 organizations joined.
-
Japan Registry Services Co., Ltd. joined.
-
Linked Data, UAB joined.
-
Open Knowledge Foundation joined.
-
GitHub
HydraCG/Specifications
-
8 issues opened.
-
Date ranges / intervals for LDF HydraCG/Specifications#56, by @akuckartz.
-
Triple Pattern Fragments: [RDF-CONCEPTS] should reference "RDF 1.1 Concepts and Abstract Syntax" HydraCG/Specifications#54, by @akuckartz.
-
Some Points Regarding 'Linked Data Fragments' HydraCG/Specifications#53, by @vanthome.
-
Improve documentation of the hydra:entrypoint property HydraCG/Specifications#52, by @lanthaler.
-
Improve definition of hydra:search HydraCG/Specifications#51, by @lanthaler.
-
Allow hydra:returns on IriTemplate? HydraCG/Specifications#50, by @lanthaler.
-
Typo in rdfs:comment of hydra:ReplaceResourceOperation HydraCG/Specifications#49, by @jindrichmynarz.
-
Add domainIncludes/rangeIncludes statements HydraCG/Specifications#48, by @lanthaler.
-
-
4 issues closed.
-
Triple Pattern Fragments: [RDF-CONCEPTS] should reference "RDF 1.1 Concepts and Abstract Syntax" HydraCG/Specifications#54.
-
Some Points Regarding 'Linked Data Fragments' HydraCG/Specifications#53.
-
Typo in rdfs:comment of hydra:ReplaceResourceOperation HydraCG/Specifications#49.
-
Word missing: "A Hydra client would look a Link Header with a relation type ..." HydraCG/Specifications#47.
-
-
10 issues received 11 new comments.
-
Some Points Regarding 'Linked Data Fragments' HydraCG/Specifications#53 (2 comments by @RubenVerborgh, @vanthome)
-
Triple Pattern Fragments: [RDF-CONCEPTS] should reference "RDF 1.1 Concepts and Abstract Syntax" HydraCG/Specifications#54 (1 comment by @RubenVerborgh)
-
Typo in rdfs:comment of hydra:ReplaceResourceOperation HydraCG/Specifications#49 (1 comment by @lanthaler)
-
Support exemplary values for properties and IRI template variables HydraCG/Specifications#46 (1 comment by @RubenVerborgh)
-
Word missing: "A Hydra client would look a Link Header with a relation type ..." HydraCG/Specifications#47 (1 comment by @lanthaler)
-
-
1 pull request opened.
-
changed schema.org spec to use respec-w3c-common from w3.org HydraCG/Specifications#55, by @elf-pavlik.
-
Participants
-
2 participants joined.
-
Alexandr Krylovskiy joined.
-
Kjetil Kjernsmo joined.
-
-
1 participant left.
-
Alexandr Krylovskiy left.
-
-
2 organizations joined.
-
InSideOut10 joined.
-
Pentandra Research Solutions, Inc. joined.
-
GitHub
HydraCG/Specifications
-
2 issues opened.
-
Word missing: "A Hydra client would look a Link Header with a relation type ..." HydraCG/Specifications#47, by @akuckartz.
-
Support exemplary values for properties and IRI template variables HydraCG/Specifications#46, by @lanthaler.
-
-
4 issues received 8 new comments.
-
Discuss how usage of Collections "breaks" relationships HydraCG/Specifications#41 (5 comments by @akuckartz, @gkellogg, @lanthaler)
-
Map predefined operations to CRUD operations and name them accordingly HydraCG/Specifications#4 (1 comment by @cdchapman)
-
Remove predefined operations from the core vocabulary. HydraCG/Specifications#11 (1 comment by @cdchapman)
-
Participants
-
3 participants joined.
-
Carsten Klee joined.
-
Pascal Giessler joined.
-
Pascal Giessler joined.
-
-
1 participant left.
-
Pascal Giessler left.
-
-
3 organizations joined.
-
D&B Corporation joined.
-
Google LLC joined.
-
Freshheads BV joined.
-
GitHub
HydraCG/Specifications
-
4 issues opened.
-
Introduce hydra:filter (subPropertyOf hydra:search) HydraCG/Specifications#45, by @lanthaler.
-
Restructure spec to talk about application state, resource state, and API as whole HydraCG/Specifications#44, by @lanthaler.
-
Try to make spec interactive, link examples to HydraConsole HydraCG/Specifications#43, by @lanthaler.
-
Rethink paging HydraCG/Specifications#42, by @RubenVerborgh.
-
-
1 issue closed.
-
Clarify relationship between Hydra operations and OPTIONS request HydraCG/Specifications#10.
-
-
27 issues received 33 new comments.
-
Restructure spec to talk about application state, resource state, and API as whole HydraCG/Specifications#44 (4 comments by @lanthaler, @RubenVerborgh)
-
Introduce hydra:filter (subPropertyOf hydra:search) HydraCG/Specifications#45 (3 comments by @gkellogg, @lanthaler)
-
Specify the expected cardinality of properties (using OWL) HydraCG/Specifications#35 (1 comment by @lanthaler)
-
Should properties and types that only differ in their capitalization be avoided? HydraCG/Specifications#28 (1 comment by @lanthaler)
-
Expansion of IRI templates should be better documented HydraCG/Specifications#30 (1 comment by @lanthaler)
-
Should sorting of paged collections be specified (in Hydra core)? HydraCG/Specifications#6 (1 comment by @lanthaler)
-
Allow SupportedProperty to overwrite a vocabulary's rdfs:label and rdfs:comment HydraCG/Specifications#1 (1 comment by @lanthaler)
-
Are Operations violating REST's uniform interface constraint? HydraCG/Specifications#31 (1 comment by @lanthaler)
-
Document how "errors" can be given an identifier and be reused in responses HydraCG/Specifications#39 (1 comment by @lanthaler)
-
Having both hydra:statusCode and hydra:statusCodes should be avoided HydraCG/Specifications#27 (1 comment by @lanthaler)
-
Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? HydraCG/Specifications#32 (1 comment by @lanthaler)
-
Explain how operations dependent on a resource's state can be described HydraCG/Specifications#23 (1 comment by @lanthaler)
-
Map predefined operations to CRUD operations and name them accordingly HydraCG/Specifications#4 (1 comment by @lanthaler)
-
Remove predefined operations from the core vocabulary. HydraCG/Specifications#11 (1 comment by @lanthaler)
-
Should we introduce a property to associate operations and their target directly to an entity? HydraCG/Specifications#3 (1 comment by @lanthaler)
-
Clarify relationship between Hydra operations and OPTIONS request HydraCG/Specifications#10 (1 comment by @lanthaler)
-
Reports
-
1 report published.
-
Hydra Core Vocabulary published as a draft report.
-
Participants
-
4 participants joined.
-
Rosario Garcia de Zuniga joined.
-
Alfredo Serafini joined.
-
Alexander Zeitler joined.
-
Vagif Abilov joined.
-
-
1 participant left.
-
Mark Baker left.
-
-
2 organizations joined.
-
National Technical University of Athens joined.
-
Semaku joined.
-
-
1 organization left.
-
University of Pennsylvania left.
-
GitHub
HydraCG/Specifications
-
3 issues opened.
-
Discuss how usage of Collections "breaks" relationships HydraCG/Specifications#41, by @lanthaler.
-
Reversed SupportedProperty HydraCG/Specifications#40, by @lanthaler.
-
Document how "errors" can be given an identifier and be reused in responses HydraCG/Specifications#39, by @lanthaler.
-
-
8 issues received 15 new comments.
-
Expansion of IRI templates should be better documented HydraCG/Specifications#30 (6 comments by @gkellogg, @RubenVerborgh)
-
Discuss how usage of Collections "breaks" relationships HydraCG/Specifications#41 (3 comments by @gkellogg, @lanthaler)
-
Document how "errors" can be given an identifier and be reused in responses HydraCG/Specifications#39 (1 comment by @lanthaler)
-
Remove predefined operations from the core vocabulary. HydraCG/Specifications#11 (1 comment by @lanthaler)
-
Participants
-
4 participants joined.
-
Cedric Brancourt joined.
-
Michael Härtl joined.
-
Khalid Nobani joined.
-
Herbert Snorrason joined.
-
-
3 participants left.
-
Andrew Mackie left.
-
Paul Capestany left.
-
Robin Berjon (W3C) left.
-
-
2 organizations joined.
-
Argo Data Resource Corporation joined.
-
Kévin Dunglas joined.
-
GitHub
HydraCG/Specifications
-
12 issues opened.
-
Define "priority of constituencies" HydraCG/Specifications#38, by @lanthaler.
-
Define/change the range of "supportedProperty" HydraCG/Specifications#37, by @lanthaler.
-
Interoperability with Linked Data Platform (especially regarding collections and paging) HydraCG/Specifications#36, by @akuckartz.
-
Specify the expected cardinality of properties (using OWL) HydraCG/Specifications#35, by @lanthaler.
-
How should indirections through collections be handled/interpreted HydraCG/Specifications#33, by @lanthaler.
-
Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? HydraCG/Specifications#32, by @lanthaler.
-
Are Operations violating REST's uniform interface constraint? HydraCG/Specifications#31, by @lanthaler.
-
Expansion of IRI templates should be better documented HydraCG/Specifications#30, by @lanthaler.
-
There seem to be some bugs with the textual rendering of the vocabulary HydraCG/Specifications#29, by @lanthaler.
-
Should properties and types that only differ in their capitalization be avoided? HydraCG/Specifications#28, by @lanthaler.
-
Having both hydra:statusCode and hydra:statusCodes should be avoided HydraCG/Specifications#27, by @lanthaler.
-
Nested structures (supportedProperty) HydraCG/Specifications#26, by @lanthaler.
-
-
1 issue closed.
-
Plural properties should become singular HydraCG/Specifications#25.
-
-
18 issues received 43 new comments.
-
Plural properties should become singular HydraCG/Specifications#25 (7 comments by @damnhandy, @gkellogg, @lanthaler, @RubenVerborgh)
-
Specify the expected cardinality of properties (using OWL) HydraCG/Specifications#35 (7 comments by @akuckartz, @lanthaler, @RubenVerborgh)
-
Interoperability with Linked Data Platform (especially regarding collections and paging) HydraCG/Specifications#36 (3 comments by @lanthaler, @vanthome)
-
Nested structures (supportedProperty) HydraCG/Specifications#26 (3 comments by @gkellogg, @lanthaler)
-
Expansion of IRI templates should be better documented HydraCG/Specifications#30 (2 comments by @akuckartz, @RubenVerborgh)
-
Add Turtle serialization of the examples HydraCG/Specifications#18 (2 comments by @akuckartz, @damnhandy)
-
Having both hydra:statusCode and hydra:statusCodes should be avoided HydraCG/Specifications#27 (2 comments by @RubenVerborgh)
-
Should properties and types that only differ in their capitalization be avoided? HydraCG/Specifications#28 (2 comments by @gkellogg, @RubenVerborgh)
-
Rename readonly/writeonly to readable/writeable HydraCG/Specifications#14 (1 comment by @mikehaertl)
-
Remove predefined operations from the core vocabulary. HydraCG/Specifications#11 (1 comment by @RubenVerborgh)
-
Define/change the range of "supportedProperty" HydraCG/Specifications#37 (1 comment by @RubenVerborgh)
-
Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? HydraCG/Specifications#32 (1 comment by @RubenVerborgh)
-
-
1 pull request opened.
-
Singularize properties HydraCG/Specifications#34, by @RubenVerborgh.
-
-
1 pull request closed.
-
Singularize properties HydraCG/Specifications#34.
-
Participants
-
5 participants joined.
-
Giovanni De Facci joined.
-
Kristoffer Lie Braathen joined.
-
Dominik Tomaszuk joined.
-
Laszlo Janszky joined.
-
Andreas Kuckartz joined.
-
-
6 organizations joined.
-
DK Computer Systems Ltd joined.
-
Logical Reality Design joined.
-
Galileo University of Guatemala joined.
-
INNOVIMAX joined.
-
World Wide Technology joined.
-
Best Buy joined.
-
GitHub
HydraCG/Specifications
-
3 issues opened.
-
Plural properties should become singular HydraCG/Specifications#25, by @lanthaler.
-
Improve vocabulary illustration HydraCG/Specifications#24, by @lanthaler.
-
Explain how operations dependent on a resource's state can be described HydraCG/Specifications#23, by @lanthaler.
-
-
2 issues received 3 new comments.
-
Plural properties should become singular HydraCG/Specifications#25 (2 comments by @lanthaler, @RubenVerborgh)
-
Explain how operations dependent on a resource's state can be described HydraCG/Specifications#23 (1 comment by @lanthaler)
-