Base ontology: Suggest adding new class 'Material' , 'MaterialType' and 'SamplingType'.

[krisnadhi]

From #52 @sparkji:

Suggest adding new class 'Material' , 'MaterialType' and 'SamplingType'.

[krisnadhi]

Comment from @sparkji in #52

Makes sense to me. So a MaterialType would be eg. "Mineral".. and instances of Material would be Acanthite, Almandine, Anhydrite, ..

[krisnadhi]

My comment in #52:

Are they controlled vocabulary terms? Which one uses controlled vocabulary terms: MaterialType or Material or both? If Acanthite, Almandine, etc. are controlled vocabulary terms, aren't they actually material types and not materials?

Any comment @robertarko ?

[krisnadhi]

Comment from @sparkji in #52:

MaterialType would be controlled, SESAR uses ODM2 medium vocabulary (http://vocabulary.odm2.org/medium/), like Rock and Mineral. Material would also be controlled, like Acanthite and Almandine are instances of mineral (MaterialType). For mineral type, SESAR would like to use IMA minerals list (http://www.ima-mineralogy.org/Minlist.htm). For rock type, SESAR has its own suggested terms(http://www.geosamples.org/help/vocabularies/rock). Does make sense?

[krisnadhi]

My comment in #52:

Then, I would model MaterialType and not Material. All those vocabulary terms like Rock, Mineral, Acanthite and Almandine are instances of MaterialTypes. If you insist on adding Material class, I would then add Rock, Mineral, Acanthite and Almandine as subclasses of Material, but not instances.

[krisnadhi]

Comment from @sparkji in #52:

SESAR uses the format list below to store material related information, there is a little bit confusion. In my view, Acanthite is a instance of Mineral, Igneous>Plutonic>Exotic is a subtype of Rock. But you also could say Acanthite is a subtype of Mineral.

So, if we just create MaterialType class, could we also create 'hasMaterialSubType' property for PhysicalSample? Then, we could populate material related information of SESAR with 'hasMaterialType' and 'hasMaterialSubType' properties.

Any Comments?

sampleId top_level_classification classification xxxxxxx Mineral Acanthite xxxxxxx Mineral Almandine

xxxxxxx Rock Igneous>Plutonic>Exotic xxxxxxx Rock Metamorphic>Meta-Ultramafic

[krisnadhi]

My comment in #52:

SESAR uses the format list below to store material related information, there is a little bit confusion. In my view, Acanthite is a instance of Mineral, Igneous>Plutonic>Exotic is a subtype of Rock. But you also could say Acanthite is a subtype of Mineral.

I think the latter is more appropriate. If you say that Acanthine is an instance of Mineral, then you would essentially say that there is only one Acanthine in the world, although in reality, I would imagine there will be definitely more than one.

So, if we just create MaterialType class, could we also create 'hasMaterialSubType' property for PhysicalSample? Then, we could populate material related information of SESAR with 'hasMaterialType' and 'hasMaterialSubType' properties.

Do you want to capture the hierarchy of material types in the ontology? If yes, then we should do it using classes instead of properties, like what we do with NERC vocabulary terms.

[krisnadhi]

Comment from @sparkji in #52:

It's good. So, we still have 'hasMaterialType' property, just create voc for materialType with class and subClass, then create triple like below, is it right?

http://geolink.geosamples.org/id/sample/MGD0007VE hasMaterialType < http://schema.geolink.org/dev/voc/materialType/#32223>

[krisnadhi]

My comment in #52:

It would be something like that. For NERC vocabularies, I was able to create OWL files containing URIs minted, sort of automatically, from the NERC vocabulary server. I have no source for minting URIs for material types though. Do you have anything as such?

[krisnadhi]

Comment from @sparkji in #52:

IMA publishes mineral list each two month with PDF file, most minerals has unique IMA NO. like '2014-084', As a partnership with the IMA, RRUF http://rruff.info/ima/# also maintained the copy of IMA mineral list, CSV or EXCEL file could be downloaded. SESAR maintained a controlled vocabulary for Rock types.

Maybe I could create owl file for material type vocabulary, I will talk about it with Bob, let's see what will happen?

[krisnadhi]

My comment in #52:

That would be a good start. You could look at how L06.owl file was implemented as an example.

[krisnadhi]

Comment from @sparkji in #52:

I talked with Bob in this morning, he agreed with you, I will create owl file for MaterialType vocabulary and maintain it. And suggest to create a new class 'MaterialType', it works like 'PlatformType' or 'FeatureType'. Also please remove the property 'hasMaterial' from main.owl, we don't need it any more.

[krisnadhi]

Moved to #67