ISSUE-1: Investigate structured data API
Structured API
Investigate structured data API
- State:
- OPEN
- Product:
- Raised by:
- Joakim Söderberg
- Opened on:
- 2009-01-20
- Description:
- should we have a fine grain API returning only simple types (e.g. getDateGeneral vs. getPubDate), or a coarser grain API returning more complex data.
An alterenative method would be to have an optional flags in each method
to explicitly require structure data / specific data. E.g.
getDate()
-> "2008-01-13" // creationDate by default
getDate(QUALIFIERS)
-> [ "2008-01-13", "creationDate" ]
getDate(QUALIFIERS|MULTIPLE)t
-> [["2008-01-13","creationDate"],["2008-01-14", "publishDate"] ]
getDate("publishDate")
-> "2008-01-14"
- Related Actions Items:
- No related actions
- Related emails:
- ISSUE-1 (Structured API): Investigate structured data API (from sysbot+tracker@w3.org on 2009-01-20)
Related notes:
Makes all sense. To implement this I would replace "property=dateGeneral" in
inputURI=http%3A%2F%2Fgdata.youtube.com%2Ffeeds%2Fbase%2Fvideos%2F-%2FExperte%3Fclient%3Dytapi-youtube-browse%26v%3D2&property=dateGeneral
with one of the function calls you describe above. From an implementation point of view the above and the function call are the same effort. What is more convinient from a users point of view, or for specific use cases
http://lists.w3.org/Archives/Public/public-media-annotation/2009Jan/0034.html
Joakim Söderberg, 20 Jan 2009, 15:23:14Display change log
