[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cmis] Namespace proposal and complex properties with lists
On 20 Apr 2009, at 23:18, Julian Reschke wrote:
> Hm,
> this puts property structure into the identifier. Is this really a
> good idea?
> As CMIS doesn't have residual properties, would that mean that all
> of these properties would need to be defined on the document type?
As I mentioned, this is just syntactic extension so that parsers don't
have to be rewritten *if* we later go that route, in extensions or
CMIS 2.
As I said:
> This sidesteps the problem of having these properties actually
> available in object types, so this proposal is purely syntactic and
> for future extensibility, but I think that it makes sense.
I agree that ideally it may be better to have the (currently) fictional:
<properties name="acme:book">
<propertyString name="acme:title">
<value>Brave New World II</value>
</propertyString>
<propertyList name="acme:releases">
<properties>
<propertyDateTime name="acme:date">
<value>2008-04-01T00:00:00.000+02:00</value>
</propertyDateTime>
<propertyString name="acme:format">
<value>Hardcover</value>
</propertyString>
</properties>
<properties>
<propertyDateTime name="acme:date">
<value>2009-04-15T00:00:00.000+02:00</value>
</propertyDateTime>
<propertyString name="acme:format">
<value>Mass Market Paperback</value>
</propertyString>
</properties>
</propertyList>
</properties>
rather than:
<propertyString name="acme:book:title">
<value>Brave New World II</value>
</propertyString>
<propertyDateTime name="acme:book:releases:0:date">
<value>2008-04-01T00:00:00.000+02:00</value>
</propertyDateTime>
<propertyString name="acme:book:releases:0:format">
<value>Hardcover</value>
</propertyString>
<propertyDateTime name="acme:book:releases:1:date">
<value>2009-04-15T00:00:00.000+02:00</value>
</propertyDateTime>
<propertyString name="acme:book:releases:1:format">
<value>Mass Market Paperback</value>
</propertyString>
But the latter is simpler to retrofit in to the current XSD schemas
and protocols.
Florent
--
Florent Guillaume, Head of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]