[Data-modeling] /lang/de vs /en/german_language

[Alec Flett]

On Jun 14, 2009, at 12:23 PM, Tom Morris wrote:

> These two got flagged for merge recently which reminded me that I've
> been meaning to ask why there are two parallel sets of language
> definitions.  The /type/lang topics appear to be used internally for
> things like tagging strings and users languages, etc, but semantically
> it appears to be identical to the topics which are typed
> /language/human_language.
>
> I imagine that the /type/lang languages were needed for bootstrapping,
> but are they still needed.  If they are, is there a way that they can
> be hidden or made less visible as well as locked so that people don't
> try to add the /language/human_language type to them (as happened
> recently to German when someone picked the wrong one).

You've described the situation well - the /type/lang instances are  
part of how the system works, and even though they're similar to /en/ 
german_language, they're not topics, they shouldn't be user visible.

I've just filed a bug CLI-8407 on this...

Alec

>
> Tom
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20090615/cf4d811c/attachment.htm