Regrep WikiSee most current summary of changes instead of this page.
THIS PAGE IS OUTDATED STUFF FOR HISTORICAL VALUE ONLY
This page contains the working plan for regrep 4.0 specifications:
Here is a list of other important regrep4 related pages:
Content Management Services Improvements (Cataloging, Validation, ...)
Register functionality to manage collections of information in distributed registry settings
Below is a set of proposed work items for RegRep 4. Note that the details in the wiki pages above are more recent than work items below and the two have not been harmonized yet.
|
Proposed Content for RegRep 4.0 |
||||
ID |
Title (Feature / Change Request) |
Description |
Priority |
Justification |
Resolution |
farrukh-1 |
Fix relational schema binding to be a machine generated mapping from XSD |
Currently the SQL Schema is manully mapped from rim.xsd resulting in inconsistencies |
P1 |
Reduce bugs. Support TypeExtensibility feature |
|
farrukh-2 |
Fix inheritance mapping in relational schema |
Fix relational schema to use <http://www.hibernate.org/hib_docs/ejb3-api/javax/persistence/InheritanceType.html#JOINED> instead of <http://www.hibernate.org/hib_docs/ejb3-api/javax/persistence/InheritanceType.html#TABLE_PER_CLASS> |
P1 |
Current mapping of inheritence intruduces Identifiable and RegistryObject views which do a UNION across 20 or so table and are very inefficent for queries like "SELECT * FROM RegistryObject" |
|
farrukh-3 |
Add support for EJB-QL Query Syntax |
|
P2 |
EJB-QL query syntax makes it easier to specify complex queries due to its more OO capabilities: <http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/EJBQL.html> |
|
farrukh-4 |
Extensible Slots |
Allow Slots to have extension sub-elements |
P1 |
Simple name value is often not enough |
|
unknown-1 |
See http://wiki.oasis-open.org/regrep/documents/proposals/typeExtensibility |
P1 |
See: http://wiki.oasis-open.org/regrep/documents/proposals/typeExtensibility |
|
|
farrukh-5 |
Replace decrecate/undeprecate/approve with a new setStatus protocol |
The new protocol would support any statusType and not be hardwired. Alternatively, this may be handled by supporting partial object updates. |
P1 |
Remove Hardwired protocols with a single extensible one |
|
farrukh-6 |
Align with latest versions of our spec dependencies |
WSDL 2.0, SOAP12-MTOM, XACML 2.0, WSS 1.1 |
P1 |
Must keep pace with standards |
|
farrukh-7 |
Align with new standards |
WS-Addressing (for endpoint references etc.), WS-Notification (for subscription/notification) What Others? |
P1 |
Must leverage relevant standards that improve ours |
|
farrukh-8 |
Define a pluggable repository |
Allow our "Reg" part to work with 3rd party "Rep" parts. Examples include DAV , SVN, CVS, Custom |
P1 |
Address needs of customers that have one or more existing repositories |
|
farrukh-9 |
Add full text indexing and search |
We do structured searches well, google does keyword searches well. We need to add support for plain text indexing and keyword search in a pluggable manner |
P1 |
This requirement has been heard from numerous deployments |
|
farrukh-10 |
Define an ATOM binding |
ATOM binding allows a RegRep to be a content feed and deliver focused content to interested parties. Has similarities with but different from Notification feature. |
P3 |
Improves a RegRep's value by allowing it to deliver content |
|
farrukh-11 |
Improve Versioning feature |
Simplify versioning feature. Allow pluggable Versioning plugins. |
|
Needed to handle specialized versioning needs |
|
farrukh-12 |
Allow partial update of a RegistryObject |
|
|
Needed for efficiency |
|
farrukh-13 |
Fix AuditableEvent so multiple actions can be part of same event |
Currently an AuditableEvent allows only one action. If a request does an update as well as insert it results in separate auditable events. The fix is to modify rim.xsd so an AuditableEvent has 1 or more Actions where an Action may have 1 or more affectedObjects. |
|
|
|
david-1 |
Add REST binding |
Current HTTP interface is not consistent with REST principals. Need to support RESTful interface to registry. |
P1 |
|
|
farrukh-14 |
Add support for Checkout / Checkin / Lock / Merge |
These features are lacking at present and are a competitive issue. |
P2 |
|
|
farrukh-15 |
Slot declaration and enforcement on a per-object type basis |
Allow definition of expected slots, their datatypes, their cardinality, their optionality etc. to be defined on a per-ObjectType basis. Require registry to enforce that slots on objects conform to the definition for that ObjectType. |
P2 |
|
|
nikola-1 |
String Limits |
Allow for more flexible definitions of various strings regarding their sizes, e.g., Slot Value (Sequence of LongName - 256 chars) |
|
|
|
nikola-2 |
Common RIM classes |
Align classes like TelephoneNumber with other standards, e.g., Core Components. |
|
|
|
farrukh-16 |
Multi parent for ClassificationNode |
A ClassificationNode can only have one parent in 3.0. This limitation should be addressed in 4.0 |
P2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|