-
Key: ODM11-142
-
Legacy Issue Number: 16038
-
Status: closed
-
Source: Adaptive ( Mr. Pete Rivett)
-
Summary:
It’s unclear how derived Association OWLBase::/TripleForGraph is supposed to interact/be merged with underived RDFBase::TripleForGraph. There seems no need for a derived OWLGraph::/triple when OWLGraph inherits triple from RDFGraph. Or is it the intent that OWLGraph::triple
{redefines RDFGraph::triple} in which case that should be stated along with how it would be derived: via OWLGraph::ontology and Ontology::triple? And is it the intent that Triple has both a derived /owlGraph and a (non-derived) graph property? In which case the former should
{subset}the latter and the derivation should be expressed.
-
Reported: ODM 1.0 — Wed, 16 Feb 2011 05:00 GMT
-
Disposition: Resolved — ODM 1.1
-
Disposition Summary:
1. In section 11.2.1 remove “OWLGraph” from the following clause:
Exceptions to this convention include OWLUniverse, OWLGraph, and OWLStatement,
2. In Figure 11.2 remove OWLGraph, and the lines to it. Also remove RDFGraph which has no purpose in this diagram3. Remove section 11.2.1, OWLGraph
4. In section 11.2.2, OWLOntology:
Remove the first association:
owlGraph: OWLGraph [1..*] in association GraphForOntology - links an ontology to one or more graphs containing the triples that define it.
Remove all 4 constraints [1] through [4].5. Remove section 11.2.4 Triple (Augmented Definition)
-
Updated: Fri, 6 Mar 2015 20:58 GMT
ODM11 — derived Association OWLBase::/TripleForGraph
- Key: ODM11-142
- OMG Task Force: Ontology Definition Metamodel (ODM) 1.1 RTF