[x3d-public] xml:lang language identification

[vmarchetti at kshell.com]

> On Nov 16, 2021, at 6:00 PM, Brutzman, Donald (Don) (CIV) <brutzman at nps.edu> wrote:
> 
> XML allows identification of language via the reserved xml:lang attribute on any attribute.
>  
> XML Recommendation, fifth edition, W3C, section2.12 Language Identification
> https://www.w3.org/TR/REC-xml/#sec-lang-tag <https://www.w3.org/TR/REC-xml/#sec-lang-tag>
>  
> and
>  
> W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes, W3C Recommendation 5 April 2012 section 3.4.3 language
> https://www.w3.org/TR/xmlschema11-2/#language <https://www.w3.org/TR/xmlschema11-2/#language>

These excerpts from the XML documents assert that the xml:lang attribute is not as granular as applying to individual attributes, but applies at
the XML element level, and so to all the attributes and subelements , with some clear rules for overriding the xml:lang attribute in sub-elements.

With that in mind, I think that the function of the xml:lang attribute can, in the X3D abstract specification, be performed by a MetadataString node which can be applied to any X3D node, including
other Metadata nodes. The advantage of this approach would be that the language attribution can be readily transferred between different encodings of the same X3D content.




>  
> Today while working on XMP metadata transcription from RDF/XML (or TTL) form into X3D/XML form, Jakub and I found that we needed to utilize xml:lang attribute for lossless two-way conversion.
>  
> I can think of the following X3D elements that might need to indicate which identification of human language might be appropriate:
> Text node (corresponding to ‘string’ field)
> MetadataString
> <field> and <fieldValue> declarations, if type is SFString/MFString
>  
> Conceivably we might also permit this whenever a description field is present also (Viewpoint, sensors, etc.).
>  
> Not looking to change X3D expressive power but think that xml:lang information ought to be permissible in X3D XML encoding since it is an allowed part of XML.
>  
> Thus am planning to add xml:lang as indicated above in the X3D XML Schema and X3D XML DOCTYPE to avoid incorrect, misleading validation errors.
>  
> Any other considerations appropriate?  Will enter Mantis issue when ready to proceed.  All comments welcome.
>  
> all the best, Don
> -- 
> Don Brutzman  Naval Postgraduate School, Code USW/Br        brutzman at nps.edu <mailto:brutzman at nps.edu>
> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA    +1.831.656.2149
> X3D graphics, virtual worlds, navy robotics https:// faculty.nps.edu/brutzman <http://faculty.nps.edu/brutzman>
>  
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org <http://web3d.org/mailman/listinfo/x3d-public_web3d.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20211116/9b4e499f/attachment-0001.html>