Difference: DataLink (1 vs. 10)

Revision 102024-03-14 - FrancoisBonnarel

 
META TOPICPARENT name="IvoaDAL"
Back to: DAL

Data Linking

DataLink-1.1 Next page to gather feedback on current REC to be used for next minor/major version.

DataLink-1.0 Next page to gather feedback on 1.0 REC which helped to define REC 1.1.

REC approved. See the last specification here .

Changed:
<
<
%TODO: define the scope and meaning of DataLink
>
>
%Old hope: define the scope and meaning of DataLink
 
Added:
>
>
The way to implement DataLink is described here : https://github.com/ivoa/DataLinkRecImplNote. See the pdf below
 

Maintenance , curation of the "semantics" parameter

http://www.ivoa.net/rdf/datalink/core contains the list of agreed values for the "semantics" field.

Each entry in this list serves as a unique label and allow to point to individually to each description.

A test to fix the referencing mechanism is needed to make it work from the current version on-line .

http://wiki.ivoa.net/twiki/bin/view/IVOA/UpdateDatalinkTerms

is a page where new terms can be suggested , discussed and validated .

Topics for Pune2011 interop discussions

1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort

2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery

3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.

4. what kind of access? download? preview? cutouts? transformations?


<--  
-->

META FILEATTACHMENT attr="" comment="DataLink Working draft. premiminary version" date="1336888416" name="DataLink.pdf" path="DataLink.pdf" size="221130" user="FrancoisBonnarel" version="1.1"
META FILEATTACHMENT attachment="NOTE-DataLinkProposal-1.0-20130502.pdf" attr="" comment="IVOA Note Version1.0" date="1367591727" name="NOTE-DataLinkProposal-1.0-20130502.pdf" path="NOTE-DataLinkProposal-1.0-20130502.pdf" size="2884651" user="LaurentMichel" version="1"
Added:
>
>
META FILEATTACHMENT attachment="DataLinkImp-draft-1.pdf" attr="" comment="DataLink implementation Note" date="1710438401" name="DataLinkImp-draft-1.pdf" path="DataLinkImp-draft-1.pdf" size="366786" user="FrancoisBonnarel" version="1"
 

Revision 92024-03-14 - FrancoisBonnarel

 
META TOPICPARENT name="IvoaDAL"
Back to: DAL

Data Linking

Changed:
<
<
DataLink-1.0 Next page to gather feedback on current REC to be used for next minor/major version.
>
>
DataLink-1.1 Next page to gather feedback on current REC to be used for next minor/major version.
Added:
>
>
DataLink-1.0 Next page to gather feedback on 1.0 REC which helped to define REC 1.1.
  REC approved. See the last specification here .

%TODO: define the scope and meaning of DataLink

Maintenance , curation of the "semantics" parameter

http://www.ivoa.net/rdf/datalink/core contains the list of agreed values for the "semantics" field.

Each entry in this list serves as a unique label and allow to point to individually to each description.

A test to fix the referencing mechanism is needed to make it work from the current version on-line .

http://wiki.ivoa.net/twiki/bin/view/IVOA/UpdateDatalinkTerms

is a page where new terms can be suggested , discussed and validated .

Topics for Pune2011 interop discussions

1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort

2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery

3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.

4. what kind of access? download? preview? cutouts? transformations?


<--  
-->

META FILEATTACHMENT attr="" comment="DataLink Working draft. premiminary version" date="1336888416" name="DataLink.pdf" path="DataLink.pdf" size="221130" user="FrancoisBonnarel" version="1.1"
META FILEATTACHMENT attachment="NOTE-DataLinkProposal-1.0-20130502.pdf" attr="" comment="IVOA Note Version1.0" date="1367591727" name="NOTE-DataLinkProposal-1.0-20130502.pdf" path="NOTE-DataLinkProposal-1.0-20130502.pdf" size="2884651" user="LaurentMichel" version="1"

Revision 82018-05-31 - MarcoMolinaro

 
META TOPICPARENT name="IvoaDAL"
Back to: DAL

Data Linking

Added:
>
>
DataLink-1.0 Next page to gather feedback on current REC to be used for next minor/major version.
  REC approved. See the last specification here .

%TODO: define the scope and meaning of DataLink

Maintenance , curation of the "semantics" parameter

http://www.ivoa.net/rdf/datalink/core contains the list of agreed values for the "semantics" field.

Each entry in this list serves as a unique label and allow to point to individually to each description.

A test to fix the referencing mechanism is needed to make it work from the current version on-line .

http://wiki.ivoa.net/twiki/bin/view/IVOA/UpdateDatalinkTerms

is a page where new terms can be suggested , discussed and validated .

Topics for Pune2011 interop discussions

1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort

2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery

3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.

4. what kind of access? download? preview? cutouts? transformations?


<--  
-->

META FILEATTACHMENT attr="" comment="DataLink Working draft. premiminary version" date="1336888416" name="DataLink.pdf" path="DataLink.pdf" size="221130" user="FrancoisBonnarel" version="1.1"
META FILEATTACHMENT attachment="NOTE-DataLinkProposal-1.0-20130502.pdf" attr="" comment="IVOA Note Version1.0" date="1367591727" name="NOTE-DataLinkProposal-1.0-20130502.pdf" path="NOTE-DataLinkProposal-1.0-20130502.pdf" size="2884651" user="LaurentMichel" version="1"

Revision 72018-05-31 - MireilleLouys

 
META TOPICPARENT name="IvoaDAL"
Back to: DAL

Data Linking

REC approved. See the last specification here .

%TODO: define the scope and meaning of DataLink

Maintenance , curation of the "semantics" parameter

http://www.ivoa.net/rdf/datalink/core contains the list of agreed values for the "semantics" field.

Each entry in this list serves as a unique label and allow to point to individually to each description.

A test to fix the referencing mechanism is needed to make it work from the current version on-line .

Added:
>
>
http://wiki.ivoa.net/twiki/bin/view/IVOA/UpdateDatalinkTerms

is a page where new terms can be suggested , discussed and validated .

 

Topics for Pune2011 interop discussions

1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort

2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery

3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.

4. what kind of access? download? preview? cutouts? transformations?


<--  
-->

META FILEATTACHMENT attr="" comment="DataLink Working draft. premiminary version" date="1336888416" name="DataLink.pdf" path="DataLink.pdf" size="221130" user="FrancoisBonnarel" version="1.1"
META FILEATTACHMENT attachment="NOTE-DataLinkProposal-1.0-20130502.pdf" attr="" comment="IVOA Note Version1.0" date="1367591727" name="NOTE-DataLinkProposal-1.0-20130502.pdf" path="NOTE-DataLinkProposal-1.0-20130502.pdf" size="2884651" user="LaurentMichel" version="1"

Revision 62016-05-18 - MireilleLouys

 
META TOPICPARENT name="IvoaDAL"
Back to: DAL
Deleted:
<
<
Jumps:
Meetings:
 

Data Linking

Changed:
<
<
TODO: define the scope and meaning of DataLink
>
>
REC approved. See the last specification here .
 
Changed:
<
<

Topics for Pune2011 interop discussions

>
>
%TODO: define the scope and meaning of DataLink
 
Changed:
<
<
1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort
>
>

Maintenance , curation of the "semantics" parameter

 
Changed:
<
<
2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery
>
>
http://www.ivoa.net/rdf/datalink/core contains the list of agreed values for the "semantics" field.
 
Changed:
<
<
3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.
>
>
Each entry in this list serves as a unique label and allow to point to individually to each description.
 
Changed:
<
<
4. what kind of access? download? preview? cutouts? transformations?
>
>
A test to fix the referencing mechanism is needed to make it work from the current version on-line .
 
Changed:
<
<
5.
>
>

Topics for Pune2011 interop discussions

 
Added:
>
>
1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort
 
Added:
>
>
2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery
 
Added:
>
>
3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.
 
Added:
>
>
4. what kind of access? download? preview? cutouts? transformations?
 
Changed:
<
<
>
>

Changed:
<
<
>
>
 

META FILEATTACHMENT attr="" comment="DataLink Working draft. premiminary version" date="1336888416" name="DataLink.pdf" path="DataLink.pdf" size="221130" user="FrancoisBonnarel" version="1.1"
META FILEATTACHMENT attachment="NOTE-DataLinkProposal-1.0-20130502.pdf" attr="" comment="IVOA Note Version1.0" date="1367591727" name="NOTE-DataLinkProposal-1.0-20130502.pdf" path="NOTE-DataLinkProposal-1.0-20130502.pdf" size="2884651" user="LaurentMichel" version="1"

Revision 52013-05-03 - LaurentMichel

 
META TOPICPARENT name="IvoaDAL"
Back to: DAL

Jumps:
Meetings:

Data Linking

TODO: define the scope and meaning of DataLink

Topics for Pune2011 interop discussions

1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort

2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery

3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.

4. what kind of access? download? preview? cutouts? transformations?

5.


Changed:
<
<
>
>
 
Added:
>
>
 
META FILEATTACHMENT attr="" comment="DataLink Working draft. premiminary version" date="1336888416" name="DataLink.pdf" path="DataLink.pdf" size="221130" user="FrancoisBonnarel" version="1.1"
Added:
>
>
META FILEATTACHMENT attachment="NOTE-DataLinkProposal-1.0-20130502.pdf" attr="" comment="IVOA Note Version1.0" date="1367591727" name="NOTE-DataLinkProposal-1.0-20130502.pdf" path="NOTE-DataLinkProposal-1.0-20130502.pdf" size="2884651" user="LaurentMichel" version="1"
 

Revision 42012-06-26 - root

 
META TOPICPARENT name="IvoaDAL"
Back to: DAL

Jumps:
Meetings:

Data Linking

TODO: define the scope and meaning of DataLink

Topics for Pune2011 interop discussions

1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort

2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery

3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.

4. what kind of access? download? preview? cutouts? transformations?

5.


META FILEATTACHMENT attr="" comment="DataLink Working draft. premiminary version" date="1336888416" name="DataLink.pdf" path="DataLink.pdf" size="221130" user="FrancoisBonnarel" version="1.1"

Revision 32012-05-13 - FrancoisBonnarel

 
META TOPICPARENT name="IvoaDAL"
Back to: DAL

Jumps:
Meetings:

Data Linking

TODO: define the scope and meaning of DataLink

Topics for Pune2011 interop discussions

1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort

2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery

3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.

4. what kind of access? download? preview? cutouts? transformations?

5.


<--  
-->
Added:
>
>
 
Added:
>
>
META FILEATTACHMENT attr="" comment="DataLink Working draft. premiminary version" date="1336888416" name="DataLink.pdf" path="DataLink.pdf" size="221130" user="FrancoisBonnarel" version="1.1"
 

Revision 22011-10-06 - PatrickDowler

 
META TOPICPARENT name="IvoaDAL"
Deleted:
<
<
 Back to: DAL

Jumps:
Meetings:

Changed:
<
<

Data Linking

>
>

Data Linking

 
Added:
>
>
TODO: define the scope and meaning of DataLink

Topics for Pune2011 interop discussions

1. are we defining a data-access-only service? E.g. one where a required input is a dataset identifier of some sort

2. can DataLink be used as a packaging mechansim? E.g. deliver multiple files originating from one "result" from a data discovery

3. if it is a service, then every service that can give identifiers out should also define the DataLink service the caller should use to access the identified data.

4. what kind of access? download? preview? cutouts? transformations?

5.

 


<--  
-->

Revision 12011-10-06 - PatrickDowler

 
META TOPICPARENT name="IvoaDAL"

Back to: DAL

Jumps:
Meetings:

Data Linking


<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback