...
Structuring FCR Metadata is a LDP Container
Currently, non-RDF resources have the descriptive metadata structured using fcr:metadata
fcr:metadata itself is a pseudo-container (in that, one cannot use to perform the operations which one can perform using a true LDP container)
Restructuring this fcr:metadata as a proper container is the request
It should be noted that no individuals volunteered for addressing this issue
There appears to be a lack of documentation regarding the outcome of past discussions involving this issue
No specifications or discussions relating to the scoping of FCR metadata appear to have been drafted or have taken place
It was proposed that this topic be discussed upon the return of A. Woods
Regarding the precise definition of fcr:metadata (rather than the construct of the container)...
A clarification was made in which it was confirmed that a discussion of the FCR metadata (proper) never indeed took place; This was simply understood as an LDP construct
Perhaps this conversation is necessary...several parties seemed to support this
The context in which this is undertaken is typically one in which repository architects or administrators seek to store metadata structured in the XML without transforming it into the RDF
The suspicion was such that individuals are far more interested in simply adding this content as another bitstream
Without a clear sense for a time frame, this shall need to be discussed during the next call.
fc-repo Client and Issues Related to the Linking of fcr:metadata
James R. Griffin III seemed to be interested in undertaking this from the standpoint of becoming familiar with the code base
A. Coburn clarified that this issue seemed to solely afflict the fcrepo-client
Michael Durbin felt that this client was out of parity with the Fedora Commons code base (as well as untested)
A. Coburn confirmed that this was the case (and specified that they did not leverage this from with Apache Camel integration)
M. Durbin also advised that, if any such client is to be supported by other components of Fedora Commons 4.x, it would be best to have it covered within integration testing suites