[OASIS Issue Tracker] (OSLCCORE-24) Is there a reason OSLC domain vocabulary properties are not owl object properties?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60347#comment-60347 ] 

Nick Crossley commented on OSLCCORE-24:
---------------------------------------

There was a deliberate decision made back in the OSLC 2.0 days to minimize the use of OWL, and to stick to rdf and rdfs where possible. One reason was to avoid any of the OWL constructs that used, implied, or required inferencing; inferencing was considered too confusing, and potentially too slow. I believe the class owl:Ontology was used for the vocabulary resource itself simply because rdf/rdfs had no real equivalent.

Having said that, I see no reason not to add additional properties to the ontology resource itself, and to the vocabulary terms, provided those extra properties are not ones that imply any inferencing.

> Is there a reason OSLC domain vocabulary properties are not owl object properties?
> ----------------------------------------------------------------------------------
>
>                 Key: OSLCCORE-24
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-24
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> I ask because the OSLC Core 3.0 common vocabulary Turtle files can be loaded into Protege 5, but the properties do not show up because they are RDFS properties not OWL. Is there a reason OSLC uses declares the vocabularies are OWL ontologies but doesn't use OWL in the conventional way? Could this be changed without impacting existing implementations by simply adding the rdf:type?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)