CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 15:13:50 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:23:49 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 20:59:04 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98c0ccb5ccce0d27
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=E3D19iaHu2jyd5_1GJ0udZGKvNh5zbofz3RV6IR0ytk-1760109230-1.0.1.1-T1p2arMn.ZvhlwN26O4fdT1O4MBRnjI35j_Rt2lf3E1dDeYomt3TAxp61CVeR7fdDZd3Ca5UkehiqC_pyHF5sMwicg0Zik_vXu53TlTLG0U; path=/; expires=Fri, 10-Oct-25 15:43:50 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c7105ded3be8e0-BLR
alt-svc: h3=":443"; ma=86400
Comment on ITS 2.0 WD-its20-20121206 - NLP Interchange Format (NIF) - 1.0/2.0, Canonical XML, Unicode Normalization Forms from Lieske, Christian on 2013-01-10 (public-multilingualweb-lt-comments@w3.org from January 2013)
Comment on ITS 2.0 WD-its20-20121206 - NLP Interchange Format (NIF) - 1.0/2.0, Canonical XML, Unicode Normalization Forms
- From: Lieske, Christian <christian.lieske@sap.com>
- Date: Thu, 10 Jan 2013 10:50:46 +0100
- To: "public-multilingualweb-lt-comments@w3.org" <public-multilingualweb-lt-comments@w3.org>
- Message-ID: <8EA44C66E2911C4AB21558F4720695DC60D7CA8609@DEWDFECCR01.wdf.sap.corp>
Hi, Please find below comments/observations/questions/ideas concerning the ITS 2.0 working draft dated December 6, 2012 (https://www.w3.org/TR/2012/WD-its20-20121206/). Please feel free to contact me for clarifications if anything is unclear. The objectives of the NLP Interchange Format (NIF) - such as interoperability between Natural Language Processing (NLP) tools, language resources and annotations, and easy conversion to Resource Description Format (RDF) - from my point of view are important ones. Accordingly, relating ITS 2.0 - with its direction to move ITS 1.0 closer to Natural Language Processing (NLP) - to NIF may help to realize synergies. While looking at the relation between ITS 2.0 and NIF in the current Working Draft (WD), I have come up with the observations/questions below. I apologize in advance if a reply to this comment may require that discussions which presumably already took place may have to be summarized. 1. Does the WD refer to NIF 1.0, or 2.0? NIF 2.0 already seems to be under development. 2. I am a bit unsure about the approval procedure, the official status, and the organizational home of NIF 1.0 (and NIF 2.0). My assumption is that the LOD2 Consortium declared NIF 1.0 as finished, and hasn't handed it over to an accredited standardization organization such as ISO. 3. Wouldn't the ITS2NIF mapping benefit from/need the following as prerequisites? a. Input and output have to be Canonical XML (for XML-based formats) b. Input and output have to consider Unicode Normalization Forms/Unicode Equivalence (e.g. so that the algorithm does produce identical results for sentences that contain "?ffin" and "A\u0308ffin") Best regards, Christian
Received on Thursday, 10 January 2013 09:51:15 UTC