Remove ApprovedRevs properties (now part of SemanticApprovedRevs)

[mwjames]

Setup and configuration

• SESP: 2.x

Issue

• As noted in Approved Revisions related properties to not update after initial annotation #108 (comment), ApprovedRevs properties should be removed to avoid storage conflicts (DBKey is referencing to the same Approved by, Approved date, Approved revision, and Approval status labels)
• Copy SESP (ApprovedRevs) properties SemanticApprovedRevs#1
• Removal should happen before the 2.1 release

[kghbln]

Removal should happen before the 2.1 release

Since this is breaking we need to do a 3.0.0 release once SAR 1.0.0 was released.

[kghbln]

Once SemanticMediaWiki/SemanticApprovedRevs#3 is done this can be tackled and release with 3.0.0

[kghbln]

@mwjames I am not sure how difficult this is. However ideally I would like to release 3.0.0 in February to get this off both our buttocks sooner than later. I guess the bigger pile of work is to get SAR back on track (SemanticMediaWiki/SemanticApprovedRevs#14)

[alex-mashin]

Is this task still valid? For some reason, the commit f6ad08e does not seem to be a part of any pull request and has not been merged.

[gesinn-it-gea]

I see the following issues with moving ApprovedRevs properties to SAR:

1. SAR does not need the extra properties to do its job. SAR aims to "control the storage of approved revision content", not to provide some semantic annotations about an approval.

2. Other SESP's have dependencies to other extensions to "lift" their meta data to the semantic world like "_SHORTURL" or "_PAGEIMG". With the same reasoning, separate Semantic Properties extensions would also have to be developed for these extensions. This is especially true because it cannot be assumed that extension developers who have nothing to do with SMW maintain / test code in their extension to provide Extra Properties.

3. SAR is experimental, so the operation of this extension by administrators may not be acceptable. At the moment, by using SESP and AR, the approval status of a page can be queried through semantic attributes, even if SAR is not used.

I suggest the following:

• in a first step remove extra special properties from SAR
• stabilize SAR (status = stable)
• leave or repair AR properties in SESP
• if still wanted, ban all SESP "with further dependencies" at a later time