Entity Reconciliation Community Group - Activity in 2023
No matches.
Past meetings
GitHub
reconciliation-api/specs
-
1 issue opened.
-
Advertise score range used by a service in its manifest reconciliation-api/specs#147, by @wetneb.
-
-
4 issues closed.
-
Add ability to mark reconciliation property as required (used for candidate retrieval) reconciliation-api/specs#101.
-
Supplying multiple properties with the same pid in a reconciliation query reconciliation-api/specs#105.
-
Allow more flexible filter constraint handling of property arrays reconciliation-api/specs#88.
-
Date comparison needs an absolute settings to compute relative diff score reconciliation-api/specs#114.
-
-
1 issue received 2 new comments.
-
Advertise score range used by a service in its manifest reconciliation-api/specs#147 (2 comments by @Abbe98, @thadguidry)
-
-
1 pull request opened.
-
Move 'query' field inside 'properties' reconciliation-api/specs#149, by @wetneb.
-
-
3 pull requests merged.
-
Add section on setting the text direction reconciliation-api/specs#137.
-
Tweak language content to address remaining checklist issues reconciliation-api/specs#136.
-
Optional details for matching properties in reconciliation queries reconciliation-api/specs#131.
-
-
3 pull requests received 8 new comments.
-
Optional details for matching properties in reconciliation queries reconciliation-api/specs#131 (6 comments by @fsteeg, @thadguidry, @wetneb)
-
Tweak language content to address remaining checklist issues reconciliation-api/specs#136 (1 comment by @fsteeg)
-
reconciliation-api/census
-
1 issue opened.
-
Implementation in Excel? reconciliation-api/census#24, by @sklarman.
-
-
1 issue received 1 new comment.
Past meetings
GitHub
reconciliation-api/specs
-
2 issues opened.
-
Suggestion: add more easy-to-understand explanation of examples reconciliation-api/specs#146, by @GO5IT.
-
Reformulate the 'type' parameter as another property reconciliation-api/specs#145, by @wetneb.
-
-
1 issue closed.
-
Using identifierSpace when the entity set uses a mixture of namespaces reconciliation-api/specs#139.
-
-
5 issues received 14 new comments.
-
Submitting multiple entity names in the same reconciliation query reconciliation-api/specs#134 (7 comments by @osma, @thadguidry, @wetneb)
-
Suggestion: add more easy-to-understand explanation of examples reconciliation-api/specs#146 (2 comments by @GO5IT, @wetneb)
-
Simplify type syntax in reconciliation queries reconciliation-api/specs#109 (2 comments by @thadguidry, @wetneb)
-
Support for multi-lingual candidate names reconciliation-api/specs#138 (2 comments by @fsteeg, @wetneb)
-
Reformulate the 'type' parameter as another property reconciliation-api/specs#145 (1 comment by @thadguidry)
-
-
2 pull requests merged.
-
Remove JSONP support reconciliation-api/specs#142.
-
Remove identifierSpace and schemaSpace; make view templates mandatory reconciliation-api/specs#140.
-
Past meetings
GitHub
reconciliation-api/testbench
-
1 issue opened.
-
Error in first sentence on https://reconciliation-api.github.io/testbench/#/ ?? reconciliation-api/testbench#59, by @ookgezellig.
-
-
1 issue received 1 new comment.
-
Error in first sentence on https://reconciliation-api.github.io/testbench/#/ ?? reconciliation-api/testbench#59 (1 comment by @wetneb)
-
reconciliation-api/specs
-
2 issues opened.
-
Fix list punctuation reconciliation-api/specs#144, by @tfmorris.
-
Remove notion of "notable" types reconciliation-api/specs#143, by @wetneb.
-
-
2 issues closed.
-
Make scores of reconciliation candidates optional reconciliation-api/specs#127.
-
View template should support type-specific templates reconciliation-api/specs#45.
-
-
5 issues received 14 new comments.
-
Using identifierSpace when the entity set uses a mixture of namespaces reconciliation-api/specs#139 (9 comments by @osma, @tfmorris, @wetneb)
-
Submitting multiple entity names in the same reconciliation query reconciliation-api/specs#134 (2 comments by @fsteeg, @osma)
-
Unify the syntax for property values in reconciliation queries and data extension responses reconciliation-api/specs#94 (1 comment by @wetneb)
-
View template should support type-specific templates reconciliation-api/specs#45 (1 comment by @wetneb)
-
-
3 pull requests opened.
-
Remove JSONP support reconciliation-api/specs#142, by @osma.
-
Change remaining URI templates in examples to RFC6570 syntax reconciliation-api/specs#141, by @osma.
-
Remove identifierSpace and schemaSpace; make view templates mandatory reconciliation-api/specs#140, by @osma.
-
-
2 pull requests merged.
-
Make reconciliation score optional reconciliation-api/specs#133.
-
Change remaining URI templates in examples to RFC6570 syntax reconciliation-api/specs#141.
-
-
3 pull requests received 9 new comments.
-
Remove identifierSpace and schemaSpace; make view templates mandatory reconciliation-api/specs#140 (2 comments by @osma)
-
Optional details for matching properties in reconciliation queries reconciliation-api/specs#131 (1 comment by @wetneb)
Past meetings
GitHub
reconciliation-api/specs
-
4 issues opened.
-
Using identifierSpace when the entity set uses a mixture of namespaces reconciliation-api/specs#139, by @osma.
-
Support for multi-lingual candidate names reconciliation-api/specs#138, by @saumier.
-
use semantic versioning for protocol versions (?) reconciliation-api/specs#135, by @awagner-mainz.
-
Submitting multiple entity names in the same reconciliation query reconciliation-api/specs#134, by @wetneb.
-
-
1 issue closed.
-
define `type_strict` reconciliation-api/specs#60.
-
-
5 issues received 9 new comments.
-
Using identifierSpace when the entity set uses a mixture of namespaces reconciliation-api/specs#139 (4 comments by @fsteeg, @osma, @thadguidry)
-
use semantic versioning for protocol versions (?) reconciliation-api/specs#135 (2 comments by @awagner-mainz, @wetneb)
-
Simplify type syntax in reconciliation queries reconciliation-api/specs#109 (1 comment by @thadguidry)
-
Add "description" field to type and property classes reconciliation-api/specs#93 (1 comment by @thadguidry)
-
-
2 pull requests opened.
-
Add section on setting the text direction reconciliation-api/specs#137, by @fsteeg.
-
Tweak language content to address remaining checklist issues reconciliation-api/specs#136, by @fsteeg.
-
-
4 pull requests received 18 new comments.
-
Tweak language content to address remaining checklist issues reconciliation-api/specs#136 (9 comments by @awagner-mainz, @fsteeg, @thadguidry, @wetneb)
-
Optional details for matching properties in reconciliation queries reconciliation-api/specs#131 (3 comments by @fsteeg, @thadguidry, @wetneb)
-
Past meetings
-
1 meeting.
GitHub
reconciliation-api/specs
-
1 pull request merged.
-
Add Accept-Language and Content-Language headers reconciliation-api/specs#108.
-
-
1 pull request received 2 new comments.
-
Make reconciliation score optional reconciliation-api/specs#133 (2 comments by @paulgirard, @wetneb)
-
Past meetings
-
1 meeting.
GitHub
reconciliation-api/specs
-
4 issues received 10 new comments.
-
Add an additional property match context to the features reconciliation-api/specs#128 (4 comments by @fsteeg, @tfmorris, @thadguidry)
-
Add new `output` field to `features` reconciliation-api/specs#130 (3 comments by @fsteeg, @thadguidry)
-
Make scores of reconciliation candidates optional reconciliation-api/specs#127 (2 comments by @fsteeg, @tfmorris)
-
-
3 pull requests opened.
-
Make reconciliation score optional reconciliation-api/specs#133, by @wetneb.
-
Rough upgrade of openapi schema to newer schema versions reconciliation-api/specs#132, by @wetneb.
-
Optional details for matching properties in reconciliation queries reconciliation-api/specs#131, by @fsteeg.
-
-
1 pull request merged.
-
Rough upgrade of openapi schema to newer schema versions reconciliation-api/specs#132.
-
-
2 pull requests received 18 new comments.
-
Optional details for matching properties in reconciliation queries reconciliation-api/specs#131 (13 comments by @fsteeg, @paulgirard, @tfmorris, @wetneb)
-
Make reconciliation score optional reconciliation-api/specs#133 (5 comments by @paulgirard, @tfmorris)
-
reconciliation-api/testbench
-
1 pull request opened.
-
Update JSON schemas to match specs reconciliation-api/testbench#57, by @wetneb.
-
-
1 pull request merged.
-
Update JSON schemas to match specs reconciliation-api/testbench#57.
-
Past meetings
-
1 meeting.
GitHub
reconciliation-api/specs
-
1 issue opened.
-
Add new `output` field to `features` reconciliation-api/specs#130, by @thadguidry.
-
-
2 issues received 5 new comments.
-
Add an additional property match context to the features reconciliation-api/specs#128 (3 comments by @fsteeg, @thadguidry)
-
-
1 pull request merged.
-
Add section on text-processing language reconciliation-api/specs#129.
-
-
1 pull request received 2 new comments.
-
Add Accept-Language and Content-Language headers reconciliation-api/specs#108 (2 comments by @fsteeg, @wetneb)
-
Past meetings
-
1 meeting.
GitHub
reconciliation-api/specs
-
4 issues opened.
-
Add an additional property match context to the features reconciliation-api/specs#128, by @thadguidry.
-
Make scores of reconciliation candidates optional reconciliation-api/specs#127, by @wetneb.
-
I18n checklist: text direction reconciliation-api/specs#126, by @fsteeg.
-
I18n checklist: language reconciliation-api/specs#125, by @fsteeg.
-
-
1 issue closed.
-
Simplify type syntax in reconciliation queries reconciliation-api/specs#109.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add section on text-processing language reconciliation-api/specs#129, by @fsteeg.
-
-
1 pull request merged.
-
Remove support for supplying multiple types in recon queries reconciliation-api/specs#115.
-
-
1 pull request received 1 new comment.
-
Add Accept-Language and Content-Language headers reconciliation-api/specs#108 (1 comment by @fsteeg)
-
Past meetings
-
1 meeting.
GitHub
reconciliation-api/specs
-
4 issues closed.
-
listing properties in the service manifest reconciliation-api/specs#107.
-
Clarity on difference between versions reconciliation-api/specs#112.
-
I am having trouble viewing the specs this morning reconciliation-api/specs#82.
-
Redirect to the final version of the 0.1 specs reconciliation-api/specs#122.
-
-
2 issues received 2 new comments.
-
I am having trouble viewing the specs this morning reconciliation-api/specs#82 (1 comment by @wetneb)
-
2 pull requests opened.
-
Add usage of empty prefix in suggest services reconciliation-api/specs#124, by @fsteeg.
-
Set up redirect for 0.1 and 0.2 specs reconciliation-api/specs#123, by @wetneb.
-
-
2 pull requests merged.
-
Add usage of empty prefix in suggest services reconciliation-api/specs#124.
-
Set up redirect for 0.1 and 0.2 specs reconciliation-api/specs#123.
-
-
3 pull requests received 5 new comments.
-
Add Accept-Language and Content-Language headers reconciliation-api/specs#108 (2 comments by @tfmorris, @wetneb)
-
Remove support for supplying multiple types in recon queries reconciliation-api/specs#115 (1 comment by @fsteeg)
Past meetings
-
1 meeting.
GitHub
reconciliation-api/specs
-
4 issues opened.
-
Redirect to the final version of the 0.1 specs reconciliation-api/specs#122, by @wetneb.
-
Normalize field descriptions in JSON schemas reconciliation-api/specs#120, by @wetneb.
-
No JSON schema for data extension property proposal response reconciliation-api/specs#118, by @wetneb.
-
Date comparison needs an absolute settings to compute relative diff score reconciliation-api/specs#114, by @paulgirard.
-
-
1 issue closed.
-
No JSON schema for data extension property proposal response reconciliation-api/specs#118.
-
-
4 issues received 15 new comments.
-
Date comparison needs an absolute settings to compute relative diff score reconciliation-api/specs#114 (7 comments by @paulgirard, @tfmorris, @thadguidry, @wetneb)
-
Supplying multiple properties with the same pid in a reconciliation query reconciliation-api/specs#105 (5 comments by @fsteeg, @paulgirard)
-
Redirect to the final version of the 0.1 specs reconciliation-api/specs#122 (2 comments by @fsteeg, @thadguidry)
-
-
5 pull requests opened.
-
Include the data extension property proposal schemas in the specs reconciliation-api/specs#121, by @wetneb.
-
Add schema for data extension property proposal responses reconciliation-api/specs#119, by @wetneb.
-
Further clean-up before publication of 0.1 and 0.2 reconciliation-api/specs#117, by @wetneb.
-
Mark 0.1 and 0.2 as final reports reconciliation-api/specs#116, by @wetneb.
-
Remove support for supplying multiple types in recon queries reconciliation-api/specs#115, by @wetneb.
-
-
5 pull requests merged.
-
Include the data extension property proposal schemas in the specs reconciliation-api/specs#121.
-
Add schema for data extension property proposal responses reconciliation-api/specs#119.
-
Further clean-up before publication of 0.1 and 0.2 reconciliation-api/specs#117.
-
Mark 0.1 and 0.2 as final reports reconciliation-api/specs#116.
-
Move current draft to the 'draft' directory instead of 'latest' reconciliation-api/specs#113.
-
-
1 pull request closed.
-
Remove support for single type in queries reconciliation-api/specs#110.
-
-
4 pull requests received 5 new comments.
-
Add schema for data extension property proposal responses reconciliation-api/specs#119 (2 comments by @fsteeg, @wetneb)
-
Include the data extension property proposal schemas in the specs reconciliation-api/specs#121 (1 comment by @wetneb)
-
Add Accept-Language and Content-Language headers reconciliation-api/specs#108 (1 comment by @tfmorris)
-
Past meetings
GitHub
reconciliation-api/specs
-
4 issues opened.
-
Clarity on difference between versions reconciliation-api/specs#112, by @rogerhyam.
-
Describe compatibility requirements for clients and services reconciliation-api/specs#111, by @tfmorris.
-
Simplify type syntax in reconciliation queries reconciliation-api/specs#109, by @wetneb.
-
listing properties in the service manifest reconciliation-api/specs#107, by @eroux.
-
-
1 issue closed.
-
Describe compatibility requirements for clients and services reconciliation-api/specs#111.
-
-
7 issues received 22 new comments.
-
Clarity on difference between versions reconciliation-api/specs#112 (9 comments by @rogerhyam, @tfmorris, @thadguidry, @wetneb)
-
listing properties in the service manifest reconciliation-api/specs#107 (4 comments by @eroux, @fsteeg)
-
Simplify type syntax in reconciliation queries reconciliation-api/specs#109 (2 comments by @fsteeg, @wetneb)
-
Describe compatibility requirements for clients and services reconciliation-api/specs#111 (2 comments by @tfmorris, @wetneb)
-
Supplying multiple properties with the same pid in a reconciliation query reconciliation-api/specs#105 (1 comment by @paulgirard)
-
-
3 pull requests opened.
-
Move current draft to the 'draft' directory instead of 'latest' reconciliation-api/specs#113, by @wetneb.
-
Remove support for single type in queries reconciliation-api/specs#110, by @wetneb.
-
Add Accept-Language and Content-Language headers reconciliation-api/specs#108, by @wetneb.
-
-
2 pull requests received 7 new comments.
-
Remove support for single type in queries reconciliation-api/specs#110 (4 comments by @tfmorris, @thadguidry, @wetneb)
-
Move current draft to the 'draft' directory instead of 'latest' reconciliation-api/specs#113 (3 comments by @fsteeg, @wetneb)
-
Past meetings
Participants
-
1 participant joined.
-
Paul Girard joined.
-
GitHub
reconciliation-api/specs
-
2 issues opened.
-
Reformulate the `query` parameter as one of the `properties` in reconciliation queries reconciliation-api/specs#106, by @wetneb.
-
Supplying multiple properties with the same pid in a reconciliation query reconciliation-api/specs#105, by @wetneb.
-
-
5 issues received 12 new comments.
-
Multilingual support reconciliation-api/specs#52 (8 comments by @eroux, @thadguidry, @VladimirAlexiev, @wetneb)
-
Add ability to mark reconciliation property as required (used for candidate retrieval) reconciliation-api/specs#101 (1 comment by @thadguidry)
-
Reformulate the `query` parameter as one of the `properties` in reconciliation queries reconciliation-api/specs#106 (1 comment by @thadguidry)
-
Supplying multiple properties with the same pid in a reconciliation query reconciliation-api/specs#105 (1 comment by @thadguidry)
-
-
1 pull request merged.
-
Content on accessibility reconciliation-api/specs#103.
-
-
1 pull request received 3 new comments.