Re: [CODE4LIB] Access 2013 - room-mate
Hi, This doesn't help Bobbi any, but along the same lines, I've got a room at a BB about ten minutes' walk from the Masonic Temple. Happy to have a male non-smoker share the room, if anyone's interested. (It's $99 a night, so half of that isn't too bad) the room: http://bit.ly/Access2013Room the place: http://bit.ly/therosesnl Take care, Joe Montibello, MLIS Library Systems Manager Dartmouth College Library 603.646.9394 joseph.montibe...@dartmouth.edu On 9/12/13 4:59 PM, Fox, Bobbi bobbi_...@harvard.edu wrote: If you're a woman going to Access 2013 (http://accessconference.ca/) the week after next, would you like to save money by sharing a room? I currently have something booked at the Extended Stay St Johns -- Downtown, but can cancel it if you have a better deal :-) Time's growing short, so please give a shout soon. Thanks, Bobbi
[CODE4LIB] Expressing negatives and similar in RDF
Hello, I'm not sure how sensible a question this is (it's certainly theoretical), but it cropped up in relation to a rare books cataloguing discussion. Is there a standard or accepted way to express negatives in RDF? This is best explained by examples, expressed in mock-turtle: If I want to say this book has the title Cats in RDA I would do something like: example:thisbook dc:title Cats in RDA . Normally, if a predicate like dc:title is not relevant to example:thisbook I believe I am right in thinking that it would simply be missing, i.e. it is not part of a record where a set number of fields need to be filled in, so no need to even make the statement. However, there are occasions where a positively negative statement might be useful. I understand OWL has a way of managing the statement This book does not have the title Cats in RDA [1]: [] rdf:type owl:NegativePropertyAssertion ; owl:sourceIndividual example:thisbook ; owl:assertionProperty dc:title ; owl:targetIndividual Cats in RDA . However, it would be more useful, and quite common at least in a bibliographic context, to say This book does not have a title. Ideally (?!) there would be an ontology of concepts like none, unknown, or even something, but unspecified: This book has no title: example:thisbook dc:title hasobject:false . It is unknown if this book has a title (sounds undesirable but I can think of instances where it might be handy[2]): example:thisbook dc:title hasobject:unknown . This book has a title but it has not been specified: example:thisbook dc:title hasobject:true . In terms of cataloguing, the answer is perhaps to refer to the rules (which would normally mandate supplied titles in square brackets and so forth) rather than use RDF to express this kind of thing, although the rules differ depending on the part of description and, in the case of the kind of thing that prompted the question- the presence of clasps on rare books- there are no rules. I wonder if anyone has any more wisdom on this. Many thanks, Tom [1] Adapted from http://www.w3.org/2007/OWL/wiki/Primer#Object_Properties [2] No many tbh, but e.g. title in an unknown script or indecipherable hand. --- Thomas Meehan Head of Current Cataloguing Library Services University College London Gower Street London WC1E 6BT t.mee...@ucl.ac.uk
Re: [CODE4LIB] Expressing negatives and similar in RDF
Thomas- This isn't something I've run across yet. But one thing you could do is create some URIs for different kinds of unknown/nonexistent titles: example:book1 dc:title example:unknownTitle example:book2 dc:title example:noTitle etc. You could then describe example:unknownTitle with a label or comment to fully describe the states you wanted to capture with the different categories. -Esme -- Esme Cowles escow...@ucsd.edu Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. -- William Pitt, 1783 On 09/13/2013, at 7:32 AM, Meehan, Thomas t.mee...@ucl.ac.uk wrote: Hello, I'm not sure how sensible a question this is (it's certainly theoretical), but it cropped up in relation to a rare books cataloguing discussion. Is there a standard or accepted way to express negatives in RDF? This is best explained by examples, expressed in mock-turtle: If I want to say this book has the title Cats in RDA I would do something like: example:thisbook dc:title Cats in RDA . Normally, if a predicate like dc:title is not relevant to example:thisbook I believe I am right in thinking that it would simply be missing, i.e. it is not part of a record where a set number of fields need to be filled in, so no need to even make the statement. However, there are occasions where a positively negative statement might be useful. I understand OWL has a way of managing the statement This book does not have the title Cats in RDA [1]: [] rdf:type owl:NegativePropertyAssertion ; owl:sourceIndividual example:thisbook ; owl:assertionProperty dc:title ; owl:targetIndividual Cats in RDA . However, it would be more useful, and quite common at least in a bibliographic context, to say This book does not have a title. Ideally (?!) there would be an ontology of concepts like none, unknown, or even something, but unspecified: This book has no title: example:thisbook dc:title hasobject:false . It is unknown if this book has a title (sounds undesirable but I can think of instances where it might be handy[2]): example:thisbook dc:title hasobject:unknown . This book has a title but it has not been specified: example:thisbook dc:title hasobject:true . In terms of cataloguing, the answer is perhaps to refer to the rules (which would normally mandate supplied titles in square brackets and so forth) rather than use RDF to express this kind of thing, although the rules differ depending on the part of description and, in the case of the kind of thing that prompted the question- the presence of clasps on rare books- there are no rules. I wonder if anyone has any more wisdom on this. Many thanks, Tom [1] Adapted from http://www.w3.org/2007/OWL/wiki/Primer#Object_Properties [2] No many tbh, but e.g. title in an unknown script or indecipherable hand. --- Thomas Meehan Head of Current Cataloguing Library Services University College London Gower Street London WC1E 6BT t.mee...@ucl.ac.uk
Re: [CODE4LIB] Expressing negatives and similar in RDF
+1 On Fri, Sep 13, 2013 at 8:51 AM, Esmé Cowles escow...@ucsd.edu wrote: Thomas- This isn't something I've run across yet. But one thing you could do is create some URIs for different kinds of unknown/nonexistent titles: example:book1 dc:title example:unknownTitle example:book2 dc:title example:noTitle etc. You could then describe example:unknownTitle with a label or comment to fully describe the states you wanted to capture with the different categories. -Esme -- Esme Cowles escow...@ucsd.edu Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. -- William Pitt, 1783 On 09/13/2013, at 7:32 AM, Meehan, Thomas t.mee...@ucl.ac.uk wrote: Hello, I'm not sure how sensible a question this is (it's certainly theoretical), but it cropped up in relation to a rare books cataloguing discussion. Is there a standard or accepted way to express negatives in RDF? This is best explained by examples, expressed in mock-turtle: If I want to say this book has the title Cats in RDA I would do something like: example:thisbook dc:title Cats in RDA . Normally, if a predicate like dc:title is not relevant to example:thisbook I believe I am right in thinking that it would simply be missing, i.e. it is not part of a record where a set number of fields need to be filled in, so no need to even make the statement. However, there are occasions where a positively negative statement might be useful. I understand OWL has a way of managing the statement This book does not have the title Cats in RDA [1]: [] rdf:type owl:NegativePropertyAssertion ; owl:sourceIndividual example:thisbook ; owl:assertionProperty dc:title ; owl:targetIndividual Cats in RDA . However, it would be more useful, and quite common at least in a bibliographic context, to say This book does not have a title. Ideally (?!) there would be an ontology of concepts like none, unknown, or even something, but unspecified: This book has no title: example:thisbook dc:title hasobject:false . It is unknown if this book has a title (sounds undesirable but I can think of instances where it might be handy[2]): example:thisbook dc:title hasobject:unknown . This book has a title but it has not been specified: example:thisbook dc:title hasobject:true . In terms of cataloguing, the answer is perhaps to refer to the rules (which would normally mandate supplied titles in square brackets and so forth) rather than use RDF to express this kind of thing, although the rules differ depending on the part of description and, in the case of the kind of thing that prompted the question- the presence of clasps on rare books- there are no rules. I wonder if anyone has any more wisdom on this. Many thanks, Tom [1] Adapted from http://www.w3.org/2007/OWL/wiki/Primer#Object_Properties [2] No many tbh, but e.g. title in an unknown script or indecipherable hand. --- Thomas Meehan Head of Current Cataloguing Library Services University College London Gower Street London WC1E 6BT t.mee...@ucl.ac.uk
[CODE4LIB] Fwd: Semantic Web Challenge 2013: Deadline Approaching
Be semantic / Win money - the winning entries should be quite interesting. - kc Original Message Subject: Semantic Web Challenge 2013: Deadline Approaching Resent-Date: Fri, 13 Sep 2013 09:47:29 + Resent-From: public-openannotat...@w3.org Date: Fri, 13 Sep 2013 09:47:00 + From: Sean Bechhofer sean.bechho...@manchester.ac.uk To: semantic...@w3.org semantic...@w3.org, public-...@w3.org public-...@w3.org, public-owl-...@w3.org public-owl-...@w3.org, semantic...@yahoogroups.com semantic...@yahoogroups.com, PlanetKR plane...@kr.org, public-esw-t...@w3.org public-esw-t...@w3.org, public-openannotat...@w3.org public-openannotat...@w3.org Deadline for submissions is in one week. *** Semantic Web Challenge 2013 - Call for Participation http://challenge.semanticweb.org/2013/ Sydney, Australia October 23-25, 2013 *** Submissions are now invited for the 11th Semantic Web Challenge, the premier event for demonstrating practical progress towards achieving the vision of the Semantic Web. The Challenge will take place at the 12th International Semantic Web Conference in Sydney, Australia. The Semantic Web Challenge will consist of two tracks: the Open Track and the Big Data Track. The key difference between the two tracks is that the Big Data Track requires the participants to make use of large- scale data sets. The Open Track has no such restrictions. The Challenge is open to everyone from industry and academia. The authors of the best applications will be awarded prizes and featured prominently at special sessions during the conference. Important Dates * Friday, September 20, 2013, 23:59 CET: Submissions due Please note that you need a visa to enter Australia. You can find more on the visa process on the ISWC website: http://iswc2013.semanticweb.org/content/visa-information You may have to apply for a visa before the submission deadline! Challenge Criteria * The Challenge is defined in terms of minimum requirements and additional desirable features that submissions should exhibit. The criteria for the Semantic Web Challenge 2013 are described here: http://challenge.semanticweb.org/2013/criteria.html. How to Participate * Visit http://challenge.semanticweb.org/ in order to participate and register for the Semantic Web Challenge by submitting the required information. The following information must be provided: 1. Abstract: no more than 200 words. 2. Description: The description should show details of the system, including why the system is innovative, which features or functions the system provides, what design choices were made and what lessons were learned. The description must include an appendix of 1-2 pages summarising explicitly how participants have addressed the evaluation requirements (including mandatory and any relevant desirable criteria). Papers should not exceed eight pages (including the appendix) and must be formatted according to the same guidelines as the papers in the Research Track (see http://iswc2013.semanticweb.org/). 3. Web access: The application should be accessible via the web. If the application is not publicly accessible, passwords should be provided. A (short) set of instructions on how to start and use the application should also be provided on the web page. Descriptions (including the appendix) will be published in the form of online proceedings on the Semantic Web Challenge website. Judging and Prizes *** In addition to submitting a system description and working demo, all participants are required to present their systems at the posters and demos session at the ISWC conference. A jury consisting of experts from industry and academia will be appointed to judge the systems at the conference. In the first round of judging, the jury will take into consideration the descriptions submitted, the online demos, and the presentation at the conference, in order to determine an initial set of up to eight finalists. The entries will be scored by the judges and the eight highest scoring entries will then proceed to the second round of the competition. The split between the two tracks will be determined according to the proportion of entries in each track. The eight finalists will proceed to the second round of the competition, where they will have to present their work in an open session the following day. They will have a slot of approximately 15 minutes to present their work. The judges will be present and will evaluate the systems in more detail, according to the specific criteria detailed on the website. The judges will then meet in private to discuss the entries and to determine the winners. A monetary prize will be provided to the winners of each track, along with publicity for their work. There will normally be three winners of the
Re: [CODE4LIB] Expressing negatives and similar in RDF
At a theoretical level, doesn't the Open World Assumption in RDF rule out outright negations? That is, someone else may know the title, and could assert it in a separate RDF document. RDF semantics seem to conflate unknown with nonexistent. Practically, Esme's approach seems better in these cases. -Don -- Donald Brower, Ph.D. Digital Library Infrastructure Lead Hesburgh Libraries, University of Notre Dame On 9/13/13 8:51 AM, Esmé Cowles escow...@ucsd.edu wrote: Thomas- This isn't something I've run across yet. But one thing you could do is create some URIs for different kinds of unknown/nonexistent titles: example:book1 dc:title example:unknownTitle example:book2 dc:title example:noTitle etc. You could then describe example:unknownTitle with a label or comment to fully describe the states you wanted to capture with the different categories. -Esme -- Esme Cowles escow...@ucsd.edu Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. -- William Pitt, 1783 On 09/13/2013, at 7:32 AM, Meehan, Thomas t.mee...@ucl.ac.uk wrote: Hello, I'm not sure how sensible a question this is (it's certainly theoretical), but it cropped up in relation to a rare books cataloguing discussion. Is there a standard or accepted way to express negatives in RDF? This is best explained by examples, expressed in mock-turtle: If I want to say this book has the title Cats in RDA I would do something like: example:thisbook dc:title Cats in RDA . Normally, if a predicate like dc:title is not relevant to example:thisbook I believe I am right in thinking that it would simply be missing, i.e. it is not part of a record where a set number of fields need to be filled in, so no need to even make the statement. However, there are occasions where a positively negative statement might be useful. I understand OWL has a way of managing the statement This book does not have the title Cats in RDA [1]: [] rdf:type owl:NegativePropertyAssertion ; owl:sourceIndividual example:thisbook ; owl:assertionProperty dc:title ; owl:targetIndividual Cats in RDA . However, it would be more useful, and quite common at least in a bibliographic context, to say This book does not have a title. Ideally (?!) there would be an ontology of concepts like none, unknown, or even something, but unspecified: This book has no title: example:thisbook dc:title hasobject:false . It is unknown if this book has a title (sounds undesirable but I can think of instances where it might be handy[2]): example:thisbook dc:title hasobject:unknown . This book has a title but it has not been specified: example:thisbook dc:title hasobject:true . In terms of cataloguing, the answer is perhaps to refer to the rules (which would normally mandate supplied titles in square brackets and so forth) rather than use RDF to express this kind of thing, although the rules differ depending on the part of description and, in the case of the kind of thing that prompted the question- the presence of clasps on rare books- there are no rules. I wonder if anyone has any more wisdom on this. Many thanks, Tom [1] Adapted from http://www.w3.org/2007/OWL/wiki/Primer#Object_Properties [2] No many tbh, but e.g. title in an unknown script or indecipherable hand. --- Thomas Meehan Head of Current Cataloguing Library Services University College London Gower Street London WC1E 6BT t.mee...@ucl.ac.uk
Re: [CODE4LIB] Expressing negatives and similar in RDF
On 9/13/13 5:51 AM, Esmé Cowles wrote: Thomas- This isn't something I've run across yet. But one thing you could do is create some URIs for different kinds of unknown/nonexistent titles: example:book1 dc:title example:unknownTitle example:book2 dc:title example:noTitle etc. I'm bothered by the semantics of this... but maybe I'm being too rigid. This states that the title is a URI, not a string, and that the URI is a status, not the actual title. Your system will have a mixture of literal strings that ARE titles and URIs that say something about titles, both as objects of dc:title. The object of DC title needs to be the title. The title COULD be a URI if the URI represents the title (e.g. a uniform title in an authority file). Even if this turns out to be legal from an RDF point of view, it seems that this would complicate title displays because you'd have to treat these URIs differently from the usual title literals, which you could just grab and toss into a display. I'd probably leave title as the literal string, and create a new property for title status that takes its value from a controlled list. In fact, wouldn't we need something almost identical for anonymous works, to say that there really isn't an author. (Cataloging knowledge lapse: we quit using Anonymous as an author a while ago, right?) Given the open world assumption, we are going to need to make these kinds of negative statements. Also, remember that OWL does NOT constrain your data, it constrains only the inferences that you can make about your data. OWL operates at the ontology level, not the data level. (The OWL 2 documentation makes this more clear, in my reading of it. I agree that the example you cite sure looks like a constraint on the data... it's very confusing.) This book has no title: example:thisbook dc:title hasobject:false . I don't think the title itself can be hasobject:false. I think you need to have a property like: xx:hasATitle and this can be true or false. But I'm going to run this by the folks who developed dc in RDF and see what they say. [Did so, they concur = value of title must be a title, not information about title or status of title.] Note that dcterms title is defined specifically as having a literal value: Term Name: title URI:http://purl.org/dc/terms/title Label: Title Definition: A name given to the resource. Type of Term: Property http://www.w3.org/1999/02/22-rdf-syntax-ns#Property Refines:http://purl.org/dc/elements/1.1/title Version:http://dublincore.org/usage/terms/history/#titleT-002 Has Range: http://www.w3.org/2000/01/rdf-schema#Literal Whereas dc 1.1 (the old 15 element set) is more open: URI:http://purl.org/dc/elements/1.1/title Label: Title Definition: A name given to the resource. Type of Term: Property http://www.w3.org/1999/02/22-rdf-syntax-ns#Property Version:http://dublincore.org/usage/terms/history/#title-006 Note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document DCMI Metadata Terms (http://dublincore.org/documents/dcmi-terms/) for an explanation. I still think you are going outside of the definition of dc:title, which is The name of the resource. UNLESS you treat your no title as the actual name of the resource, like untitled as the title of a painting. But then we do have a serial with the actual title Title varies ... ;-) kc It is unknown if this book has a title (sounds undesirable but I can think of instances where it might be handy[2]): example:thisbook dc:title hasobject:unknown . This book has a title but it has not been specified: example:thisbook dc:title hasobject:true . In terms of cataloguing, the answer is perhaps to refer to the rules (which would normally mandate supplied titles in square brackets and so forth) rather than use RDF to express this kind of thing, although the rules differ depending on the part of description and, in the case of the kind of thing that prompted the question- the presence of clasps on rare books- there are no rules. I wonder if anyone has any more wisdom on this. Many thanks, Tom [1] Adapted from http://www.w3.org/2007/OWL/wiki/Primer#Object_Properties [2] No many tbh, but e.g. title in an unknown script or indecipherable hand. --- Thomas Meehan Head of Current Cataloguing Library Services University College London Gower Street London WC1E 6BT t.mee...@ucl.ac.uk -- Karen Coyle kco...@kcoyle.net http://kcoyle.net ph: 1-510-540-7596 m: 1-510-435-8234 skype: kcoylenet
[CODE4LIB] capturing only relevant CSS for a selection
Hi all, I'm looking for a tool that I hope exists, and that I hope someone here might be able to point me too. I want to select a portion of a web page (or of the html behind it), and be able to copy it ALONG WITH whatever CSS rules apply to that section of code. I don't want the whole 1000+ lines of css that pertain to the page, just the 5-10-100 rules that affect the styling of that section of the page. The situation: my library web page is, by university fiat, wrapped up in our university's overall web design (see: http://www6.wittenberg.edu/lib/ ). It's so complex that it's hard to extract portions of a page for reuse. I want to take the top part of the page and re-write it in a simplified (ie, not 1000s of lines on non-relevant CSS) so I can re-purpose the same look-and-feel at the top of our customizable external services (discovery layer, etc.) I could laboriously reconstruct it, but I'm hoping that something exists to help. The inspect element feature built into most browsers is a start. I'm hoping that some tool can leverage the same technology to look at all 50 divs at the same time and spit out a combined pile of CSS rules that will make it all look ok. Does such a tool exist? Thanks Ken
Re: [CODE4LIB] Access 2013 - room-mate
Hey, I'm staying there too! It looked like such a charming place. See you soon, Roy On Fri, Sep 13, 2013 at 4:31 AM, Joseph Montibello joseph.montibe...@dartmouth.edu wrote: Hi, This doesn't help Bobbi any, but along the same lines, I've got a room at a BB about ten minutes' walk from the Masonic Temple. Happy to have a male non-smoker share the room, if anyone's interested. (It's $99 a night, so half of that isn't too bad) the room: http://bit.ly/Access2013Room the place: http://bit.ly/therosesnl Take care, Joe Montibello, MLIS Library Systems Manager Dartmouth College Library 603.646.9394 joseph.montibe...@dartmouth.edu On 9/12/13 4:59 PM, Fox, Bobbi bobbi_...@harvard.edu wrote: If you're a woman going to Access 2013 (http://accessconference.ca/) the week after next, would you like to save money by sharing a room? I currently have something booked at the Extended Stay St Johns -- Downtown, but can cancel it if you have a better deal :-) Time's growing short, so please give a shout soon. Thanks, Bobbi
Re: [CODE4LIB] Expressing negatives and similar in RDF
The MARC21 Authority format does have some negative assertions. Field 675 asserts that a source contains no relevant information (vs. 670 which asserts the source and its relevant information). Field 673 asserts that a title is not related to the entity in the 1XX (vs. 672 which asserts that the two are related). These aren't yet mapped in any detail to RDF or to MADS, but finding a way to map them could be a practical approach the question of negative assertions. Stephen On Fri, Sep 13, 2013 at 9:12 AM, Karen Coyle li...@kcoyle.net wrote: On 9/13/13 5:51 AM, Esmé Cowles wrote: Thomas- This isn't something I've run across yet. But one thing you could do is create some URIs for different kinds of unknown/nonexistent titles: example:book1 dc:title example:unknownTitle example:book2 dc:title example:noTitle etc. I'm bothered by the semantics of this... but maybe I'm being too rigid. This states that the title is a URI, not a string, and that the URI is a status, not the actual title. Your system will have a mixture of literal strings that ARE titles and URIs that say something about titles, both as objects of dc:title. The object of DC title needs to be the title. The title COULD be a URI if the URI represents the title (e.g. a uniform title in an authority file). Even if this turns out to be legal from an RDF point of view, it seems that this would complicate title displays because you'd have to treat these URIs differently from the usual title literals, which you could just grab and toss into a display. I'd probably leave title as the literal string, and create a new property for title status that takes its value from a controlled list. In fact, wouldn't we need something almost identical for anonymous works, to say that there really isn't an author. (Cataloging knowledge lapse: we quit using Anonymous as an author a while ago, right?) Given the open world assumption, we are going to need to make these kinds of negative statements. Also, remember that OWL does NOT constrain your data, it constrains only the inferences that you can make about your data. OWL operates at the ontology level, not the data level. (The OWL 2 documentation makes this more clear, in my reading of it. I agree that the example you cite sure looks like a constraint on the data... it's very confusing.) This book has no title: example:thisbook dc:title hasobject:false . I don't think the title itself can be hasobject:false. I think you need to have a property like: xx:hasATitle and this can be true or false. But I'm going to run this by the folks who developed dc in RDF and see what they say. [Did so, they concur = value of title must be a title, not information about title or status of title.] Note that dcterms title is defined specifically as having a literal value: Term Name: title URI:http://purl.org/dc/terms/title Label: Title Definition: A name given to the resource. Type of Term: Property http://www.w3.org/1999/02/22-** rdf-syntax-ns#Propertyhttp://www.w3.org/1999/02/22-rdf-syntax-ns#Property Refines: http://purl.org/dc/elements/1.**1/titlehttp://purl.org/dc/elements/1.1/title Version: http://dublincore.org/usage/**terms/history/#titleT-002http://dublincore.org/usage/terms/history/#titleT-002 Has Range: http://www.w3.org/2000/01/rdf-**schema#Literalhttp://www.w3.org/2000/01/rdf-schema#Literal Whereas dc 1.1 (the old 15 element set) is more open: URI: http://purl.org/dc/elements/1.**1/titlehttp://purl.org/dc/elements/1.1/title Label: Title Definition: A name given to the resource. Type of Term: Property http://www.w3.org/1999/02/22-** rdf-syntax-ns#Propertyhttp://www.w3.org/1999/02/22-rdf-syntax-ns#Property Version: http://dublincore.org/usage/**terms/history/#title-006http://dublincore.org/usage/terms/history/#title-006 Note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document DCMI Metadata Terms (http://dublincore.org/ **documents/dcmi-terms/ http://dublincore.org/documents/dcmi-terms/) for an explanation. I still think you are going outside of the definition of dc:title, which is The name of the resource. UNLESS you treat your no title as the actual name of the resource, like untitled as the title of a painting. But then we do have a serial with the actual title Title varies ... ;-) kc It is unknown if this book has a title (sounds undesirable but I can think of instances where it might be handy[2]): example:thisbook dc:title hasobject:unknown . This book has a title but it has not been specified: example:thisbook dc:title hasobject:true . In terms of cataloguing, the answer is perhaps to refer to the rules (which would normally mandate supplied titles in square brackets and so forth) rather than use RDF to express this kind of thing, although the
Re: [CODE4LIB] PHP HTTP Client preference
Thanks everyone for your helpful feedback on the PHP HTTP Client library. I ended up choosing Guzzle and am in the process of incorporating and testing it. If you're interested in my rationale and when the OCLC WSKey (Web Service key) code library will be available, check out my post on the development effort on the Developer Network website - http://oc.lc/RyoUKC Karen On Tue, Sep 3, 2013 at 6:01 PM, Walker, David dwal...@calstate.edu wrote: We're also using Guzzle, and really like it. --Dave - David Walker Director, Systemwide Digital Library Services California State University 562-355-4845 -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Karen Coombs Sent: Tuesday, September 03, 2013 3:52 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] PHP HTTP Client preference Thanks so much for all the feedback guys. Keep it coming. I'll definitely check out Guzzle as an option. Karen On Tue, Sep 3, 2013 at 4:26 PM, Hagedon, Mike haged...@u.library.arizona.edu wrote: Guzzle++ -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Kevin S. Clarke Sent: Tuesday, September 03, 2013 8:37 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] PHP HTTP Client preference Another +1 for Guzzle Kevin On Tue, Sep 3, 2013 at 11:32 AM, Kevin Reiss reiss.ke...@yahoo.com wrote: I can second Guzzle. We have been using it for our our in-house PHP applications that require HTTP interactions for about six months and it has worked out very well. Guzzle has also been incorporated as the new default HTTP client in the next version of Drupal. From: Ross Singer rossfsin...@gmail.com To: CODE4LIB@LISTSERV.ND.EDU Sent: Tuesday, September 3, 2013 10:59 AM Subject: Re: [CODE4LIB] PHP HTTP Client preference Hey Karen, We use Guzzle: http://guzzlephp.org/ It's nice, seems to work well for our needs, is available in packagist, and is the HTTP client library in the official AWS SDK libraries (which was a big endorsement, in our view). We're still in the process of moving all of our clients over to it (we built a homegrown HTTP client on top of CURL first), but have been really impressed with it so far. -Ross. On Sep 3, 2013, at 10:49 AM, Coombs,Karen coom...@oclc.org wrote: One project I'm working on for OCLC right now is building a set of object-oriented client libraries in PHP that will assist developers with interacting with our web services. The first of these libraries we'd like to release provides classes for authentication and authorization to our web services. You can read more about Authentication/Authorization and our web services on the Developer Network sitehttp://oc.lc/devnet The purpose of this project is to make a simple and easy to use object oriented library that supports our various authentication methods. This library need to make HTTP requests and I've looked at a number of potential libraries and HTTP clients in PHP. Why am I not just considering using CURL natively? The standard CURL functions in PHP are not object-oriented. All of our code libraries (both our authentication/authorization library and future libraries for interacting with the REST services themselves) need to perform a robust set of HTTP interactions. Using the standard CURL functions would very likely increase the size of the code libraries and the potential for errors and inconsistencies within the code base because of how much we use HTTP. Given this, I believe there are three possible options and would like to get the community's feedback on which option you would prefer. Option 1. - Write my own HTTP Client on top of the standard PHP CURL implementation. This means people using the code library can only download it and now worry about any dependencies. However, that means adding extra code to our library which, although essential, isn't at the core of what we're trying to support. My fear is that my client will never be as good as an existing client. Option 2. - Use HTTPful code library (http://phphttpclient.com/). This is a well developed and supported code base which is designed specifically to support REST interactions. It is easy to install via Composer or Phar, or manually. It is slim and trim and only does the HTTP Client functions. It does create a dependency on an external (but small) library. Option 3. - Use the Zend 2 HTTPClient. This is a well developed and supported code base. The biggest downside is that Zend is a massive code library to require. A developer could choose to download only the specific set of classes that we are dependent on, but asking people to do this may prove confusing to some developers. I'd appreciate your feedback so we can provide the most useful set of libraries to the community. Karen Karen A.
Re: [CODE4LIB] Expressing negatives and similar in RDF
OWL contains some negative assertions, as Thomas noted. Nothing prevents anyone else from negating your negative, however, in that Open World. Assuming that we have provenance on statements, then you might be able to make sense of two conflicting bits of information. I've found two vocabularies that do a Boolean negation (Not, as well as And and Or): http://vocab.deri.ie/csp http://vocab.deri.ie/ppo# The CSP is used for car models, where there can be hundreds of options on a car (color, radio, #doors, gps, etc etc). However, looking at the diagram [1] I think it would take me great concentration to figure out what they are doing (not to mention their weird use of the term Fluent). I'm going to look for examples but am not sure how to do that - hunt and peck, I guess. kc [1] http://vocab.deri.ie/csp#Not On 9/13/13 6:46 AM, Donald Brower wrote: At a theoretical level, doesn't the Open World Assumption in RDF rule out outright negations? That is, someone else may know the title, and could assert it in a separate RDF document. RDF semantics seem to conflate unknown with nonexistent. Practically, Esme's approach seems better in these cases. -Don -- Donald Brower, Ph.D. Digital Library Infrastructure Lead Hesburgh Libraries, University of Notre Dame On 9/13/13 8:51 AM, Esmé Cowles escow...@ucsd.edu wrote: Thomas- This isn't something I've run across yet. But one thing you could do is create some URIs for different kinds of unknown/nonexistent titles: example:book1 dc:title example:unknownTitle example:book2 dc:title example:noTitle etc. You could then describe example:unknownTitle with a label or comment to fully describe the states you wanted to capture with the different categories. -Esme -- Esme Cowles escow...@ucsd.edu Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. -- William Pitt, 1783 On 09/13/2013, at 7:32 AM, Meehan, Thomas t.mee...@ucl.ac.uk wrote: Hello, I'm not sure how sensible a question this is (it's certainly theoretical), but it cropped up in relation to a rare books cataloguing discussion. Is there a standard or accepted way to express negatives in RDF? This is best explained by examples, expressed in mock-turtle: If I want to say this book has the title Cats in RDA I would do something like: example:thisbook dc:title Cats in RDA . Normally, if a predicate like dc:title is not relevant to example:thisbook I believe I am right in thinking that it would simply be missing, i.e. it is not part of a record where a set number of fields need to be filled in, so no need to even make the statement. However, there are occasions where a positively negative statement might be useful. I understand OWL has a way of managing the statement This book does not have the title Cats in RDA [1]: [] rdf:type owl:NegativePropertyAssertion ; owl:sourceIndividual example:thisbook ; owl:assertionProperty dc:title ; owl:targetIndividual Cats in RDA . However, it would be more useful, and quite common at least in a bibliographic context, to say This book does not have a title. Ideally (?!) there would be an ontology of concepts like none, unknown, or even something, but unspecified: This book has no title: example:thisbook dc:title hasobject:false . It is unknown if this book has a title (sounds undesirable but I can think of instances where it might be handy[2]): example:thisbook dc:title hasobject:unknown . This book has a title but it has not been specified: example:thisbook dc:title hasobject:true . In terms of cataloguing, the answer is perhaps to refer to the rules (which would normally mandate supplied titles in square brackets and so forth) rather than use RDF to express this kind of thing, although the rules differ depending on the part of description and, in the case of the kind of thing that prompted the question- the presence of clasps on rare books- there are no rules. I wonder if anyone has any more wisdom on this. Many thanks, Tom [1] Adapted from http://www.w3.org/2007/OWL/wiki/Primer#Object_Properties [2] No many tbh, but e.g. title in an unknown script or indecipherable hand. --- Thomas Meehan Head of Current Cataloguing Library Services University College London Gower Street London WC1E 6BT t.mee...@ucl.ac.uk -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: 1-510-435-8234 skype: kcoylenet
[CODE4LIB] Job: Performing Arts Cataloger/Metadata Librarian at University of California, Santa Barbara
The University of California, Santa Barbara, one of ten campuses of the University of California system, is seeking dynamic, flexible, and highly motivated candidates for the position of Performing Arts Cataloger/Metadata Librarian to provide leadership in creating, reviewing, editing metadata for Library-led digitization and data curation efforts in the area of performing arts collections. **RESPONSIBILITIES** Reporting to Head of Cataloging Metadata Services (CMS), the Performing Arts Cataloger/Metadata Librarian has responsibility for providing cataloging and metadata services for the Library's performing arts collections in all formats, including but not limited to video recordings, sound recordings, electronic resources, and born-digital contents. The incumbent is responsible for creating, reviewing, and editing metadata for performing arts collections, working with colleagues to support the discovery of and access to the Library's digital content through metadata creation, analysis, enrichment, and maintenance according to local and national cataloging and metadata standards. In addition, the incumbent is responsible for original cataloging and classification of music scores and sound recordings for the Music Library and Special Collections and training of the related individuals. Revises the work of the individuals responsible for the copy cataloging of scores and audiovisual materials for the Music Library and Special Collections as required. Actively participates in creating or modifying NACO authority records for personal and corporate names and series, and SACO authority records for music genres and mediums of performance as appropriate. The incumbent is responsible for creating, and reviewing metadata for Library-led digitization and data curation efforts in the area of performing arts collections. Participates in the development, evaluation, and implementation of metadata policies, standards, goals, procedures, and workflows in cooperation with necessary stakeholders. **QUALIFICATIONS** Required: ALA accredited MLS. Demonstrated knowledge and minimum two years professional-level experience in original cataloging of music/media resources (including scores and sound recordings) and special collection materials. Knowledge of AACR2, RDA, LCSH, LC Classification, DACS, music cataloging decisions and MARC 21. Familiarity with two or more non-MARC metadata standards and schemas, such as Dublin Core, EAD, VRACore, MODS, METS, TEI, and PBCore. Knowledge of trends in information access pertaining to libraries, and cataloging librarianship. Ability to work independently and collaboratively, prioritizing work to ensure that departmental and library goals are realized. Excellent organizational skills, proven problem solving ability, and flexibility. Demonstrated initiative in fostering new ideas and in implementing change. Excellent oral, written, and interpersonal communication skills. Preferred: Demonstrated interest in music and the performing arts. Knowledge of one or more European languages. Experience with Archivists' Toolkit and NACO, BIBCO or other PCC programs. **SALARY AND BENEFITS** Salary commensurate with experience and qualifications. Librarians at the University of California, Santa Barbara are professional academic appointees who accrue vacation at the rate of two days per month and sick leave at the rate of one day per month. The University has an excellent retirement system which is coordinated with Social Security. A selection of group health, dental, vision, and life insurance plans are offered by the University. **TO APPLY:** •Consideration of applications begins immediately and continues until the position is filled; applications received by Monday, October 21 will receive first consideration. •Applications will be accepted online through UC Recruit: https://recruit.ap.ucsb.edu/apply/JPF00221. oHelp for UC Recruit is available at https://recruit.ap.ucsb.edu/help/applicants. •For additional assistance, contact Ryan George with Library Human Resources at (805) 893-3841 or rgeo...@library.ucsb.edu. •Appointment and/or continued employment is contingent on successful completion of a background check. The Library is especially interested in candidates who can contribute to the diversity and excellence of the academic community through research, teaching and service. The University of California is an Equal Opportunity Affirmative Action Employer. Brought to you by code4lib jobs: http://jobs.code4lib.org/job/10012/
Re: [CODE4LIB] capturing only relevant CSS for a selection
I can't speak for the other browsers, but at least in Chrome, it's pretty easy to determine which rules are applied and which are overriden for whatever reason On Sep 13, 2013 8:36 AM, Ken Irwin kir...@wittenberg.edu wrote: Hi all, I'm looking for a tool that I hope exists, and that I hope someone here might be able to point me too. I want to select a portion of a web page (or of the html behind it), and be able to copy it ALONG WITH whatever CSS rules apply to that section of code. I don't want the whole 1000+ lines of css that pertain to the page, just the 5-10-100 rules that affect the styling of that section of the page. The situation: my library web page is, by university fiat, wrapped up in our university's overall web design (see: http://www6.wittenberg.edu/lib/). It's so complex that it's hard to extract portions of a page for reuse. I want to take the top part of the page and re-write it in a simplified (ie, not 1000s of lines on non-relevant CSS) so I can re-purpose the same look-and-feel at the top of our customizable external services (discovery layer, etc.) I could laboriously reconstruct it, but I'm hoping that something exists to help. The inspect element feature built into most browsers is a start. I'm hoping that some tool can leverage the same technology to look at all 50 divs at the same time and spit out a combined pile of CSS rules that will make it all look ok. Does such a tool exist? Thanks Ken
