"Bruce D'Arcus" <[email protected]> writes:
> So as a first comment (will look at details later, though I have
> confidence it's well thought-out given the background work you've
> done, Frank; thanks for that), let me explain why the syntax is the
> way it is. E.g. it wasn't an accident.
>
> Given that CSL is an XML language, I really wanted to keep the
> language as clean to process as possible using the most pure XML
> processing language extant: XSLT.
>
> So the idea was any significant CSL logic was represented in terms of
> native XML structures: nodes (elements and attributes) and values.
>
> Going this route, where the values themselves take on core logical
> semantics, and where those values themselves must be processed (though
> admittedly, the processing is simple here; just split on a colon and
> treat as key-value), is a change in direction.
This is quite a strong argument, indeed. I wonder if we could increase
the conditional expressiveness by just permitting boolean connectors
(and, or, xor, plus the prefix not:) inside attributes.
Something like:
<if type-all="article-journal" variable-all="volume issue"
is-numeric-any="not:volume not:issue" match="all">
could be expressed:
<if type="article-journal" variable="volume and issue"
is-numeric="not:volume or not:issue" match="all">
(possibly 'or' could be the default).
Just a thought.
--
andrea
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
