Closed krisnadhi closed 9 years ago
Related to #55
Comment from me in #52:
Do we want to collect this gazetteer instance into a class in the ontology? If yes, we change the property into ObjectProperty. Otherwise, we simply keep the property as a DataProperty with xsd:anyURI as range.
@robertarko @fils @sparkji
Should we create a class called StratigraphicUnit
to capture stratigraphic gazetteer names?
Or should we simply say that hasStratigraphicUnit
can point to any URIs?
Yes, we should create stratigraphicUnit class to capture stratigraphic gazetteer names.
On Thu, Sep 10, 2015 at 6:30 PM, krisnadhi notifications@github.com wrote:
@robertarko https://github.com/robertarko @fils https://github.com/fils @sparkji https://github.com/sparkji Should we create a class called StratigraphicUnit to capture stratigraphic gazetteer names? Or should we simply say that hasStratigraphicUnit can point to any URIs?
— Reply to this email directly or view it on GitHub https://github.com/ec-geolink/design/issues/57#issuecomment-139400772.
Are the stratigraphic gazetteer names available as URIs anywhere? Or are they simply string values?
They should be available as both URIs and string value. On Sep 11, 2015 8:59 AM, "krisnadhi" notifications@github.com wrote:
Are the stratigraphic gazetteer names available as URIs anywhere? Or are they simply string values?
— Reply to this email directly or view it on GitHub https://github.com/ec-geolink/design/issues/57#issuecomment-139539499.
But having a class StratigraphicUnit implies that all the names have to be available as URIs and string values should not be used (except only as a label), i.e., you cannot have a triple like
:sample1 :hasStratigraphicUnit "Portland Formation"
Ok. Let's create class StratigraphicUnit, and just use URIs for property hasStratigraphicUnit.
On Fri, Sep 11, 2015 at 12:53 PM, krisnadhi notifications@github.com wrote:
But having a class StratigraphicUnit implies that all the names have to be available as URIs and string values should not be used (except only as a label), i.e., you cannot have a triple like :sample1 :hasStratigraphicUnit "Portland Formation"
— Reply to this email directly or view it on GitHub https://github.com/ec-geolink/design/issues/57#issuecomment-139597714.
Okay. We got an agreement :+1: In any case, we could still add string information through the labels of the instances.
StratigraphicUnit is now added to the base ontology.
Moved from #52
@robertarko suggests the range of PhysicalSample.hasStratigraphicUnit is a gazetteer of named instances (eg. from the USGS National Geologic Map Database):
Bonneville Formation Portland Formation Gray Gulch Formation etc.
Doug - comments ?