Hi,
True MVPs could handle the first example easily - it was too simple. As
soon as you start nesting properties it becomes very messy to express
using MVPs e.g.
<D:prop>
<X:contributors>
<X:contributor>
<X:name>Angela Schreiber<x:name>
<X:details>
<X:phone>xxx</X:phone>
<X:email>yyy</X:email>
<X:address>zzz</X:address>
</X:details>
</X:contributor>
<X:contributor>
<X:name>Julian Reschke<x:name>
<X:details>
<X:email>www</X:email>
</X:details>
</X:contributor>
</X:contributors>
</D:prop>
Cheers,
Justin.
Julian Reschke wrote:
Justin Lipton wrote:
I like Julian's example of <xhtml:em>important</xhtml:em> which is an
illustration of mixed content XML but it is also convenient where you
have a
straight multivalued property e.g.
<D:prop><X:contributors><X:contributor>Angela
Schreiber</X:contributor><X:contributor>Julian
Reschke</X:contributor></X:contributors></D:prop>
There are obviously other ways of achieving this CSV, different property
names (X:contributor1, X:contributor2) etc but XML is probably the least
nasty.
Cheers,
Justin.
Well, that's a simple one, as JCR *does* support multivalued properties.
See <http://greenbytes.de/tech/webdav/rfc4316.html> for how to specify
types upon PROPPATCH, and
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-property-datatypes-07.html#rfc.section.A>
for a format for multivalued properties that is already supported by
at least two servers (SAP KM, Xythos) and one client (SAP KM).
BR, Julian
!DSPAM:47bd513d105259164112916!
