search

iptc / newsinjson

Home of the IPTC ninjs standard
https://iptc.org/standards/ninjs/
MIT License
35 stars 9 forks source link

Support multiple news items per file, support RSS-like properties #69

Open bquinn opened 3 years ago

bquinn commented 3 years ago

Similar to #19 ...

We could support multi-item feeds. It could be similar to JSONFeed https://jsonfeed.org/version/1.1 which is a simple conversion of RSS from XML to JSON.

It would/could be similar to a PackageItem in NewsML-G2.

Ideas...

nitmws commented 3 years ago

I suggest to extend this issue to "multiple items in a package" - actually a structure like the NewsML-G2 Package Item.

My customer needed "a simple package: x latest news of a service is chronological order". As simple solution I created an object as array with a simple set of references for each news item: uri, version, versioncreated and headline. That works at a simple level, but it would be great to indicate when this package was created, and having its own guid would not be bad ;-)

bquinn commented 3 years ago

Today we discussed two possible approaches: creating a separate schema to cover the package aspects, versus adding new property/ies to the existing schema.

We would like use cases around packaging / multiple items so we can test which approach makes sense.

jolla56 commented 3 years ago

Very similar to #62

jolla56 commented 2 years ago

Comments from issue #62: Brendan: Apple podcasts still point to Media RSS specs from 2003 and use very old constructs:

https://help.apple.com/itc/podcasts_connect/#/itcb54353390

Is there a way we can make ninjs support podcast behaviour, perhaps even talk to podcast providers to see what they would like to add, so people could mark up podcasts using ninjs instead of Media RSS?

Johan: Maybe step 1 is to map ninjs to media RSS and see what maps directly and what needs adding.

Johan: I had a look at this and to my understanding RSS is a XML standard with this podcast extensions defined by Apple. So is this a question for NAR/NewsML-G2 primarily?

bquinn commented 1 year ago

Discussion on 9/1/23:

Use cases ideas:

  1. A "piece" comprised of multiple media objects: a "main story" with "associated media". The "main story" shouldn't have to be a text item.
  2. A collection of photos or videos around a topic - want to be able to describe the relationship of these pieces to the package
  3. Search results - a list of items that match certain criteria.
  4. A feed - latest X stories (maybe latest in a topic, etc)
  5. API results

Implications of the above:

  1. We should be able to implement ordering (in 2.x this is implied by the JS array in associations, in 1.x we would have to add a property to the association)
    • In some cases, order is editorially relevant (was chosen by an editor) and in other cases its less relevant - eg an image gallery. So maybe it's worth adding it as a property to 2.x as well, so that users have the option to express the order explicitly if they choose
  2. We should be able to describe the item's "role" in the package
  3. For API type results, we might want to be able to express metadata about the query parameters that generated the list - the API version, access credentials, search terms used, sort order, the query given etc - and maybe also some information about how detailed the list is, if it's page X of N results, how to access the next and previous pages of results, etc. This information would be quite provider/API-dependent and might not be wort trying to standardise.
jolla56 commented 1 year ago

At recent meetings we have concluded that this is not part of ninjs directly. Maybe not even a standard but more of documentation and best practices from present solutions to give others ideas.