Re: [xml-dev] RE: XML-vocabulary-specific programming idioms

[Stephen D Green <stephengreenubl@gmail.com>]

"Bottom-up" constraint evaluation?
http://en.wikipedia.org/wiki/Constraint_logic_programming#Bottom-up_evaluation

----
Stephen D Green



On 27 April 2011 14:28, Costello, Roger L. <costello@mitre.org> wrote:
> I need a verb for this programming idiom.  (Examples of other programming idioms -- map, filter, fold -- and they are all verbs)
>
> Here are some ideas:
>
>     inherit
>
>    inherit restrictions
>
>    cascade
>
>    cascade restrictions
>
>    accumulate
>
>    accumulate restrictions
>
> Which do you like?
>
> /Roger
>
>
> -----Original Message-----
> From: David Lee [mailto:dlee@calldei.com]
> Sent: Wednesday, April 27, 2011 9:22 AM
> To: Costello, Roger L.; xml-dev@lists.xml.org
> Subject: RE: [xml-dev] RE: XML-vocabulary-specific programming idioms
>
> You can always put new names on anything.
> I don't consider restrictions different from capabilities, they are both
> attributes, and differ only in how a runtime engine would evaluate them.
> Not in how they are collected.
> But it would depend at what level of abstraction you want to focus.
>
>
> ----------------------------------------
> David A. Lee
> dlee@calldei.com
> http://www.xmlsh.org
>
>
> -----Original Message-----
> From: Costello, Roger L. [mailto:costello@mitre.org]
> Sent: Wednesday, April 27, 2011 9:03 AM
> To: xml-dev@lists.xml.org
> Subject: RE: [xml-dev] RE: XML-vocabulary-specific programming idioms
>
>
>> Inheritance
>
> You may be right David. Inheritance may be the word and the concept that
> represents this programming idiom. It seems a tad different, however. Isn't
> inheritance about accumulating/cascading capabilities? Whereas the activity
> that I have been discussing is about accumulating/cascading restrictions.
> Does that difference warrant a new name?
>
> /Roger
>
> -----Original Message-----
> From: David Lee [mailto:dlee@calldei.com]
> Sent: Wednesday, April 27, 2011 8:52 AM
> To: Costello, Roger L.; xml-dev@lists.xml.org
> Subject: RE: [xml-dev] RE: XML-vocabulary-specific programming idioms
>
> "Inheritance" ?
>
>
> ----------------------------------------
> David A. Lee
> dlee@calldei.com
> http://www.xmlsh.org
>
> -----Original Message-----
> From: Costello, Roger L. [mailto:costello@mitre.org]
> Sent: Wednesday, April 27, 2011 8:44 AM
> To: xml-dev@lists.xml.org
> Subject: [xml-dev] RE: XML-vocabulary-specific programming idioms
>
>
> Hi Folks,
>
>>     I have a simpleType and I need to know
>>     all the constraints on it.
>
> A colleague pointed out that CSS has an analogous activity:
>
>    The styles that are to be applied to an element depend
>    not only on the element's CSS rule but also on the element's
>    parent's CSS rule and its parent's CSS rule, and so forth.
>
> So, this programming idiom seems to be more universal than I thought.
>
> Can you think of other examples where we accumulate restrictions based on
> parent, grandparent, great-grandparent, etc. restrictions?
>
> My colleague suggested a name for this programming idiom:
>
>    Cascading Data Component Restrictions
>
> What do you think?
>
> /Roger
>
> -----Original Message-----
> From: Costello, Roger L.
> Sent: Wednesday, April 27, 2011 6:11 AM
> To: xml-dev@lists.xml.org
> Subject: XML-vocabulary-specific programming idioms
>
> Hi Folks,
>
> There are programming idioms that are common across many applications, such
> as: map, fold, filter.
>
> There are application-specific programming idioms.
>
> Finally, there are XML-language-specific programming idioms. For example,
> there are common activities that are performed on XML Schemas (see below for
> an example), common programming activities that are performed on SVG
> documents, common programming activities that are performed on XBRL
> documents, and so forth. Has anyone put together a list of programming
> idioms for the various XML vocabularies?
>
> /Roger
>
> One activity that I frequently perform when processing XML Schemas is this:
>
>     I have a simpleType and I need to know
>     all the constraints on it.
>
> Example: consider this simpleType:
>
>    <xsd:simpleType name="BostonAreaSurfaceElevation">
>        <xsd:restriction base="elev:EarthSurfaceElevation">
>            <xsd:minInclusive value="0"/>
>            <xsd:maxInclusive value="120"/>
>        </xsd:restriction>
>    </xsd:simpleType>
>
> What are all the constraints on it? Well, it identifies a base type,
> elev:EarthSurfaceElevation. That base type may contain some constraints that
> must be considered. Further, that base type may have a base type, which has
> a base type, etc. That entire dependency tree must be considered.
>
> Determining all the constraints on a simpleType is an important programming
> idiom (at least, it is for my applications).
>
> What would you name this programming idiom? I have been naming it
> "simpleType accumulated restrictions" but wonder if there is a better name?
>
> Even better, is there a functional programming language (e.g., Haskell)
> function that does this kind of activity, or an analogous activity?
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>