| ||||||||
Changed: | ||||||||
< < | SCS-1.03 Next | |||||||
> > | Simple Cone Search 1.03 Next | |||||||
| ||||||||
Changed: | ||||||||
< < | This page collects ideas and features to bring Simple Cone Search to revision 1.1 (or, possibly further). Items collected here can be directly discussed within their sections or on the DAL mailing list. Remember to sign your comments using your wikiname (and date). | |||||||
> > | This page collects ideas and features to bring Simple Cone Search to revision 1.1 (or, possibly further). Items collected here can be directly discussed within their sections or on the DAL mailing list. | |||||||
Added: | ||||||||
> > | Remember to sign your comments using your wikiname (and date). | |||||||
ChangesError ResponseChanged to conform DALI, letting heritage as allowed but deprecated.Resource RegistrationDropped SCS-1.03 section and appendixes related to metadata mapping and imported SimpleDALRegExt SCS-related content.RA and Dec datatypeRelaxed to allow float alongside doubleMAXREC and RESPONSEFORMATAdded to follow DALI, but without outlawing SR=0 and mandatory VOTable response. [Possible next change: suggest usage of RESPONSEFORMAT for BINARY VOTable output]DALI/VOSI endpointsAdded support for capabilities and availability, but check discussion about this referring to GET/POST ARGSVOTable response versionRelaxed to allow any (but discussion on back-compatibility still in place)Metadata discoveryMoved to MAXREC=0 usage, but not removing the SR=0 alternative.HTTP methodsAllowing HTTP POST actions, but see discussion on GET argsDiscussion TopicsMinor vs. Major revisionEspecially with reference to the VOTable output version and UCD usage. Major version would solve issues, but it can be a problem for recommendation takeup time. Minor version may face an impossibility, depending on the 1.0 and 1.1 server and client software requirements.RESOURCE type="results" and its TABLECurrently most 1.0 services do not set the @type for RESOURCE. Also 1.1 should relax a bit on the number of RESOURCES/TABLES allowed in response, e.g. with respect to Datalink needs.ReST versus query-param interfaceMost services use fixed parameters in the SCS base URL. SCS-1.1 will allow this but deprecate it. Allowing it there's a clear constraint on:
§2.3b INFO element error validationMost SCS-1.03 service fail validation due to a controversial interpretation of the "single INFO element" to be used to report error responses. Should this be matter for an Erratum to SCS-1.03 (and then be cleaned up in SCS-1.1)? An Erratum has been issued to solve this point -- MarcoMolinaro - 2017-10-09UCD updateSCS-1.03 requires UCD 1.0 annotations. Is there a way to make UCD1+ cope with back compatibility? Seems there's not this chance for minor revision. We can probably live with 3 UCD-1.0 elements.EPOCH query parameterFor correct searches on sky positions stored at different epochs server-side.<--
|