RE: [xliff-comment] Resource Data Module <source> and <target> elements need a unique name

["Yves Savourel" <yves@opentag.com>]

> Yves, do you have examples of where relying on 
> local names enables people to work in confusing ways?

I've seen many programs, including for XLIFF, where developers blissfully ignore namespaces and use only local names (heck, I do it
myself on occasions). Doing this on documents like 2.0 where namespaces are important is just asking for trouble. I think trying to
use different element/attribute names in each namespace simply encourage such bad behavior.

XLIFF 2.0 is modular and based on namespaces, people who don't understand namespaces should either a) learn about them (it's not
that complicated) or b) refrain themselves from doing anything with XLIFF.

Sorry if I sound finicky about this, but our target audience should normal XML users, not recreational ones.
Or, see it another way: It's an opportunity for many to learn more about the wonders of XML. 

Cheers,
-ys


-----Original Message-----
From: Schnabel, Bryan S [mailto:bryan.s.schnabel@tektronix.com] 
Sent: Saturday, May 25, 2013 9:28 AM
To: Yves Savourel; xliff-comment@lists.oasis-open.org
Cc: xliff@lists.oasis-open.org
Subject: RE: [xliff-comment] Resource Data Module <source> and <target> elements need a unique name

Perhaps you are right. I only have a gut feeling that <xlf:souce> and <xlf:target> storing text and inline elements, and having a
set of attributes; vs. <res:source> and <res:target> being empty, and having a different set of attributes; . . . is confusing.

In my experience people sometimes have a difficult time grasping namespaces. I've known smart people to get confused when this

<xlf:source>,
<res:source>

is the same as

<source xmlns="urn:oasis:names:tc:xliff:document:2.0">,
<source xmlns="urn:oasis:names:tc:xliff:resourcedata:2.0">

As I said, this is a gut feeling, but I cannot point to another standard or case that shows this.

Yves, do you have examples of where relying on local names enables people to work in confusing ways? 

Maybe others have opinions?

As I said, mine is not a strong opinion, just a gut feel.
________________________________________
From: Yves Savourel [yves@opentag.com]
Sent: Friday, May 24, 2013 7:40 PM
To: xliff-comment@lists.oasis-open.org
Subject: RE: [xliff-comment] Resource Data Module <source> and <target> elements need a unique name

> It seems to me that in the Resource Data Module,  the  <res:source> 
>and <res:target> elements should have
> different names in order to avoid confusing them with  core elements 
>with the same local names.

My 2 cents: Namespaces are there to avoid such confusion. Allowing people to rely on local names is, in my opinion, not good: It
just enable people to work in confusing ways.

Cheers,
-ys



--
This publicly archived list offers a means to provide input to the OASIS XML Localisation Interchange File Format (XLIFF) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required
before posting.

Subscribe: xliff-comment-subscribe@lists.oasis-open.org
Unsubscribe: xliff-comment-unsubscribe@lists.oasis-open.org
List help: xliff-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/xliff-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff
Join OASIS: http://www.oasis-open.org/join/




--
This publicly archived list offers a means to provide input to the OASIS XML Localisation Interchange File Format (XLIFF) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required
before posting.

Subscribe: xliff-comment-subscribe@lists.oasis-open.org
Unsubscribe: xliff-comment-unsubscribe@lists.oasis-open.org
List help: xliff-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/xliff-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff
Join OASIS: http://www.oasis-open.org/join/