ISSUE-426: Section 3.4 provides too much guidance
arbitrary-data
Section 3.4 provides too much guidance
- State:
- CLOSED
- Product:
- Accessing and Querying Provenance
- Raised by:
- Paul Groth
- Opened on:
- 2012-06-20
- Description:
- Given that we do not define how to deal with arbitrary data the section may provide too much guidance.
- Related Actions Items:
- No related actions
- Related emails:
- PROV-ISSUE-426 (arbitrary-data): Section 3.4 provides too much guidance [Accessing and Querying Provenance] (from sysbot+tracker@w3.org on 2012-06-20)
Related notes:
I tend to agree. You don't indicate what you think should go.
I propose dropping from half way through 3rd para:
"At this time, it is not clear what format that should be..."
to the end of the section.
This would leave the following general guidance in section 3.4:
[[
If a resource is represented using a data format other than HTML or RDF, and no URI for the resource is known, provenance discovery becomes trickier to achieve. This specification does not define a specific mechanism for such arbitrary resources, but this section discusses some of the options that might be considered.
For formats which have provision for including metadata within the file (e.g. JPEG images, PDF documents, etc.), use the format-specific metadata to include a target-URI, provenance-URI and/or service-URI. Format-specific metadata provision might also be used to include provenance information directly in the resource.
Use a generic packaging format that can combine an arbitrary data file with a separate metadata file in a known format, such as RDF.
]]
(+ some wordsmithing)
Changes made, awaiting feedback to close
Graham Klyne, 10 Nov 2012, 09:12:14Remove section 3.4 with intention of putting material in the FAQ (copy text tpo FAQ - see link on WG front page)
Graham Klyne, 14 Nov 2012, 23:13:31Text removed to http://www.w3.org/2001/sw/wiki/PROV-FAQ#Access_and_query_-_arbitrary_data
Graham Klyne, 20 Nov 2012, 12:18:55Display change log