-
The SHACL shape and https://ns.mh1.eu/epcis/ show `xsd:anyURI` as range for several properties. However, `xsd:anyURI` is a **literal** not a URI.
Instead, these props:
- should be defined as `owl:…
-
@mgh128 and @CraigRe, cc @philarcher
- #214 discusses the current 3 MasterData examples: only 1 is any good, and needs to be made more precise
- I see in `2021_03_08b GS1-White-Paper-On-demand-mast…
-
Examples are great, examples in multiple formats even better.
But if I'm a new developer, how will I know which example demonstrates what?
I think we need an index (README.md) listing all examples…
-
Minor remarks on document `2021_03_23b EPCIS 2-0 COMMREV.docx`. "->" means "replace with".
I've numbered them so you can refer to these items in replies:
1) "two kinds of data: event data and mast…
-
The spec includes numerous field dependencies. We should try to express as many of them as possible in a validatable way:
- SHACL has things like `xor` (exclusive fields), `lessThan`
- XSD can't cap…
-
There is an inner `id` field? Is that really necessary?
-
While the XSD and JSON schemas (should) define EPCIS content precisely, and the spec and UML makes sure the same content is expressed, there is no formal definition of a transformation between XML and…
-
Hi @RalphTro, @mgh128,
The description for endpoints listed below needs a slight change in `openapi.yaml` and `2021_01_26y EPCIS 2-0 COMMREV` as well.
- GET /eventTypes/{eventType}/events/{event…
-
I tried to get historical data from Brazilian market, but got some anomalies:
```
import yfinance as yf
for i in ["KLBN11", "SANB11", "YDUQ3"]:
ticker = yf.Ticker(f"{i}.SA")
data = ti…
-
As of the latest discussion in the EPCIS/CBV 2.0 group, readPoint/bizLocation ID, when expressed in JSON/JSON-LD, now looks as follows:
"readPoint": {"id": "urn:epc:id:sgln:0614141.07346.1234"},
P…