RS Issues: Filter Query issues

[Len Gallagher <LGallagher@nist.gov>]

ebXML Regrep,

Last week I sent around a proposal on behalf of myself and Nikola
Stojanovic to address some name changes and other improvements in the
Filter Query section of the Registry Services (RS) specification. Those
changes were adopted by the Regrep teleconference meeting on Friday, April 6.

However, the proposal also listed a few issues with no solution. The
purpose of this email is to ensure that those issues do not get lost. We
propose that they be included in the Regrep Issues list:


FQ Issue #1: Terminology for Packages in associationType 
          (RIM Section 10.1.1, line 631, page 28)

RS line 1182 
Change "HasMember" to whatever term is used in RIM to indicate the 
AssociationType that identifies a package as containing a member. That term 
currently is "Packages", but we think a better term is needed.

RS line 1397 
In the RIM Binding figure, put "HasMember" in italics. Also see comments 
attached to line 1182 above.

RS line 1739 
Change "HasMember" to whatever term is used in RIM to indicate the 
AssociationType that identifies a package as containing a member. That term 
currently is "Packages", but we think a better term is needed.

RS line 1748 
Change "HasMember" to whatever term is used in RIM to indicate the 
AssociationType that identifies a package as containing a member. That term 
currently is "Packages", but we think a better term is needed.



FQ Issue #2: Branch terminology for AuditableEventQuery

RS line 1212 
For consistency, consider changing "UserFilter" to "InvokedByUserBranch" 
in an AudtableEventQuery (Section 8.2.3 page 42) and then define a new
element "InvokedByUserBranch" as follows:

 <!ELEMENT InvokedByUserBranch 
   ( UserFilter?, 
     OrganizationQuery? )>

This modification would also require re-writing of Semantic Rules 1c and 
1d, so it is proposed for further consideration only. It would also require 
labeling the link between AuditableEvent and User in the figure to "InvokedBy".



FQ Issue #3: WithdrawnObject as part of GetRepositoryItemResult

RS lines 1784 and 1799 
Discuss the usefulness of the "WithdrawnObject" Element in a
GetRepositoryItemResult (Section 8.2.8, page 58). Nikola and Len 
have differing opinions. No changes proposed yet.



FQ Issue #4: Packaging of returned objects

RS lines 1795-1797 
Consider re-structuring of the ExtrinsicObject element in a
GetRepositoryItemResult (Section 8.2.8, page 58) to take advantage of
encodings specified in Message Services specification and in MIME type
representations. No changes proposed yet!



Here is one other result from the telephone conference regarding last weeks
proposal re: camelCase in examples and XML attribute names:

-----------------------------------------
1178 
Use capital "O" on "objectType" to be consistent with other examples. 
Alternatively, could use camelCase in all examples.

1373-1375 
Decide if attributes in examples begin with uppercase or lowercase.

2073-2098 
Raise a discussion item as to the use of camelCase for "leftargument", 
"connectivepredicate", "booleanpredicate", "logicalpredicate", and 
"stringpredicate".

Note: We agreed to implement the camelCase solution consistently in all of
the examples in Section 8.2 and in the syntax for Clause in Section 8.2.10
(line 2037, pages 66-70).

-----------------------------------------



**************************************************************
Len Gallagher                             LGallagher@nist.gov
NIST                                      Work: 301-975-3251
Bldg 820  Room 562                        Home: 301-424-1928
Gaithersburg, MD 20899-8970 USA           Fax: 301-948-6213
**************************************************************