Last chance to get your JSON/XML speedtest results in before publication !

I am preparing to collect the last set of samples before publication of JSON and XML browser performance
test results,
to be presented at Balisage 2013 (http://www.balisage.net)

If you have not done so, or have and want to try again please take a few minutes to contribute your test results.

What You Do

Go to
   http://speedtest.xmlsh.org

Click "Run Tests And Submit..."
Test takes about 1 - 3 minutes depending on your internet and device speed.

Repeat as often as have patience on as many difference OS's, machines, browser vendors and versions and devices.
I am particularly interested in mobile devices as these have had much less coverage in these kinds of
experiments, but anything you can try is valuable.

Please feel free to pass this link on ... I will be updating the tests pending comments of this initial public
beta and then intend on distributing the test to a wider audience (including full source).

The results are intended to be published publicly at the Balisage 2013 conference and then put online.

Thank you for any assistance and comments.

----------------------------------------
David A. Lee
dlee <at> calldei.com<mailto:dlee <at> calldei.com>
http://www.xmlsh.org

[announce] W3C Workshop/industry consultation event in Paris, September 16th/17th, regarding publishing workflow

I shall be co-chairing a W3C Workshop in Paris in September,
along with Peter Linss of HP, on the area of digital publishing,
particularly to print.

The question is: what changes do we need to make to the Open Web
Platform to make it the obvious suitable choice as a platform for print
publishing? ... e.g....
. authoring in the browser
. content management & workflow
. using CSS and XSLT to generate XHTML for print
  (this obviously includes the question of what needs to be done
  to CSS, polite answers on a postcard please... )
. how to control imposition, binding, finishing,
  all the rest of the workflow to create a physical object
. issues around multiple outputs, marketing, branding...

http://www.w3.org/2012/12/global-publisher/

The event is free to attend (you're on your own for hotels and food
though, and right now we don't have a lunch sponsor), but you have to
submit at least a short position paper. Feel free to contact me directly
if you're not sure about position papers.

I also wrote a blog post about it here:
http://www.w3.org/QA/2013/06/w3c_workshop_industry_consulta.html

Liam

--

-- 

Re: overlapping markup

Hello Oleg,

as the developer of XStandoff I'll try to answer your question.

Standoff annotation was a feasible option for annotating multiple or 
overlapping markup, when XStandoff and its ancestor SGF was developed as 
part of a project.
In addition, we wanted to use an XML-based solution, that is, without 
any extra brackets (the solution you proposed reminds me of XConcur btw.).
There are of course other ways to describe parallel or overlapping 
markup, such as pure LMNL's sawtooth syntax, or others (you may want to 
have a look at the Balisage 2008 and 2009 papers for a list of techniques).

In my opinion, a key benefit of an XML-based solution is the possibility 
to use all the XML-tools such as XML validators, XSLT, and XQuery (and 
in fact, that was our main concern to choose the way we did).

Let me know, if you have further questions.

Regards,

Maik Stührenberg

Oleg Parashchenko schrieb:
> Hello all,
>
> looking at XStandoff and xLMNL examples in the XML Prague 2012 paper "Quo
> vadis XML", I'm a bit confused by theirs complexity. See the pages 150,
> 151 and 155.
>

overlapping markup

Hello all,

looking at XStandoff and xLMNL examples in the XML Prague 2012 paper "Quo
vadis XML", I'm a bit confused by theirs complexity. See the pages 150,
151 and 155.

http://archive.xmlprague.cz/2013/files/xmlprague-2013-proceedings.pdf

If I needed a parallel markup, instead of using these formats, I'd try
something simple, such as:

<dialog_plus_text>
{u who="peter"}<s>Hey Paul!</s> <s>Would you give me{/u}
{u who="Paul"}the hammer?</s>{/u}
</dialog_plus_text>

So, each content model gets its own sort of brackets. What wrong with it,
why such format is not used?

--

-- 
Mit freundlichen Grüßen,

Oleg Parashchenko  olpa <at>  http://uucode.com/
http://uucode.com/blog/  XML, TeX, Python, Mac, Chess

_______________________________________________________________________

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.

Re: Recommendation for XSLT book?

At 2013-06-16 14:36 +0200, =?KOI8-R?B?z8zYx8Egy9LZ1sHOz9fTy8HR?= wrote:
>Can any one recommend a programmers book for learning XSLT?
>
>Olga

I have a number of options for you as I've written an in-depth, 
hands-on XSLT and XPath training class:

   Practical Transformation Using XSLT and XPath
   - covering every element, every attribute and every function
     of XSLT and XPath versions 1.0 and 2.0, used in creating
     new transformations of existing structured information

The materials are written in XML and I use XSLT and XSL-FO to produce 
a number of different products from that single source of content ... 
choose the product to best meet your needs ... some of the options are free:

(1) - 5 hours of free streaming video lecture introducing XSLT/XPath
       versions 1 and 2 (scroll down the page and you'll see a
       number of lectures marked as "free"; you do not need to have
       a Udemy account in order to view the free content):

       http://www.CraneSoftwrights.com/links/udemy-ptux-online.htm

(2) - 24 hours of paid streaming video lecture overviewing every
       element, every attribute and every function of XSLT/XPath
       versions 1 and 2, with hands-on exercises (one-time fee for
       perpetual access by one person):

       http://www.CraneSoftwrights.com/links/udemy-ptux-online.htm

[ANN] Sirix - a versioned XML storage system

What Serializer to Use in a Java SAX Pipe

Hi Folks

Related to my serializer question - but different enough for its own post.

By the way, what do people recommend for a serializer.

I use the trax type code of:

         TransformerFactory transFact = this.getTransformerFactory();
         SAXTransformerFactory saxTFactory = (SAXTransformerFactory)
transFact;
         m_tranHandler = saxTFactory.newTransformerHandler();
         m_transformer = m_tranHandler.getTransformer();

However for getTransformerFactory()

      // TransformerFactory transFact = new
net.sf.saxon.TransformerFactoryImpl();
      // TransformerFactory transFact = new TransformerFactoryImpl();  //
gets the JDK built in one - newInstance did not work.
      //TransformerFactory transFact = TransformerFactory.newInstance();
      // TransformerFactory transFact =
TransformerFactory.newInstance("net.sf.saxon.TransformerFactoryImpl",null);

      TransformerFactory transFact = new
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl();

I can only get the built in xalan factory working well - might be some other
requirements I have  - but curious what people are doing there.
I really don't like reaching into the jdk like that as it is not supported

Also, is there a way on the serializer to turn off DTD defaulted values
without wrapping the serializer and using the Attributes.isSpecified?

Jim

> -----Original Message-----
> From: George Cristian Bina [mailto:george <at> oxygenxml.com]
> Sent: June-11-13 6:22 AM
> To: Michael Kay
> Cc: Jim Tivy; xml-dev <at> lists.xml.org
> Subject: Re: [xml-dev] Processing and Serialization of FIXED attributes
> 
> Hi Mike,
> 
> I think Jim wants this on the serialization part, while -expand:off seems
to apply
> to loading a document. He needs the values for processing the document but
> when the processing is done he does not want to save values that come from
> the DTD/schema.
> 
> Hi Jim,
> 
> The values added by the parser that are not present in the XML document
itself
> can be identified at SAX level by looking at the isSpecified() property -
if this is
> true then the value comes from the document, otherwise the value comes
from
> the DTD/schema. See for example:
> http://xerces.apache.org/xerces2-
>
j/javadocs/api/org/xml/sax/ext/Attributes2.html#isSpecified%28java.lang.Stri
ng
> %29
> 
> Hope this helps!
> 
> Best Regards,
> George
> --
> George Cristian Bina
> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
> 
> On 6/11/13 10:02 AM, Michael Kay wrote:
> > Saxon has an option (-expand:off) to suppress the expansion of fixed
> > attribute values defined in the schema or DTD.
> >
> > Michael Kay
> > Saxonica
> >
> > On 11 Jun 2013, at 04:47, Jim Tivy wrote:
> >
> >> Hello
> >> The DITA XML DTD has a number of #FIXED declarations in the DTDs that
> >> imply fixed values for class attributes.
> >> When this is processed in SAX and serialized the DITA class
> >> attributes are also serialized.
> >> It would be cleaner, for future XML authors to not have to see these
> >> class attributes inlined into the XML document.
> >> Do XSLT or other serializers commonly take out FIXED attributes or
> >> does the infoset mark them so they are not serialized - or is the
> >> usual form to serialize these.
> >> Inhttp://www.w3.org/TR/xslt-xquery-serialization-30/#xml-outputit
> >> states "MAY"
> >>
> >> .  Thereconstructed tree
> >> <http://www.w3.org/TR/xslt-xquery-serialization-30/#reconstructed-tre
> >> e>*MAY*contain
> >> additional attributes and textnodes
> >> <http://www.w3.org/TR/xslt-xquery-serialization-30/#dt-node>resulting
> >> from the expansion of default and fixed values in its DTD or schema;
> >> also, in the presence of a DTD, non-CDATA attributes may lose
> >> whitespace characters as a result of attribute value normalization.
> >>
> >> My question is, what do most java based implementations of XLST
> >> processors, SAX processors and associated serializers do with respect
> >> to inlining or stripping out #FIXED attributes.
> >>
> >> Jim
> >>
> >

_______________________________________________________________________

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 <at> lists.xml.org
subscribe: xml-dev-subscribe <at> lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[ANN] Balisage Late-breaking News Proposals due Friday

Proposals for Late-breaking News slots at Balisage 2013 are due on Friday. 

This is you last change to: 
 - share your markup related news, project, or perspective with 
    your peers
 - speak at Balisage 2013
 - register at speaker rates
 - be published in the Balisage proceedings

For details see: http://www.balisage.net/latebreaking-call.html
questions: info <at> balisage.net

======================================================================
Balisage: The Markup Conference 2013          mailto:info <at> balisage.net
August 6-9, 2013                              http://www.balisage.net
Preconference Symposium                       August 5, 2012
======================================================================

_______________________________________________________________________

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 <at> lists.xml.org
subscribe: xml-dev-subscribe <at> lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[ann] oXygen XML Editor version 15

Hi,

I am happy to announce that a new major version of oXygen XML Editor is 
available from our website:
http://www.oxygenxml.com/

You can find below a highlight of some of the new additions in version 
15 but for the complete list of additions and details (including many 
short video demos) please see
http://www.oxygenxml.com/index.html#new-version

oXygen XML Editor 15.0 streamlines the development of web services with 
major improvements to its WSDL editing support which now features 
intelligent search and refactoring actions, hierarchy and dependencies 
views, context-aware editing assistance and support for generating 
documentation. There are also improvements in working with XML databases 
and in the validation support.

When authoring XML content, you benefit from the improvements to the 
reviewing support, allowing you to easily find changes or annotations 
across all your project files. The power of XML is leveraged by 
providing built-in transformation from DITA and DocBook to 
mobile-friendly WebHelp that allows your users to access your content 
from their mobile devices.

There are many additions to the DITA functionality, including the 
integration of "The DITA Style Guide" by Tony Self, which provides 
immediate access to the relevant style guide topic depending on the 
current editing context.

As usual, oXygen keeps you up-to-date and we updated a number of 
components to better support XSLT, XQuery, XPath, XProc, EPUB, SVN, 
DocBook, TEI and DITA standards.

Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

_______________________________________________________________________

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 <at> lists.xml.org
subscribe: xml-dev-subscribe <at> lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Processing and Serialization of FIXED attributes

PLOS blog about relative merits of XML (JATS) and HTML in workflows