Re: IRI escaping in CTM?

"Andrew S. Townley" <[email protected]>
Newsgroups gmane.text.xml.xtm.general
Message-ID <[email protected]>
Hi Lars,

Thanks for the clarification.  That's kinda what I was thinking, but there weren't any examples to this effect in the CTM spec, and it wasn't entirely clear that iri-delimited as defined in 3.3.3 of the spec were suitable for this purpose.

This is great news though.  Thanks.

ast

On 5 Apr 2011, at 2:43 PM, Lars Heuer wrote:

> Hi Andrew,
> 
> [...]
>> How would I specify either the relative IRI 'foo:bar' used as an
>> item locator or http://example.com/path/foo:bar to get CTM not to complain?
> 
> You have to use <> for rootless IRIs:
> 
>    <foo:bar> isa baz.
> 
> (foo would be your schema name in this case)
> 
> 
> This should work, though:
> 
>    http://example.com/path/foo:bar isa something.
> 
> 
> IRIs which start with <schema-name> '://' are detected automatically.
> Schemas like "mailto", "urn" etc. require the delimiters:
> 
>    <mailto:[email protected]> isa duck.
> 
> 
> Invalid examples:
> 
>    mailto:[email protected] isa duck.
> 
>    foo:bar isa baz. # (unless foo was defined as prefix)
> 
> 
> [...]
>> As an aside, the whole CTM "qname" with prefixes vs XML Namespace
>> "QName" as orthogonal naming pair semantic dissonance seems to be
>> wrong.  Is it too late to change the terminology from 'qname' in
>> CTM?
> 
> Yes, the train has left the station. In four (?) years we may revise
> the CTM specification acc. to ISO regularities.
> 
> Best regards,
> Lars
> -- 
> Semagia 
> <http://www.semagia.com>
> 
> <http://www.topicmaps.de/mailinglist/> German Topic Maps mailing list
> <http://tinytim.sourceforge.net/> Open Source Topic Maps engine
> <http://mappa.semagia.com/> Mappa - Python Topic Maps engine
> 

--
Andrew S. Townley <[email protected]>
http://atownley.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.