[Fiware-data] Updating version of a file while keeping the previous URL

Moltchanov Boris boris.moltchanov at telecomitalia.it
Thu May 26 20:10:34 CEST 2011


Dear Juanjo and FI-WARE Data partners,

I've just uploaded the Publish/Subscribe Enabler's high-level (I would say a very high-level) description considering following aspects:

1.       Logistic:

a.       The name of the file is the same as proposed and then suggested to keep the same by Juanjo. However, the morfeo shall support internal versioning in order to keep the trace of all updates (date and partner). Otherwise we have to do it explicitly in the document name (example doc_draft-r0.1, r0.2, ..., r1.0-final), considering the number of partners and agile dynamicity of the project we will soon get a mess in this last case. I wish we have internal morfeo versioning as in CVS repositories SW;

b.      I've kept the same internal structure and style as from the initial draft by Juanjo and didn't have any problem. I've just inserted new Enabler section

2.       Content-wise:

a.       The content describing this enabler, including the pictures, is inspired by context management framework interface and context information as the data, therefore don't blame on me now :). I've prepared this first very simple and I hope clear text just as an exercise to discuss in the call tomorrow;

b.      There are not references neither to a certain solution nor to a technical implementation of the architecture or of the interface as it is asked in the document to be asset-agnostic and not giving technical or implementation details. Of course, if this way is agreed and if need I could drill deeper and increase the granularity, which is I repeat on a very high level now. Let's discuss it also tomorrow;

c.       No references are given in the end of the document at the moment. Mainly the same requirements for this interface we have used in C-CAST project mentioned in the FI-WARE DoW. Therefore my idea was to insert just one reference to the C-CAST EU FP7 project (already ended) or at least to its internal public deliverable that threat this matter. Lets you say me something about this also tomorrow.

We are in the first attempts of the deliverable therefore please excuse me if something is wrong and lets discuss it, share and agree starting on this "raw" first drafts and attempts.

Best Regards,
Boris

From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro
Sent: Wednesday, May 25, 2011 1:27 PM
To: fiware-data at lists.fi-ware.eu
Cc: fiware at lists.fi-ware.eu
Subject: [Fiware-data] Updating version of a file while keeping the previous URL

Hi,

  I'm answering Guy's question copying the general FI-WARE list because the answer may be useful for other people.

  Yes.   You can update the file while keeping the same URL.   But this would work provided you don't change the name of the file because this is indeed taken as part of the generated URL.   Otherwise they are considered different files (not an updated version of the file)

  To upload an updated version of the file you simply need to click on the Admin menu option in the Docs tab:

[cid:image001.png at 01CC1BE0.82FDB0F0]


  Then find the document you want to update ...

[cid:image002.png at 01CC1BE0.82FDB0F0]


  and click on it.   It should drive you to a form where you can update the file linked to a document (as well as its decription, access status, etc.):


  [cid:image003.png at 01CC1BE0.82FDB0F0]

  Hope it helps.   Keep in mind that the file has to be named the same way ... otherwise the system will update the file, but the old URL would not work.

  I guess we should use release/version numbers in the description.

  Best regards,

-- Juanjo

On 25/05/11 12:49, Guy Sharon wrote:

I have submitted this under the Docs section of the project - is there a way to manage \ update version?
Would expect the same URL be used to get to the most updated version of the file.
This is going to be messy very quickly if not

Regards,
Guy Sharon

Manager

Event-based Middleware & Solutions Group

________________________________

[cid:image004.gif at 01CC1BE0.82FDB0F0]<http://www.ibm.com/smarterplanet>

Event-based Middleware & Solutions<http://www.haifa.il.ibm.com/dept/services/soms_ebs.html>

phone :

+972 4 8296587

mobile :

+972 54 6976417

address :

IBM R&D Labs in Israel, Haifa University Campus, Mount Carmel, Haifa, 31905, Israel

email :

guysh at il.ibm.com<mailto:guysh at il.ibm.com>






From:        Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>
To:        fiware-data at lists.fi-ware.eu<mailto:fiware-data at lists.fi-ware.eu>
Date:        25/05/2011 13:19
Subject:        Re: [Fiware-data] [FIware-data] High level description - draft
Sent by:        fiware-data-bounces at lists.fi-ware.eu<mailto:fiware-data-bounces at lists.fi-ware.eu>
________________________________



Dear Guy,

 Thanks very much for starting to roll-out the ball with a first contribution.

 In a very quick review I found you didn't follow the guidelines for allowed paragraph styles (particularly, bullet lists) we put in the preface of the document.

 Please try to generate a new version with this editorial point fixed.

 For the rest: I would kindly ask you to follow the guidelines provided in the template.

 Best regards,

-- Juanjo

On 25/05/11 09:59, Guy Sharon wrote:
Hi all,

I have uploaded a draft version on the Real-time Processing - CEP Generic Enabler
Since I am the first one (I think) lets use this as a punching bag by commenting on it and flushing out the best way of describing and representing a GE
http://forge.fi-ware.eu/docman/view.php/9/62/FI-WARE+High-Level+Description+11-06-1+v0.1IBM.docx
Guy Sharon

Manager

Event-based Middleware & Solutions Group

________________________________

[cid:image004.gif at 01CC1BE0.82FDB0F0]<http://www.ibm.com/smarterplanet>

Event-based Middleware & Solutions<http://www.haifa.il.ibm.com/dept/services/soms_ebs.html>

phone :

+972 4 8296587

mobile :

+972 54 6976417

address :

IBM R&D Labs in Israel, Haifa University Campus, Mount Carmel, Haifa, 31905, Israel

email :

guysh at il.ibm.com<mailto:guysh at il.ibm.com>



________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________
Fiware-data mailing list
Fiware-data at lists.fi-ware.eu<mailto:Fiware-data at lists.fi-ware.eu>
http://lists.fi-ware.eu/listinfo/fiware-data

________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110526/10b40399/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 75961 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110526/10b40399/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 151044 bytes
Desc: image002.png
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110526/10b40399/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 136218 bytes
Desc: image003.png
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110526/10b40399/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.gif
Type: image/gif
Size: 2558 bytes
Desc: image004.gif
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110526/10b40399/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia.jpg
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110526/10b40399/attachment.jpg>


More information about the Old-Fiware-data mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy