[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [regrep] Issues for this week and beyond
-------- Original Message --------
Subject: [regrep] Issues for this week and beyond
From: Farrukh Najmi <farrukh@wellfleetsoftware.com>
Date: Mon, July 05, 2010 5:56 pm
To: ebXML Regrep <regrep@lists.oasis-open.org>
Dear colleagues,
With WD6, we have now a considerably mature spec set for RegRep 4. I would like us to get aligned and focused on getting RegRep 4 finalized and submitted for OASIS approval this fall. To that end we need to start having regular issue driven meetings. We need to send issue lists out in advance, consider each issue in advance and discuss issues in meetings to a resolution.
To that end, here is a list of issues I would like to propose we start discussing this week and in the next several meetings:
Please feel free to suggest changes to this list.
- Issue-167: Add recursiveDelete option to RemoveObjectsRequest
- Agree
- Issue-166: Add stored query GarbageCollectorQuery
- Agree
- Issue-165: Should Cataloged objects be members of the same RegistryPackages as their source object
- Potential issue for garbage removal?
- Issue-164: Should cataloged objects automatically be assigned the same accesControlPOlicy as their source object?
- Agree
- Issue-160: The prefix in canonical functions should be bound to a namespace and be allowed to vary
- Agree
- Issue-151: FindAllMyObjects canonical query should have an objectType parameter
- Agree
- Issue-150: Does a Subscription.DeliveryInfo need to provide Locale information and specifically TZ information
- Agree
- Issue-131: Remove ExternalIdentifier from ebRIM
- Agree
- Issue-130: Remove ClassificationType from ebRIM
- Needs clarification. Classification functionality is obviously a base need for registry.
- Issue-117: Explore whether QueryExpressionType hierarchy makes sense
- Issue-109: Need a generic way for queries to specify flexible ClassificationNode matching semantics
- Issue-89: Is current StatusType scheme and RegistryObjectType.status too overloaded
- Issue-75: BasicQuery need to support some way to search by slot name/value
- Issue-73: Need to enforce reference checking on submit and update by default with a per request & per object override
- Issue-66: How to control access to who can change status of a RegistryObject
- Issue-21: Attribute definition and validation on a per-objecttype basis using Slots
- Issue-15: Federations - allow federations to be members of other federations
- Issue-12: Make PersonName attributes more culturally neutral
- middleName is repeatable I assume. Maybe title is desired as well?
Please try and make every effort to attend this weeks meeting with considered opinions on the issues above. Thank you.
-- Regards, Farrukh Web: http://www.wellfleetsoftware.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]