|
Thanks Nick,
I just looked into the comment TAB-1647 and, strictly speaking, they are fully correct regarding the substitution of the 301 permanent redirect code because you are not able to change permanent redirects (I mean you can but browsers can simply
cache the 301 redirect FOREVER).
What we need to do instead is to ensure
https://httpstatuses.com/301 is not returned. I recall asking Koneksys to set it to the
https://httpstatuses.com/303 code for RDF; I guess we need to extend it to HTML too. If IBM's homepage does locale-based redirect, it should use 303 (or the more common 302 code) too but I will stay out of
that one :)
/A
We should not
follow all the recommendations concerning redirected links. For example, links to
open-services.net/ns MUST stay as is, and not be changed to the target of the redirection: the redirection takes into account the content type being requested, and is also subject to occasional change. Similarly,
I do not believe a link to ibm.com should be redirected to the English sub-page: I might guess in this case the redirection is locale-sensitive.
Jim, you might want to mention to the reviewer these issues with their recommendations that a link that is redirected should necessarily be replaced by the target of that redirection. Obviously there are some cases
where that action is appropriate, such as the Wikipedia and OASIS document links, or changing http to https.
Nick.
From: David Honey1 <DavidHoney@uk.ibm.com>
To: "Jim Amsden" <jamsden@us.ibm.com>
Cc: "OASIS OSLC Core TC Discussion List (oslc-core@lists.oasis-open.org)" <oslc-core@lists.oasis-open.org>
Date: 02/13/2019 04:18 AM
Subject: Re: [oslc-core] OSLC Query 3.0 public review responses
Sent by: <oslc-core@lists.oasis-open.org>
Hi Jim,
Re TAB-1656:
I think we should reference https://www.w3.org/TR/rdf11-concepts/#section-XMLLiteral.
Note this is a non-normative specification for the reasons stated in that W3 document.
Re TAB-1657:
I don't understand the submitter's description. The spec is describing elements of oslc.where and these are not XML. Maybe all that is needed is a reference to a W3C document for xsd:string and rdf:XMLLiteral.
With all the moving around and the fact that I have had little time for anything other than working on high severity issues for two Jazz applications nearing 6.0.6.1 release, I have no idea where the current OSLC Query 3.0 spec is. My last known reference is
http://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/trunk/specs/oslc-query.html#conformance.
Hopefully things should start ease up over the next few weeks and I will time for OSLC.
Best regards,
David
From: "Jim Amsden" <jamsden@us.ibm.com>
To: "OASIS OSLC Core TC Discussion List (oslc-core@lists.oasis-open.org)" <oslc-core@lists.oasis-open.org>
Date: 11/02/2019 18:38
Subject: [oslc-core] OSLC Query 3.0 public review responses
Sent by: <oslc-core@lists.oasis-open.org>
Here's the comments from the TAB with my initial responses. Could you (especially David) provide any needed corrections to my responses.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
[attachment "oslc-query-v3.0.csv" deleted by David Honey1/UK/Contr/IBM] [attachment "oslc-query-v3.0.numbers" deleted by David Honey1/UK/Contr/IBM]
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
|