Data LinkingDataLink-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" parameterhttp://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 discussions1. 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?<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
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" parameterhttp://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 discussions1. 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?<--
|
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" parameterhttp://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 discussions1. 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?<--
|
Data LinkingREC approved. See the last specification here . %TODO: define the scope and meaning of DataLinkMaintenance , curation of the "semantics" parameterhttp://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 discussions1. 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?<--
|
| ||||||||
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: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Meetings: Data LinkingTODO: define the scope and meaning of DataLinkTopics for Pune2011 interop discussions1. 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: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
Meetings: Data LinkingTODO: define the scope and meaning of DataLinkTopics for Pune2011 interop discussions1. 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.
|
Meetings: Data LinkingTODO: define the scope and meaning of DataLinkTopics for Pune2011 interop discussions1. 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: | ||||||||
> > |
| |||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
Back to: DAL
Jumps:
Meetings: | ||||||||
Changed: | ||||||||
< < | Data Linking | |||||||
> > | Data Linking | |||||||
Added: | ||||||||
> > | TODO: define the scope and meaning of DataLink
Topics for Pune2011 interop discussions1. 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. | |||||||
<--
|
Meetings: Data Linking<--
|