Re: ACTION-293 Check global rules examples in provenance

Hi Mauricio,
You you are right that second provRule overrides the first, but the idea 
is that the standoff mechanism now allows you to overcome that, i.e. you 
put the two sets of attribute in two different provRec elements in a 
provRecs element referred to by a provRecsRef attribute in a single tool 
- similar to how we do this for locqualityissues.

Does that work OK for you?

I also see now that I've not been consistent with the attribute naming, 
so i'll change activity/person/tool/org to 
provActivity/provPerson/provTool/provOrg

cheers,
Dave

On 14/11/2012 09:03, Mauricio del Olmo wrote:
>
> Hello Dave.
>
> If I understand it correctly, after the attribute names unification 
> for translation and revision in the provenance data category:
>
> Before I used the global rule this way:
>
> <its:transProvRuleselector="//item"transOrg="Linguaserve"transPerson="11236"transRevOrg="Linguaserve"transRevPerson="11239"/>
>
> Now I should do this with the new proposal:
>
> <its:provRuleactivity="translation"org="Linguaserve"person="11236"selector="//item" 
> />
>
> <its:provRuleactivity="transRevision"org="Linguaserve"person="11239"selector="//item" 
> />
>
> But this doesn't mean that the second rule overrides the first one 
> (the revision rule overrides the translation rule)?
>
> Note that the translator and the revisor are not the same person.
>
> Thank you.
>
> Cheers.
>
> *__________________________________*
>
> *Mauricio del Olmo Martínez*
>
> *Dpto. Técnico/I+D+i*
>
> *Linguaserve Internacionalización de Servicios, S.A.*
>
> *Tel.: +34 91 761 64 60 ext. 0421
> Fax: +34 91 542 89 28 *
>
> *E-mail: **tecnico@linguaserve.com <mailto:tecnico@linguaserve.com>***
>
> *www.linguaserve.com <http://www.linguaserve.com/>*
>
> **
>
> *«En cumplimiento con lo previsto con los artículos 21 y 22 de la Ley 
> 34/2002, de 11 de julio, de Servicios de la Sociedad de Información y 
> Comercio Electrónico, le informamos que procederemos al archivo y 
> tratamiento de sus datos exclusivamente con fines de promoción de los 
> productos y servicios ofrecidos por LINGUASERVE INTERNACIONALIZACIÓN 
> DE SERVICIOS, S.A. En caso de que Vdes. no deseen que procedamos al 
> archivo y tratamiento de los datos proporcionados, o no deseen recibir 
> comunicaciones comerciales sobre los productos y servicios ofrecidos, 
> comuníquenoslo a clients@linguaserve.com 
> <mailto:clients@linguaserve.com>, y su petición será inmediatamente 
> cumplida.»*
>
> **
>
> *"According to the provisions set forth in articles 21 and 22 of Law 
> 34/2002 of July 11 regarding Information Society and eCommerce 
> Services, we will store and use your personal data with the sole 
> purpose of marketing the products and services offered by LINGUASERVE 
> INTERNACIONALIZACIÓN DE SERVICIOS, S.A. If you do not wish your 
> personal data to be stored and handled, or you do not wish to receive 
> further information regarding products and services offered by our 
> company, please e-mail us to clients@linguaserve.com 
> <mailto:clients@linguaserve.com>. Your request will be processed 
> immediately."*
>
> *__________________________________*
>
> -----Mensaje original-----
> De: Dave Lewis [mailto:dave.lewis@cs.tcd.ie]
> Enviado el: martes, 13 de noviembre de 2012 1:59
> Para: Felix Sasaki; public-multilingualweb-lt@w3.org
> Asunto: provenance text update
>
> Hi Felix,
>
> Here's that provenance text update where I've:
>
> - made some wording updates on the description
>
> - renamed the data category, actually just to provenance (the provRef 
> aspect amkes it slightly broader than just agents)
>
> - removed the trans/transRev subdivision and introduced a 
> differnetiating flag 'activity'. Currently this just has values 
> translation and translationRevision, but we can quickly add to this as 
> suggested by marcis
>
> - made the use of pointer and non pointer rules mutually exclusive 
> (hopefullly examples will now tell us which we really need)
>
> - allow stand off provenance records to be used in global _and_ local
>
> - I broadened the language for the provRef attribute, so it can still 
> point to a PROV record (specifically an entity one), but could also 
> point to other records. Seeing the work starting on XML change records 
> at TPAC and also seeing some convergence on a specific PEMT activity 
> logging format in XML between CNGL and the CASMECAT project - it 
> seemed prudent not to exclude these others (note this isn't bound to 
> the activity value like the other attributes)
>
> Note, I didn't yet update the attribute names in the notes on pointer 
> with html usage.
>
> Later Tuesday I'll aim to get you the informative annex on PROV usage 
> - I was just updating the content Dom provided to give the turtle 
> rather than the native text version of examples - I think that will 
> make it more relevant for the HTML and SemWeb crowd.
>
> Then I'll start on reworking the examples, to make them more 
> realistic, and to remove pointer/non-pointer mixes.
>
> thanks for your patience on this,
>
> cheers,
>
> Dave
>