[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
Re: [xml-dev] RE: When maxOccurs=1 means an unbounded number ofoccurrences is valid
- From: David Carlisle <d.p.carlisle@gmail.com>
- To: "Costello, Roger L." <costello@mitre.org>
- Date: Tue, 21 Nov 2017 13:58:16 +0000
On 21 November 2017 at 13:47, Costello, Roger L. <costello@mitre.org> wrote:
> Hi Folks,
>
>
>
> Here is more context to my post. I am reading the vCard RFC.
> (https://tools.ietf.org/html/rfc6350) The RFC specifies number of
> occurrences this way:
>
>
>
> +-------------+--------------------------------------------------+
>
> | Cardinality | Meaning |
>
> +-------------+--------------------------------------------------+
>
> | 1 | Exactly one instance per vCard MUST be present. |
>
> | *1 | Exactly one instance per vCard MAY be present. |
>
> | 1* | One or more instances per vCard MUST be present. |
>
> | * | One or more instances per vCard MAY be present. |
>
> +-------------+--------------------------------------------------+
>
>
>
> I interpreted that table this way:
>
>
>
> Cardinality = 1 means: minOccurs=1 and maxOccurs=1
>
> Cardinality = *1 means: minOccurs=0 and maxOccurs=1
>
> Cardinality = 1*means: minOccurs=1 and maxOccurs=unbounded
>
> Cardinality = * means: minOccurs=0 and maxOccurs=unbounded
>
>
>
> Do you agree?
No your interpretation is wrong, which is why ypour the initial
wording at the start of this thread was confusing.
the cardinality in the table refers to some abstract notion of card
but maxOccurs counts explicit elements and they are not the same in
this markup.
David
>
>
>
> The RFC says this interesting thing: Elements with the same altid
> (alternative identifier) don’t count toward cardinality.
>
>
>
> /Roger
>
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]