Open rorlic opened 10 months ago
It’s not bad!
One small comment on choosing the dcat:Catalog IRI more carefully:
http://localhost:8080
is the IRI for your landing page of your server. I would disambiguate it from the catalog of datasets and services that are available from this server.
How about using http://localhost:8080/catalog#Catalog
? This way, we have a page http://localhost:8080/catalog
describing a catalog http://localhost:8080/catalog#Catalog
. A client that visits http://localhost:8080
could be temporarily redirected to http://localhost:8080/catalog
, so you can still use the base hostname for something else in the future.
Solved together with issue #964
Hello @rorlic @jobulcke,
With version /ldes-server:2.13.0-SNAPSHOT.
The description can be added to the view.
e.g. http://localhost:8080/bearb/timebased-50/description
But this url is not dereferenceable. (I mean this link, links to nothing)
IMO, the link should link to a page?
Thanks
it never pointed to anything before, but to what would you expect it to point? what should the page display?
Hello @rorlic ,
I am just wondering should all info regarding http://localhost:8080/bearb/timebased-50/description
be in the context (in-band) of page localhost/bearb/timebased-50
.
Or it is also possible there will be extra info regarding http://localhost:8080/bearb/timebased-50/description
is at the page http://localhost:8080/bearb/timebased-50/description
.
Thanks
Simple fix would indeed be to use http://localhost:8080/bearb/timebased-50#description → hash instead of a slash here
Please add
dcat:endpointDescription
to eachdcat:DataService
(aka a view) referring to thedcat:Catalog
. In addition, adddct:conformsTo
to both<https://w3id.org/tree/specification>
&<https://w3id.org/ldes/specification>
.Technically it is not a MUST but a SHOULD, see TREE specification.
Example:
add: