XSLT, XQuery, XSL-FO Training in the SF Bay Area

[ANN] Complete Balisage 2009 Program posted

The complete Balisage: The Markup Conference 2009 program, including 
late-breaking news, has just been posted.

   * Detailed program: http://www.balisage.net/2009/Program.html
   * Schedule at a Glance:  http://www.balisage.net/2009/At-A-Glance.html

Balisage 2009 is the place to come to think about XML, and about 
markup. The Balisage program varies from the practical to the 
theoretical, with a little heresy mixed in:

   * Practical
      - pipelines
      - creating XML schemas from UML
      - editing tools
      - version control for XML documents
      - checking and validating XML documents

   * Real-world Uses of XML
      - healthcare
      - large humanities datasets
      - archives

   * Overlap and complex documents
      - TEI feature structures
      - encoding non-hierarchical structures in RDF
      - tagging and manipulating structures that are not well managed
         as trees

   * Proposed changes
      - to XML Namespaces
      - extensions to XPath

   * Theoretical
      - nature of documents
      - analysis of marked-up texts
      - the process of marking up documents

   * Future
      - XML in the browser
      - visual designers
      - XML and open data

Balisage is the place for data modelers, software engineers, 
librarians, ontologists and taxonomists, document managers, standards 
developers, system architects, archivists, markup theoreticians and 
practitioners, and kindred spirits to talk with each other. Indulge 
your inner markup geek at Balisage 2009 this August in Montreal.
-- 
======================================================================
Balisage: The Markup Conference 2009          mailto:info <at> balisage.net
August 11-14, 2009                             http://www.balisage.net
Processing XML Efficiently: August 10, 2009           Montreal, Canada
======================================================================

_______________________________________________________________________

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

interesting: xmlvm

Hi,

This looks interesting:

http://www.xmlvm.org/overview/

"Overview

The goal of XMLVM is to offer a flexible and extensible cross-compiler  
toolchain. Instead of cross-compiling on a source code level, XMLVM  
cross-compiles byte code instructions from Sun Microsystem's virtual  
machine and Microsoft's Common Language Runtime. The benefit of this  
approach is that byte code instructions are easier to cross-compile  
and the difficult parsing of a high-level programming language is left  
to a regular compiler. In XMLVM, byte code-based programs are  
represented as XML documents. This allows manipulation and translation  
of XMLVM-based programs using advanced XML technologies such as XSLT,  
XQuery, and XPath."

Anybody played around with this? Opinions :)

best,
-Rob

p.s. apologies if you received a bounce from me. Moved back to SF and  
had issues with altering my mail settings.

_______________________________________________________________________

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

What entities do you use for common XML dialects?

Hi,

I would like to get links to or examples of entities that people
return to again and again for common XML dialects.

In this case I am not talking about the obvious ones for XHTML etc.
but the more esoteric uses such as entities with markup for expansion
in processing chains.

Do you find that there are entities that you use a lot for particular
dialects to assemble XML for processing?

Normally the entities I see are for Docbook, XHTML, MathML...
I am wondering about if people have entities they use a lot for XSLT,
XSL-FO, SVG, XSD, XBRL...that vary significantly from the XHTML
entities..

As an aside on this - I want to find XML Catalogs maintained by
various organizations, if you do not know the location of the XML
Catalog or the purpose of it but just want to find every incident of
an XML Catalog how would you do it (aside from the obvious write a
webcrawler), does anyone have a search engine trick, know a central
resource that tries to maintain lists of all catalogs (for example
some part of XML Coverpages or a way to search there that tells me
every XML Catalog they have listed)

Best Regards,
Bryan Rasmussen

_______________________________________________________________________

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

Re: generate common xml shema from multiple xml instances

I think a Weighted Likelihood algorithm of some sort would be usable
(although what the weights should be I'm unsure), for example
something like:

User says they would like to Generate Enumerations - this could
actually be used as how would you like to Generate Enumerations -
never generate enumerations, only generate enumerations if highly
certain, generate enumerations where likely, Always Generate
Enumerations..

Check if node for set of documents is likely to be enumeration,
variations to check for would be:

No Whitespace - most enumerations are non whitespace, give user
opportunity to allow whitespace in enumeration. If whitespace found
and no whitespace allowed in enumeration then type is just string.

If there is whitespace allowed I would also note that the the node
would probably still have some regularity that could be used to
determine if it was likely to  be an enumeration.

Do values repeat in any of these documents:
if for example we have a set with 100 nodes with all different values
we could have an enumeration with 100 values, but if the nodes
sometimes repeat values that would increase the chance of it being an
enumeration. I think the way the question was first phrased would be
to be able to generate enumerations based on giving something like

RED
GREEN
ORANGE
BLUE

This gives us pretty good clues to guess it is an enumeration - one
the size of the data in each instance is pretty close to each other,
they are all letters in  a particular alphabet, they are words
(wordnet turns them up)

I think an algorithm could be written to make this an enumeration
pretty easily. However in situations like this you like it if your
inputs can guide you, if the rule of the application was that

RED
GREEN
ORANGE
BLUE
RED

Has a 20% higher chance of being an enumeration than
RED
GREEN
ORANGE
BLUE
that would be useful.

On Thu, Jun 18, 2009 at 8:30 AM, Paul
Spencer<xml-dev-list <at> boynings.co.uk> wrote:
> XML to schema tools tend to allow the user to set various options. For example, XML Spy asks if you want to
create enumerations or not. If you had a single instance, you might just get
>
> <xs:simpleType name="Color">
>  <xs:restriction base="xs:string">
>    <xs:enumeration value="RED" />
>  </xs:restriction>
> </xs:simpleType>
>
> As Mukul says, it is then up to the schema author to fix this. I saw the original message as trying to improve
this "first cut" by taking account of several instance documents. The complexity of the tool goes up
markedly with more than one instance. For example, how would you handle this:
>
> Instance 1
> <a>
>  <b/>
>  <c/>
> </a>
>
> Instance 2
> <a>
>  <b/>
>  <d/>
> </a>
>
> Is there a choice between c and d? Or are both optional? If optional, which order do they go in?

I think this part actually comes into the thing stated above it being
a weighted likelihood algorithm and the choice of user inputs.

When you say: The complexity of the tool goes up markedly with more
than one instance.
you mean not just the complexity of programming but also the
complexity of making the right choice, but these should probably be
separated.

The complexity of programming goes up markedly with more than one
instance, but the complexity of making the right choice goes down
after some point if there is some guiding repetition:

 Instance 1
 <a>
  <b/>
  <c/>
 </a>

 Instance 2
 <a>
  <b/>
  <d/>
 </a>

Instance 3
 <a>
  <b/>
  <c/>
  <d/>
 </a>

furthermore just as you can ask the user  - do you want to make
enumerations - you can ask do you want to generate choices

the choice is generally less used than cardinality games therefore I
suppose the default would be to go to minOccurs= 0
the problem then is, as you noted, how to get things to be in the
right order. The right order problem decreases if we have multiple
instances that adumbrates the order.

The problems with this are of course -
1. if it takes 100 instances to get something good out you would
probably write a schema :)
2. The likely UI for a tool that allowed you to do this would be crap,
or it would be a command line tool which would be pretty sweet I
guess.

finally - I think actually it would be easier to write something that
generated Schematron schemas based on multiple outputs that handled a
weighted likelihood algorithm in the generation than something that
generated XSD - or maybe I just mean it would be more enjoyable.

Cheers,
Bryan Rasmussen

_______________________________________________________________________

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 10.3

Hi,

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

The 10.3 version comes with improvements on the visual XML editing like 
new extension APIs, automatic ID generation, etc. as well as on the XML 
development side.
One important new development feature is the Component Dependencies view 
  (available for  XSLT, XML Schema, Relax NG and NVDL) that shows a tree 
of component dependencies starting with a specified component.

The complete list of new additions (37 items) and more details can be 
found here:
http://www.oxygenxml.com/index.html#new-version

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

targetNamespace vs default namespace

RE: targetNamespace vs default namespace

	A customer gave us an xml schema having different default ns and
targetNamspace, like that:
	<xsd:schema xmlns="ProprietaryNamespace"
targetNamespace="AnotherProprietaryNamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	...
	    <xsd:complexType name="complexTypeOne">
	        <xsd:sequence>
	            ...
	            <xsd:element name="SubElementWithoutPrefix"
type="ElementTypeWithoutPrefix" /> <!-- a line with a problem -->
	        </xsd:sequence>
	    </xsd:complexType>
	    ...
	</xsd:schema>
	
	Now we have problem validating values of SubElementWithoutPrefix on
different java plattforms.
	
	According to the XML schema specification, every element/attribute
without namespace prefix belongs to the default namespace.

MHK> No, that's not the case. Generally, the "name" attribute contains a
local name, which is combined with the targetNamespace of the schema
document. Attributes that refer to another schema component, such as "type",
are QNames in which no prefix means "default namespace".

	On the other hand, unqualified elements defined in an xml schema
belong to the schemas targetNamespace.

MHK> Only if form="qualified" or elementFormDefault="qualified" (which is
present in most schema documents but not, apparently, in this one). Without
this, a locally-declared element, as here, is in no namespace, it is not in
the targetNamespace.

 So, there is this contradicition
	to be resolved.
	
	When SUNs Java 6 implementation resolves it, SubElementWithoutPrefix
belongs to the default namespace. On the other hand,
	when IBMs java 5 implementation resolves it, SubElementWithoutPrefix
belongs to the targetNamespace.
	
	How is it defined in XML schema specs?

MHK> Neither of the above. SubElementWithoutPrefix should be in no
namespace.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 	

_______________________________________________________________________

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

Re: targetNamespace vs default namespace

Hi Tama,

Some of your comments are incorrect, or perhaps imprecise.  For example:

> According to the XML schema specification, every element/attribute without 
> namespace prefix belongs to the default namespace.

This is really specified in the XML namespaces specification.  So the 
sentence should read something like:

According to the XML {schema}->{namespace} specification, every element 
{/attribute}->{} without namespace prefix belongs to the default namespace 
{}->{if such a namespace has been defined, otherwise no they belong to no 
namespace}.

Note that attributes have slightly different rules.  No namespace prefix 
ALWAYS means no namespace.

> On the other hand, unqualified elements defined in an xml schema belong to 
> {the schemas targetNamespace}->{no namespace}. {}->{Qualified elements 
> defined in an xml schema belong to the schemas targetNamespace.}

(I hope you understand my change markup notation.  As change marks are a bit 
difficult to do in text only e-mails I've done {ABC}->{DEF} to indicate that 
the text ABC should be changed to DEF.  {}->{DEF} equates to add text DEF, 
{ABC}->{} equates to delete ABC.)

The correct behavior here depends on the value of the elementFormDefault 
attribute in the xs:schema element.  If it's absent, then by default 
elements are unqualified.  That means that SubElementWithoutPrefix belongs 
to no namespace.

Which means that, as global elements are always qualified irrespective of 
the value of elementFormDefault, your XML instance (pretty much) HAS to 
define a non-default xml namespace prefix for use with the top level element 
name, and then elements like SubElementWithoutPrefix can be unprefixed and 
belong to no namespace.  e.g.

<ns:top xmlns:ns='AnotherProprietaryNamespace'>
    <SubElementWithoutPrefix>...</SubElementWithoutPrefix>
</ns:top>

HTH,

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using XML C++
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
for more info
----- Original Message ----- 
From: "REV Tamas" <tamas.rev <at> gmail.com>
To: <xml-dev <at> lists.xml.org>
Sent: Monday, July 06, 2009 4:35 PM
Subject: [xml-dev] targetNamespace vs default namespace

> Hello,
>
> A customer gave us an xml schema having different default ns and
> targetNamspace, like that:
> <xsd:schema xmlns="ProprietaryNamespace"
> targetNamespace="AnotherProprietaryNamespace" xmlns:xsd="
> http://www.w3.org/2001/XMLSchema">
> ...
>    <xsd:complexType name="complexTypeOne">
>        <xsd:sequence>
>            ...
>            <xsd:element name="SubElementWithoutPrefix"
> type="ElementTypeWithoutPrefix" /> <!-- a line with a problem -->
>        </xsd:sequence>
>    </xsd:complexType>
>    ...
> </xsd:schema>
>
> Now we have problem validating values of SubElementWithoutPrefix on
> different java plattforms.
>
> According to the XML schema specification, every element/attribute without
> namespace prefix belongs to the default namespace.
> On the other hand, unqualified elements defined in an xml schema belong to
> the schemas targetNamespace. So, there is this contradicition
> to be resolved.
>
> When SUNs Java 6 implementation resolves it, SubElementWithoutPrefix 
> belongs
> to the default namespace. On the other hand,
> when IBMs java 5 implementation resolves it, SubElementWithoutPrefix 
> belongs
> to the targetNamespace.
>
> How is it defined in XML schema specs?
>
> Best Regards,
> Tamas
> 

_______________________________________________________________________

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

Re: targetNamespace vs default namespace

----- Original Message From: "REV Tamas"

> Hi Pete,
>
> Thank you for your reply. It made me realize that I omitted some important
> data: the schema has elementFormDefault="qualified" and
> attributeFormDefault="unqualified":
>
> <xsd:schema xmlns="ProprietaryNamespace" targetNamespace="
> AnotherProprietaryNamespace"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
> elementFormDefault="qualified"
> attributeFormDefault="unqualified"
> xmlns:abc="YetAnotherPropriateryNamespace">
> ...
>    <xsd:complexType name="complexTypeOne">
>        <xsd:sequence>
>            ...
>            <xsd:element name="SubElementWithoutPrefix"
> type="ElementTypeWithoutPrefix" /> <!-- a line with a problem -->
>        </xsd:sequence>
>    </xsd:complexType>
>    ...
> </xsd:schema>
>
> This is the schema "as is" the customer gave us. This schema belongs to 
> the
> interface definition of a webservice.
> One of our tasks is to validate the messages sent to this interface. The
> customer gave us test messages too.
>
> ...
>
>
> The corresponding part looks like that:
> <Soapenv:Envelope 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:ns1="AnotherProprietaryNamespace"> <!-- ns1 matches the
> targetNamespace of the schema -->
>    ...
>    <ns1:ComplexEelement>
>        ...
>        <ns1:SubElementWithoutPrefix>trallala</ns1:SubElementWithoutPrefix>
>        ...
>    </ns1:ComplexElement>
>
> If I understand it well, this message excrept conforms to the schema
> excrept, because elementFormDefault="qualified" means that the elements
> conforming to this schema must be qualified with the schemas 
> targetNamspace.

Hi Tama,

This looks right to me.

HTH,

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using XML C++
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
for more info

(cc-ed to xml-dev list in case others want to follow updates.) 

_______________________________________________________________________

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