-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tempo:validFrom, tempo:validTill or FIBO props? #4
Comments
Alas, neither as DatatypeProperty nor AnnotationProperty. |
I'm a bit doubtful about the usefulness of the MIC "date" fields.
So I learned the difficult way that these dates have nothing to do with the real-world exchange, they are only related to the MIC record (when the MIC keeper got the information or added the entry) You correctly:
So I guess my question is to @ElisaKendall: is this modeled correctly? |
FIBO distinguishes between the real-world exchange |
In ISO10383.tarql you use:
I looked at http://purl.org/tempo and it's a good ontology.
However, I'm pretty sure that FIBO has its own props to express the temporal validity of an identifier.
Right @ElisaKendall?
The text was updated successfully, but these errors were encountered: