If lso:Condition is same as service:ServiceLimitation one might better drop this additional class. A condition, however may differ from a limitation. Are normal price specifications or periods included in service:ServiceLimitation? One might alernatively connect gr:hasPriceSpecification directly to the lso:LibraryService, making the latter a a gr:Offer and schema:Offer too.
Separation of Service and Product is not obligated by the Service ontolgy but (possibly?) by Schema.org vocabular. See dini-ag-kim/service-ontology#2 about how to relate Service and Offer in the Service Ontology.
If
lso:Conditionis same as service:ServiceLimitation one might better drop this additional class. A condition, however may differ from a limitation. Are normal price specifications or periods included in service:ServiceLimitation? One might alernatively connect gr:hasPriceSpecification directly to thelso:LibraryService, making the latter a a gr:Offer and schema:Offer too.Separation of Service and Product is not obligated by the Service ontolgy but (possibly?) by Schema.org vocabular. See dini-ag-kim/service-ontology#2 about how to relate Service and Offer in the Service Ontology.