Issue 16505: Properties as Assertions (sacm-rtf)
Source: MITRE (Mr. Samuel Redwine, samredwine(at)verizon.net)
Nature: Revision
Severity: Significant
Summary: The property elements of various kinds contain assertions concerning proper values for various properties (or attributes). Should they not therefore inherit from Assertion? This includes tagged values unless these are used to tag kinds of “annotations” instead of using general Annotation elements.
Resolution: 
Revised Text: 
Actions taken:
August 25, 2011: received issue
Discussion: 
Although every property can be considered to be asserted, SACM focus is on argument
structuring elements. Therefore no change made to inherit properties from assertion. Property
class was removed, which did not bring much to the table. May consider reintroducing it. This is a
unification between ARM and SAEM that cannot be achieved at this stage - Defer to RTF
Disposition: Deferred
End of Annotations:=====

m: webmaster@omg.org
Date: 25 Aug 2011 13:06:55 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          Samuel T. Redwine, Jr.   
Company:       Sam Redwine Consulting
mailFrom:      samredwine@ieee.org
Notification:  Yes
Specification: Argumentation Metamodel (ARM) 
Section:       June Day 2 Diagram
FormalNumber:  ptc/2010-08-36
Version:       FTF - Beta 1
RevisionDate:  August 2010
Page:          All
Title:         Properties as Assertions
Nature:        Revision
Severity:      Significant
test:          3qw8
B1:            Report Issue


Description:

The property elements of various kinds contain assertions concerning proper values for various properties (or attributes). Should they not therefore inherit from Assertion? This includes tagged values unless these are used to tag kinds of .annotations. instead of using general Annotation elements.