-
The test newly added in https://github.com/RalphTro/epcis-event-hash-generator/commit/03d74635f316014a75b770181fde6584432dc7a7 spottet that `urn:epcglobal:cbv:btt:desadv` is not contained in the preha…
-
Websocket connections as per draft are supported only for subscription. Subscribing to a query requires persisting that query whereas in case of anonymous query , persistence does not happen. Can we i…
-
@dakbhavesh asked if we can optionally include @context within query-schema.json to be able to support queries that make use of user-defined / vendor-defined namespaces.
@context is used to referen…
-
@sboeckelmann, if we are to vote on it, could you please find concrete examples of similar systems where such timeouts are used?
-
-
Presence of `/queries/{queryName}/masterdata` endpoint lead us to bring up following #1, #2 and #3 observation. If we are only going to support querying master data through `/queries/SimpleMasterData/…
-
Using dedicated endpoint for processing pagination might lead to better separation of concerns.
Some sort of pagination context must be managed on server-side. Being able to separate pure pagination…
-
Review EPCIS concepts relating to BusinessLocation and ReadPoint to inform thinking on the Location RFC. Intent is to make sure we're well positioned for EPCIS support if that is the path we're going …
-
If we execute an anonymous query with a POST, we can't use pagination. Pagination goes with GET. We can't use GET with a query payload, because the GET payload is not supposed to change the response. …
-
Potentially by treating the filtering on {eventType} exactly the same was as we already support filtering on bizStep and disposition:
We already support:
/bizSteps/{bizStep}**/events**
/disposi…