Closed lrosenthol closed 3 years ago
The major question we will have to decide on is about the scope of the work: is it only about web pages and resources referenced there (in which case a solution based on a json-ld manifest embedded in the web page works) or is it about any web resource accessed on the web (in which case embedding data inside the resource does not work and a solution based on http headers is fine)?
We'll share info about existing solutions, more or less adaptable to our use case, to make it clear.
in which case embedding data inside the resource does not work
Why not? There are standards in place today for asset-embedded metadata, eg. XMP (ISO 16684), for exactly this purpose.
Fixed by #8.
I would make the following changes to the Requirements.
Since, as I commented in #3 , TDM applies to cases other than crawlers, while this is important it should be a secondary requirement and not a primary one.
Easy is a problematic word, I would rewrite this sentence as: "Able to be implemented without any economic or technical barriers"
Most web resources are not
present
in a Web page, they are, instead, referenced by a Web page. I would therefore changepresent in
toreferenced by
.I believe that this should also include similar language to the above about "individual resources..."
Since a TDM Actor is a machine process, should we say anything here about a "machine processable application"??
Given the scope of supporting all Web Resources, I wonder if we should change this to be "at least one"?
Since the EU Directive says NOTHING about web crawling (as noted also in #3 ), this needs to be a primary requirement in order to deliver a solution that actually meets the needs of the EU Directive.