What Metadata are Specific to a PWP?

[prototypo]

A Web Publication is anticipated to have some Descriptive Properties, or WP-specific metadata.

What PWP-specific metadata should a PWP contain, if any?

[iherman]

I do not have very clear ideas but, in the light of PWP, we may have to revisit the role of address and identifier, as well as whether absolute URL-s are usable in a PWP information set or not and, if yes, whether there are restrictions (e.g., they may have share a common domain or 'root' with the identifier, etc). The issue is what happens when I unpack a package onto a specific Web site.

[lrosenthol]

Yes, @iherman - the entire packing/unpacking scenario raises all sorts of questions.

[llemeurfr]

Proposal: close this issue, as no descriptive property specific to a packaged publication has been proposed so far.

The issue of WP address and canonical id is addressed in #47.

Note: As the LPF manifest IS a WP manifest, there is no place for extra metadata there. extra-metadata would require an extra file.

[iherman]

This issue was discussed in a meeting.

• No actions or resolutions

View the transcript

metadata specific to PWP
Laurent Le Meur: #10
Laurent Le Meur: the next is about descriptive metadata. We have 3 specifications… Issue #10 - what metadata is specific to PWP - we saw that there is no descriptive metadata related to a package, but there is a canonical ID and web publication address.
Ivan Herman: +1
Laurent Le Meur: both are discussed in a different issue. I propose we close this and note that there is no descriptive metadata related to the package - but keep open #47
Tzviya Siegman: +1
Luc Audrain: +1
Nick Ruffilo: .. do you agree and can we close
Benjamin Young: The manifest includes a reference to the canonical ID - are you saying that sufficient?
Laurent Le Meur: we must treat descriptive metadata and canonical ID separate. We’re discussing specifically descriptive metadata. This issue is exclusively about descriptive metadata.
Nick Ruffilo: +1
Wendy Reid: +1