OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  Content of

    Posted 08-29-2008 14:25 
    Hi All,

The specification document says that  contains text and zero, one
or more children elements.

The schema doesn't force  to contain text.

My doubt is: can a  element be empty?

Regards,
Rodolfo
-- 
Rodolfo M. Raya


  • 2.  RE: [xliff] Content of

    Posted 09-17-2008 01:34 
    Hi Rodolfo etc,

Following up on this topic from our meeting today I propose we address
this by adding a general note something to the effect of: "unless
otherwise specified 'text' should be interpreted as 'zero or more
characters'".

I believe that would be consistent with how text is generally
interpreted in XML, HTML, SGML and most other markup languages.

Best regards,
Magnus


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 3.  RE: [xliff] Content of

    Posted 09-17-2008 15:02 
    I agree. Although it is possible in XSD schema to define an element as
containing text and constrain its minimum and maximum length, it would
be very awkward if that element also allows tags because the tags and
text would be mixed.

For example,



What is the length of the text in


  • 4.  RE: [xliff] Content of

    Posted 09-17-2008 15:15 
    Ah, so the HTML spec addresses the issue directly (similar to the suggestion of Magnus to add a note to the XLIFF spec).  Being an old SGML/XML student, I really like the phrase Magnus suggested (zero or more characters). But it would be worthwhile to see the wording in the HTML spec, to see how they address it.

Thanks,

Bryan

________________________________________
From: Doug Domeny [ddomeny@ektron.com]
Sent: Wednesday, September 17, 2008 8:03 AM
To: XLIFF TC
Subject: RE: [xliff] Content of  element

I agree. Although it is possible in XSD schema to define an element as
containing text and constrain its minimum and maximum length, it would
be very awkward if that element also allows tags because the tags and
text would be mixed.

For example,



What is the length of the text in


  • 5.  Re: [xliff] Content of

    Posted 09-17-2008 16:59 
    On Wed, 17 Sep 2008 11:03:30 -0400
"Doug Domeny"


  • 6.  RE: [xliff] Content of

    Posted 09-17-2008 18:36 
    Hi all,

I strongly believe that we should refrain from restricting what textual content can be left empty unless it really does introduce a significant problem. I believe it is almost impossible to foresee all use cases, and introducing such restrictions may cause problems for implementations.

To illustrate this, here are some arbitrary counter-examples for the cases Rodolfo mentions below:

1) A  element may contain content that has only tags, but no text. (In case tags need to be localized.)

2) An empty


  • 7.  RE: [xliff] Content of

    Posted 09-17-2008 18:53 
    Rodolfo,

This philosophical debate has existed for a long time. There are two
camps regarding interpreting U.S. constitutional law: (1) only those
this stated in the constitution are permitted, and (2) all things are
permitted except those prohibited by law. Common sense lies between the
two.

In regard to tags, the question is: should the schema strictly define
what is valid and all else is invalid, or detect that which is in
conflict and disorderly.

Empty


Related Content