Hydra Community Group - Activity in 2013
No matches.
Participants
-
1 organization joined.
-
Digital Bazaar joined.
-
-
1 organization left.
-
Digital Bazaar left.
-
GitHub
HydraCG/Specifications
-
4 issues opened.
-
Allow returns/expects to be expressed in terms of a media type; what about multiple types? HydraCG/Specifications#22, by @lanthaler.
-
State more explicitely that hydra:return etc. are just hints HydraCG/Specifications#21, by @lanthaler.
-
Ideas for additional features/vocabularies HydraCG/Specifications#20, by @lanthaler.
-
Change the namespace to w3.org HydraCG/Specifications#19, by @lanthaler.
-
-
1 issue closed.
-
Change the namespace to w3.org HydraCG/Specifications#19.
-
-
3 issues reopened.
-
Add RetrieveResourceOperation HydraCG/Specifications#5, by @lanthaler.
-
Map predefined operations to CRUD operations and name them accordingly HydraCG/Specifications#4, by @lanthaler.
-
Should sorting of paged collections be specified (in Hydra core)? HydraCG/Specifications#6, by @lanthaler.
-
-
9 issues received 11 new comments.
-
State more explicitely that hydra:return etc. are just hints HydraCG/Specifications#21 (2 comments by @bradjonesca, @lanthaler)
-
Should sorting of paged collections be specified (in Hydra core)? HydraCG/Specifications#6 (2 comments by @elf-pavlik, @lanthaler)
-
Map predefined operations to CRUD operations and name them accordingly HydraCG/Specifications#4 (1 comment by @lanthaler)
-
Rename readonly/writeonly to readable/writeable HydraCG/Specifications#14 (1 comment by @elf-pavlik)
-
Participants
-
5 participants joined.
-
Samuel Morello joined.
-
Melvin Carvalho joined.
-
David Booth joined.
-
Mark Baker joined.
-
Achim Friedland joined.
-
-
1 participant left.
-
Erik Ringsmuth left.
-
-
4 organizations joined.
-
Universidad Politécnica de Madrid joined.
-
PlantRobot LLC joined.
-
OpenLink Software Inc. joined.
-
Wipro Technologies joined.
-
GitHub
HydraCG/Specifications
-
5 issues opened.
-
Add Turtle serialization of the examples HydraCG/Specifications#18, by @lanthaler.
-
Introduce a datatype for RFC6570 IRI templates HydraCG/Specifications#17, by @lanthaler.
-
Introduce something like hydra:memberTemplate HydraCG/Specifications#16, by @lanthaler.
-
Define a property to be used for untyped links? HydraCG/Specifications#15, by @lanthaler.
-
Rename readonly/writeonly to readable/writeable HydraCG/Specifications#14, by @lanthaler.
-
-
1 issue received 1 new comment.
Participants
-
2 participants joined.
-
Adrian Gschwend joined.
-
Ryan McDonough joined.
-
-
1 organization joined.
-
Université de Lyon joined.
-
GitHub
HydraCG/Specifications
-
3 issues opened.
-
Describe how hydra:apiDocumentation can be used to associate information to concepts defined in other vocabularies HydraCG/Specifications#13, by @lanthaler.
-
Add rdfs:isDefinedBy to all concepts and rdfs:seeAlso to vocabulary itself HydraCG/Specifications#12, by @lanthaler.
-
Remove predefined operations from the core vocabulary. HydraCG/Specifications#11, by @lanthaler.
-
Participants
-
2 participants joined.
-
Kuno Woudt joined.
-
Erik Ringsmuth joined.
-
GitHub
HydraCG/Specifications
-
1 issue received 1 new comment.
-
Clarify relationship between Hydra operations and OPTIONS request HydraCG/Specifications#10 (1 comment by @lanthaler)
-
Participants
-
4 participants joined.
-
Arnau Siches joined.
-
Benjamin Young joined.
-
Paul Hermans joined.
-
Andrew Mackie joined.
-
-
2 organizations joined.
-
Sprint Nextel joined.
-
n-fuse GmbH joined.
-
GitHub
HydraCG/Specifications
-
7 issues opened.
-
Clarify relationship between Hydra operations and OPTIONS request HydraCG/Specifications#10, by @dschulten.
-
missing comma at example 6 HydraCG/Specifications#8, by @arnau.
-
Mention how authorization might be handled HydraCG/Specifications#7, by @lanthaler.
-
Should sorting of paged collections be specified (in Hydra core)? HydraCG/Specifications#6, by @lanthaler.
-
Add RetrieveResourceOperation HydraCG/Specifications#5, by @lanthaler.
-
Map predefined operations to CRUD operations and name them accordingly HydraCG/Specifications#4, by @lanthaler.
-
Should we introduce a property to associate operations and their target directly to an entity? HydraCG/Specifications#3, by @lanthaler.
-
-
1 issue closed.
-
missing comma at example 6 HydraCG/Specifications#8.
-
-
1 issue received 7 new comments.
-
1 pull request opened.
-
Example review HydraCG/Specifications#9, by @arnau.
-
-
1 pull request merged.
-
Example review HydraCG/Specifications#9.
-
-
1 pull request received 5 new comments.
Participants
-
2 participants joined.
-
Alexey Zakhlestin joined.
-
Stuart Charlton joined.
-
-
3 organizations joined.
-
Department of Health and Human Services joined.
-
E NET Production joined.
-
University of Pennsylvania joined.
-
GitHub
HydraCG/Specifications
-
2 issues opened.
-
Use the term Action instead of Operation HydraCG/Specifications#2, by @lanthaler.
-
Allow SupportedProperty to overwrite a vocabulary's rdfs:label and rdfs:comment HydraCG/Specifications#1, by @lanthaler.
-
-
1 issue received 3 new comments.
-
Allow SupportedProperty to overwrite a vocabulary's rdfs:label and rdfs:comment HydraCG/Specifications#1 (3 comments by @lanthaler, @matleh)
-
Participants
-
14 participants joined.
-
Gregg Kellogg (Spec-Ops) joined.
-
Paul Capestany joined.
-
Dietrich Schulten joined.
-
Pavlik elf joined.
-
Robin Berjon (W3C) joined.
-
Sam Alloing joined.
-
Shane McCarron joined.
-
Guille Carlos joined.
-
Bo Ferri joined.
-
Brad Jones joined.
-
Kevin Swiber joined.
-
Mike Amundsen joined.
-
Ioseb Dzmanashvili joined.
-
Markus Lanthaler (Google LLC) joined.
-
-
2 organizations joined.
-
imec joined.
-
Globo.com joined.
-