RE: [Bug 4639] Allow cycle checking on element graphs as well as document graphs

I did not intend to support acyclic=true on types and elements. I am sorry for the confusion if the text I wrote appeared to convey this. That was not the intention. acyclic should appear only on types.

-----Original Message-----
From: public-sml-request@w3.org [mailto:public-sml-request@w3.org] On Behalf Of Smith, Virginia (HP Software)
Sent: Thursday, November 01, 2007 8:52 AM
To: public-sml@w3.org
Subject: RE: [Bug 4639] Allow cycle checking on element graphs as well as document graphs


Kumar,

OK, I think I understand now. You propose that acyclic can be placed on
the SML reference complexType definition -or- on the SML reference
element declaration. If it is on the type that all elements (SM
references) derived from this type are considered as arcs in detecting a
cycle. If it is on the element then only this sml reference element is
considered an arc in detecting a cycle.

Do I have that right?

--
g

-----Original Message-----
From: bugzilla@wiggum.w3.org [mailto:bugzilla@wiggum.w3.org]
Sent: Thursday, November 01, 2007 1:47 AM
To: Smith, Virginia (HP Software)
Subject: [Bug 4639] Allow cycle checking on element graphs as well as
document graphs

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4639





------- Comment #10 from kumarp@microsoft.com  2007-11-01 08:47 -------
If the schema author put acyclic=true on personref then it is his/her
intent to detect cycles in personrefType and any type derived from
personrefType. Thus it is by definition that friend cycle and child are
not distinct.

On the other hand, if the child and person cycles are meant to be
distinct the one would not put acyclic on personref. In that case, one
would put acyclic=true on child and friend separately.

The second example depends on where acyclic=true is defined.

Received on Thursday, 1 November 2007 16:52:13 UTC