Seems reasonable to add the (optional) ability for inferencers to use the vocabulary and check that it adheres to DC's recommendations. I.e. I cannot think of any cases where inferring <?s,rdf:type,foaf:Agent> given <?s,rdf:type, oslc:Publisher> would be INcorrect. The key is that we're enabling, rather than requiring, inferencing via this change.
Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario From: Steve K Speicher/Raleigh/IBM@IBMUS To: [email protected], Date: 02/13/2013 11:59 AM Subject: [oslc-core] Since dcterms:publisher's range is dcterms:Agent, we should consider making oslc:Publisher a subClassOf Agent Sent by: "Oslc-Core" <[email protected]> Looking at the range of dcterms:publisher [1] and seeing its range of dcterms:Agent. Also seeing that in OSLC we recommend using dcterms:publisher with a value/range of oslc:Publisher [2]. So you can see the problem here, not critical but those that use ontology checkers may get tripped up. My proposal is to update oslc:Publisher to be a rdfs:subClassOf of dcterms:Agent. Updating both the description in [2] and the published vocabulary. [1] - http://dublincore.org/documents/dcmi-terms/#terms-publisher [2] - http://open-services.net/bin/view/Main/OslcCoreSpecification#Resource_Publisher Thanks, Steve Speicher IBM Rational Software OSLC - Lifecycle integration inspired by the web -> http://open-services.net _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
