- From: Stephan Zednik <zednis2@rpi.edu>
- Date: Thu, 9 May 2013 10:28:55 -0600
- To: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
- Cc: "public-prov-wg@w3.org" <public-prov-wg@w3.org>
Comments below. On May 7, 2013, at 4:22 PM, Luc Moreau <L.Moreau@ecs.soton.ac.uk> wrote: > Hi Stephan, > > See below. > > On 07/05/13 22:51, Stephan Zednik wrote: >> Hi Luc, >> >> Comments below. >> >> On May 7, 2013, at 3:55 AM, Luc Moreau <l.moreau@ecs.soton.ac.uk> wrote: >> >>> Hi Stephan, >>> >>> I updated the provx file: prov:key now appears before entity. >>> >>> The challenge is for identifiers. >>> >>> We can manually edit ids so that no / appears in the local name. >>> >>> chairs:2012AprJun/0037 -> chairs_2012AprJun:0037 >>> >>> but the challenge is for local identifiers starting with a number. All w3c email archives identify >>> messages with numbers :-( >>> >>> Not sure what the right approach is >> Hmm, >> >> What if the number is part of the prefix and we append a local name? A URI to the web page could be a non-PROV attribute on the entity. >> >> How about >> >> <prov:entity prov:id="email_2011Oct_0141:msg" xmlns:email_2011Oct_0141="https://lists.w3.org/Archives/Member/w3c-archive/2011Oct/0141/"> >> ... >> </prov:entity> >> >> I don't remember, but is '#' a valid NCName? >> >> If so, I believe the QName above could be "email_2011Oct_0141:#", which would expand to be similar (equivalent?) to the URL you want the identifier to expand to. > > I don't think that # is allowed in an NCNAme. > > So, trying to generalize your proposal, when the id (prefix:local) of a resource does not > have a localname that is an NCName, > > - mint a proper QName > - add an attribute provx:url= ... with the url. Well, I think I see a possible solution but we would need to modify the schema. If we supported the xlink:href attribute on any elements that support prov:id or prov:ref attributes then we could use that to specify the full URI. In this way we could specify the URI & PROV ID for prov objects that are referenced but not locally declared... As it is now, we should use a prov-"attrifbute" xml element and constrain all elements in our document that qnames to have a declaration and this prov-"attribute" xml element. > > > I guess this is all fine when you "declare" an entity (or any prov object). But what if you just refer to one and there is no declaration for it in the same file? > > Should the minted QNames be recognizable? so that they can be converted back to the uri? > Should we request that all minted QNames should have a corresponding declaration? In our case I think so. --Stephan > > > > > Luc > > >> >> Stephan >> >> >>> >>> Luc >>> >>> On 05/02/2013 04:27 PM, Stephan Zednik wrote: >>>> I just ran a schema validator on prov-family.provx and there are a number of errors, but most are about invalid xs:QName values and should be straightforward to resolve. >>>> >>>> The validation results are attached. >>>> >>>> The most common issue by far is that the local part of a prov:id starts with a number, which is not allowed in xs:QName. >>>> >>>> w3:2011/01/prov-wg-charter >>>> email:2012Apr/0583 >>>> chairs:2011OctDec/0004 >>>> ... >>>> >>>> I believe our other issues are caused by >>>> >>>> 1) having a '/' in the local part of a xs:QName >>>> 2) our use of prov:key >>>> >>>> I will look further into these. >>>> >>>> --Stephan >>> -- >>> Professor Luc Moreau >>> Electronics and Computer Science tel: +44 23 8059 4487 >>> University of Southampton fax: +44 23 8059 2865 >>> Southampton SO17 1BJ email: l.moreau@ecs.soton.ac.uk >>> United Kingdom http://www.ecs.soton.ac.uk/~lavm >>> >>> >>> > > -- > Professor Luc Moreau > Electronics and Computer Science tel: +44 23 8059 4487 > University of Southampton fax: +44 23 8059 2865 > Southampton SO17 1BJ email: l.moreau@ecs.soton.ac.uk > United Kingdom http://www.ecs.soton.ac.uk/~lavm > > >
Received on Thursday, 9 May 2013 16:29:21 UTC