#572 prefix: colon or not?

Syd Bauman

schemaSpec/@prefix is defined as
   "" | data.name

Why, I wonder? Doesn't seem like putting a colon in a prefix is a good idea. (At least, not for RELAX NG schemas, in which every single prefixed pattern would generate an "is not a valid local name" error.)

Ah, look! The ﹤remarks﹥ for this attribute say "Colons, although permitted inside the value, will cause an invalid schema to be generated". Well, at least it is correctly documented.

But wouldn't it be better to just use
   "" | xs:NCName
as the definition? (Or a new "data.localName" if we really insist on indirection.)


  • Sebastian Rahtz

    Sebastian Rahtz - 2013-05-06

    sounds like a corrigible error to me. if we have a tighter datatype, lets use it

    Sebastian Rahtz
    Director (Research) of Academic IT
    University of Oxford IT Services
    13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

  • Syd Bauman

    Syd Bauman - 2013-05-06

    Wow. Turns out we do. data.xmlName already exists. (Mis-named, I fear, since in XML per se a name can contain a colon. But that's a pretty small impact problem :-)

    Change checked in at 12083, let's see if Mr. Jenkins (or anyone else) objects.

  • Syd Bauman

    Syd Bauman - 2013-06-21
    • status: open --> closed-fixed
    • Priority: 5 --> 1(low)
  • Syd Bauman

    Syd Bauman - 2013-06-21

    Fixed and thus closed, but also see bug 579.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks