SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

TCG Review Period

30 January 2012 - 27 February 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Great job as usual ! I approve. -- ChristopheArviset - 31 Jan 2012

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

Approved. And curious to see if anyone has attempted to connect an IVOA page to a Web Profile hub... -- SebastienDerriere - 28 Feb 2012

VOEvent Working Group (Matthew Graham, John Swinbank)

Approved. -- MatthewGraham - 07 Mar 2012

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Approved. -- AlbertoAccomazzi - 08 Feb 2012

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Approved even if we are not qualified to understand all the technical details -- HerveWozniak - 24 Feb 2012

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

TCG Review Period

30 January 2012 - 27 February 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Great job as usual ! I approve. -- ChristopheArviset - 31 Jan 2012

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

Approved. And curious to see if anyone has attempted to connect an IVOA page to a Web Profile hub... -- SebastienDerriere - 28 Feb 2012

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Approved. -- AlbertoAccomazzi - 08 Feb 2012

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Approved even if we are not qualified to understand all the technical details -- HerveWozniak - 24 Feb 2012

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

TCG Review Period

30 January 2012 - 27 February 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Great job as usual ! I approve. -- ChristopheArviset - 31 Jan 2012

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

Approved. And curious to see if anyone has attempted to connect an IVOA page to a Web Profile hub... -- SebastienDerriere - 28 Feb 2012

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Approved. -- AlbertoAccomazzi - 08 Feb 2012

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Approved even if we are not qualified to understand all the technical details -- HerveWozniak - 24 Feb 2012

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

TCG Review Period

30 January 2012 - 27 February 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Great job as usual ! I approve. -- ChristopheArviset - 31 Jan 2012

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Approved. -- AlbertoAccomazzi - 08 Feb 2012

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Approved even if we are not qualified to understand all the technical details -- HerveWozniak - 24 Feb 2012

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

TCG Review Period

30 January 2012 - 27 February 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Great job as usual ! I approve. -- ChristopheArviset - 31 Jan 2012

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Approved. -- AlbertoAccomazzi - 08 Feb 2012

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Approved even if we are not qualified to understand all the technical details -- HerveWozniak - 24 Feb 2012

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

TCG Review Period

30 January 2012 - 27 February 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Great job as usual ! I approve. -- ChristopheArviset - 31 Jan 2012

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Approved. -- AlbertoAccomazzi - 08 Feb 2012

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

TCG Review Period

30 January 2012 - 27 February 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Great job as usual ! I approve. -- ChristopheArviset - 31 Jan 2012

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Approved. -- AlbertoAccomazzi - 08 Feb 2012

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

TCG Review Period

30 January 2012 - 27 February 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Great job as usual ! I approve. -- ChristopheArviset - 31 Jan 2012

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Approved. -- GretchenGreene - Jan 30, 2012

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Recommendations from TCG members during TCG Review Period (30 Jan 2012 - 27 Feb 2012)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick)

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

Following a short discussion, to address this issue, the following text has been added (rev 1626) to section 5.4.2.1:

There may be circumstances under which it is appropriate to relax this local host restriction, for instance to enable collaboration with a known external host not capable of Standard Profile communication, such as a mobile device operated by the hub user. However, it is RECOMMENDED that Web Profile implementations at least restrict access to the local host in their default configuration, and if access is permitted to external hosts it is only by explicit user request, and to a named host or list of hosts. Opening the well-known Web Profile hub server port to the internet at large would invite denial of service and perhaps phishing attacks in which the user is exposed to unwanted SAMP registration requests.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

Comments by Hugo Buddelmeijer

Hugo (currently waiting for wiki password) has commented on the apps-samp list that the web profile does not facilitate use of a tablet for SAMP control, since connections from non-local hosts are blocked by the web profile hub. Followups on the mailing list or here - the discussion will at least be summarised here.

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Applications WG (MarkTaylor, EnriqueSolano)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

This page contains public discussion of the SAMP v1.3 Proposed Recommendation. The RFC was announced on 12 December 2011 and will run until 29 January 2012 (period extended in consideration of the Christmas break).

Version under review

PR-SAMP-1.3-20111128

RFC Review Period

12 December 2011 - 29 January 2012

Change Summary

The main change between the previous version 1.2 and this version 1.3 is the addition of a new section (Section 5) defining the new SAMP Web Profile. Some other more minor changes and clarifications have been made elsewhere in the document as listed in Appendix B.

This document has been developed within the public subversion repository Volute, in directory projects/samp/doc. The exact changes between the 1.2 REC and 1.3 PR LaTeX source files can be seen on this diff page.

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

SAMPy (Python)

From version 1.2.1 includes a Web Profile hub implementation. This currently has one small incompatibility in the registration call (left over from a previous draft of the standard) which will be fixed in the next release.

JSAMP (Java)

From version 1.3-1 includes a Web Profile hub implementation and (mainly for testing) a Web Profile client.

A Web Profile client implementation library (working, though not beautiful) in JavaScript (which, unlike Python and desktop Java, is one of the languages it makes sense to write Web Profile clients in) is available at http://www.star.bristol.ac.uk/~mbt/websamp/, along with a few examples of web pages that use it.

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK, Opera not working, others not tried). This is down to variable implementation of relevant standards in browsers, and not unexpected.

JSAMP contains a hub validation suite which tests pretty much all of SAMP and runs without error against both SAMPy and JSAMP hubs. There is not however a comprehensive validation suite that runs from a web page, which might be a good idea for testing the Web Profile.

-- MarkTaylor - 08 Dec 2011

In order to add a comment to the document, please edit this page and add your comment to the list below. When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses may be conducted on the apps-samp@ivoa.net mailing list. However, please enter your initial comments here for full consideration in any future revisions of this document.

IVOA Community Comments during RFC period (12 Dec 2011 - 29 Jan 2012)

TCG Comments during the RFC period (12 Dec 2011 - 29 Jan 2012)

(TCG members are encouraged to consider the document during the RFC stage so that any problems can be addressed before the TCG Review stage when the chair or vice chair of each WG will be required to review it).

Applications WG (MarkTaylor, EnriqueSolano)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 Proposed Recommendation: Request For Comments

Change Summary

The main change between the previous version

This document has been developed within the public subversion repository

Implementations and Validators

There are two interoperating implementations of the entire SAMP standard, including the new Web Profile:

These all work with no known problems, except that the Web Profile doesn't work from all browsers (Firefox, IE, Chrome, Safari all OK,

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 RFC Discussion

This page is a marker for the discussion of the SAMP v1.3 standard.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SAMP v1.3 RFC Discussion

This page is a marker for the discussion of the SAMP v1.3 standard. The RFC is expected to start in mid-September.