Closed der-bruemmer closed 5 years ago
Hi @der-bruemmer - as the maintainer of the PoC mapping of Datex2 I’m eager to help out to find a future-proof solution for this mapping!
hey @pietercolpaert, that's great. I'm aware datex2 is a standard we have to consider in our work on mobivoc. However, I'm not sure this repository is the right place to work on the mapping. Shouldn't it have its own repository and release cycle?
What I would see relevant in the mobivoc repository is a mapping that maps datex2 to semantically equivalent mobivoc constructs or otherwise clarifies the relationship between the standards.
This could happen via owl:equivalentClass properties or other constructs that describe semantic similarity between constructs. This could also happen with a mapping specification describing how to transform mobility data described in datex2 to mobivoc representations or vice-versa.
It does have its own repository. No idea why it just got copied in here :-)
See: https://github.com/OpenTransport/linked-datex2
Would be happy to add owl:equivalentClass
or even deprecate vocab.datex.org URIs in favour of URIs of mobivoc, if this one is going to be better maintained. Also the Transport Disruption Ontology has some equivalent classes (already added).
I’m going to present the vocab.datex.org initiative at the datex2 user group in The Netherlands next year. Hope these URIs are just going to be published by CEN themselves after that :-)
@np00 as discussed today, we should just re-use the linked-datex2 uris.
@pietercolpaert next year is now - do you know when? :-)
I’m presenting the Linked Datex II ontology at the Datex 2 summit in Utrecht. I hope that they are willing to maintain this vocabulary. If not, I will deprecate it in favour of mobivoc!
Hi @pietercolpaert,
as part of the Limbo Project [1], we want to transform Road Construction Site data from XML (Datex 2) to RDF which is published via the German Government Portal Mobility Data Marketplace [2]. So that is why I came across your work which seems very valuable for our task at hand.
Currently, I am in the process of evaluating whether I can use your ontology as a basis or whether I need to change too many things in the structure. And also I have to see how it can be integrated into MobiVoc. I will let you know once I have a first version and I am happy to push it to your repository.
[1] https://www.limbo-project.org/ [2] http://www.mdm-portal.de/en/
Thanks @np00! Looks interesting!
Datex2 road construction sites are now part of develop branch: https://github.com/vocol/mobivoc/commit/567dc138e2df58dffd02c7345b4246a4a8dd8a8b
They will be properly documented (ReadMe, schema.mobivoc.org) in the next release.
If you want to dct:conformsTo datex2.eu
you should at least use their base URIs, no? Does it make sense to use http://vocab.datex.org/terms#?
If for some reason http://vocab.datex.org/terms does not address your use cases, we should ask the CEN group a formal question to make sure it is addressed
Hi @pietercolpaert, I forgot to mention that I also added links to your vocabulary via owl:equivalentClass or owl:equivalentProperty.
I wanted to keep a reference to both: to your vocabulary hosted on your domain datex.org
but also to the "official" datex homepage datex.eu
. Or did I miss something, is datex.org part of the official datex2 community? :)
Example:
mv:SituationRecord owl:equivalentClass datex:SituationRecord;
dct:conformsTo "https://datex2.eu/" ;
.
Example class description: https://github.com/vocol/mobivoc/blob/develop/schema/RoadConstruction.ttl#L32
Aha, right! I didn’t find it in the pull request but this does indeed make me happy!
Hi @np00, as of this commit you added a datex2 RDF version to this repository. I can not see any direct usage of mobivoc in this version and thus I'm not clear what its significance in regard to Mobivoc is.
We should clarify this with some discussion and optimally add some additional mapping. As long as this datex2 vocabulary only describes datex2 in RDF and does not relate to mobivoc, I don't think we should maintain it in this repository.
For now, I removed it from the develop branch and created https://github.com/vocol/mobivoc/tree/feature/datex2mapping where we can sole this issue and develop the relationship between both vocabularies.
In general, please refrain from pushing directly for develop. Please create feature branches for new features and handled the merge with develop using pull requests. This guarantees we have an orderly, agreed-upon process for extension of the vocabulary.