Motivation and proposal for oslc:archive property

Motivation:

In typical lifecycle management tools, resources are
rarely deleted.  They instead are marked with such a state as not
longer being "active" or "available", some refer to
this state as being "archived".  By having a uniform way
to express whether a resource is in this state or not, allows for a consistent
way to build queries and solutions that federate information from various
tools.

Proposal:

The term for being archived would be

        http://open-services.net/ns/core#archived

and it would take a boolean value. If this property is absent then the
resource is not archived.

This has a semantically different meaning than existing
oslc:hidden [1], which indicates a hint as to whether the resource or property
should be included in a UI.  oslc:archived would be used to express
the state of a resource, an application may or may not decide to hide these
in the UI.

Timeframe:

I suggest this be included in Core 3 common vocabulary.

[1]: http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA#oslc_ResourceShape_Resource

Thanks,

Steve Speicher

IBM Rational Software

OSLC - Lifecycle integration inspired by the web -> http://open-services.net