newsml-g2 : Messages : 844-873 of 873

To add an example to my previous considerations:

The New York Times released its first controlled vocabulary for persons - see http://data.nytimes.com - as a SKOS file.

These namespaces are defined:

xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

xmlns:skos="http://www.w3.org/2004/02/skos/core#"

xmlns:nyt="http://data.nytimes.com/elements/"

xmlns:cc="http://creativecommons.org/ns#"

xmlns:fb="http://rdf.freebase.com/ns/"

xmlns:owl="http://www.w3.org/2002/07/owl#"

xmlns:dc="http://purl.org/dc/elements/1.1/"

xmlns:dcterms="http://purl.org/dc/terms/"

xmlns:time="http://www.w3.org/2006/time#">

A happy mix of # and / at the end.

Michael

--------------------------------------------------

On 4 Nov 2009 at 18:21 misha.wolf@... wrote:

The IPTC News Architecture group is discussing, among other matters, the pros and cons of "#" and "/" in the construction of URIs representing concepts. Your input is welcome.

Regards,

Misha

From: Wolf, Misha (M Cont Ent)
Sent: 04 November 2009 18:19
To: 'iptc-news-architecture-dev@yahoogroups.com'
Subject: RE: [IPTC-NAR-dev] Scheme URIs

The Semantic Web allows both "#" and "/". In deciding which to use, one must consider a number of things, including:

- the intended UI

- the implementation

The "#" approach lends itself to describing an entire Scheme on one static Web page.

The "/" approach implies a flat directory, containing many items.

In reality, software can be made to deliver any UI, based on either mechanism.

This W3C document discusses very detailed implementation issues for the two options:

Best Practice Recipes for Publishing RDF Vocabularies

http://www.w3.org/TR/swbp-vocab-pub/

Regards,

Misha

This email was sent to you by Thomson Reuters, the global news and information company.
Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.

==================================================

Sent by:

Michael Steidl

Managing Director of the IPTC <mdirector@...>

International Press Telecommunications Council - www.iptc.org

Business office address:

20 Garrick Street, London WC2E 9BT, United Kingdom

Registered in England, company no 101096

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

    ---- File information -----------
      File:  DEFAULT.BMP
      Date:  4 Nov 2007, 19:21
      Size:  358 bytes.
      Type:  Unknown

#872

From: "Michael Steidl (IPTC)" <mdirector@...>
Date: Thu Nov 26, 2009 10:08 am
Subject: Re: Terminating Scheme URIs with "#" vs "/"

mdiptc

Offline

Misha and group:

my - a bit cynical - answer is: it depends on what you want to achive. This is my summary:

a) in the scope of creating valid URIs [1]: both terminating characters can be used

b) in the scope of creating URI References as used by RDF [2]: both may be used, but in the scope of practical use and implementations the # is clearly preferred

c) in the scope of publishing RDF vocabularies [3]: both can be used.

This all again more in detail:

Prerequisite: the issue is: the IPTC G2-Standards define that a scheme must have a URI for identifying it and codes representing members of the scheme shall be concatenated to this Scheme URI and the result should be again a valid URI - and preferentially a URL which resolves to a web resource.

re a) the scope which is the easiest to discuss: the current URI RFC allows a URIs with both a "/" and a "#" at the end, and appending a code is not big issue as most of the Unicode characters can be used.

re b) Things get more complex in this scope as the RDF documents are contentious about what a URI reference exactly is: an identifier - in any case - which can be resolved to a web resource ... hm, this excludes URNs per se. I guess this comes i) from different editors for the six basic RDF document and ii) that in some document an explicit or implicit assumption is made: RDF is about the Web, thus all URIs must be web URLs = http: URLs.

Go provide some references to corresponding sections in RDF document:

- in the RDF Concepts [4], under 6.4 on can read: " ...and would produce a valid URI character sequence (per RFC2396 [URI], sections 2.1) representing an absolute URI with optional fragment identifier when subjected to the encoding described below. "

- in the RDF Semantics [5], under 1.2 one can read: (2 quotes follow)

-- "This document does not take any position on the way that URI references may be composed from other expressions, e.g. from relative URIs or QNames; the semantics simply assumes that such lexical issues have been resolved in some way that is globally coherent, so that a single URI reference can be taken to have the same meaning wherever it occurs."

-- "The semantics does not assume any particular relationship between the denotation of a URI reference and a document or Web resource which can be retrieved by using that URI reference in an HTTP transfer protocol, or any entity which is considered to be the source of such documents. Such a requirement could be added as a semantic extension, but the formal semantics described here makes no assumptions about any connection between the denotations of URI references and the uses of those URI references in other protocols."

My comment: this sounds very aloof regarding the relationship between URIs as identifier and http URLs - it tells in other words: others may add more specific definitions.

- in the RDF Primer [6], on can read under 2.1, Basic Concepts:

-- "Because of this generality, RDF uses URIs as the basis of its mechanism for identifying the subjects, predicates, and objects in statements. To be more precise, RDF uses URI references [URIS]. A URI reference (or URIref) is a URI, together with an optional fragment identifier at the end. For example, the URI reference http://www.example.org/index.html#section2 ...."

My comment: This chapter is in its first section about the subject of RDF triples and it is quite obvious that this is a http URL for all Web resources - and RDF is made for them. But in this later section it extends this view to URIs for predicates and objects - and this is much less obvious.

The major problem with this http-URL focused thinking is that even standards are tweaked to abide to it. Example: the XML Schema specification provides this namespace URL: "http://www.w3.org/2001/XMLSchema". When it comes to RDF the URL is suddenly "http://www.w3.org/2001/XMLSchema#" - to be strict: that are two different namespaces.

Another major issue is: I got aware that many people working in the RDF area assume that the # termination is a MUST for RDF and many software vendors do not support a / at the end of a namespace URI - this results in URIs like this one: http://namespace.example.org/ns1/#predicate1" if a namespace is defined as http://namespace.example.org/ns1/ and a predicate of "predicate1" is applied to it. Apparently the software checks if a # is in the namespace URI and if not it is appended.

An important issue regarding http-URLs is fragment values: in case of referring to a section of an XHTML document the @id of the corresponding tag (e.g. <p>, or <div>) is used. This approach inherits the lexical space limitations for @id in XML documents: e.g. not digit is allowed as first character. And this was one of the main reasons for the IPTC not to adopt the # as recommended termination character as this would exclude any code (of a scheme) starting with a digit.

re c) This document explicitly - and completely in parallel - discribes how vocabularies with a # (hash) or a / (slash) at the end of the scheme's URI can be accessed and retrieved.

Happy considerations and drawing conclusions

Michael

--------------------------------

[1] RFC 3986 - http://tools.ietf.org/html/rfc3986

[2] http://www.w3.org/RDF/

[3] http://www.w3.org/TR/swbp-vocab-pub/

[4] http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-URIref

[5] http://www.w3.org/TR/rdf-mt/#urisandlit

[6] http://www.w3.org/TR/rdf-primer/#basicconcepts

--------------------------------------------------

On 4 Nov 2009 at 18:21 misha.wolf@... wrote:

The IPTC News Architecture group is discussing, among other matters, the pros and cons of "#" and "/" in the construction of URIs representing concepts. Your input is welcome.

Regards,

Misha

From: Wolf, Misha (M Cont Ent)
Sent: 04 November 2009 18:19
To: 'iptc-news-architecture-dev@yahoogroups.com'
Subject: RE: [IPTC-NAR-dev] Scheme URIs

The Semantic Web allows both "#" and "/". In deciding which to use, one must consider a number of things, including:

- the intended UI

- the implementation

The "#" approach lends itself to describing an entire Scheme on one static Web page.

The "/" approach implies a flat directory, containing many items.

In reality, software can be made to deliver any UI, based on either mechanism.

This W3C document discusses very detailed implementation issues for the two options:

Best Practice Recipes for Publishing RDF Vocabularies

http://www.w3.org/TR/swbp-vocab-pub/

Regards,

Misha

==================================================

Sent by:

Michael Steidl

Managing Director of the IPTC <mdirector@...>

International Press Telecommunications Council - www.iptc.org

Business office address:

20 Garrick Street, London WC2E 9BT, United Kingdom

Registered in England, company no 101096

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

    ---- File information -----------
      File:  DEFAULT.BMP
      Date:  4 Nov 2007, 19:21
      Size:  358 bytes.
      Type:  Unknown

#871

From: Jan Algermissen <algermissen1971@...>
Date: Wed Nov 25, 2009 9:45 pm
Subject: Re: Terminating Scheme URIs with "#" vs "/"

algermissen1971

Offline

On Nov 4, 2009, at 7:21 PM, misha.wolf@... wrote:

>
>
> The IPTC News Architecture group is discussing, among other matters,
> the pros and cons of "#" and "/" in the construction of URIs
> representing concepts.  Your input is welcome.

Incidently I just ran across this posting by Roy Fielding which
explaines the issue a *lot* better than I did:

http://lists.w3.org/Archives/Public/www-tag/2002Jul/0253.html

Jan



>
> Regards,
> Misha
>
>
> From: Wolf, Misha (M Cont Ent)
> Sent: 04 November 2009 18:19
> To: 'iptc-news-architecture-dev@yahoogroups.com'
> Subject: RE: [IPTC-NAR-dev] Scheme URIs
>
> The Semantic Web allows both "#" and "/".  In deciding which to use,
> one must consider a number of things, including:
> -    the intended UI
> -    the implementation
>
> The "#" approach lends itself to describing an entire Scheme on one
> static Web page.
>
> The "/" approach implies a flat directory, containing many items.
>
> In reality, software can be made to deliver any UI, based on either
> mechanism.
>
> This W3C document discusses very detailed implementation issues for
> the two options:
>     Best Practice Recipes for Publishing RDF Vocabularies
>     http://www.w3.org/TR/swbp-vocab-pub/
>
> Regards,
> Misha
>
>
>
> This email was sent to you by Thomson Reuters, the global news and
> information company.
> Any views expressed in this message are those of the individual
> sender, except where the sender specifically states them to be the
> views of Thomson Reuters.
>
>

--------------------------------------
Jan Algermissen

Mail: algermissen@...
Blog: http://algermissen.blogspot.com/
Home: http://www.jalgermissen.com
--------------------------------------

#870

From: "Evain, Jean-Pierre" <evain@...>
Date: Wed Nov 4, 2009 6:36 pm
Subject: RE : Terminating Scheme URIs with "#" vs "/"

jpevain_ebu

Offline

Misha, as far as I am concerned I prefer the #.

This allows me to define URIs pointing to any form of documents (xml, pdf, doc)
and still have a pointer. When not using rdf and concepts like defined in SKOS,
there is always an issue on knowing how ot resolve a reference to a concept
identified by a URI. Another attractive feature of # is that it doesn't enter
the debate of safely resolving URLs while it opens the document within which a
reference is provided. This means an average user should be able to decide then
what's the best way for him for resolving the URI.

Regards,

Jean-pierre
________________________________
De : newsml-g2@yahoogroups.com [newsml-g2@yahoogroups.com] de la part de
misha.wolf@... [misha.wolf@...]
Date d'envoi : mercredi, 4. novembre 2009 19:21
� : newsml-g2@yahoogroups.com
Objet : [newsml-g2] Terminating Scheme URIs with "#" vs "/"



The IPTC News Architecture group is discussing, among other matters, the pros
and cons of "#" and "/" in the construction of URIs representing concepts.  Your
input is welcome.

Regards,
Misha


________________________________
From: Wolf, Misha (M Cont Ent)
Sent: 04 November 2009 18:19
To: 'iptc-news-architecture-dev@yahoogroups.com'
Subject: RE: [IPTC-NAR-dev] Scheme URIs

The Semantic Web allows both "#" and "/".  In deciding which to use, one must
consider a number of things, including:
-    the intended UI
-    the implementation

The "#" approach lends itself to describing an entire Scheme on one static Web
page.

The "/" approach implies a flat directory, containing many items.

In reality, software can be made to deliver any UI, based on either mechanism.

This W3C document discusses very detailed implementation issues for the two
options:
     Best Practice Recipes for Publishing RDF Vocabularies
     http://www.w3.org/TR/swbp-vocab-pub/

Regards,
Misha



This email was sent to you by Thomson Reuters, the global news and information
company.
Any views expressed in this message are those of the individual sender, except
where the sender specifically states them to be the views of Thomson Reuters.

#869

From: <misha.wolf@...>
Date: Wed Nov 4, 2009 6:21 pm
Subject: Terminating Scheme URIs with "#" vs "/"

wolf_misha

Offline

The IPTC News Architecture group is discussing, among other matters, the pros and cons of "#" and "/" in the construction of URIs representing concepts. Your input is welcome.

Regards,

Misha

From: Wolf, Misha (M Cont Ent)
Sent: 04 November 2009 18:19
To: 'iptc-news-architecture-dev@yahoogroups.com'
Subject: RE: [IPTC-NAR-dev] Scheme URIs

The Semantic Web allows both "#" and "/". In deciding which to use, one must consider a number of things, including:

- the intended UI

- the implementation

The "#" approach lends itself to describing an entire Scheme on one static Web page.

The "/" approach implies a flat directory, containing many items.

In reality, software can be made to deliver any UI, based on either mechanism.

This W3C document discusses very detailed implementation issues for the two options:

Best Practice Recipes for Publishing RDF Vocabularies

http://www.w3.org/TR/swbp-vocab-pub/

Regards,

Misha

#868

From: "fitzphoto" <brian@...>
Date: Mon Oct 19, 2009 3:06 pm
Subject: Re: Looking for real NewsML examples

fitzphoto

Offline

Robert,

Thanks for your response.  Our company (www.epiccycle.com) ingests feeds for use
in proprietary CMS systems primarily for media companies such as newspapers and
sports companies like NFL franchises.  We have a big interest in maintaining and
promoting standards such as Sports ML, NewsML and EventsML.  Our tool will work
with other publishers of content as well, allowing them to convert a feed or
feeds from their proprietary format to, for example, NewsML.

Thanks for your help!
Brian

--- In newsml-g2@yahoogroups.com, <robert.schmidt-nia@...> wrote:
>
> Hi B rian,
>
> Actually dpa provides information about events in EventsML-G2. This month we
are also starting to process images as NewsML-G2 items. If you like I could send
you some examples. Can you give some information about your organisation and
your business segment?
>
> Robert
>
>
> Von: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] Im Auftrag
von fitzphoto
> Gesendet: Dienstag, 6. Oktober 2009 16:59
> An: newsml-g2@yahoogroups.com
> Betreff: [newsml-g2] Looking for real NewsML examples
>
>
>
> Folks,
>
> Trying to develop a tool that can parse NewsML feeds. Anyone have an example
of a good feed we can use?
>
> Also, I'm looking for examples of feeds or static NewsML files that contain
multiple story packages in the same feed or file....looking for how NewsML
separates distinct packages from one another.
>
> Does anyone have any ideas or information? It's very much appreciated!
>
> Brian
>

Reply | Forward | Messages in this Topic (3)

#867

From: <robert.schmidt-nia@...>
Date: Mon Oct 19, 2009 7:16 am
Subject: AW: Looking for real NewsML examples

schmidt_nia

Offline

Hi B rian,

Actually dpa provides information about events in EventsML-G2. This month we are also starting to process images as NewsML-G2 items. If you like I could send you some examples. Can you give some information about your organisation and your business segment?

Robert

Von: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] Im Auftrag von fitzphoto
Gesendet: Dienstag, 6. Oktober 2009 16:59
An: newsml-g2@yahoogroups.com
Betreff: [newsml-g2] Looking for real NewsML examples

Folks,

Trying to develop a tool that can parse NewsML feeds. Anyone have an example of a good feed we can use?

Also, I'm looking for examples of feeds or static NewsML files that contain multiple story packages in the same feed or file....looking for how NewsML separates distinct packages from one another.

Does anyone have any ideas or information? It's very much appreciated!

Brian

Reply | Forward | Messages in this Topic (3)

#866

From: "laurent_le_meur" <llemeur@...>
Date: Wed Oct 7, 2009 8:40 pm
Subject: From Web 2.0 to the Semantic Web: Bridging the gap in newsmedia

laurent_le_meur

Offline

Quite interesting, an entry from Joel Amoussou about the possible mapping of
newsml-g2 items to rdf/skos items:

http://www.slideshare.net/jamoussou/from-web-20-to-the-semantic-web-bridging-the\
-gap-in-the-newsmedia-industry-1432440

+ http://twitter.com/jamoussou/status/2243982556 .

Reply | Forward | Messages in this Topic (1)

#865

From: "fitzphoto" <brian@...>
Date: Tue Oct 6, 2009 2:58 pm
Subject: Looking for real NewsML examples

fitzphoto

Offline

Folks,

Trying to develop a tool that can parse NewsML feeds.  Anyone have an example of
a good feed we can use?

Also, I'm looking for examples of feeds or static NewsML files that contain
multiple story packages in the same feed or file....looking for how NewsML
separates distinct packages from one another.

Does anyone have any ideas or information?  It's very much appreciated!

Brian

Reply | Forward | Messages in this Topic (3)

#864

From: <misha.wolf@...>
Date: Fri Oct 2, 2009 8:49 pm
Subject: W3C Launches Provenance Incubator Group

wolf_misha

Offline

Of interest to News providers ...

W3C Launches Provenance Incubator Group

   W3C is pleased to announce the creation of the Provenance
   Incubator Group, whose mission is to provide a state-of-the art
   understanding and develop a roadmap in the area of provenance
   for Semantic Web technologies, development, and possible
   standardization. The group will be chaired by Yolanda Gil. The
   following W3C Members have sponsored the charter for this
   group: Renssealaer Polytechnic Institute, Talis Information
   Limited, University of Manchester, University of Southampton,
   University of Southern California Information Sciences
   Institute (USC / ISI), and Vrije Universiteit. Read more about
   the Incubator Activity, an initiative to foster development of
   emerging Web-related technologies. Incubator Activity work is
   not on the W3C standards track.

   http://www.w3.org/2005/Incubator/prov/
   http://www.w3.org/2005/Incubator/prov/charter
   http://www.w3.org/2005/Incubator/

The 2009-09-29 version of the W3C Public Newsletter is online:
http://www.w3.org/News/Public/pnews-20090929

Reply | Forward | Messages in this Topic (1)

#863

From: <misha.wolf@...>
Date: Fri Sep 4, 2009 11:57 pm
Subject: FW: [rfc-dist] BCP 47, RFC 5646 on Tags for Identifying Languages

wolf_misha

Offline

fyi

-----Original Message-----
From: rfc-dist-bounces@...
[mailto:rfc-dist-bounces@...] On Behalf Of
rfc-editor@...
Sent: 04 September 2009 23:20
To: ietf-announce@...; rfc-dist@...
Cc: ltru@...; rfc-editor@...
Subject: [rfc-dist] BCP 47, RFC 5646 on Tags for Identifying Languages

A new Request for Comments is now available in online RFC libraries.

         BCP 47
         RFC 5646

         Title:      Tags for Identifying Languages
         Author:     A. Phillips, Ed.,
                     M. Davis, Ed.
         Status:     Best Current Practice
         Date:       September 2009
         Mailbox:    addison@...,
                     markdavis@...
         Pages:      84
         Characters: 208592
         Obsoletes:  RFC4646
         See Also:   BCP0047

         I-D Tag:    draft-ietf-ltru-4646bis-23.txt

         URL:        http://www.rfc-editor.org/rfc/rfc5646.txt

This document describes the structure, content, construction, and
semantics of language tags for use in cases where it is desirable to
indicate the language used in an information object.  It also
describes how to register values for use in language tags and the
creation of user-defined extensions for private interchange.  This
document
specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

This document is a product of the Language Tag Registry Update Working
Group of the IETF.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
   http://www.ietf.org/mailman/listinfo/ietf-announce
   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see
http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@....  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute

_______________________________________________
rfc-dist mailing list
rfc-dist@...
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

This email was sent to you by Thomson Reuters, the global news and information
company.
Any views expressed in this message are those of the individual sender, except
where the sender specifically states them to be the views of Thomson Reuters.

Reply | Forward | Messages in this Topic (1)

#862

From: "kelvin_holland" <kholland@...>
Date: Tue Sep 1, 2009 3:13 pm
Subject: Re: Named write-throughs

kelvin_holland

Offline

Is "nth Lead" really a role? Is it not the nth version of a "Lead"?

Kelvin

#861

From: "Paul Harman" <paul.harman@...>
Date: Tue Sep 1, 2009 9:15 am
Subject: RE: Re: Named write-throughs

seancortan

Offline

From: Michael Steidl (IPTC) [mailto:mdirector@...]
> - or is it only a string to be communicated to the receiver?
> In this case a literal value alone does not help, the
> "human readable" string must be in a <name> child of the role.


Point taken. I'd need to invent an @literal then, but that's okay - I'm
doing it in loads of places already.


> But: actually we already have something for this purpose: the
> edNote.


Er... Yes, I could do that. I'm already using edNote with other @roles
for other purposes, but I suppose that's fair. The thing is, it is about
the life cycle of the news item, and that's the explicit purpose of
<role>, so I'd rather use <role>.

	 Paul

This email is from the Press Association.  For more information, see
www.pressassociation.com.
This email may contain confidential information.
Only the addressee is permitted to read, copy, distribute or otherwise use this
email or any attachments.
If you have received it in error, please contact the sender immediately.
Any opinion expressed in this email is personal to the sender and may not
reflect the opinion of the Press Association.
Any email reply to this address may be subject to interception or monitoring for
operational reasons or for lawful business practices.

#860

From: "Michael Steidl (IPTC)" <mdirector@...>
Date: Fri Aug 28, 2009 3:25 pm
Subject: RE: Re: Named write-throughs

mdiptc

Offline

Hi Paul

my 2 cents on this:

I'm wondering how exactly the value of itemMeta/role will be used:

- for filtering on the receiver side? Then the values should be known to the receiver as else he could not set up a filter efficiently = some CV is required.

- or is it only a string to be communicated to the receiver? In this case a literal value alone does not help, the "human readable" string must be in a <name> child of the role.

But: actually we already have something for this purpose: the edNote. You could do this

</itemMeta>

Michael

--------------------------------------------------

On 26 Aug 2009 at 12:30 Paul Harman wrote:

Thanks Darko.

itemMeta/role is a QCodePropType, so it only allows values drawn from a controlled vocabulary. Unfortunately, the roles I need to use are - whilst not uncontrolled - not suitable to put into a CV, because they are essentially unbounded. The sequence is: Sunstitute, Lead, 2nd Lead, 3rd Lead, 4th Lead ... 99999999999999th Lead, Nightlead, 2nd Nightlead ..... aleph-null Nightlead.

So the best I could do for 2nd Lead perhaps is:

...bit I'd prefer to be allowed to do:

Could this change be accommodated?

Paul

From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On Behalf Of Darko Gulija
Sent: 26 August 2009 11:37
To: newsml-g2@yahoogroups.com
Subject: Re: [newsml-g2] Re: Named write-throughs

Late addition to the old discussion:

I was doing something completely different and come across "itemMeta/role" property - which is the one I was looking for (and the right one for the problem).

The definition is:

10.6.114 Role in the Workflow
Role in the Workflow
(XML) Data Model         Element
Namespace (prefix)       nar
Name                           role
Title                             Role in the Workflow
Definition                      The role of the Item in the editorial workflow.
User Note(s)                 Among other possibilities this property may indicate the importance of the item in a fee by concepts like “flash”, “bulletin”, “alert”, “urgent”, “newsbreak”, and so on.
XML Schema Spec At: Both CCL and PCL
Datatype                      QualPropType (page 212)

Hope it's not too late :)

2009/7/14 Darko Gulija < dgulija.hina@... >

I checked the list archive after I realized we never added a specific property for this.

The last "solution" I found was to use <signal> property and create a special CV for various "leads" (Message #3277 &#3278).

The other option was to define specific "editStatus" property, but it was never done.

The argument I remember was that every provider had its own meaning for the same terms, so it was impossible to create a common CV.

Signal sounds better to me than <genre> for the matter.

2009/7/14 Darko Gulija < dgulija.hina@... >

I would not say <genre> is the right one: genre should express journalistic nature of the story, and this is in fact "editing stage" - how far has the story developed through it's lifecycle (it will probably have the same genre in all the versions).

I remember we discussed a property with similar name, but could not find it in the spec (I have 2.0 PCL spec with me - did we add it later ?)

Misha, Michael - do you remember what happened with editing stage - I remember few quite lively discussions on the matter ?

2009/7/14 kelvin_holland < kholland@... >

Paul,

Use <genre>? The IPTC Genre NewsCodes have values for "update" and
"wrapup". This seems to align with what you are trying to express,
although you would have to use your own scheme to get exactly what you
want.

Kelvin

--- In newsml-g2@yahoogroups.com , "Paul Harman" <paul.harman@...> wrote:
>
> PA has a naming scheme for its write-throughs. The first write- through
> of a story is called the "Substitute", the second is called the
"Lead".
> Then we have a succession of numbered leads e.g. "2nd Lead", "3rd
Lead",
> etc until such point as the content reaches a milestone (tied into
> newspaper publishing schedules) when the next write-through is named
> "Nightlead"; then we get into ordinal nightleads e.g. "2nd Nightlead",
> and so on.
>
> These names are well-known and understood in the UK media industry,
and
> so I need to be able to support them somehow. In NITF, I use
> du-key/@version for this.
>
> As ever, I could invent a namespaced element to handle this... But I'm
> interested to hear if the concept of naming write-throughs is common
> enough to warrant a proper home in NewsML-G2.
>
> Paul
>

------------------------------------

Any member of this IPTC moderated Yahoo group must comply with the Intellectual Property Policy of the IPTC, available at http://www.iptc.org/goto/ipp . Any posting is assumed to be submitted under the conditions of this IPTC IP Policy.
Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/newsml-g2/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/newsml-g2/join
(Yahoo! ID required)

<*> To change settings via email:
mailto: newsml-g2-digest@yahoogroups.com
mailto: newsml-g2-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
newsml-g2-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

This email is from the Press Association. For more information, see www.pressassociation.com. This email may contain confidential information. Only the addressee is permitted to read, copy, distribute or otherwise use this email or any attachments. If you have received it in error, please contact the sender immediately. Any opinion expressed in this email is personal to the sender and may not reflect the opinion of the Press Association. Any email reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.

==================================================

Sent by:

Michael Steidl

Managing Director of the IPTC <mdirector@...>

International Press Telecommunications Council

"Information Technology for News"

Visit us on the web at http://www.iptc.org

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

    ---- File information -----------
      File:  DEFAULT.BMP
      Date:  4 Nov 2007, 20:21
      Size:  358 bytes.
      Type:  Unknown

#859

From: Darko Gulija <darko.gulija@...>
Date: Fri Aug 28, 2009 2:20 pm
Subject: Re: Re: Named write-throughs

dgulija

Offline

See no harm in it. We could discuss it on one of the next conf calls.

However, be aware that the new versions of the standards family have just been approved at the AGM, so - if accepted -� it would (probaly) not be finalized before the spring meeting.

Would such a solution satisfy your needs ?

Darko

2009/8/26 Paul Harman <paul.harman@...>

Thanks Darko.

�

itemMeta/role is a QCodePropType, so it only allows values drawn from a controlled vocabulary. Unfortunately, the roles I need to use are - whilst not uncontrolled - not suitable to put into a CV, because they are essentially unbounded. The sequence is: Sunstitute, Lead, 2nd Lead, 3rd Lead, 4th Lead ... 99999999999999th Lead, Nightlead, 2nd Nightlead ..... aleph-null Nightlead.

�

So the best I could do for 2nd Lead perhaps is:

�

�� <itemMeta>

�� <role qcode="pawritethroughrole:Lead" pa:ordinal="2"/>

�

...bit I'd prefer to be allowed to do:

�

�� <itemMeta>

�� <role literal="2nd Lead"/>

�

Could this change be accommodated?

�

�� Paul

From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On Behalf Of Darko Gulija
Sent: 26 August 2009 11:37

To: newsml-g2@yahoogroups.com
Subject: Re: [newsml-g2] Re: Named write-throughs

�

Late addition to the old discussion:

I was doing something completely different and come across "itemMeta/role" property - which is the one I was looking for (and the right one for the problem).

The definition is:

10.6.114 Role in the Workflow
Role in the Workflow
(XML) Data Model�� Element
Namespace (prefix)�� nar
Name�� role
Title�� Role in the Workflow
Definition�� The role of the Item in the editorial workflow.
User Note(s)�� Among other possibilities this property may indicate the importance of the item in a fee by concepts like �flash�, �bulletin�, �alert�, �urgent�, �newsbreak�, and so on.
XML Schema Spec At: � Both CCL and PCL
Datatype�� QualPropType (page 212)

Hope it's not too late :)

2009/7/14 Darko Gulija <dgulija.hina@...>

I checked the list archive after I realized we never added a specific property for this.

The last "solution" I found was to use <signal> property and create a special CV for various "leads" (Message #3277 & #3278).

The other option was to define specific "editStatus" property, but it was never done.

The argument I remember was that every provider had its own meaning for the same terms, so it was impossible to create a common CV.

Signal sounds better to me than <genre> for the matter.

2009/7/14 Darko Gulija <dgulija.hina@...>

I would not say <genre> is the right one: genre should express journalistic nature of the story, and this is in fact "editing stage" - how far has the story developed through it's lifecycle (it will probably have the same genre in all the versions).

I remember we discussed a property with similar name, but could not find it in the spec (I have 2.0 PCL spec with me - did we add it later ?)

Misha, Michael - do you remember what happened with editing stage - I remember few quite lively discussions on the matter ?

2009/7/14 kelvin_holland <kholland@...>

Paul,

Use <genre>? The IPTC Genre NewsCodes have values for "update" and
"wrapup". This seems to align with what you are trying to express,
although you would have to use your own scheme to get exactly what you
want.

Kelvin

--- In newsml-g2@yahoogroups.com, "Paul Harman" <paul.harman@...> wrote:
>
> PA has a naming scheme for its write-throughs. The first write-through
> of a story is called the "Substitute", the second is called the
"Lead".
> Then we have a succession of numbered leads e.g. "2nd Lead", "3rd
Lead",
> etc until such point as the content reaches a milestone (tied into
> newspaper publishing schedules) when the next write-through is named
> "Nightlead"; then we get into ordinal nightleads e.g. "2nd Nightlead",
> and so on.
>
> These names are well-known and understood in the UK media industry,
and
> so I need to be able to support them somehow. In NITF, I use
> du-key/@version for this.
>
> As ever, I could invent a namespaced element to handle this... But I'm
> interested to hear if the concept of naming write-throughs is common
> enough to warrant a proper home in NewsML-G2.
>
> �Paul
>

------------------------------------

Any member of this IPTC moderated Yahoo group must comply with the Intellectual Property Policy of the IPTC, available at http://www.iptc.org/goto/ipp. Any posting is assumed to be submitted under the conditions of this IPTC IP Policy.
Yahoo! Groups Links

<*> To visit your group on the web, go to:
� �http://groups.yahoo.com/group/newsml-g2/

<*> Your email settings:
� �Individual Email | Traditional

<*> To change settings online go to:
� �http://groups.yahoo.com/group/newsml-g2/join
� �(Yahoo! ID required)

<*> To change settings via email:
� �mailto:newsml-g2-digest@yahoogroups.com
� �mailto:newsml-g2-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
� �newsml-g2-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
� �http://docs.yahoo.com/info/terms/

This email is from the Press Association. For more information, see www.pressassociation.com. This email may contain confidential information. Only the addressee is permitted to read, copy, distribute or otherwise use this email or any attachments. If you have received it in error, please contact the sender immediately. Any opinion expressed in this email is personal to the sender and may not reflect the opinion of the Press Association. Any email reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.

#858

From: "Paul Harman" <paul.harman@...>
Date: Wed Aug 26, 2009 11:30 am
Subject: RE: Re: Named write-throughs

seancortan

Offline

Thanks Darko.

So the best I could do for 2nd Lead perhaps is:

...bit I'd prefer to be allowed to do:

Could this change be accommodated?

Paul

From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On Behalf Of Darko Gulija
Sent: 26 August 2009 11:37
To: newsml-g2@yahoogroups.com
Subject: Re: [newsml-g2] Re: Named write-throughs

Late addition to the old discussion:

I was doing something completely different and come across "itemMeta/role" property - which is the one I was looking for (and the right one for the problem).

The definition is:

10.6.114 Role in the Workflow
Role in the Workflow
(XML) Data Model          Element
Namespace (prefix)        nar
Name                            role
Title                              Role in the Workflow
Definition                       The role of the Item in the editorial workflow.
User Note(s)                  Among other possibilities this property may indicate the importance of the item in a fee by concepts like “flash”, “bulletin”, “alert”, “urgent”, “newsbreak”, and so on.
XML Schema Spec At: Both CCL and PCL
Datatype                       QualPropType (page 212)

Hope it's not too late :)

2009/7/14 Darko Gulija <dgulija.hina@gmail.com>

I checked the list archive after I realized we never added a specific property for this.

The last "solution" I found was to use <signal> property and create a special CV for various "leads" (Message #3277 & #3278).

The other option was to define specific "editStatus" property, but it was never done.

The argument I remember was that every provider had its own meaning for the same terms, so it was impossible to create a common CV.

Signal sounds better to me than <genre> for the matter.

2009/7/14 Darko Gulija <dgulija.hina@gmail.com>

I would not say <genre> is the right one: genre should express journalistic nature of the story, and this is in fact "editing stage" - how far has the story developed through it's lifecycle (it will probably have the same genre in all the versions).

I remember we discussed a property with similar name, but could not find it in the spec (I have 2.0 PCL spec with me - did we add it later ?)

Misha, Michael - do you remember what happened with editing stage - I remember few quite lively discussions on the matter ?

2009/7/14 kelvin_holland <kholland@point-house.co.uk>

Paul,

Use <genre>? The IPTC Genre NewsCodes have values for "update" and
"wrapup". This seems to align with what you are trying to express,
although you would have to use your own scheme to get exactly what you
want.

Kelvin

--- In newsml-g2@yahoogroups.com, "Paul Harman" <paul.harman@...> wrote:
>
> PA has a naming scheme for its write-throughs. The first write-through
> of a story is called the "Substitute", the second is called the
"Lead".
> Then we have a succession of numbered leads e.g. "2nd Lead", "3rd
Lead",
> etc until such point as the content reaches a milestone (tied into
> newspaper publishing schedules) when the next write-through is named
> "Nightlead"; then we get into ordinal nightleads e.g. "2nd Nightlead",
> and so on.
>
> These names are well-known and understood in the UK media industry,
and
> so I need to be able to support them somehow. In NITF, I use
> du-key/@version for this.
>
> As ever, I could invent a namespaced element to handle this... But I'm
> interested to hear if the concept of naming write-throughs is common
> enough to warrant a proper home in NewsML-G2.
>
> Paul
>

------------------------------------

Any member of this IPTC moderated Yahoo group must comply with the Intellectual Property Policy of the IPTC, available at http://www.iptc.org/goto/ipp. Any posting is assumed to be submitted under the conditions of this IPTC IP Policy.
Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/newsml-g2/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/newsml-g2/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:newsml-g2-digest@yahoogroups.com
mailto:newsml-g2-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
newsml-g2-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

This email is from the Press Association. For more information, see www.pressassociation.com. This email may contain confidential information. Only the addressee is permitted to read, copy, distribute or otherwise use this email or any attachments. If you have received it in error, please contact the sender immediately. Any opinion expressed in this email is personal to the sender and may not reflect the opinion of the Press Association. Any email reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.

#857

From: Darko Gulija <darko.gulija@...>
Date: Wed Aug 26, 2009 10:37 am
Subject: Re: Re: Named write-throughs

dgulija

Offline

Late addition to the old discussion:

I was doing something completely different and come across "itemMeta/role" property - which is the one I was looking for (and the right one for the problem).

The definition is:

10.6.114 Role in the Workflow
Role in the Workflow
(XML) Data Model�� Element
Namespace (prefix)�� nar
Name�� role
Title�� Role in the Workflow
Definition�� The role of the Item in the editorial workflow.
User Note(s)�� Among other possibilities this property may indicate the importance of the item in a fee by concepts like �flash�, �bulletin�, �alert�, �urgent�, �newsbreak�, and so on.
XML Schema Spec At: � Both CCL and PCL
Datatype�� QualPropType (page 212)

Hope it's not too late :)

2009/7/14 Darko Gulija <dgulija.hina@...>

I checked the list archive after I realized we never added a specific property for this.

The last "solution" I found was to use <signal> property and create a special CV for various "leads" (Message #3277 & #3278).

The other option was to define specific "editStatus" property, but it was never done.

The argument I remember was that every provider had its own meaning for the same terms, so it was impossible to create a common CV.

Signal sounds better to me than <genre> for the matter.

2009/7/14 Darko Gulija <dgulija.hina@...>

I would not say <genre> is the right one: genre should express journalistic nature of the story, and this is in fact "editing stage" - how far has the story developed through it's lifecycle (it will probably have the same genre in all the versions).

I remember we discussed a property with similar name, but could not find it in the spec (I have 2.0 PCL spec with me - did we add it later ?)

Misha, Michael - do you remember what happened with editing stage - I remember few quite lively discussions on the matter ?

2009/7/14 kelvin_holland <kholland@...>

Paul,

Use <genre>? The IPTC Genre NewsCodes have values for "update" and
"wrapup". This seems to align with what you are trying to express,
although you would have to use your own scheme to get exactly what you
want.

Kelvin

--- In newsml-g2@yahoogroups.com, "Paul Harman" <paul.harman@...> wrote:
>
> PA has a naming scheme for its write-throughs. The first write-through
> of a story is called the "Substitute", the second is called the
"Lead".
> Then we have a succession of numbered leads e.g. "2nd Lead", "3rd
Lead",
> etc until such point as the content reaches a milestone (tied into
> newspaper publishing schedules) when the next write-through is named
> "Nightlead"; then we get into ordinal nightleads e.g. "2nd Nightlead",
> and so on.
>
> These names are well-known and understood in the UK media industry,
and
> so I need to be able to support them somehow. In NITF, I use
> du-key/@version for this.
>
> As ever, I could invent a namespaced element to handle this... But I'm
> interested to hear if the concept of naming write-throughs is common
> enough to warrant a proper home in NewsML-G2.
>
> �Paul
>

------------------------------------

Any member of this IPTC moderated Yahoo group must comply with the Intellectual Property Policy of the IPTC, available at http://www.iptc.org/goto/ipp. Any posting is assumed to be submitted under the conditions of this IPTC IP Policy.
Yahoo! Groups Links

<*> To visit your group on the web, go to:
� �http://groups.yahoo.com/group/newsml-g2/

<*> Your email settings:
� �Individual Email | Traditional

<*> To change settings online go to:
� �http://groups.yahoo.com/group/newsml-g2/join
� �(Yahoo! ID required)

<*> To change settings via email:
� �mailto:newsml-g2-digest@yahoogroups.com
� �mailto:newsml-g2-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
� �newsml-g2-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
� �http://docs.yahoo.com/info/terms/

#856

From: "kelvin_holland" <kholland@...>
Date: Tue Aug 11, 2009 2:15 pm
Subject: Re: Mapping for IIM: digital creation date/time?

kelvin_holland

Offline

If there is no business case (that we can think of), I won't refer to
this topic in the Guide. If we wanted to include it, I think we would
need a considered recommendation, not a workaround.

Maybe this could be used as an example for Extension Points?

Kelvin

--- In newsml-g2@yahoogroups.com, "Paul Harman" <paul.harman@...> wrote:
>
> From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On
> Behalf Of Michael Steidl (IPTC)
> > should *all* metadata fields from all previous IPTC standards be
> mapped to G2?
> > [...] 2:15 Category which is used by IIM V2 implementers but IIM V4
> defines
> > its use is deprecated.
>
>
>
> Category might be deprecated in the spec but it is still widely used -
> not everyone was prepared to use subject codes :-P
>
> But the point is well made: if IPTC considers digital creation date
(for
> example) now to be deprecated too (since the Phot Metadata working
group
> hasn't been asked to map it), then there's no reason for the IPTC to
> provide a mapping; I'm quite happy to use my own namespaces elements
in
> G2 to carry deprecated information.
>
> To answer Kelvin's point, I'm not sure there /is/ a business case.
>
>  Paul
>
> This email is from the Press Association.  For more information, see
www.pressassociation.com.
> This email may contain confidential information.
> Only the addressee is permitted to read, copy, distribute or otherwise
use this email or any attachments.
> If you have received it in error, please contact the sender
immediately.
> Any opinion expressed in this email is personal to the sender and may
not reflect the opinion of the Press Association.
> Any email reply to this address may be subject to interception or
monitoring for operational reasons or for lawful business practices.
>

#855

From: "Michael Steidl (IPTC)" <mdirector@...>
Date: Tue Aug 11, 2009 12:21 pm
Subject: RE: Re: Mapping for IIM: digital creation date/time?

mdiptc

Offline

Paul

* re Category: guess why I mentioned it - a well known example of undestructible property.

* ad-hoc workaround for IIM metadata:

The IPTC already created a specification for mapping IIM fields to XMP (the RDF based metadata language created by Adobe) - see:

http://www.iptc.org/std/IIM/4.1/specification/IPTC-IIM-Schema4XMP-1.0-spec_1.pdf

This document gives at least a guideline for the naming of elements - quite formal: use a prefix of "IIM" and then append the record number, a hyphen and the dataset number in the record in a three-digit-format, e.g. Category would be IIM2-015

Then we only would have to agree on a namespace identifier and a recommended ns prefix.

Michael

On 11 Aug 2009 at 12:54 Paul Harman wrote:

> From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On

> Behalf Of Michael Steidl (IPTC)

> > should *all* metadata fields from all previous IPTC standards be

> mapped to G2?

> > [...] 2:15 Category which is used by IIM V2 implementers but IIM V4

> defines

> > its use is deprecated.

> Category might be deprecated in the spec but it is still widely used -

> not everyone was prepared to use subject codes :-P

> But the point is well made: if IPTC considers digital creation date

> (for

> example) now to be deprecated too (since the Phot Metadata working

> group

> hasn't been asked to map it), then there's no reason for the IPTC to

> provide a mapping; I'm quite happy to use my own namespaces elements in

> G2 to carry deprecated information.

> To answer Kelvin's point, I'm not sure there /is/ a business case.

> Paul

> This email is from the Press Association. For more information, see

> www.pressassociation.com.

> This email may contain confidential information.

> Only the addressee is permitted to read, copy, distribute or otherwise

> use this email or any attachments.

> If you have received it in error, please contact the sender immediately.

> Any opinion expressed in this email is personal to the sender and may not

> reflect the opinion of the Press Association.

> Any email reply to this address may be subject to interception or

> monitoring for operational reasons or for lawful business practices.

> ------------------------------------

> Any member of this IPTC moderated Yahoo group must comply with the

> Intellectual Property Policy of the IPTC, available at

> http://www.iptc.org/goto/ipp. Any posting is assumed to be submitted

> under the conditions of this IPTC IP Policy.

> Yahoo! Groups Links

> <*> To visit your group on the web, go to:

> http://groups.yahoo.com/group/newsml-g2/

> <*> Your email settings:

> Individual Email | Traditional

> <*> To change settings online go to:

> http://groups.yahoo.com/group/newsml-g2/join

> (Yahoo! ID required)

> <*> To change settings via email:

> mailto:newsml-g2-digest@yahoogroups.com

> mailto:newsml-g2-fullfeatured@yahoogroups.com

> <*> To unsubscribe from this group, send an email to:

> newsml-g2-unsubscribe@yahoogroups.com

> <*> Your use of Yahoo! Groups is subject to:

> http://docs.yahoo.com/info/terms/

==================================================

Sent by:

Michael Steidl

Managing Director of the IPTC <mdirector@...>

International Press Telecommunications Council

"Information Technology for News"

Visit us on the web at http://www.iptc.org

#854

From: "Paul Harman" <paul.harman@...>
Date: Tue Aug 11, 2009 11:54 am
Subject: RE: Re: Mapping for IIM: digital creation date/time?

seancortan

Offline

From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On
Behalf Of Michael Steidl (IPTC)
> should *all* metadata fields from all previous IPTC standards be
mapped to G2?
> [...] 2:15 Category which is used by IIM V2 implementers but IIM V4
defines
> its use is deprecated.



Category might be deprecated in the spec but it is still widely used -
not everyone was prepared to use subject codes :-P

But the point is well made: if IPTC considers digital creation date (for
example) now to be deprecated too (since the Phot Metadata working group
hasn't been asked to map it), then there's no reason for the IPTC to
provide a mapping; I'm quite happy to use my own namespaces elements in
G2 to carry deprecated information.

To answer Kelvin's point, I'm not sure there /is/ a business case.

	 Paul

This email is from the Press Association.  For more information, see
www.pressassociation.com.
This email may contain confidential information.
Only the addressee is permitted to read, copy, distribute or otherwise use this
email or any attachments.
If you have received it in error, please contact the sender immediately.
Any opinion expressed in this email is personal to the sender and may not
reflect the opinion of the Press Association.
Any email reply to this address may be subject to interception or monitoring for
operational reasons or for lawful business practices.

#853

From: "kelvin_holland" <kholland@...>
Date: Tue Aug 11, 2009 11:23 am
Subject: Re: Mapping for IIM: digital creation date/time?

kelvin_holland

Offline

What could be the business case(s) for exchanging the Digital Creation
date/time between partners?

Kelvin


--- In newsml-g2@yahoogroups.com, "Michael Steidl (IPTC)"
<mdirector@...> wrote:
>
> Paul and Dave
>
> this could and should be discussed but I want to point out that this
is a very generic issue:
>
> - should *all* metadata fields from all previous IPTC standards be
mapped to G2?
>
> - some metadata of e.g. IIM do not fully align with corresponding G2
properties - what to do?
>
> - which version of IIM to replicate to G2 - there are some tripwires
as the 2:15 Category
> which is used by IIM V2 implementers but IIM V4 defines its use is
deprecated.
>
> - IIM has dataset which don't fit into the G2 design at all - e.g.
2:125 Rasterized Caption
> defined as: Not repeatable, 7360 octets, consisting of binary data,
one bit
> per pixel, two value bitmap where 1 (one) represents black and
> 0 (zero) represents white.
> Image width 460 pixels and image height 128 pixels.
> Scanning direction bottom to top, left to right.
>
> ------
>
> Finally I want to point at the pending project of a property map
across all IPTC exchange
> format standards to be used as a reference - but as this is a lot of
work it is still unfinished.
>
> Michael
>
>
>
> --------------------------------------------------
> On 11 Aug 2009 at 9:04  dave.compton@... wrote:
>
>
>
> > I'd like to be able to potentially preserve any populated IIM field
> rather thank just map the ones I think are used, and then get
surprised
> later.
>
> Agreed. We have the same use case, and an internal mapping spreadsheet
from IIM (and
> other formats) -> NML2. I'll see if we can share this (or part of it)
publically.
> Rgds
> DC
>
>
> From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On
Behalf Of
> Paul Harman
> Sent: 11 August 2009 08:56
> To: newsml-g2@yahoogroups.com
> Subject: RE: [newsml-g2] Re: Mapping for IIM: digital creation
date/time?
>
> From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On
> Behalf Of Michael Steidl (IPTC)
> > A final note: interesting to see a demand for this digitizing
> > date as in the course of creating and extending the IPTC
> > Photo Metadata Standards the corresponding Working Group
> > was not approach with a request.
>
> :-)
>
> I don't know if PA's archive is using digital creation date - I will
> check. I was just looking at the IIM spec and mapping to the G2 spec;
> I'd like to be able to potentially preserve any populated IIM field
> rather thank just map the ones I think are used, and then get
surprised
> later.
>
> Paul
>
> This email is from the Press Association. For more information, see
> www.pressassociation.com.
> This email may contain confidential information.
> Only the addressee is permitted to read, copy, distribute or otherwise
use this email or any
> attachments.
> If you have received it in error, please contact the sender
immediately.
> Any opinion expressed in this email is personal to the sender and may
not reflect the opinion
> of the Press Association.
> Any email reply to this address may be subject to interception or
monitoring for operational
> reasons or for lawful business practices.
>
> This email was sent to you by Thomson Reuters, the global news and
information company.
> Any views expressed in this message are those of the individual
sender, except where the
> sender specifically states them to be the views of Thomson Reuters.
>
>
> ==================================================
> Sent by:
> Michael Steidl
> Managing Director of the IPTC mdirector@...
> International Press Telecommunications Council
> "Information Technology for News"
> Visit us on the web at  http://www.iptc.org
>
>
> The following section of this message contains a file attachment
> prepared for transmission using the Internet MIME message format.
> If you are using Pegasus Mail, or any other MIME-compliant system,
> you should be able to save it or view it from within your mailer.
> If you cannot, please ask your system administrator for assistance.
>
>    ---- File information -----------
>      File:  DEFAULT.BMP
>      Date:  4 Nov 2007, 20:21
>      Size:  358 bytes.
>      Type:  Unknown
>

#852

From: "Michael Steidl (IPTC)" <mdirector@...>
Date: Tue Aug 11, 2009 10:21 am
Subject: RE: Re: Mapping for IIM: digital creation date/time?

mdiptc

Offline

Paul and Dave

this could and should be discussed but I want to point out that this is a very generic issue:

- should *all* metadata fields from all previous IPTC standards be mapped to G2?

- some metadata of e.g. IIM do not fully align with corresponding G2 properties - what to do?

- which version of IIM to replicate to G2 - there are some tripwires as the 2:15 Category which is used by IIM V2 implementers but IIM V4 defines its use is deprecated.

- IIM has dataset which don't fit into the G2 design at all - e.g. 2:125 Rasterized Caption defined as: Not repeatable, 7360 octets, consisting of binary data, one bit

per pixel, two value bitmap where 1 (one) represents black and

0 (zero) represents white.

Image width 460 pixels and image height 128 pixels.

Scanning direction bottom to top, left to right.

------

Finally I want to point at the pending project of a property map across all IPTC exchange format standards to be used as a reference - but as this is a lot of work it is still unfinished.

Michael

--------------------------------------------------

On 11 Aug 2009 at 9:04 dave.compton@... wrote:

> I'd like to be able to potentially preserve any populated IIM field
rather thank just map the ones I think are used, and then get surprised
later.

Agreed. We have the same use case, and an internal mapping spreadsheet from IIM (and other formats) -> NML2. I'll see if we can share this (or part of it) publically.

Rgds

From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On Behalf Of Paul Harman
Sent: 11 August 2009 08:56
To: newsml-g2@yahoogroups.com
Subject: RE: [newsml-g2] Re: Mapping for IIM: digital creation date/time?

From: newsml-g2@yahoogroups.com [mailto: newsml-g2@yahoogroups.com ] On
Behalf Of Michael Steidl (IPTC)
> A final note: interesting to see a demand for this digitizing
> date as in the course of creating and extending the IPTC
> Photo Metadata Standards the corresponding Working Group
> was not approach with a request.

:-)

I don't know if PA's archive is using digital creation date - I will
check. I was just looking at the IIM spec and mapping to the G2 spec;
I'd like to be able to potentially preserve any populated IIM field
rather thank just map the ones I think are used, and then get surprised
later.

Paul

This email is from the Press Association. For more information, see www.pressassociation.com.
This email may contain confidential information.
Only the addressee is permitted to read, copy, distribute or otherwise use this email or any attachments.
If you have received it in error, please contact the sender immediately.
Any opinion expressed in this email is personal to the sender and may not reflect the opinion of the Press Association.
Any email reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.

==================================================

Sent by:

Michael Steidl

Managing Director of the IPTC <mdirector@...>

International Press Telecommunications Council

"Information Technology for News"

Visit us on the web at http://www.iptc.org

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

    ---- File information -----------
      File:  DEFAULT.BMP
      Date:  4 Nov 2007, 20:21
      Size:  358 bytes.
      Type:  Unknown

#851

From: <dave.compton@...>
Date: Tue Aug 11, 2009 8:04 am
Subject: RE: Re: Mapping for IIM: digital creation date/time?

davecompton987

Offline

> I'd like to be able to potentially preserve any populated IIM field
rather thank just map the ones I think are used, and then get surprised
later.

Agreed. We have the same use case, and an internal mapping spreadsheet from IIM (and other formats) -> NML2. I'll see if we can share this (or part of it) publically.

Rgds

From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On
Behalf Of Michael Steidl (IPTC)
> A final note: interesting to see a demand for this digitizing
> date as in the course of creating and extending the IPTC
> Photo Metadata Standards the corresponding Working Group
> was not approach with a request.

:-)

I don't know if PA's archive is using digital creation date - I will
check. I was just looking at the IIM spec and mapping to the G2 spec;
I'd like to be able to potentially preserve any populated IIM field
rather thank just map the ones I think are used, and then get surprised
later.

Paul

This email is from the Press Association. For more information, see www.pressassociation.com.
This email may contain confidential information.
Only the addressee is permitted to read, copy, distribute or otherwise use this email or any attachments.
If you have received it in error, please contact the sender immediately.
Any opinion expressed in this email is personal to the sender and may not reflect the opinion of the Press Association.
Any email reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.

#850

From: "Paul Harman" <paul.harman@...>
Date: Tue Aug 11, 2009 7:55 am
Subject: RE: Re: Mapping for IIM: digital creation date/time?

seancortan

Offline

From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On
Behalf Of Michael Steidl (IPTC)
> A final note: interesting to see a demand for this digitizing
> date as in the course of creating and extending the IPTC
> Photo Metadata Standards the corresponding Working Group
> was not approach with a request.


:-)

I don't know if PA's archive is using digital creation date - I will
check. I was just looking at the IIM spec and mapping to the G2 spec;
I'd like to be able to potentially preserve any populated IIM field
rather thank just map the ones I think are used, and then get surprised
later.

	 Paul

This email is from the Press Association.  For more information, see
www.pressassociation.com.
This email may contain confidential information.
Only the addressee is permitted to read, copy, distribute or otherwise use this
email or any attachments.
If you have received it in error, please contact the sender immediately.
Any opinion expressed in this email is personal to the sender and may not
reflect the opinion of the Press Association.
Any email reply to this address may be subject to interception or monitoring for
operational reasons or for lawful business practices.

#849

From: "Michael Steidl (IPTC)" <mdirector@...>
Date: Mon Aug 10, 2009 7:37 pm
Subject: Re: Re: Mapping for IIM: digital creation date/time?

mdiptc

Offline

Paul and Kelvin

just returned from some days off - taking photos etc. ;-)

Seriously: no, there is no G2 metadata property to reflect the date of digitizing a photo.

A few comments on Kelvin's proposal:

re 3: scanning a photo is not modifying the content - which would be something like gropping, changing the colourspace etc.

re 2: I feel this is the worst workaround as this content created date is also relevant to intellectual property and copyright issues.

re 1: this could work if the just scanned photos is also ingested into a G2 item - at least on the same day. But in practice there will be thousands of photos scanned years ago and made a G2 item now - then this does not work.

A final note: interesting to see a demand for this digitizing date as in the course of creating and extending the IPTC Photo Metadata Standards the corresponding Working Group was not approach with a request.

Michael

On 10 Aug 2009 at 17:27 kelvin_holland wrote:

> Paul,

> I didn't see a response so I will jump in here, as I would also like to

> answer this question in the Guidelines.

> As a "straw man" I will suggest some options, and hope someone agrees,

> disagreess, or comes up with something better. At least we might get

> somewhere. In reverse order of (my) preference:

> 3. You could use <contentModified>, although it doesn't seem quite right.

> After all, has the content been modified? No, it's just a digital

> representation of the same content. (Changing the metadata should not

> trigger a new Content Modified date)

> 2. You could ignore the difference in semantics between the two IIM

> DataSets, and map the Digital Creation Date to <contentCreated>, if

> present and later than Date Created. This would result in an archive

> picture of the Titanic having a Content Created date sometime in the late

> 20th Century - also a strange result.

> 1. Or you could use <firstCreated> in <itemMeta> for the Digital Creation

> Date? I can't think of a reason why this would yield an strange result.

> Objections, anyone?

> Regards

> Kelvin

> Or--- In newsml-g2@yahoogroups.com, "Paul Harman" <paul.harman@...>

> wrote:

> >

> > I can't find a suitable slot in G2 to hold the digital creation

> > date/time for photos (IIM fields 2:62 and 2:63). I'm happy to use

> > namespacing to introduce my own, but I wanted to check first whether

> > this is the subject of an upcoming change?

> >

> > Paul

> >

> > This email is from the Press Association. For more information, see

> www.pressassociation.com.

> > This email may contain confidential information.

> > Only the addressee is permitted to read, copy, distribute or otherwise

> use this email or any attachments.

> > If you have received it in error, please contact the sender

> immediately.

> > Any opinion expressed in this email is personal to the sender and may

> not reflect the opinion of the Press Association.

> > Any email reply to this address may be subject to interception or

> monitoring for operational reasons or for lawful business practices.

> >

> ------------------------------------

> Any member of this IPTC moderated Yahoo group must comply with the

> Intellectual Property Policy of the IPTC, available at

> http://www.iptc.org/goto/ipp. Any posting is assumed to be submitted

> under the conditions of this IPTC IP Policy.

> Yahoo! Groups Links

> <*> To visit your group on the web, go to:

> http://groups.yahoo.com/group/newsml-g2/

> <*> Your email settings:

> Individual Email | Traditional

> <*> To change settings online go to:

> http://groups.yahoo.com/group/newsml-g2/join

> (Yahoo! ID required)

> <*> To change settings via email:

> mailto:newsml-g2-digest@yahoogroups.com

> mailto:newsml-g2-fullfeatured@yahoogroups.com

> <*> To unsubscribe from this group, send an email to:

> newsml-g2-unsubscribe@yahoogroups.com

> <*> Your use of Yahoo! Groups is subject to:

> http://docs.yahoo.com/info/terms/

==================================================

Sent by:

Michael Steidl

Managing Director of the IPTC <mdirector@...>

International Press Telecommunications Council

"Information Technology for News"

Visit us on the web at http://www.iptc.org

#848

From: "kelvin_holland" <kholland@...>
Date: Mon Aug 10, 2009 5:27 pm
Subject: Re: Mapping for IIM: digital creation date/time?

kelvin_holland

Offline

Paul,

I didn't see a response so I will jump in here, as I would also like to answer
this question in the Guidelines.

As a "straw man" I will suggest some options, and hope someone agrees,
disagreess, or comes up with something better. At least we might get somewhere.
In reverse order of (my) preference:

3. You could use <contentModified>, although it doesn't seem quite right. After
all, has the content been modified? No, it's just a digital representation of
the same content. (Changing the metadata should not trigger a new Content
Modified date)

2. You could ignore the difference in semantics between the two IIM DataSets,
and map the Digital Creation Date to <contentCreated>, if present and later than
Date Created. This would result in an archive picture of the Titanic having a
Content Created date sometime in the late 20th Century - also a strange result.

1. Or you could use <firstCreated> in <itemMeta> for the Digital Creation Date?
I can't think of a reason why this would yield an strange result. Objections,
anyone?

Regards

Kelvin

Or--- In newsml-g2@yahoogroups.com, "Paul Harman" <paul.harman@...> wrote:
>
> I can't find a suitable slot in G2 to hold the digital creation
> date/time for photos (IIM fields 2:62 and 2:63). I'm happy to use
> namespacing to introduce my own, but I wanted to check first whether
> this is the subject of an upcoming change?
>
>  Paul
>
> This email is from the Press Association.  For more information, see
www.pressassociation.com.
> This email may contain confidential information.
> Only the addressee is permitted to read, copy, distribute or otherwise use
this email or any attachments.
> If you have received it in error, please contact the sender immediately.
> Any opinion expressed in this email is personal to the sender and may not
reflect the opinion of the Press Association.
> Any email reply to this address may be subject to interception or monitoring
for operational reasons or for lawful business practices.
>

#847

From: Darko Gulija <darko.gulija@...>
Date: Wed Jul 29, 2009 12:46 pm
Subject: Re: How do I include new contententMeta items?

dgulija

Offline

IPTC is also working on usage guidelines for the whole G2 standards family, which would give you more information on how to implement some features (including the extension points). The guidelines should be available in early fall.

Would you be so kind and share with us which kind of data you would like to include into NewsML-G2 ?

You may get some useful advices form other people having similar problems, or provide ideas for their inclusion in the next version of the standard.

Best regards,

Darko Gulija

G2-Standards WP chairman

Knowledge Management Consultant

Infodom d.o.o.
A. Žaje 61/1

10000 Zagreb, Croatia

T: +385 1 3090 507

F: +385 1 3040 593

W: www.infodom.hr

2009/7/28 tentonipete <tentonipete@...>

I would like to include extra elements which are not covered by the NewsML-G2 schema. How do I go about doing this?

Are there any examples available that show it?

Thanks

------------------------------------

Any member of this IPTC moderated Yahoo group must comply with the Intellectual Property Policy of the IPTC, available at http://www.iptc.org/goto/ipp. Any posting is assumed to be submitted under the conditions of this IPTC IP Policy.
Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/newsml-g2/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/newsml-g2/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:newsml-g2-digest@yahoogroups.com
mailto:newsml-g2-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
newsml-g2-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

#846

From: <robert.schmidt-nia@...>
Date: Wed Jul 29, 2009 11:03 am
Subject: AW: How do I include new contententMeta items?

schmidt_nia

Offline

Hi,

another question is, what kind of data do you want to use within G2 which are not modelled in G2 yet. Are these internal data, or have we forgotten some data?

Robert

#845

From: <dave.compton@...>
Date: Wed Jul 29, 2009 6:35 am
Subject: RE: How do I include new contententMeta items?

davecompton987

Offline

www.linkedin.com/in/davecompton

You can use the Extension Point (0..unbounded) on any element, which permits any set of provider-defined properties. Additionally, extension attributes can be added. An appropriate namespace is required.

Example: A Thomson Reuters extension to itemMeta:

Similarly, you could extend contentMeta (using, say the xyz namespace) as below:

      <contentMeta>
        <urgency>4</urgency>
         ...
        <xyz:myExtElement>Ext Element Value</xyz:myExtElement>
      </contentMeta>

Regards

------------------------------------------------------------------------------------

Dave Compton
Senior Technologist. NewsML Technical Owner.

Thomson Reuters

Phone: +44 (0)20 7542 8341
Mobile: +44 (0) 7990 56 8341

dave.compton@...
dave.compton.reuters.com@...
mediadev.uki.ime.reuters.com/users/djc/ref/
www.thomsonreuters.com

From: newsml-g2@yahoogroups.com [mailto:newsml-g2@yahoogroups.com] On Behalf Of tentonipete
Sent: 28 July 2009 17:25
To: newsml-g2@yahoogroups.com
Subject: [newsml-g2] How do I include new contententMeta items?

I would like to include extra elements which are not covered by the NewsML-G2 schema. How do I go about doing this?

Are there any examples available that show it?

Thanks

#844

From: "tentonipete" <tentonipete@...>
Date: Tue Jul 28, 2009 4:24 pm
Subject: How do I include new contententMeta items?

tentonipete

Offline

I would like to include extra elements which are not covered by the NewsML-G2
schema. How do I go about doing this?

Are there any examples available that show it?

Thanks