adding a resultType format

[gilleslandais]

The current DocRegExt seems to focus on HTML or PDF documents (accessible via HTTP interface).
There are also notebooks, and I think it would be useful for users to know the format of the documents they want to upload.

I propose to add the document format in the interface

for instance:

 <capability xsi:type="doc:Edition">
    <interface xsi:type="vr:WebDocument">
        <resultType>application/x-ipynb+json</resultType>
       <accessURL>https://cdsarc.cds.unistra.fr/viz-bin/notebook/J/MNRAS/320/451</accessURL>
    </interface>
  </capability>

[msdemlei]

On Fri, Jan 30, 2026 at 10:11:35AM -0800, gilleslandais wrote: gilleslandais created an issue (ivoa-std/DocRegExt#5) The current DocRegExt seems to focus on HTML or PDF documents (accessible via HTTP interface). There are also notebooks, and I think it would be useful for users to know the format of the documents they want to upload. I propose to add the document format in the interface for instance: ``` <capability xsi:type="doc:Edition"> <interface xsi:type="vr:WebDocument"> <resultType>application/x-ipynb+json</resultType> <accessURL>https://cdsarc.cds.unistra.fr/viz-bin/notebook/J/MNRAS/320/451</accessURL> </interface> </capability> ```

Hm... vr:WebDocument doesn't exist at this point, and I'd hate to tie DocRegExt to a VOResource overhaul. Now, vr:WebBrowser doesn't support resultType (vs:ParamHTTP would, but making the doc:Edition interfaces vs:ParamHTTPs really feels wrong). But then, vr:WebBrowser is not the ideal interface type here, anyway; the intended semantics of that is, I think, that the interface gives you a web form or something like that, which isn't really true here, either. So... I think you have convinced me that DocRegExt should define an interface type of its own. I'm not too wild about WebDocument, though: What does the "Web" in there intended to communicate? Perhaps we can call the type doc:StaticDocument? This would then be vr:Interface plus a resultType child as in vs:ParamHTTP. If you think that's a good idea: would you draft a DocRegExt entry for your MNRAS/320/451 example, perhaps also already including pertinent ascl links? I could then use it as a sample for the document, and use it to guide the changes to the document.

[gilleslandais]

doc:StaticDocument sound good for me.

I dont think about this notebook in particular (because it is a notebook dedicated for a catalogue and we have one for all catalogues) . So may be to start with tutorials (jupyter notebook) make by @ManonMarchand. We could send you a draft contaning both vs:ParamHTTP and ascl identifier!

if it looks good, I would suggest to add something about vs:ParamHTTPs in the docRegExt document?

[msdemlei]

On Mon, Feb 02, 2026 at 05:40:32PM +0000, gilleslandais wrote: gilleslandais left a comment (ivoa-std/DocRegExt#5) *doc:StaticDocument* sound good for me. make by @ManonMarchand. We could send you a draft contaning both *vs:ParamHTTP* and ascl identifier!

That would be great, thanks!

if it looks good, I would suggest to add something about *vs:ParamHTTPs* in the docRegExt document?

Ummm... you mean protocol capabilities like SCS or SIAP? Or would you like to see vs:ParamHTTP interfaces in doc:Edition capabilities?