Subscribe to the XML-Dev Blog in XML format
RSS 2.0
Atom 0.3

The XML-DEV Blog

The XML-DEV email discussion forum was started nearly 10 years ago by Dr. Peter Murray-Rust and Dr. Henry Rzepa of Imperial College (UK), covering XML development topics including XML standards, XML specifications, and technical questions related to the eXtensible Markup Language. The XML-DEV Blog brings the XML-DEV community into the blogging era, enabling XML developers to easily follow the hottest threads in the blogosphere.


Re: Enumerating a set of values using the pattern facetversus

Posted 11/10/2017 8:36:22 AM

On 9 November 2017 at 02:01, Eliot Kimber <ekimber@contrext.com> wrote:In addition, the enumeration markup allows binding of annotations to each item, whereas the pattern can only take a single annotation for the entire pattern. I hadn& . . . Read full entry »


Enumerating a set of values using the pattern facet versus theenumeratio

Posted 11/8/2017 6:18:43 PM

Hi Folks,   Below are two XML Schema element declarations. Both enumerate a set of values for the <type> element. The first uses the pattern facet to enumerate the set of values. The second uses the enumeration facet. Is there a reason to prefer one over the other? Or, are they iden . . . Read full entry »


Re: Enumerating a set of values using the pattern facetversus

Posted 11/8/2017 2:28:05 PM

I would not expect grammar-driven editors to be able to use the pattern to guide authoring but to always be able to use the enumeration. Cheers, E. --Eliot Kimberhttp://contrext.com   From: "Costello, Roger L." <costello@&# . . . Read full entry »


RE: XPath expression which checks that all commas areescaped

Posted 11/3/2017 9:10:40 PM

Michael Kay wrote: > I suspect that there must only be one > backslash before the comma: if there > are two ("\\,") then the comma is not > escaped because the "\\" represents > a real backslash. Wow! I had not thought about that. > not(matches(replace(., . . . Read full entry »


Re: XPath expression which checks that all commas are escaped

Posted 11/3/2017 9:02:41 PM

> On 3 Nov 2017, at 19:22, Dimitre Novatchev <dnovatchev@gmail.com> wrote: > >> not(contains(replace(., '\\,', ''), ',')) > > And, of course: > > not(matches(., '[^\\],')) > I don't think that detects an unescaped co . . . Read full entry »


XPath expression which checks that all commas are escaped

Posted 11/3/2017 6:40:53 PM

Hi Folks, Do you deal with Request for Comments (RFCs)? Then the following might come in handy someday. Note: Thanks to Martin Honnen for helping me with the XPath expression (below). Some RFCs (e.g., vCard) have this rule:             &nb . . . Read full entry »


Re: XPath expression which checks that all commas are escaped

Posted 11/3/2017 12:22:50 PM

> not(contains(replace(., '\\,', ''), ',')) And, of course: not(matches(., '[^\\],')) Cheers, Dimitre On Fri, Nov 3, 2017 at 12:14 PM, Dimitre Novatchev <dnovatchev@gmail.com> wrote: > not(contains(replace(., '\\,', ''), ',')) > > On Fri, . . . Read full entry »


Re: XPath expression which checks that all commas are escaped

Posted 11/3/2017 12:14:51 PM

not(contains(replace(., '\\,', ''), ',')) On Fri, Nov 3, 2017 at 11:40 AM, Costello, Roger L. <costello@mitre.org> wrote: > Hi Folks, > > Do you deal with Request for Comments (RFCs)? Then the following might come > . . . Read full entry »


Expat 2.2.5 released

Posted 11/1/2017 8:01:57 PM

Hi everyone, Expat 2.2.5 has been released. It fixes miscellaneous bugs. For more details, please check the changelog [1]. If you maintain Expat packaging or a bundled version of Expat somewhere, please update it to 2.2.5. Thanks! Best Sebastian [1] https://github.com/libexpat/libexpat/blo . . . Read full entry »


Re: Is this a good use of XML: XML-formatted images?

Posted 10/30/2017 12:02:04 PM

On Sun, 29 Oct 2017 13:01:22 +0000, "Costello, Roger L." <costello@mitre.org> wrote: | Thoughts? RFC 3252. . . . Read full entry »


Re: Is this a good use of XML: XML-formatted images?

Posted 10/29/2017 5:51:08 PM

On 29 Oct 2017, at 13:01, Costello, Roger L. <costello@mitre.org> wrote: Hi Folks,JPEG/JFIF, GIF, PNG, BMP are, as you know, binary data formats for images.Why are there no XML-formatted images? Is XML not a good format for images? If it’s not, why . . . Read full entry »


Re: Is this a good use of XML: XML-formatted images?

Posted 10/29/2017 3:00:56 PM

Raster images are  one of the types types of image elements SVG supportshttps://www.w3.org/TR/SVG11/render.html#TypesOfGraphicsElementsOn Sun, Oct 29, 2017 at 10:56 AM Costello, Roger L. <costello@mitre.org> wrote: Thanks Timothy.   I was thinkin . . . Read full entry »


RE: Is this a good use of XML: XML-formatted images?

Posted 10/29/2017 2:55:57 PM

Thanks Timothy.   I was thinking bitmapped images, not vector images.   /Roger   From: Timothy Cook [mailto:timothywayne.cook@gmail.com] Sent: Sunday, October 29, 2017 10:25 AM To: Cos . . . Read full entry »


Is this a good use of XML: XML-formatted images?

Posted 10/29/2017 1:01:22 PM

Hi Folks, JPEG/JFIF, GIF, PNG, BMP are, as you know, binary data formats for images. Why are there no XML-formatted images? Is XML not a good format for images? If it’s not, why not? I’ll speculate: perhaps the reason is simply that XML is too verbose. Is that the reason? Are there . . . Read full entry »


Re: Is this a good use of XML: XML-formatted images?

Posted 10/29/2017 12:25:29 PM

Maybe you have heard of this?"This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML."https://www.w3.org/TR/SVG11/On Sun, Oct 29, 2017 at 11:01 . . . Read full entry »


Re: XML-formatted data can be incrementally enriched with more

Posted 10/28/2017 8:48:43 PM

The ability to extend a data format while retaining backwards compatibility is important, and was no doubt one of the objectives of the design of XML.But I don't think that's primarily what the "extensibility" property is about. The "X" in "XML" is there primarily to contrast with HTML, and it refe . . . Read full entry »


RE: XML-formatted data can be incrementally enriched with more andmore i

Posted 10/28/2017 7:10:23 PM

Hi Folks,   Thank you (again) for your outstanding responses.   I found your responses surprising. In a nutshell, you told me that many, if not most, data formats – both text and binary – are extensible.   XML, it seems to me, has always made it a point to advertise t . . . Read full entry »


Re: XML-formatted data can be incrementally enriched withmore

Posted 10/28/2017 1:38:34 PM

Hi Roger, > Lesson Learned: XML is the only data format that supports incremental enrichment. At first I thought that what you describe is related to strong vs. weak vs. no typing, late binding and so on It is related to some extent, however extensibility can be achieved in a standard way ev . . . Read full entry »


Re: XML-formatted data can be incrementally enriched with more

Posted 10/27/2017 7:46:23 PM

You can do it with CSV: just add fields to the right-hand end of a line P On 27 October 2017 14:33:59 Michael Kay <mike@saxonica.com> wrote: Do you agree with those assertions? No. We were doing this with binary type-length-value formats . . . Read full entry »


Re: XML-formatted data can be incrementally enriched with more

Posted 10/27/2017 2:31:36 PM

Do you agree with those assertions? No. We were doing this with binary type-length-value formats 50 years ago.Michael KaySaxonica . . . Read full entry »


XML-formatted data can be incrementally enriched with more and moreinfor

Posted 10/27/2017 12:18:08 PM

Hi Folks,   Assertion: The XML data format is the only data format that lends itself to incremental enrichment.   Assertion: If data is to traverse through a workflow and you want the data to be incrementally enriched along the way, then you must format the data as XML.   Do yo . . . Read full entry »


Re: XML-formatted data can be incrementally enriched withmore

Posted 10/27/2017 8:45:43 AM

On Fri, Oct 27, 2017 at 8:18 AM, Costello, Roger L. <costello@mitre.org> wrote: Suppose the data is binary. For example, suppose the data is a JPEG file. How would you incrementally enrich JPEG files? How would you bundle together mu . . . Read full entry »


Re: DSDL.org

Posted 10/25/2017 10:01:05 PM

The webarchive of the original DSDL.org is available at https://web.archive.org/web/20160122193526/http://dsdl.orgRegards,Makoto2017/10/25 午後6:38 "yamahito" <yamahito@gmail.com>:I note that the above website is now a norwegian bl . . . Read full entry »


DSDL.org

Posted 10/25/2017 9:38:17 AM

I note that the above website is now a norwegian blog extolling the values of playing online slots.Does/will DSDL have a new home?The webmaster for nvdl.org might also like to know so that he can edit/remove the link on that page. . . . Read full entry »


[ANN] XML Prague 2018 - Call for Proposals

Posted 10/23/2017 2:00:58 PM

Hello, we are glad to announce that call for proposals for XML Prague 2018 conference is open now. The XML Prague conference will include two full days of single track sessions, as well as a multitrack unconference day. The conference is held on the Thursday, Friday and Saturday (February 8-10, . . . Read full entry »


[ANN] Release of XMLmind XSL-FO Converter v5.4.6

Posted 10/23/2017 10:09:19 AM

Release of XMLmind XSL-FO Converter v5.4.6. Highlights: - XMLmind XSL Utility and XMLmind XSL Server can now be used to convert DocBook v5.1 assemblies to PDF, RTF, WML, DOCX and ODT. - Updated some software components in XMLmind XSL Utility and XMLmind XSL Server. More information in http://w . . . Read full entry »


Re: [ANN] XML Prague 2018 - Call for Proposals

Posted 10/22/2017 8:26:15 PM

On 22/10/17 15:00, Jirka Kosek wrote: > we are glad to announce that call for proposals for XML Prague 2018 > conference is open now. I have updated the entry in the FAQ at http://xml.silmaril.ie/moreinfo.html#events ///Peter Attachment: signature.asc Description: OpenPGP digital signatur . . . Read full entry »


[ANN] XML Prague 2018 - Call for Proposals

Posted 10/22/2017 4:00:50 PM

Hello, we are glad to announce that call for proposals for XML Prague 2018 conference is open now. The XML Prague conference will include two full days of single track sessions, as well as a multitrack unconference day. The conference is held on the Thursday, Friday and Saturday (February 8-10, . . . Read full entry »


RE: NVDL & ISO Schematron?

Posted 10/18/2017 12:17:16 PM

Hi,   We use Jing to do NVDL and Schematron validation. There is basic ISO Schematron support but there are things you cannot do – for instance if your Schematron uses queryBinding="xslt2" and contains XSL elements, it will not work. We forked the project to add the ful . . . Read full entry »


editors and schemas

Posted 10/18/2017 11:29:30 AM

This might interest the document-centric folks here: ProseMirror: A toolkit for building rich-text editors on the Web http://prosemirror.net/ In particular, the sections describing ProseMirror's schemas and transformations might seem familiar, but not very familiar: http://prosemirror.net/docs/ . . . Read full entry »


NVDL & ISO Schematron?

Posted 10/18/2017 10:34:42 AM

What would people currently recommend to do NVDL validation including standalone schematron?It looks like the current version of Jing from github has some degree of support, but documentation doesn’t mention it explicitly; can anyone enlighten as to what support is offered, or if there are any alte . . . Read full entry »


Re: PE's in internal subset with non-validating processors

Posted 10/17/2017 11:48:37 AM

Parameter entities can also be declared in an internal declaration, right?  That could be thought of as parsing rather than validation, IMO...On Mon, 16 Oct 2017 at 01:25 David John Burrowes <biede0@gmail.com> wrote:Thank you John Cowan a . . . Read full entry »


Re: PE's in internal subset with non-validating processors

Posted 10/17/2017 4:54:02 AM

> Parameter entities can also be declared in an internal declaration, right? Yes.> That could be thought of as parsing rather than validation, IMO…I’m not quite sure i understand what you mean.  But a non-validating parser can indeed parse a PE declaration if it chooses, and do noth . . . Read full entry »


Re: PE's in internal subset with non-validating processors

Posted 10/15/2017 6:12:15 PM

On Sun, Oct 15, 2017 at 3:18 PM, David John Burrowes <biede0@gmail.com> wrote:The phrase "and in any parameter entity that they read” is what is puzzling me.  Yes, it probably should have been "any parameter entity that they choose to rea . . . Read full entry »


Re: PE's in internal subset with non-validating processors

Posted 10/15/2017 5:25:29 PM

Thank you John Cowan and Tim Bray for your swift responses!DavidOn Oct 15, 2017, at 3:12 PM, John Cowan <johnwcowan@gmail.com> wrote:On Sun, Oct 15, 2017 at 3:18 PM, David John Burrowes <biede0@g...> wrote:The phrase "and in any parameter entity that they re . . . Read full entry »


Re: PE's in internal subset with non-validating processors

Posted 10/15/2017 1:37:58 PM

We'll, even a non-validating processor *might* decide to read parameter entities. Nothing forbids it.On Oct 15, 2017 12:18 PM, "David John Burrowes" <biede0@gmail.com> wrote:I have a question about a passage in section 5.1 of the XML standard that . . . Read full entry »


PE's in internal subset with non-validating processors

Posted 10/15/2017 12:18:45 PM

I have a question about a passage in section 5.1 of the XML standard that I can’t quite wrap my head around:Non-validating processors are required to check only the document entity, including the entire internal DTD subset, for well-formedness. [Definition: While they are not required to check . . . Read full entry »


For the mathematically inclined.

Posted 10/10/2017 1:33:17 PM

https://www.youtube.com/watch?v=OyfBQmvr2Hc The mention of tree processing in Schema alongside DSSSL made me smile. Enjoy -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk . . . Read full entry »


Re: For the mathematically inclined.

Posted 10/10/2017 8:37:40 AM

I've watched the first half last night. The math must be in the second half.On Tue, Oct 10, 2017 at 8:33 AM, Dave Pawson <dave.pawson@gmail.com> wrote:https://www.youtube.com/watch?v=OyfBQmvr2Hc The mention of tree processing . . . Read full entry »


Shoehorning (was RE: Re: XML vs JSON)

Posted 10/6/2017 11:39:00 AM

While we are on the subject of shoehorning (facades/views to allow use of one technology that is weak in some area with a different technology that is strong in the same area): http://schematron.com/2017/08/can-i-assert-patterns-in-java-objects-with-schematron/RegardsRickOn 6 Oct 2017 09:57, " . . . Read full entry »


RE: Re: XML vs JSON

Posted 10/5/2017 3:57:18 PM

Hi, In addition, it may be worth mentioning that a draft version of WoT (Web of Things) Thing Description [1]specification also attempts to define JSON-schema to XML-schema mapping, based on the JSON-XML mapping defined by EXI. One consequence of this is one will be able to validate JSON . . . Read full entry »


Re: XML vs JSON

Posted 10/5/2017 11:27:40 AM

I think one can probably prove that no mapping JSON to/from XML will satisfy all the following objectives:(1) Handles any JSON document(2) Handles any XML document(3) is round-trippable (to-json(to-xml(J)) = J, and to-xml(to-json(X)) = X).and the more you try and get close to this, the more you sac . . . Read full entry »


AW: Re: XML vs JSON

Posted 10/5/2017 9:07:08 AM

Hi, Many of these JSON<->XML tools provide a good coverage for some XML/JSON constructs but not for all. The tool [1] you pointed to fails for example when converting the following "simple" JSON example to XML. { "a number": 1 } The reason is rather simple. The qualifi . . . Read full entry »


Re: XML Schema complex type restriction

Posted 10/2/2017 8:18:05 PM

> Requiring the assertion to be true ONLY for content that satisfies the grammar would be a ridiculous burden on schema authors. In fact, it has been proven untractable for XML Schema [1], but not for DTDs [2]: [1]: http://www.cs.toronto.edu/tox/papers/xsc.pdf "What's Hard about XML S . . . Read full entry »


Re: XML Schema complex type restriction

Posted 10/2/2017 7:01:24 PM

On 29 September 2017 at 14:09, Michael Kay <mike@saxonica.com> wrote:More realistically, imagine you have a complex type whose content model is <element name="para" minOccurs="0" maxOccurs="unbounded&q . . . Read full entry »


XDM and semantic identity

Posted 9/29/2017 10:46:01 PM

Dear colleagues,I have just spent indefinite time staring at a single sentence from the "National Information Exchange Model Naming and Design Rules", section 5.4:"The properties of an object may be spread across several XML elements that have the same identifier." [1]The significance of this sent . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/29/2017 7:06:31 PM

(Doh.  I meant of course a datatype facet like minInclusive and maxInclusive. )On Fri, Sep 29, 2017 at 7:03 PM, Rick Jelliffe <rjelliffe@allette.com.au> wrote:> Requiring the assertion to be true ONLY for content that satisfies the gram . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/29/2017 7:03:36 PM

> Requiring the assertion to be true ONLY for content that satisfies the grammar would be a ridiculous burden on schema authors.And it is not the way that other datatype facet work either:  minOccurs allows values that maxOccurs excludes; the type is the intersection of the facets. On Fri, Sep 2 . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/29/2017 4:39:34 PM

Oops, my example made no sense. Here is a better stab:For example, if you have an element of XSD type Integer and the assertion constrains the element to be either the text "MentalSpasm" or the number 32 (XSD assertion tests are on the typed document), the type is constrained to be the n . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/29/2017 11:18:03 AM

On 28 September 2017 at 21:07, Rick Jelliffe <rjelliffe@allette.com.au> wrote:I think assertions are always subsumptive in your terminology.  Even if they appear to allow otherwise.For example, if you have an element of type Integer and . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/29/2017 9:39:38 AM

More realistically, imagine you have a complex type whose content model is <element name="para" minOccurs="0" maxOccurs="unbounded"/>, and the assertion says test="exists(para)", then the assertion on its own would allow<para/><fig/><fig/>which the complex type's grammar doe . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/29/2017 1:37:32 AM

I think assertions are always subsumptive in your terminology.  Even if they appear to allow otherwise.For example, if you have an element of type Integer and the assertion constrains the element to be either the text "54" or the number 32, the type is constrained to be the number 32.  Th . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/28/2017 6:07:59 PM

On 25 September 2017 at 19:50, Michael Kay <mike@saxonica.com> wrote:Both these problems can be addressed by defining the restrictions using assertions. I think this is how I would normally do it in XSD 1.1.Here's the syntax of complex type r . . . Read full entry »


Re: Missing character in PDF of Schematron 2nd edition?

Posted 9/28/2017 4:00:17 PM

To follow up, the previous editor advises regarding the removal of s6.3 that it was felt that the standard describes a language, rather than a processor.Hope that helps,AndrewOn 27 September 2017 at 15:20, Andrew Sales <andrew@andrewsales.com> wrote:Thank you bot . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/28/2017 12:50:45 PM

On Tue, Sep 26, 2017 at 4:50 PM, Webb Roberts <webb@webbroberts.com> wrote:That said, I feel that JSON-LD has really threaded the needle between JSON and RDF, turning something that's fairly underspecified into something incredibly useful. We . . . Read full entry »


Re: Missing character in PDF of Schematron 2nd edition?

Posted 9/27/2017 3:20:16 PM

Thank you both -- I will add this to my list.I'm not sure why s6.3 was removed, will ask the previous editor.Andrew(Project editor, Schematron)On 27 September 2017 at 14:48, G. Ken Holman <gkholman@cranesoftwrights.com> wrote: . . . Read full entry »


Missing character in PDF of Schematron 2nd edition?

Posted 9/27/2017 2:10:21 PM

Hello everbody, Dunno if this is the right place to complain, but I think that the PDF of Schematron's second edition might contain an misleading error. I seems to me that the character used for signifying the use of parameter of an abstract pattern on page 11, in Annex C, Annex H, Annex J, and A . . . Read full entry »


Re: Missing character in PDF of Schematron 2nd edition?

Posted 9/27/2017 9:48:12 AM

In the latest version of the ISO/IEC specification currently being voted on this text reads: "prefix the name with the character $." ... in Annexes C, H and J. The dollar sign remains absent in Annexes L and M and so warrants an editorial comment. Well spotted! . . . . . . . Ken . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/27/2017 7:26:23 AM

Thank you very much, Webb - I am glad to have these answers, which, taken together with your links and earlier explanations provide food for weeks of thoughts and studies.This thread started with concerns about XSD's mechanism of restriction, xs:restriction. I would like to make an attempt and rela . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/26/2017 4:50:00 PM

Hans-Jürgen, thank you for your kind comments.On 2017-09-25, at 18:07:04, Hans-Juergen Rennau <hrennau@yahoo.de> wrote:is NIEM's being based on RDF a concept which had been present from the very beginning of NIEM, or had it been gradu . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/26/2017 3:52:54 PM

XSD misses at least five important mechanisms needed for practical schemas.First, it does not allow parameterization: i.e. parameters supplied that can be used to create cohesive subsets.  Interestingly, one of the extensions (pushed by mathematician Dave Peterson IIRC) mooted for SGML in the early . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/26/2017 10:17:35 AM

On 25 September 2017 at 19:50, Michael Kay <mike@saxonica.com> wrote:Firstly, you have to describe the restricted content model rather than describing the differences (which means the parts that are retained are described in more than one place.)I agree with t . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/26/2017 12:07:02 AM

I'd like to share my experience here with the ISO 20012 schema to represent financial transactions as used in the upcoming EU MiFIR reporting process. There's no question the schema was competently designed by domain experts, and also from a markup design PoV apart from using generated type names I . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/25/2017 10:07:04 PM

My cordial thanks for this excellent summary of the NIEM approach, Webb. I had read parts of it before, but your description pulled everything together as to give it a coherence of concept which I had not been aware of, and which impresses me deeply. Would you like to answer some of the following q . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/25/2017 9:47:34 PM

I find the idea of parameterized schemas very interesting, it had never occurred to me. But I think it does not scale out for very complex schemas where the burden of having to anticipate all needs of variation could become overwhelming.Concerning the tiny vocabulary, your scepsis is perhaps based . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/25/2017 6:01:04 PM

You are forced to use a started kitchen sink schema because is standard and therefore will make life easier.However, most of the elements and attributes are things you dont need. And you know the full schema will blow out implementatuon and confuse testing and anyway YAGNI. So you will make profile . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/25/2017 3:20:05 PM

I think there are two main problems with complex type restriction as defined in XSD.Firstly, you have to describe the restricted content model rather than describing the differences (which means the parts that are retained are described in more than one place.)Secondly, what I call "deep restrictio . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/25/2017 1:47:04 PM

On 2017-09-25, at 08:47:59, Hans-Juergen Rennau <hrennau@yahoo.de> wrote:how does NIEM treat this question, where restriction of extreme generality should be extremely important?The National Information Exchange Model (NIEM) provides a set of XM . . . Read full entry »


XML Schema complex type restriction

Posted 9/25/2017 12:57:03 PM

Hello list,    Can anyone come up with a useful business use case, to use XML Schema complex type restriction?-- Regards,Mukul Gandhi . . . Read full entry »


Re: XML Schema complex type restriction

Posted 9/25/2017 12:47:59 PM

"The trouble with restriction is not knowing exactly what the differences are or why."This is an interesting point. (And I've always avoided restriction of complex types, instinctively.)Of course it would, in principle, be very easy to specify a restriction step explicitly, using a tiny vocabulary . . . Read full entry »


Re: XML vs JSON

Posted 9/22/2017 11:38:23 AM

With respect to this thread, I could see that people have written tools to convert between XML and JSON (both ways). This seems to be nice: www.utilities-online.info/xmltojson/On 1 August 2017 at 17:04, Mukul Gandhi <gandhi.mukul@gmail.com> wro . . . Read full entry »


[ANN] Release of XMLmind Ebook Compiler v1.0.1

Posted 9/18/2017 10:19:36 AM

XMLmind Ebook Compiler v1.0.1 features a few minor enhancements. More info in http://www.xmlmind.com/ebookc/changes.html ------------------------------- What is XMLmind Ebook Compiler? ------------------------------- XMLmind Ebook Compiler (ebookc for short) is a free, open source tool which . . . Read full entry »


RE: Seek your help in compiling a list of "facts about base64-encodeddat

Posted 9/16/2017 8:03:36 PM

Thank you David and Eliot. Outstanding comments!   I updated the list, incorporating the comments from David and Eliot. See below. Does anyone else have comments?  /Roger   Here are some things to know about base64:   1.       Base64 encoding is . . . Read full entry »


Re: RE: Seek your help in compiling a list of "facts aboutbase

Posted 9/16/2017 7:09:21 PM

> I would also be very interested to hear your thoughts on 17. If you don't mind, would you post your thoughts to the list, please? well, as you ask... On 16 September 2017 at 14:09, Costello, Roger L. <costello@mitre.org> wrote: > Hi Folks, > . . . Read full entry »


Re: RE: Seek your help in compiling a list of "facts aboutbase

Posted 9/16/2017 3:10:44 PM

I'm not sure agree with the previous 17 either but this one in particular I think needs comment > 18. The size of base64-encoded data is roughly 4/3 the size of the original data. The link you gives shows that there are 4/3 as many output characters as input bytes. The relative size of the . . . Read full entry »


Re: RE: Seek your help in compiling a list of "facts aboutbase

Posted 9/16/2017 2:00:16 PM

As regards the need for more decoding for base64 data: I think the point Roger’s trying to make is that from the standpoint of communicating data to a system that is expected to be able to process it in some way, if you provide a stream of bytes that is a JPEG image then the consumer of that strea . . . Read full entry »


RE: Seek your help in compiling a list of "facts about base64-encodeddat

Posted 9/16/2017 1:09:01 PM

Hi Folks,   Thank you for your excellent comments. I added them to my list. Below is the updated list. Is it missing anything?  /Roger   Here are some things to know about base64:   1.       Base64 encoding is specified in RFC 4648. 2. &nbs . . . Read full entry »


Fwd: Re: A XSD regex to allow a QName in Clark form

Posted 9/16/2017 12:50:29 AM

---------- Forwarded message ----------From: "Rick Jelliffe" <rjelliffe@allette.com.au>Date: 15 Sep 2017 11:34 AMSubject: Re: A XSD regex to allow a QName in Clark formTo: "Christophe Marchand" <cmarchand@o...>Cc: . . . Read full entry »


Re: What does it mean to lexically distinguish significantand

Posted 9/15/2017 6:59:32 PM

On Wed, Sep 13, 2017 at 7:45 AM, Michael Kay <mike@saxonica.com> wrote:What I meant by the phrase is that when you see <a>   <b/> </a> there is nothing within the document itself to tell you whether the whitespace is signifi . . . Read full entry »


Re: Seek your help in compiling a list of "facts aboutbase64-e

Posted 9/14/2017 7:22:39 PM

On Thu, 14 Sep 2017 13:09:54 +0000 "Costello, Roger L." <costello@mitre.org> wrote: > Hi Folks, > > > Is base64 encoded data good? Bad? A security risk? A simple mechanism for > data privacy? It is probably all of those. . . . Read full entry »


Re: Seek your help in compiling a list of "facts aboutbase64-e

Posted 9/14/2017 7:10:02 PM

On Thu, Sep 14, 2017 at 9:09 AM, Costello, Roger L. <costello@mitre.org> wrote:> 1.       Base64-encoded data is plain text, consisting of these 64 ASCII characters: a-z, A-Z, 0-9, +, / and the equals symbol ( = ).As a common extension, . . . Read full entry »


Re: Seek your help in compiling a list of "facts about base64-

Posted 9/14/2017 6:17:25 PM

On 14 Sep 2017, at 14:09, Costello, Roger L. <costello@mitre.org> wrote: Hi Folks,  Is base64 encoded data good? Bad? I would suggest that the goodness or badness of a piece of data is completely independent of its encoding.The choic . . . Read full entry »


Seek your help in compiling a list of "facts about base64-encodeddata"

Posted 9/14/2017 1:09:54 PM

Hi Folks,   Is base64 encoded data good? Bad? A security risk? A simple mechanism for data privacy? It is probably all of those. Below I have attempted to objectively state the facts. Am I missing any facts?  /Roger   1.       Base64-encoded data is . . . Read full entry »


Re: A XSD regex to allow a QName in Clark form

Posted 9/14/2017 11:17:38 AM

As I use this value to create a new net.sf.saxon.s9api.QName, via constructor and factory methods, I'm gonna check this. Thanks a lot for this precises explanations. Best regards, Christophe Le 2017-09-14 11:04, Michael Kay a écrit : Some more precise terminology might help. Clark notation is . . . Read full entry »


Re: Another way to present XML data

Posted 9/14/2017 10:09:18 AM

I totally agree with all what you say. Sorry for having been too assertive.And I never said that mixed content was an edge case. I just say that it's not the case I address in my proposal.Jean-FrançoisDe: "yamahito" <yamahito@gmail.com>À: xml-dev@l.. . . . Read full entry »


Re: A XSD regex to allow a QName in Clark form

Posted 9/14/2017 10:04:26 AM

Some more precise terminology might help.Clark notation is described here:http://www.jclark.com/xml/xmlns.htmand uses the notation "{uri}local" for a name that is in a namespace. That page doesn't define a corresponding notation for a name in no namespace, but it would be wise to accept either "loc . . . Read full entry »


Re: A XSD regex to allow a QName in Clark form

Posted 9/14/2017 10:01:25 AM

It's the one I've tried, without success. ... Best, Tom. Le 2017-09-14 09:56, yamahito a écrit : Try <xs:pattern value="Q?\{[^\}]+\}[^:\{\}]+"/> ? On Thu, 14 Sep 2017 at 7:55 am, <cmarchand@oxiane.com> wrote: Hi ! I'm not . . . Read full entry »


A XSD regex to allow a QName in Clark form

Posted 9/14/2017 8:54:51 AM

Hi ! I'm not a regex killer, especially when regex flavour is not the one I use on my linux box... In a schema, I need a simple type that allows a QName, written either "prefix:localName" or in ClarkeForm "Q{nsUri}localName", or in the-last-one-I-cant-remember-the-name &quo . . . Read full entry »


Re: Another way to present XML data

Posted 9/14/2017 8:52:25 AM

> As David alludes, this shows the lie of JSON being more human readable (at least as a general rule).It's true that JSON is more human readable than XML for tree-structured data.Not recognizing that will just help JSON getting more users.I think the true strength of XML lies in its DOM.My . . . Read full entry »


Re: A XSD regex to allow a QName in Clark form

Posted 9/14/2017 7:56:12 AM

Try<xs:pattern value="Q?\{[^\}]+\}[^:\{\}]+"/>?On Thu, 14 Sep 2017 at 7:55 am, <cmarchand@oxiane.com> wrote:Hi ! I'm not a regex killer, especially when regex flavour is not the one I use on my linux box... In a schema, I need a simp . . . Read full entry »


Re: Another way to present XML data

Posted 9/14/2017 7:52:52 AM

> It's true that JSON is more human readable than XML for tree-structured data.With respect, that is an opinion presented as a fact without any evidence: you have every right to feel that way, but no right to expect everyone to agree with you.XML is, for me, primarily a markup language, as i . . . Read full entry »


Re: Another way to present XML data

Posted 9/13/2017 8:39:37 PM

> p {u underlined ;i italic}As David alludes, this shows the lie of JSON being more human readable (at least as a general rule).> Sebastian was shocked that I would expect different results to be passed into the application depending on whether a DTD/Schema as used or notThis surprises me: su . . . Read full entry »


Re: Another way to present XML data

Posted 9/13/2017 7:55:05 PM

Maybe use a stylesheet?On Wed, Sep 13, 2017 at 7:31 PM, yamahito <yamahito@gmail.com> wrote:The case I often find processors screwing up is:<p><u>underlined</u> <i>italic</i></p>Note the significant whitespa . . . Read full entry »


Re: Another way to present XML data

Posted 9/13/2017 5:42:55 PM

On 13 September 2017 11:32:10 yamahito <yamahito@gmail.com> wrote: > The case I often find processors screwing up is: > > <p><u>underlined</u> <i>italic</i></p> > > Note the significant whitesp . . . Read full entry »


Re: Another way to present XML data

Posted 9/13/2017 2:53:01 PM

> The case I often find processors screwing up is...sml.tcl passes that test easily :-)C:\JFL\Temp>"echo.exe" "<p><u>underlined</u> <i>italic</i></p>"<p><u>underlined</u> <i>italic</i></p>C:\JFL\Temp>"echo.exe" "<p& . . . Read full entry »


Re: Another way to present XML data

Posted 9/13/2017 2:16:44 PM

sml.tcl passes that test easily :-) C:\JFL\Temp>"echo.exe" "<p><u>underlined</u> <i>italic</i></p>" <p><u>underlined</u> <i>italic</i></p> C:\JFL\Temp>"echo.exe" "<p><u>und . . . Read full entry »


Re: What does it mean to lexically distinguish significant and

Posted 9/13/2017 12:45:17 PM

What I meant by the phrase is that when you see <a> <b/> </a> there is nothing within the document itself to tell you whether the whitespace is significant; you typically need external information (e.g. a schema or DTD, or just outside knowledge) to know. One can envisage oth . . . Read full entry »


Re: What does it mean to lexically distinguish significantand

Posted 9/13/2017 12:43:33 PM

It means that you can't tell from xml syntax as specified whether <x><a>z</a><b>z</b></x> means the same as <x> <a>z</a> <b>z</b> </x> you could assume it's always significant (which would never allow you to re-indent o . . . Read full entry »


Re: Another way to present XML data

Posted 9/13/2017 11:52:46 AM

For background on whitespace and mixed content in text encodings such as TEI, see https://wiki.tei-c.org/index.php/XML_Whitespace. -- On 9/13/2017 11:42 AM, Peter Flynn wrote: On 13 Sep . . . Read full entry »


What does it mean to lexically distinguish significant andinsignificant

Posted 9/13/2017 11:33:45 AM

Michael Kay wrote: > significant and insignificant whitespace > can't be lexically distinguished. What does that mean? What does it mean to "lexically distinguish" significant and insignificant whitespace? /Roger . . . Read full entry »


Re: Another way to present XML data

Posted 9/13/2017 9:31:12 AM

The case I often find processors screwing up is:<p><u>underlined</u> <i>italic</i></p>Note the significant whitespace between the <u/> and <i/>On Tue, 12 Sep 2017 at 21:45 Michael Kay <mike@saxonica.com> wrote:On 12 Sep 2 . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 10:14:39 PM

As I already answered to Michael Kay, this is HTML.My conversion script will work with XHTML (The initial X is important), but this is not the intended use case.It will really be useful with XML-based languages and databases, that usually do not use mixed data and tags like HTML.Google's KML is an . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 9:45:38 PM

On 12 Sep 2017, at 21:14, jf.larvoire@free.fr wrote:As I already answered to Michael Kay, this is HTML.No, this is XML.Google's KML is an excellent example, as are XSLT, SOAP, SVG, etc...Of those three examples, two use mixed content:XSLT:<xsl:template match="ci . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 8:56:47 PM

Maybe something like this : <p>This is a <b>bold</b> text with <u>underlined <i>italic</i> content</u> in.</p> Best, Christophe Le 12/09/2017 à 18:32, jf.lar . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 8:06:26 PM

The benefit is that the transformation is generic, and will work the same way with any XML file, without changing anything to its DOM structure.In your case the DOM changes, and you'll have trouble if attributes have the same name as inner elements, etc.Jean-FrançoisDe: "Ihe Onwuka" <ihe . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 8:00:26 PM

I see.What you call mixed content is basically what you have in HTML files.My script will convert XHTML reversibly, including with lots of complex mixed contents cases. (I've tested it successfully with the XML specification itself :-) )But it will not convert plain HTML reversibly.Also my SML form . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 6:32:29 PM

No, white spaces are significant, and are preserved by my conversion script.I don't really know what you mean by mixed contents.Please show me an example of mixed content that is not converted correctly.Jean-FrançoisDe: "Michael Kay" <mike@saxonica.com> . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 6:02:03 PM

I haven't tried the conversion tool, I've only been looking in the spec.Mixed content is essentially an element node that has both element and text node children.You convert <formats>    <format name="XML"> <author>W3C</author>toformats {    format n . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 4:49:14 PM

I actually came across this proposal a couple of months ago when trying to do something similar myself - before I found it I had in fact reinvented a lot of this, with minor variations.The thing I was finding most difficult was mixed content, and I don't think SML has really thought that through ei . . . Read full entry »


Another way to present XML data

Posted 9/12/2017 4:31:28 PM

Following last month's thread about the relative merits of XML and JSON, I think there's a way to get the advantages of both:Instead of creating yet another data format incompatible with XML, it's actually possible to transform _reversibly_ XML into something that is as human-friendly as JSON.This . . . Read full entry »


Re: Another way to present XML data

Posted 9/12/2017 1:58:04 PM

What value (or readability) does this offer over and above a scheme that simply transformed elements designated as atomic to attributes.<formats>    <format name="XML"             author="W3C"            standardized="2008"     advantage="Can define forma . . . Read full entry »


[ANN] Release of XMLmind XML Editor 7.5

Posted 9/7/2017 11:24:08 AM

Release of XMLmind XML Editor 7.5 XMLmind XHTML Editor (and of course its superset: XMLmind XML Editor) can now be used to turn a set of HTML pages into a self-contained ebook (EPUB, Web Help, PDF, DOCX, etc). More information in "Creating an ebook out of a set of HTML pages"[1]. Thi . . . Read full entry »


[ANN] New Open Source XMLmind Ebook Compiler

Posted 8/31/2017 10:41:11 AM

XMLmind Ebook Compiler (ebookc for short) is a free, open source tool which can turn a set of HTML pages into a self-contained ebook. Supported output formats are: EPUB, Web Help, PDF, RTF, WML, DOCX (MS-Word) and ODT (OpenOffice/LibreOffice). Ebookc features: - Topic-oriented like DITA and Do . . . Read full entry »


Re: Modern talking

Posted 8/30/2017 5:58:46 PM

Dear Reichardt, XQuery is different from XSLT. Of course everything depends on your specific needs/tasks, but probably you could solve most of them with, for example, BaseX XQuery: it provides extensions to the W3C recommendations, which make it a general-purpose programming language. Best, Gius . . . Read full entry »


Re: Modern talking

Posted 8/30/2017 5:53:28 AM

Liam: "Forest", this is the most beautiful name, the most meaningful one, I can imagine for what is now called XQuery. (I suggest to leave out the "Fast".)Incredible.Hans-Jürgen Liam R. E. Quin <liam@w3.org> schrieb am 17:23 Dienstag, 29.August 2017: On Tue, . . . Read full entry »


Re: Modern talking

Posted 8/29/2017 7:04:42 PM

I don't have a stake in XQuery but as a practioner working not just with markup yet still with enough XSLT experience I've found XML-specific programming languages generally limiting in that problem domains I'm using them for would often benefit from the kind of infrastructure and mindshare that ge . . . Read full entry »


Re: Modern talking

Posted 8/29/2017 4:06:26 PM

On Tue, Aug 29, 2017 at 1:04 PM, u123724 <u123724@gmail.com> wrote:I don't have a stake in XQuery but as a practioner working not just with markup yet still with enough XSLT experience I've found XML-specific programming languages generally limi . . . Read full entry »


Re: Modern talking

Posted 8/29/2017 12:19:56 PM

Hi Michael,I understand that. And I take it as an invitation for everyone to be more active and as an opportunity to thank all the people who contributed to the creation of such an amazing resource.In general, as an XQuery teacher within a university, I feel there is much potential for XQuery to ga . . . Read full entry »


Re: Modern talking

Posted 8/29/2017 11:22:13 AM

On Tue, 2017-08-29 at 12:19 +0200, Giuseppe Celano wrote: > > And yes, XQuery is tied to XML, but the problem here is, in my > experience, not XML, but the huge amount of misinformation > circulating about it (stemming from ignorance of it), misuse of it, > and laziness: if one pers . . . Read full entry »


Re: Modern talking

Posted 8/29/2017 7:49:09 AM

Hi, > But if you're going to aim for the skies in terms of a unified information model, then it has to be something RDF-like rather than something XML-like. XML is just too littered with arbitrary quirks. I've always felt that XQuery was too closely tied to XML to have aspirations to become som . . . Read full entry »


Re: XPath +/- etc not first class functions

Posted 8/28/2017 11:40:42 PM

> On 28 Aug 2017, at 21:57, Dimitre Novatchev <dnovatchev@gmail.com> wrote: > > On Mon, Aug 28, 2017 at 1:47 PM, Michael Kay <mike@saxonica.com> wrote: >> Yes: perha . . . Read full entry »


Re: XPath +/- etc not first class functions

Posted 8/28/2017 10:15:50 PM

Hi,  perhaps there is an implementation where op:numeric-add is an actual function Best, Benito  Am 28.08.2017 um 21:37 schrieb Dimitre Novatchev: Add() and Subtract() have been part of FXSL (http://fxsl.sour . . . Read full entry »


Re: Modern talking

Posted 8/28/2017 9:50:17 PM

Care should be taken to avoid speaking of completely different things, using similar words. Writing ..."But if you're going to aim for the skies in terms of a unified information model, then..."your words "unified information model" have nothing to do with what I call a "unified view of information . . . Read full entry »


Re: XPath +/- etc not first class functions

Posted 8/28/2017 9:47:30 PM

Yes: perhaps this could be the shortest EXPath spec ever. Just define a binding of the op prefix to the namespace http://expath.org/ns/operators and you're done. Michael Kay Saxonica > On 28 Aug 2017, at 21:15, Benito van der Zander <benito@benib&# . . . Read full entry »


Re: Modern talking

Posted 8/28/2017 7:19:36 PM

On 28 Aug 2017, at 06:38, Hans-Juergen Rennau <hrennau@yahoo.de> wrote:Thank you very much for these points concerning public interest and the danger of immature decisions.Valid as they are, I think the heart of the problem lies elsewhere: it is the lack of vision. For my . . . Read full entry »


Re: Modern talking

Posted 8/28/2017 7:09:46 PM

> On 28 Aug 2017, at 16:15, Giuseppe Celano <celano@informatik.uni-leipzig.de> wrote: > > I think that another XQuery Update Facility would be welcome (I hope the 3.0 draft will be soon a recommendation). > It won't, I . . . Read full entry »


Re: Modern talking

Posted 8/28/2017 6:47:24 PM

On Mon, Aug 28, 2017 at 5:50 PM, Hans-Juergen Rennau <hrennau@yahoo.de> wrote: Ironically, I take a much more pragmatic view than you: I couldn't care less about those 19 primitive types, for example, but I do care about the possibility to apply . . . Read full entry »


Re: Modern talking

Posted 8/28/2017 5:15:03 PM

I really hope that XQuery can continue to be extended because it has a clean data model and makes working on/querying texts simply immediate. Besides file and OS functions, I think that another XQuery Update Facility would be welcome (I hope the 3.0 draft will be soon a recommendation).Best,Giusepp . . . Read full entry »


Re: XPath +/- etc not first class functions

Posted 8/28/2017 4:38:59 PM

> Two problems with that: > (a) it would need syntax extensions rather than just a function library, and Yes, and this can be dealt with in a new version of XPath > (b) operators are polymorphic in a way that functions aren't (which is why we have the long names). Wasn't the new xs:nu . . . Read full entry »


Re: Modern talking

Posted 8/28/2017 4:05:10 PM

On Mon, Aug 28, 2017 at 3:19 PM, Michael Kay <mike@saxonica.com> wrote:For my part, I've always been a technician, not a visionary. I just try to make things work. I'm happy to leave the vision thing to others.​As am I.  Maybe we should think in te . . . Read full entry »


Re: XPath +/- etc not first class functions

Posted 8/28/2017 2:12:44 PM

On Mon, Aug 28, 2017 at 4:47 AM, Michael Kay <mike@saxonica.com> wrote:The absence of an example in the spec doesn't mean that something can't be done. (The XPath expression //.. never appears in the spec, but it is perfectly legal and even potent . . . Read full entry »


Re: XPath +/- etc not first class functions

Posted 8/28/2017 1:58:25 PM

On Mon, Aug 28, 2017 at 1:47 PM, Michael Kay <mike@saxonica.com> wrote: > Yes: perhaps this could be the shortest EXPath spec ever. > Just define a binding of the op prefix to the namespace http://expath.org/ns/operators and you're do . . . Read full entry »


Re: XPath +/- etc not first class functions

Posted 8/28/2017 12:37:49 PM

Add() and Subtract() have been part of FXSL (http://fxsl.sourceforge.net/) since 2001. There are a lot of other useful functions in FXSL (corresponding to almost all functions in Haskell's Prelude module) that aren't defined in the XPath/XQuery FO standard. I must find some time to produce FXSL . . . Read full entry »


Re: XPath +/- etc not first class functions

Posted 8/28/2017 9:47:15 AM

The absence of an example in the spec doesn't mean that something can't be done. (The XPath expression //.. never appears in the spec, but it is perfectly legal and even potentially useful).But yes. + and - are operators (not "primitives"), and operators are not functions. You can easily wrap a fun . . . Read full entry »


Re: Modern talking

Posted 8/28/2017 5:38:39 AM

Thank you very much for these points concerning public interest and the danger of immature decisions.Valid as they are, I think the heart of the problem lies elsewhere: it is the lack of vision. Kolodopolus spoke of a "unified view of information", revolving around values and expressions. This is r . . . Read full entry »


XPath +/- etc not first class functions

Posted 8/28/2017 2:00:01 AM

The examples at https://www.w3.org/TR/xpath-functions-31/#func-fold-leftwould seem to suggest that primitives such as + and - cannot be passed as values. Correct? . . . Read full entry »


Re: Modern talking

Posted 8/27/2017 8:16:02 PM

> > i can't give you an official answer on behalf of W3C, but i can tell > you the simple reality: we only get three or four people turning up to > XQuery meetings, and the Working Group doesn't have resources to get > more than errata done. If we could find maybe thirty or a hundr . . . Read full entry »


Re: Modern talking

Posted 8/27/2017 2:51:40 PM

On Sun, 2017-08-27 at 12:15 +0000, Hans-Juergen Rennau wrote: > [...] > G: Not bad. I notice you use extension functions defined by BaseX, > not part of the official standard.K: That's right.G: So when will the > next version of the standard be out, to make such things possible in > . . . Read full entry »


Re: Posed. Why does distinct-values not yield distinctvalues o

Posted 8/27/2017 2:08:38 PM

Hi Ihe,    (      <benefitStartDate>20170101</benefitStartDate>,<benefitEndDate>20170301</benefitEndDate>,      <benefitStartDate>20170101</benefitStartDate>,<benefitEndDate>20170501</benefitEndDate>    . . . Read full entry »


Modern talking

Posted 8/27/2017 12:15:58 PM

Recently, drowsing in a park, I became an involuntary witness of the following conversation.Kolodopolus: Do you know what XQuery is?Gaius: Sure, kind of SQL for XML, right?K: I do not think that you understood well.G: (raises eyebrows)K: XQuery is a unified view of information. G: Pardon?K: A view . . . Read full entry »


Re: Posed. Why does distinct-values not yield distinctvalues o

Posted 8/27/2017 9:10:21 AM

True dat.On Sun, Aug 27, 2017 at 8:08 AM, Michael Seiferle <ms@basex.org> wrote:Hi Ihe,    (      <benefitStartDate>20170101</benefitStartDate>,<benefitEndDate>20170301</benefitEndDate>,      <benefitStartDate>20170101 . . . Read full entry »


Re: Posed. Why does distinct-values not yield distinct values on anon-at

Posted 8/27/2017 7:13:50 AM

I know that a solution is to atomize the sequence prior to applying distinct-values. My question is why I have to do that in the first placeOn Sun, Aug 27, 2017 at 7:09 AM, Ihe Onwuka <ihe.onwuka@gmail.com> wrote:https://stackoverflow.com/questions/4590428 . . . Read full entry »


Posed. Why does distinct-values not yield distinct values on anon-atomiz

Posted 8/27/2017 7:09:07 AM

https://stackoverflow.com/questions/45904288/why-does-distinct-values-not-yield-distinct-values-on-a-non-atomized-sequence . . . Read full entry »


Re: XML vs JSON

Posted 8/24/2017 5:59:36 AM

While we are on the subject of programming languages perhaps this pithy observation by James Fuller  might divert attention back to the the heart of the issue.There is a difference between a lazy Perl programmer and a lazy _javascript_ programmer.On Mon, Aug 21, 2017 at 6:33 PM, Peter Flynn <&#x . . . Read full entry »


Expat 2.2.4 released

Posted 8/23/2017 7:11:42 PM

Hello everyone, Expat 2.2.4 [1] has recently been released. It features one major bugfix regarding files encoded as UTF-8, and improvements to the build system. If you are using a more ancient version of Visual Studio like 2012, please check the post-2.2.4 commits in Git for related fixes to co . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 11:33:51 PM

On 21/08/17 18:04, Ihe Onwuka wrote: > On Mon, Aug 21, 2017 at 12:47 PM, Peter Flynn <peter@silmaril.ie> wrote: > > [...] The most frequently-quoted objection was "IDs have to start > with a letter? What kind of **** is this? Ours all begin wi . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 5:47:31 PM

On 21/08/17 09:44, Michael Kay wrote: >> A document-oriented XML document looks more like an HTML page with >> mixed content, XHTML and docbook being two prominent examples: >> >> <paragraph>This is <bold>bold</bold> text and this is >> <italic> . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 2:49:18 PM

On Mon, 2017-08-21 at 13:04 -0400, Ihe Onwuka wrote: > > None of C++, Java, Javascript or Python allow you to start an ID with > a digit. Actually C and C++ IDs are pointers, which are numeric. Fortran IV let you start a variable name with a digit, but identifiers are not in general th . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 1:37:44 PM

I agree with Ghislain's points. Thank you.On 21 August 2017 at 13:13, Ghislain Fourny <gfourny@inf.ethz.ch> wrote:Dear Hans-Jürgen, > could you venture a definition of the term "document" in this context? The . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 1:04:47 PM

On Mon, Aug 21, 2017 at 12:47 PM, Peter Flynn <peter@silmaril.ie> wrote: We also should not forget that XML-DATA was a latecomer to the party when XML was being assembled. Lots of people jumped on that bandwagon because it leveraged an exi . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 12:59:21 PM

Sort of. It is possible, with XQuery, to do basic graph queries, but the code to do so gets recursive and expensive quickly. (RDFXML is useful primarily as a wire format, and you can't use ordinary id/idref pairs because they assume intra-document references). Kurt CagleFounder, Semantical LLCk . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 12:55:20 PM

On 8/21/2017 10:44 AM, Kurt Cagle wrote: Tom, You don't NEED RDF but it can be a useful tool nonetheless. Well, sure, I'm not saying otherwise, but there are lots of conventions (you can regard RDF-XML as a convention!) that do things that *can* be done with plain XML. TomP On Mon, Aug 21, . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 10:42:25 AM

Well, if your sentence ..."The key difference is that JSON is designed to make it easy for programs to exchange data with each other, whereas XML is designed to represent documents."must be read with "documents" meaning document-oriented (or narrative, or simply - mixed-content) XML, it does not . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 10:41:45 AM

On 8/21/2017 2:22 AM, Ghislain Fourny wrote: I agree with this statement, but I would add that it is very important to distinguish between the core data models of XML (infoset, PSVI, XDM) and other data models it is able to support indirectly. XML primarily -- natively -- has a tree-based data mo . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 10:40:19 AM

I was about to say, I know that _javascript_ has the can't start with digit restriction. Kurt CagleFounder, Semantical LLCkurtcagle@gmail.com443-837-8725 On Mon, Aug 21, 2017 at 10:04 AM, Ihe Onwuka <ihe.onwuka . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 9:44:31 AM

Tom,You don't NEED RDF but it can be a useful tool nonetheless. Kurt CagleFounder, Semantical LLCkurtcagle@gmail.com443-837-8725 On Mon, Aug 21, 2017 at 9:41 AM, Thomas Passin <list1@tompassin.net> . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 9:44:16 AM

> > A document-oriented XML document looks more like an HTML page with mixed content, XHTML and docbook being two prominent examples: > > <paragraph>This is <bold>bold</bold> text and this is <italic>italic</italic> text</paragraph> > I like t . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 9:05:10 AM

Hi Mike, Interestingly, the XBRL community had the exact opposite epiphany: when they realized that one can tag a human-readable text (aka a fiscal report, in HTML) with context here and there (such as: this number is our company's revenue of last year in US dollars, or, this paragraph is a policy . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 8:22:50 AM

Hi Thomas, > On 19 Aug 2017, at 00:57, Thomas Passin <list1@tompassin.net> wrote: > >> Unless the purpose is broadened to: tree-structured information. > > Don't be stingy... XML can represent graphs too. > I agree with . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 7:43:05 AM

Dear Hans-Jürgen, > could you venture a definition of the term "document" in this context? There is a distinction commonly made in XML: data-oriented vs. document-oriented (even though I am not sure if this terminology is settled). A data-oriented XML document looks like recor . . . Read full entry »


Re: XML vs JSON

Posted 8/21/2017 1:05:07 AM

My own two cents:https://www.linkedin.com/pulse/smackdown-xml-vs-json-kurt-cagleKurt CagleFounder, Semantical LLCkurtcagle@gmail.com443-837-8725 On Mon, Aug 21, 2017 at 12:43 AM, Ghislain Fourny <gfourny@inf . . . Read full entry »


Re: XML vs JSON

Posted 8/19/2017 6:14:40 AM

JSON is built on two structures:A collection of name/value pairs. In various languages, this is realized as an object, record, struct, dictionary, hash table, keyed list, or associative array.An ordered list of values. In most languages, this is realized as an array, vector, list, or sequence.These . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 10:59:06 PM

On 18/08/17 20:44, Hans-Juergen Rennau wrote: [snip] > And if > > <getFlights> > <departureAirport>CGN</departureAirport> > <departureDate>2017-08-18</departureDate> > </getFlights> > > is a document, as I would suppose (as i . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 10:54:12 PM

On 18/08/17 14:27, Ihe Onwuka wrote: > JSON is a data format [snip] > So why should my relational database speak JSON. I rest my case :-) ///Peter . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 10:26:36 PM

Agreed, Peter, but then Michael's assertion would amount to "XML is designed to represent XML data". The point is whether or not statements about the "purpose" of XML can really be upheld. Unless the purpose is broadened to: tree-structured information. Peter Flynn <peter@ . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 7:44:17 PM

Michael, when writing  ..."The key difference is that JSON is designed to make it easy for programs to exchange data with each other, whereas XML is designed to represent documents."could you venture a definition of the term "document" in this context?And if<getFlights>    &n . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 6:06:44 PM

These are universal data structures. Virtually all modern programming languages support them in one form or another. Not just modern ones. COBOL records are pretty much isomorphic to JSON objects, give or take a few aberrations like REDEFINES.The key difference is that JSON is designed to make . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 4:57:18 PM

On 8/18/2017 4:26 PM, Hans-Juergen Rennau wrote: Agreed, Peter, but then Michael's assertion would amount to "XML is designed to represent XML data". The point is whether or not statements about the "purpose" of XML can really be upheld. "Documents": mixed text and . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 2:57:21 PM

Dear Ihe, I just have a few spontaneous comments. > > The last sentence in the above definition begs a number of questions. > > 1. Does it then follow that a data format should ONLY be based on those 2 structures. I agree with the difficulty to justify “only", howeve . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 9:27:46 AM

JSON is a data format On Fri, Aug 18, 2017 at 3:51 AM, Peter Flynn <peter@silmaril.ie> wrote: I am still looking for a volunteer author to write a few paragraphs for the XML FAQ explaining what JSON is and why one might want to use it instead of XML . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 8:51:05 AM

I am still looking for a volunteer author to write a few paragraphs for the XML FAQ explaining what JSON is and why one might want to use it instead of XML. Please form an orderly queue... ///Peter On 18 August 2017 04:10:35 Mukul Gandhi <gandhi.mukul@gm . . . Read full entry »


Re: XML vs JSON

Posted 8/18/2017 8:39:33 AM

Thanks Elliotte, for your comments. I agree.I think that query from a JSON document is possible via an API (after the output of JSON parse). This is not same in sense as querying an XML document (for e.g using XQuery or only XPath), but similar to for e.g the XML DOM APIs.On 17 August 2017 at 23:57 . . . Read full entry »


Re: XML vs JSON

Posted 8/17/2017 2:27:47 PM

The real advantage of XML is when you can integrate the whole toolchain into your processing: schema validators, XPath, XSLT, etc. If you just want to pass a few name value pairs and lists back and forth, sure, use JSON. But as the documents become complex and you need to query and transform them, . . . Read full entry »


Re: XML vs JSON

Posted 8/17/2017 12:02:51 PM

On 17 August 2017 at 04:33, Liam R. E. Quin <liam@w3.org> wrote: Another way to say this that I use, saying essentially the same thing, is that JSON tends to win when the programmer is in control of the format and XML tends to win when the author of the docu . . . Read full entry »


Re: XML vs JSON

Posted 8/16/2017 7:03:34 PM

On Tue, 2017-08-01 at 10:12 -0400, G. Ken Holman wrote: > > [long and fascinating account elided] > I keep getting back to horses for courses:  use XML for generalized  > interchange and use JSON for the tight binding between systems  > sharing identical in-memory representations. . . . Read full entry »


Re: Converting schema to schematron

Posted 8/14/2017 6:38:01 PM

Yes, I think the availability of maps with dynamically allocated keys is a game changer, as far as this kind of complex pipelines is concerned. Being able to read the in-progress output tree would be a real help too, if it could be checkpointed to overcome the lack of execution order certainty.(I g . . . Read full entry »


Re: Converting schema to schematron

Posted 8/14/2017 5:07:26 PM

This was a tool my old company Topologi made for JSTOR, in part as an R&D project to explore the viability of the area (and becase JSTOR needed it). So it was strictly limited to only implementing the things that JSTOR needed, and we also decided to only use XSLT 2 for it.   The takeaways I got . . . Read full entry »


Re: Converting schema to schematron

Posted 8/14/2017 8:54:45 AM

> > 3) It is difficult to structure and handle so many steps in a pipeline with XSLT. There were lots of parts where a language with mutable tree would have been much more straightforward. John Lumley has been working on (and presented at Balisage) an implementation of XSLT written in XSLT . . . Read full entry »


Re: Converting schema to schematron

Posted 8/14/2017 8:53:16 AM

Hi Mike, > Once you have this basic support at the data structure level, you probably need to introduce operations that take advantage of it: rather like map:put which creates a new map as a modified copy of an existing map, with a delta implementation underneath, you need operations that creat . . . Read full entry »


Re: Converting schema to schematron

Posted 8/13/2017 4:25:24 PM

Is this what you seek, Tom?https://github.com/Schematron/schematron/tree/master/trunk/xsd2schRegards,Andrew Virus-free. www.avast.com On 12 August 2017 at 18:07, yamahito <yamahito@gmail.com> wrote:Hi all,I can find various refere . . . Read full entry »


Converting schema to schematron

Posted 8/12/2017 5:07:08 PM

Hi all,I can find various references online to an open source (xslt?) conversion from schema to schematron, including one reference by Rick Jelliffe to an implementation on github.However, I can't find it anywhere...Does anyone know if there is such a tool available for use?Thanks!Tom  . . . Read full entry »


Re: An OWL ontology for topic maps

Posted 8/10/2017 12:19:01 PM

You might want to make your web server serve it as application/octet-stream or something because my browser wants to parse it as XML. The work itself is interesting, though. I recall discussions about a canonical OWL schema and RDF representation for topic maps years ago which however wasn't final . . . Read full entry »


"In defense of XML - By focussing on where XML came from, supportersof e

Posted 8/10/2017 11:47:17 AM

Dear colleagues, I'm posting this link about a discussion going on at reddit because I know you like to discuss such things here, and find myself agreeing with the article, and also to bring a public discussion to your attention, where for once, XML "wins". Hope you enjoy it. https://ww . . . Read full entry »


Expat 2.2.3 released, includes security fixes for Windows

Posted 8/2/2017 9:32:14 PM

Hi! Just a quick note that Expat 2.2.3 has been released. For Windows users, it fixes DLL hijacking (CVE-2017-11742 [1]). On Linux, extracting entropy for Hash DoS protection no longer blocks, which affected D-Bus and systems that are low on entropy early in the boot process. For more details, pl . . . Read full entry »


Re: XML vs JSON

Posted 8/2/2017 11:09:04 AM

Thanks Ken.On 1 August 2017 at 19:42, G. Ken Holman <gkholman@cranesoftwrights.com> wrote:I have not reached the same conclusion as you that "JSON's major use case is in the use within REST&quo . . . Read full entry »


An OWL ontology for topic maps

Posted 8/2/2017 7:04:28 AM

To get myself back into ontologies, I wrote an ontology for the Topic Maps Data Model.  It's available under the 2-clause BSD license (it says here) in Manchester notation at <http://vrici.lojban.org/~cowan/tmo.owl>.Comments welcome.-- John Cowan          http://vrici.lojban.org/~cowan   . . . Read full entry »


Re: XML vs JSON

Posted 8/1/2017 6:40:34 PM

The reason this is a thing is because JSON is being pushed into domains that it was not designed for and  totally unsuited for.Huge amounts of time and money are being spent on JSON support in domains where JSON has no business being (complex data interchange models like NIEM, UML etc) for the wron . . . Read full entry »


Re: XML vs JSON

Posted 8/1/2017 6:07:00 PM

On Tue, Aug 1, 2017 at 1:54 PM, Thomas Passin <list1@tompassin.net> wrote:Many of the responses so far seem to assume that the server's output will be consumed by a web browser, and be processed with _javascript_. But if we're talk . . . Read full entry »


XML vs JSON

Posted 8/1/2017 5:04:41 PM

Hello,    I don't intend to spark a bitter debate between XML & JSON, where the outcome of debate is win of one over other. Rather, I wish to present in a friendly manner, according to me, where these two technologies differ.When talking about designing REST services, JSON seems to clearly . . . Read full entry »


Re: XML vs JSON

Posted 8/1/2017 4:36:21 PM

On 1 August 2017 at 16:14, Paul Denning <pauld@mitre.org> wrote: Agree JSON is fit for purpose where the coupling is tight, i.e., the _javascript_ running on the browser is typically sent from the server.  The server code an . . . Read full entry »


Re: XML vs JSON

Posted 8/1/2017 4:10:30 PM

On 2017-08-01 14:58, Thomas Passin wrote: ... You personally may think it is "easier" to extract the data from a JSON response compared with an XML response, or you personally may happen to encounter more JSON interfaces, but others have different experiences and would be happier with . . . Read full entry »


RE: XML vs JSON

Posted 8/1/2017 3:12:12 PM

> -----Original Message----- > From: Julian Reschke [mailto:julian.reschke@gmx.de] > Sent: August 1, 2017 10:11 > To: Thomas Passin <list1@tompassin.net>; xml-dev@l... > Subject: Re . . . Read full entry »


Re: XML vs JSON

Posted 8/1/2017 1:54:58 PM

On 8/1/2017 7:34 AM, Mukul Gandhi wrote: Hello, I don't intend to spark a bitter debate between XML & JSON, where the outcome of debate is win of one over other. Rather, I wish to present in a friendly manner, according to me, where these two technologies differ. When talking about desig . . . Read full entry »


Re: XML vs JSON

Posted 8/1/2017 11:14:17 AM

Agree JSON is fit for purpose where the coupling is tight, i.e., the _javascript_ running on the browser is typically sent from the server.  The server code and the _javascript_ sent to the browser are managed as a tightly coupled pair.  If the server needs to change, the . . . Read full entry »


Re: XML vs JSON

Posted 8/1/2017 10:12:34 AM

I do not consider myself an "expert" in the comparison of JSON and XML, but I thought I would offer my own observations. In my work with UBL we have been pressured to support both syntaxes, much to my chagrin and reluctance. Accordingly, I proposed the JSON serialization of UBL that . . . Read full entry »


Re: XML vs JSON

Posted 8/1/2017 8:58:28 AM

On 8/1/2017 7:34 AM, Mukul Gandhi wrote: When talking about designing REST services, JSON seems to clearly win. The whole software world seems to be biased in favour of JSON it seems, for this criteria. Although I have read, that in many cases REST services can use XML instead of JSON. I think, JS . . . Read full entry »


ANN: A gentle introduction to software modeling and analysis

Posted 7/16/2017 6:21:29 PM

Hi Folks, I created a slide-deck, titled: A Gentle Introduction to Software Modeling & Analysis http://www.xfront.com/Alloy/Gentle-Introduction-to-Modeling-and-Analysis.pptx Modeling is, of course, an important part of XML development. /Roger . . . Read full entry »


Expat 2.2.2 released

Posted 7/14/2017 7:42:41 PM

Hi! Just a quick pointer to the article on XML.com with details: Expat 2.2.2 released https://www.xml.com/news/2017-07-expat-222-released/ Best Sebastian . . . Read full entry »


Re: Why you should not design JSON data models

Posted 7/3/2017 10:22:08 PM

On Mon, Jul 3, 2017 at 7:47 AM, Ghislain Fourny <gfourny@inf.ethz.ch> wrote: Dear Ihe, I partly agree, partly disagree. Here are a few thoughts. 1. I would not discard JSON as a viable syntax for arborescent data, and neither would I discard XML. Each of t . . . Read full entry »


Re: Why you should not design JSON data models

Posted 7/3/2017 1:18:29 PM

On Mon, Jul 3, 2017 at 7:47 AM, Ghislain Fourny <gfourny@inf.ethz.ch> wrote: Dear Ihe, I partly agree, partly disagree. Here are a few thoughts. 1. I would not discard JSON as a viable syntax for arborescent data, and neither would I discard XML. Eac . . . Read full entry »



PURCHASE STYLUS STUDIO ONLINE TODAY!!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Attend a Live Webinar This Week!

Learn about Stylus Studio's unique features and benefits in just under an hour. Register for the Stylus Studio QuickStart Training WebCast!

Why Pay More for XML Tools?

With Stylus Studio® X14 XML Enterprise Suite, you get the most comprehensive XML tool suite at one incredibly low price. Value: it's just one of many reasons why smart XML developers are choosing Stylus Studio!

 
Free Stylus Studio XML Training:
W3C Member