RE: Moving a namespace

Oh, interesting, thank you Cord. 303 not 301? It is a permanent move but I see the thinking, yes.

Phil

On Tuesday, July 16, 2024 3:33 PM, Cord Wiljes wrote:
Dear Phil,

here are my five cents: IMO, using a server-side redirect actually is best practice to solve this. The URI's should be kept stable, though. E.g. https://gs1.org/voc/Beverage stays the URI of beverage, but visitors will now be redirected via redirect 303 ("See Other") to http://ref.gs1.org/voc/Beverage , i.e. the web page with information about beverage, formerly hosted at https://gs1.org/voc/Beverage.


Best wishes,
Cord

Cord Wiljes
Wissenschaftlicher Referent

Nationale Forschungsdateninfrastruktur (NFDI) e.V.
Albert-Nestler-Str. 13
76131 Karlsruhe
Tel. +49 721 988 994 24
Mail cord.wiljes@nfdi.de
Web www.nfdi.de

Impressum & Datenschutz
https://www.nfdi.de/impressum-datenschutz/



-----Ursprüngliche Nachricht-----
Von: Phil Archer <phil.archer@gs1.org>
Gesendet: Dienstag, 16. Juli 2024 13:04
An: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: Semantic Web <semantic-web@w3.org>
Betreff: RE: Moving a namespace

Thanks Melvin,

That makes me feel a lot better about just redirecting to the new namespace and switching off the old one without worrying too much.

@Danbri - Setting up a specific domain wouldn't obviate the need to redirect from the old one! And ref.gs1.org is our long-term repository for lots of stuff. Heck, it even has a very familiar-looking URI management policy 😊 https://ref.gs1.org/gs1/uri-policy/


Thanks again

Phil

On Tuesday, July 16, 2024 11:51 AM, Melvin Carvalho wrote:


út 16. 7. 2024 v 11:52 odesílatel Phil Archer <phil.archer@gs1.org <mailto:phil.archer@gs1.org> > napsal:


        Dear all,

        I need some advice please. We want to move our vocabulary from gs1.org/voc <http://gs1.org/voc>  (where it's been since 2014) to ref.gs1.org/voc <http://ref.gs1.org/voc>  (where internal policy states it will remain). The question is: is there any reason not to just put in a simple redirect rather than trying, and perhaps failing to set up an alias? The problem is, unless you know better (please!) that an alias, would be established by a CNAME and that would apply to the whole of gs1.org <http://gs1.org>  which we absolutely don't want and can't do. We're just talking about everything below gs1.org/voc <http://gs1.org/voc> .

        So, in short: can we just do a redirect and have done with it?



w3id.org <http://w3id.org>  uses redirects all the time.  Whether or not it's a best practice or even "allowed" I'm not 100% sure.  But its a common pattern.

Have a look at some of the name spaces there and how the redirects work.




        Thanks

        Phil



        ---

        Phil Archer
        Web Solutions Director, GS1
        https://www.gs1.org


        https://philarcher.org

        +44 (0)7887 767755
        @philarcher1

        CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium).
        If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender.
        GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone.
        GS1 may monitor communications.
        Third party rights acknowledged.
        (c) 2020.

CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium).
If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender.
GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone.
GS1 may monitor communications.
Third party rights acknowledged.
(c) 2020.

CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). 
If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. 
GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. 
GS1 may monitor communications. 
Third party rights acknowledged. 
(c) 2020.

Received on Tuesday, 16 July 2024 14:53:42 UTC