XCRI Forum: Recent Posts

XCRI Forum: Recent Posts http://www.xcri.org/forum/ XCRI Forum: Recent Posts en Sun, 05 Feb 2012 01:43:10 +0000 Alan Paull on "Error in XCRI-CAP 1.2 Terms?" http://www.xcri.org/forum/topic.php?id=180#post-706 Tue, 24 Jan 2012 11:39:24 +0000 Alan Paull 706@http://www.xcri.org/forum/ Change committed to Google Code. Scott Wilson on "Error in XCRI-CAP 1.2 Terms?" http://www.xcri.org/forum/topic.php?id=180#post-705 Tue, 24 Jan 2012 11:29:17 +0000 Scott Wilson 705@http://www.xcri.org/forum/ They certainly should be the same Alan Paull on "Error in XCRI-CAP 1.2 Terms?" http://www.xcri.org/forum/topic.php?id=180#post-704 Tue, 24 Jan 2012 11:15:01 +0000 Alan Paull 704@http://www.xcri.org/forum/ Just noticed also in XCRI-CAP 1.2 terms: xmlns="http://xcri.org/profiles/catalog/terms" targetNamespace="http://xcri.org/profiles/1.2/catalog/terms" I presume the first one should be the same namespace as the second one? If so, I'll do a correction. Alan Alan Paull on "Error in XCRI-CAP 1.2 Terms?" http://www.xcri.org/forum/topic.php?id=180#post-703 Wed, 18 Jan 2012 16:27:28 +0000 Alan Paull 703@http://www.xcri.org/forum/ OK, I'll do that. Alan https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA on "Error in XCRI-CAP 1.2 Terms?" http://www.xcri.org/forum/topic.php?id=180#post-702 Mon, 16 Jan 2012 08:00:26 +0000 https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA 702@http://www.xcri.org/forum/ I can't take the credit - I just ran a couple of tests to confirm what Alan found. I'll let Alan commit the changes to the schemas repository (unless he wants me to). Craig. Scott Wilson on "Error in XCRI-CAP 1.2 Terms?" http://www.xcri.org/forum/topic.php?id=180#post-701 Sun, 15 Jan 2012 17:47:33 +0000 Scott Wilson 701@http://www.xcri.org/forum/ Good catch Craig - feel free to commit it https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA on "Error in XCRI-CAP 1.2 Terms?" http://www.xcri.org/forum/topic.php?id=180#post-700 Sun, 15 Jan 2012 16:14:20 +0000 https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA 700@http://www.xcri.org/forum/ I can confirm that when I attempt to validate an element using the following XML, I receive an error: <code><dc:description xsi:type="xcriTerms:careerOutcome">hello world</dc:description></code> Error details: <code>The xsi:type attribute value 'http://xcri.org/profiles/1.2/catalog/terms:careerOutcome' is not valid for the element 'http://purl.org/dc/elements/1.1/:description', either because it is not a type validly derived from the type in the schema, or because it has xsi:type derivation blocked. (1 failed instance)</code> I can confirm that altering line 28 on xcri_cap_terms_1_2.xsd from <code>base="xcri:descriptionDType"</code> to <code>base="dc:descriptionDType"</code> resolves the problem. Craig. Alan Paull on "Error in XCRI-CAP 1.2 Terms?" http://www.xcri.org/forum/topic.php?id=180#post-699 Fri, 13 Jan 2012 18:39:50 +0000 Alan Paull 699@http://www.xcri.org/forum/ The XCRI-CAP 1.2 Terms schema contains a range of complexType definitions that restrict descriptionDType. They allow use of xsi:type for naming description elements, for example 'xsi:type="careerOutcome"'. However, it looks like the definitions are incorrect. descriptionDType is defined in the types.xsd schema, which picks up namespaces from where the type is used. In our current set of schemas, descriptionDType is used in a slightly altered dc schema*, so descriptionDType picks up the dc namespace. The upshot is that descriptionDType in the current version of xcri_cap_terms_1_2.xsd points to the xcri namespace ('base="xcri:descriptionDType"'), when it should point to dc ('base="dc:descriptionDType"'). Can anyone technical verify this please? Alan Paull <a href="mailto:alan@alanpaull.co.uk">alan@alanpaull.co.uk</a> * A different issue. Scott Wilson on "Adding VAT element under Presentation" http://www.xcri.org/forum/topic.php?id=179#post-698 Thu, 12 Jan 2012 17:36:30 +0000 Scott Wilson 698@http://www.xcri.org/forum/ Hi Tahir, The reason that the <cost> element seems underspecified is that EU-wide there are going to be quite a few different cost structures, and so the content of the element is just text. However, there are definitely some benefits to using a more structured cost value. This could be done by adding sub-elements, e.g. <cost> <excludingVat>£200.00</excludingVat> <Vat>£35.00<Vat> <includingVat>£235.00<includingVat> </cost> ... though thats a bit verbose. Alternatively, the information could be extracted using text patterns in the Cost text itself e.g. <cost>£235.00 (£35.00 VAT)</cost> ... though that isn't very reliable. Finally, the values can be expressed in attributes: <cost vat="35" net="200" gross="235">The cost of this course is £235, payable by cheque or direct debit</cost> In general I think we've been favouring the last approach where: - the content of the element is text that should be displayed directly to the user, but may not necessarily be machine-readable. - the attributes of the element are machine-readable, and would not normally be displayed directly to the user So providers would be free to include any general information about costs and payment methods in the <cost> element text (including marketing blurb such as "cheapest in the northwest!"), but the attributes would be specified as particular types (e.g. decimal) for machine parsing. I imagine there are other providers out there with similar requirements? S http://tapasha2.myopenid.com/ on "Adding VAT element under Presentation" http://www.xcri.org/forum/topic.php?id=179#post-697 Thu, 12 Jan 2012 17:01:59 +0000 http://tapasha2.myopenid.com/ 697@http://www.xcri.org/forum/ We have a requirement, we need VAT of cost because some learning providers charge VAT and some don't. It will help us in processing the cost when XCRI compliant data is uploaded in our database. Organisation: Skills Development Scotland https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA on "Postal addresses" http://www.xcri.org/forum/topic.php?id=170#post-696 Thu, 05 Jan 2012 20:44:59 +0000 https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA 696@http://www.xcri.org/forum/ It's validate-able, certainly, and flexible. Did you want to differentiate between <location> elements that resolve to physical locations and <location> elements that resolve to non-physical (e.g. PO Box) addresses? That's the only bit I can recall off the top of my head which has come up recently that this doesn't (directly) address. Or did you not want to try and deal with that question within this context? Craig. Alan Paull on "Postal addresses" http://www.xcri.org/forum/topic.php?id=170#post-695 Wed, 04 Jan 2012 20:52:28 +0000 Alan Paull 695@http://www.xcri.org/forum/ Retaining almost all the current restrictions of XCRI-CAP 1.2, and not wishing to redefine the address element, and not desiring to construct a complex solution, recognising the following requirements specified earlier: * Automatic identification of any full official UK postal address elements supplied in XCRI-CAP format * Input and output of any full official UK postal address with no loss of data * Separate identification and storage of Postcode * Input and output of up to 6 address lines, in addition to postcode and house number while also recognising that we will not meet the following requirement specified earlier: * Input and output of house number + Postcode for Postal Address look-up I propose the following solution to the postal address problem. If a postal address is required, then one set of address elements MUST consist of lines of the official postal address, so that these elements can be combined with the postcode to form the full postal address. Each postal address line must be contained in its own address element with an xsi:type attribute: xsi:type=”addressLine”. The addressLine typed elements must be ordered so that the sequence in the document will generate successive postal address lines. Blank addressLine typed elements MUST NOT be included. Examples: <mlo:address xsi:type="addressLine">The Open University</mlo:address> <mlo:address xsi:type="addressLine">PO Box 197</mlo:address> <mlo:address xsi:type="addressLine"> Milton Keynes</mlo:address> <mlo:postcode>MK7 6BJ</mlo:postcode> <mlo:address xsi:type="addressLine">Information Services</mlo:address> <mlo:address xsi:type="addressLine">Room B159</mlo:address> <mlo:address xsi:type="addressLine">University of Nottingham</mlo:address> <mlo:address xsi:type="addressLine">Kings Meadow Campus</mlo:address> <mlo:address xsi:type="addressLine">Nottingham</mlo:address> <mlo:postcode>NG7 2NR</mlo:postcode> Views? Alan Paull <a href="mailto:alan@alanpaull.co.uk">alan@alanpaull.co.uk</a> Alan Paull on "XCRI 1.2 Errata" http://www.xcri.org/forum/topic.php?id=176#post-694 Wed, 21 Dec 2011 09:37:46 +0000 Alan Paull 694@http://www.xcri.org/forum/ Inheritable Elements Example: Two presentation end tags are missing their '/'. https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA on "XCRI 1.2 Errata" http://www.xcri.org/forum/topic.php?id=176#post-693 Tue, 13 Dec 2011 16:30:52 +0000 https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA 693@http://www.xcri.org/forum/ Scott, I just made a change to the "FIXME" wiki page to add in things that I'm sure will come up whilst I'm documenting bits for the validation. The first I've added in there: <a href="http://www.xcri.org/wiki/index.php/XCRI_CAP_1.2_FIXME" rel="nofollow">http://www.xcri.org/wiki/index.php/XCRI_CAP_1.2_FIXME</a> Would you rather I revert the change and document them here instead? Craig. https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA on ""Official" XCRI-CAP 1.2 Schema locations" http://www.xcri.org/forum/topic.php?id=178#post-692 Mon, 12 Dec 2011 14:15:03 +0000 https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA 692@http://www.xcri.org/forum/ Hi both, That sounds good. I'm only using the trunk at the moment as that is where the most recent files are (I expected to be making a number of changes myself so expect change). As and when everyone's happy with the 1.2 release if we can tag the release then I can easily swap the XSD that I'm using. Cheers. Craig. Alan Paull on ""Official" XCRI-CAP 1.2 Schema locations" http://www.xcri.org/forum/topic.php?id=178#post-691 Mon, 12 Dec 2011 09:24:21 +0000 Alan Paull 691@http://www.xcri.org/forum/ That's fine. Thanks, Scott. Alan Scott Wilson on ""Official" XCRI-CAP 1.2 Schema locations" http://www.xcri.org/forum/topic.php?id=178#post-690 Sun, 11 Dec 2011 10:37:10 +0000 Scott Wilson 690@http://www.xcri.org/forum/ SVN is also designed to keep stable versions, so we can tag a release version once we're happy with "1.2 Final" and use that location rather than the trunk, which is where we can try out improvements without worrying about breaking implementations.. Alan Paull on ""Official" XCRI-CAP 1.2 Schema locations" http://www.xcri.org/forum/topic.php?id=178#post-689 Sun, 11 Dec 2011 10:10:48 +0000 Alan Paull 689@http://www.xcri.org/forum/ My understanding after discussion with Rob Englebright is that we will have an 'official' location at least for usage by the Course Data programme projects for the reasons you've stated, Craig. There's no 'official' location at the moment, because we don't have an official body in charge of the XSD files. Although using the version in SVN *should* be OK, I'm wary myself of using a location that's designed to enable modification. For example, how many people are aware that I've modified the files since they were lodged there? [Just for reassurance, my mods were to enable the files to be used successfully for validation.] For that reason I've put all the current working schemas in <a href="http://www.xcri.co.uk/bindings/." rel="nofollow">http://www.xcri.co.uk/bindings/.</a> So you should be able to reference, for example, <a href="http://www.xcri.co.uk/bindings/xcri_cap_1_2.xsd" rel="nofollow">http://www.xcri.co.uk/bindings/xcri_cap_1_2.xsd</a> from there. These files will not be changed by me without consultation, notification and versioning (so a new one might be xcri_cap_1_2_1.xsd). Unfortunately this has no official stamp - technically speaking I'm acting on behalf of JISC, so theoretically Rob could ask me to do something different! However, that's the line I'm taking for now. Alan https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA on ""Official" XCRI-CAP 1.2 Schema locations" http://www.xcri.org/forum/topic.php?id=178#post-688 Thu, 08 Dec 2011 12:54:21 +0000 https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA 688@http://www.xcri.org/forum/ I know that the XSDs aren't official in the same way as the spec(s) are, but they are a useful resource that (attempt to?) define the specification in a computer-readable and computer-validate-able format. And for that purpose they work well. Obviously they're not the be-all and end-all of validation (as the XSD files can only specify so much) but they're a good first step. My concern with encouraging local versions is that if issues are found with the schemas and any modifications made, we end up with a large number of potentially-subtly-different schemas everywhere. Is it important? Perhaps not. From a validation perspective I'm happy to reference the repository files but just wanted to make sure that there wasn't some other guidance that I was not aware of. However, just as XSD files are hosted in official places for standards such as XHTML itself (and indeed are/were for XCRI-CAP 1.1), it would make some sense for there to be a recognised "official" location. From a validation perspective it also means that some caching can be implemented to improve performance. As an example, validating against XCRI-CAP 1.1 became slow primarily because of the performance of serving/downloading the XML XSD every time; once I added caching of the file performance became immensely faster (literally 0.8s vs 39s - just re-ran my tests!). Just a thought. Craig. Scott Wilson on ""Official" XCRI-CAP 1.2 Schema locations" http://www.xcri.org/forum/topic.php?id=178#post-687 Thu, 08 Dec 2011 10:39:26 +0000 Scott Wilson 687@http://www.xcri.org/forum/ The XSDs aren't "official" in the same way that the spec itself is (or at least, the BSI version is) so its up to us where we want to host XSDs, and whether we want to have different flavours or versions of them. Personally I think using local versions, or referring to the version in SVN seems safer than relying on another website to have them. https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA on ""Official" XCRI-CAP 1.2 Schema locations" http://www.xcri.org/forum/topic.php?id=178#post-686 Thu, 08 Dec 2011 09:37:55 +0000 https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA 686@http://www.xcri.org/forum/ Hi all, I just wanted to confirm: what's the plan regarding referencing the official XCRI-CAP 1.2 schemas? Within the wiki (http://www.xcri.org/wiki/index.php/XCRI_CAP_1.2#XML_Schema) we point to the Google Code repository and to a downloadable ZIP. I assume that the downloadable zip is for development but is the plan to reference the XSD files within the Google Code repository directly? That's what I'm doing at the moment with a number of tests (e.g. <code>xsi:schemaLocation="http://xcri.org/profiles/1.2/catalog <a href="http://xcri-schemas.googlecode.com/svn/trunk/xsd/xcri_cap_1_2.xsd"" rel="nofollow">http://xcri-schemas.googlecode.com/svn/trunk/xsd/xcri_cap_1_2.xsd"</a></code>) but I assume this isn't the plan long-term. I have at the back of my mind that the schemas were reference-able through xcri.co.uk at one point but I can't find where. Are they still there and the wiki just needs to be updated? Regards, Craig. Scott Wilson on "Original XCRI" http://www.xcri.org/forum/topic.php?id=177#post-685 Fri, 25 Nov 2011 17:05:41 +0000 Scott Wilson 685@http://www.xcri.org/forum/ (Sorry, I think I misunderstood...) There is no current recommended "full XCRI". I think we would need a new version of the spec and documentation to be created involving suppliers interested interested in implementation. Scott Wilson on "Original XCRI" http://www.xcri.org/forum/topic.php?id=177#post-684 Fri, 25 Nov 2011 17:03:38 +0000 Scott Wilson 684@http://www.xcri.org/forum/ The actual spec is here: <a href="http://www.xcri.org/wiki/index.php/XCRI_CAP_1.2" rel="nofollow">http://www.xcri.org/wiki/index.php/XCRI_CAP_1.2</a> https://profiles.google.com/102921611215140342456 on "Original XCRI" http://www.xcri.org/forum/topic.php?id=177#post-683 Fri, 25 Nov 2011 16:27:37 +0000 https://profiles.google.com/102921611215140342456 683@http://www.xcri.org/forum/ Thank your for your reply. We are keen to ensure we are compliant with XCRI-CAP. But looking forward we also want to comply with the data that gets stored in the original XCRI. We are trying to understand the full scope of what data is captured in XCRI, but working from just the xsd without any supporting documentation is quite difficult. Is there any examples anywhere of an xml document based on the xsd xcri_r1.0.xsd? Scott Wilson on "Original XCRI" http://www.xcri.org/forum/topic.php?id=177#post-682 Fri, 25 Nov 2011 12:11:47 +0000 Scott Wilson 682@http://www.xcri.org/forum/ The immediate goal is to finish the transition of XCRI-CAP to a British Standard, so in that respect I'd say it is worth bothering with implementation, especially given the amount of effort being put into adoption at the moment across universities (about 90 projects). Beyond that, its up to us (and that includes YOU) to figure out what might happen beyond then. So revisiting the curriculum model work from the original XCRI could be something we work on, if people like yourself are willing to commit in some effort to developing it. https://profiles.google.com/102921611215140342456 on "Original XCRI" http://www.xcri.org/forum/topic.php?id=177#post-681 Fri, 25 Nov 2011 11:33:30 +0000 https://profiles.google.com/102921611215140342456 681@http://www.xcri.org/forum/ Is there any help or documents whatsoever for the original XCRI available at: <a href="http://www.xcri.co.uk/schemas/xcri_r1.0.xsd" rel="nofollow">http://www.xcri.co.uk/schemas/xcri_r1.0.xsd</a> Also is there any future for XCRI other than XCRI-CAP. I work for a software company developing products for universities and would like to know what the roadmap is for XCRI and is it worth bothering to make our software XCRI compliant. Scott Wilson on "XCRI 1.2 Errata" http://www.xcri.org/forum/topic.php?id=176#post-680 Fri, 25 Nov 2011 10:10:19 +0000 Scott Wilson 680@http://www.xcri.org/forum/ Title Guidelines: "Qualfiications: In the qualification element, Producers SHOULD use title for the name of the qualification, preferably as given by its Awarding Body." Spelling - should be "Qualifications". Scott Wilson on "XCRI 1.2 Errata" http://www.xcri.org/forum/topic.php?id=176#post-679 Fri, 25 Nov 2011 09:54:53 +0000 Scott Wilson 679@http://www.xcri.org/forum/ Identifier Guidelines: Third-party identifiers: Producers SHOULD use identifier with an encoding scheme to represent third-party identifiers; Producers shoud use dc:subject to represent third-party codes that refer to multiple objects (e.g. subject classification codes, provider type codes) "SHOULD" instead of "shoud" for the second sentence in the clause. https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA on "Building Java classes from XCRI-CAP 1.2 schema" http://www.xcri.org/forum/topic.php?id=175#post-678 Thu, 24 Nov 2011 20:49:53 +0000 https://www.google.com/accounts/o8/id?id=AItOawmrj2toFt3hnIVq7wT3FlxtfUlO5VK3GeA 678@http://www.xcri.org/forum/ Just as it's on-topic, I've noticed a number of peculiarities with the XSD files being served recently which was throwing the XCRI 1.1 validator off: <a href="http://www.xcri.org/forum/topic.php?id=171" rel="nofollow">http://www.xcri.org/forum/topic.php?id=171</a> In particular files which were served off the W3C site seemed to take forever to be downloaded and would often cause problems. In the end I downloaded the relevant XSD files and used these caches instead. This solution resolved my problem completely. I appreciate this issue may be different but it is strange to see that both you and I tracked the issue down to the XSD files being served from the W3C site. Craig. Scott Wilson on "XCRI 1.2 Errata" http://www.xcri.org/forum/topic.php?id=176#post-677 Thu, 24 Nov 2011 15:52:56 +0000 Scott Wilson 677@http://www.xcri.org/forum/ Use this topic to collect any errata for the spec. Presentation Guidelines: "Absence of Title: Where a presentation does not contain a title, but its containing course does, an Aggregator MAY use the image of the course when displaying the presentation." This should be "title", not "image". Note that this is an exception to the general "inheritance" rule, which does not apply to Title. Scott Wilson on "Building Java classes from XCRI-CAP 1.2 schema" http://www.xcri.org/forum/topic.php?id=175#post-676 Thu, 24 Nov 2011 14:16:43 +0000 Scott Wilson 676@http://www.xcri.org/forum/ I think I'm about 60% done now on creating XCRI Java classes - still got the Presentation stuff to finish, but its been pretty straightforward encoding most of the guidelines. Scott Wilson on "Building Java classes from XCRI-CAP 1.2 schema" http://www.xcri.org/forum/topic.php?id=175#post-675 Wed, 23 Nov 2011 09:19:35 +0000 Scott Wilson 675@http://www.xcri.org/forum/ I've kicked off a Java binding for XCRI 1.2 on Github so we can reduce duplication of effort: <a href="https://github.com/scottbw/Xcri4j" rel="nofollow">https://github.com/scottbw/Xcri4j</a> Scott Wilson on "Building Java classes from XCRI-CAP 1.2 schema" http://www.xcri.org/forum/topic.php?id=175#post-674 Tue, 22 Nov 2011 20:31:11 +0000 Scott Wilson 674@http://www.xcri.org/forum/ I'm not totally convinced using a schema-driven approach will always make sense. I have used XMLBeans with the XCRI schemas successfully in the past, however I'm not sure it gets you a lot further than using JDom and a few custom classes. In any case, the XCRI schema isn't all that difficult to model in Java classes with JDom, but is insanely difficult to express properly using XSD in a way that tooling across different development platforms can support. http://recidivist.myopenid.com/ on "Building Java classes from XCRI-CAP 1.2 schema" http://www.xcri.org/forum/topic.php?id=175#post-673 Mon, 21 Nov 2011 22:12:35 +0000 http://recidivist.myopenid.com/ 673@http://www.xcri.org/forum/ Hello I'm trying to build Java classes using XCRI-CAP 1.2 schema from the SVN repository at <a href="http://xcri-schemas.googlecode.com/svn/trunk." rel="nofollow">http://xcri-schemas.googlecode.com/svn/trunk.</a> I've tried both JAXB 2.0 and Castor to generate the classes but both fail to faithfull re-create the schema in classes. I'm using MyEclipse 9.1 Workbench and Java 1.5. MyEclipse plugin is JAXB Eclipse plugin <a href="http://sourceforge.net/projects/jaxb-builder/files/" rel="nofollow">http://sourceforge.net/projects/jaxb-builder/files/</a> Compiling against JAXB: Gennerating jaxb objects for C:\Documents and Settings\cs1ar\workspace\xcri\schema\dc.xsd Using XJC generator... parsing a schema... [ERROR] java.net.SocketException: Unexpected end of file from server line 33 of <a href="http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd" rel="nofollow">http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd</a> java.net.SocketException: Unexpected end of file from server at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:769) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:766) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:677) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:772) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at com.sun.xml.internal.xsom.parser.JAXPParser.parse(JAXPParser.java:86) at com.sun.tools.internal.xjc.ModelLoader$2.parse(ModelLoader.java:468) at com.sun.tools.internal.xjc.ModelLoader$XMLSchemaParser.parse(ModelLoader.java:251) at com.sun.xml.internal.xsom.impl.parser.NGCCRuntimeEx.parseEntity(NGCCRuntimeEx.java:326) at com.sun.xml.internal.xsom.impl.parser.NGCCRuntimeEx.importSchema(NGCCRuntimeEx.java:232) at com.sun.xml.internal.xsom.impl.parser.state.importDecl.action0(importDecl.java:69) at com.sun.xml.internal.xsom.impl.parser.state.importDecl.leaveElement(importDecl.java:180) at com.sun.xml.internal.xsom.impl.parser.state.NGCCRuntime.endElement(NGCCRuntime.java:299) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.tools.internal.xjc.util.SubtreeCutter.endElement(SubtreeCutter.java:97) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.tools.internal.xjc.reader.xmlschema.parser.CustomizationContextChecker.endElement(CustomizationContextChecker.java:183) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:180) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at com.sun.xml.internal.xsom.parser.JAXPParser.parse(JAXPParser.java:86) at com.sun.tools.internal.xjc.ModelLoader$2.parse(ModelLoader.java:468) at com.sun.tools.internal.xjc.ModelLoader$XMLSchemaParser.parse(ModelLoader.java:251) at com.sun.xml.internal.xsom.impl.parser.NGCCRuntimeEx.parseEntity(NGCCRuntimeEx.java:326) at com.sun.xml.internal.xsom.impl.parser.NGCCRuntimeEx.importSchema(NGCCRuntimeEx.java:232) at com.sun.xml.internal.xsom.impl.parser.state.importDecl.action0(importDecl.java:69) at com.sun.xml.internal.xsom.impl.parser.state.importDecl.leaveElement(importDecl.java:180) at com.sun.xml.internal.xsom.impl.parser.state.NGCCRuntime.endElement(NGCCRuntime.java:299) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.tools.internal.xjc.util.SubtreeCutter.endElement(SubtreeCutter.java:97) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.tools.internal.xjc.reader.xmlschema.parser.CustomizationContextChecker.endElement(CustomizationContextChecker.java:183) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:180) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at com.sun.xml.internal.xsom.parser.JAXPParser.parse(JAXPParser.java:86) at com.sun.tools.internal.xjc.ModelLoader$2.parse(ModelLoader.java:468) at com.sun.tools.internal.xjc.ModelLoader$XMLSchemaParser.parse(ModelLoader.java:251) at com.sun.xml.internal.xsom.impl.parser.NGCCRuntimeEx.parseEntity(NGCCRuntimeEx.java:326) at com.sun.xml.internal.xsom.impl.parser.NGCCRuntimeEx.includeSchema(NGCCRuntimeEx.java:223) at com.sun.xml.internal.xsom.impl.parser.state.includeDecl.action0(includeDecl.java:66) at com.sun.xml.internal.xsom.impl.parser.state.includeDecl.leaveElement(includeDecl.java:138) at com.sun.xml.internal.xsom.impl.parser.state.NGCCRuntime.endElement(NGCCRuntime.java:299) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.tools.internal.xjc.util.SubtreeCutter.endElement(SubtreeCutter.java:97) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.tools.internal.xjc.reader.xmlschema.parser.CustomizationContextChecker.endElement(CustomizationContextChecker.java:183) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1782) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2938) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at com.sun.xml.internal.xsom.parser.JAXPParser.parse(JAXPParser.java:86) at com.sun.tools.internal.xjc.ModelLoader$2.parse(ModelLoader.java:468) at com.sun.tools.internal.xjc.ModelLoader$XMLSchemaParser.parse(ModelLoader.java:251) at com.sun.xml.internal.xsom.impl.parser.NGCCRuntimeEx.parseEntity(NGCCRuntimeEx.java:326) at com.sun.xml.internal.xsom.impl.parser.ParserContext.parse(ParserContext.java:113) at com.sun.xml.internal.xsom.parser.XSOMParser.parse(XSOMParser.java:154) at com.sun.tools.internal.xjc.ModelLoader.createXSOMSpeculative(ModelLoader.java:485) at com.sun.tools.internal.xjc.ModelLoader.loadXMLSchema(ModelLoader.java:355) at com.sun.tools.internal.xjc.ModelLoader.load(ModelLoader.java:156) at com.sun.tools.internal.xjc.ModelLoader.load(ModelLoader.java:102) at com.sun.tools.internal.xjc.Driver.run(Driver.java:302) at com.sun.tools.internal.xjc.Driver.run(Driver.java:180) at com.sun.tools.internal.xjc.Driver._main(Driver.java:105) at com.sun.tools.internal.xjc.Driver.access$000(Driver.java:63) at com.sun.tools.internal.xjc.Driver$1.run(Driver.java:85) Failed to parse a schema. Gennerating jaxb objects for C:\Documents and Settings\cs1ar\workspace\xcri\schema\dc.xsd Completed! Compiling against Castor: The compiler appears to complete and the following classes are built: Any.java Credit.java Description.java DescriptionDType.java ElementContainer.java ElementsGroup.java ElementsGroupChoice.java ElementsGroupChoiceItem.java SimpleLiteral.java Subject.java SubjectDType.java TemporalDType.java VocabularyDType.java However, there are a number of problems reported such as: org.exolab.castor.xml.schema.SchemaException: Error reading import file 'http://www.w3.org/2001/xml.xsd': java.net.SocketException: Unexpected end of file from server. Can anyone suggest a reliable compiler or this approach overkill? Judging by the example xml from OU it may be simpler to use DOM to generate the xml. Andrew Scott Wilson on "Replacing XCRI URIs with PURLS" http://www.xcri.org/forum/topic.php?id=174#post-672 Thu, 17 Nov 2011 13:21:23 +0000 Scott Wilson 672@http://www.xcri.org/forum/ I've had a few comments lately about the XCRI namespace URIs in that they don't dereference to a URL. We can overcome this by using a PURL, and I've registered <a href="http://purl.org/xcri" rel="nofollow">http://purl.org/xcri</a> in case we want to take this route. The change would be that our URIs for XCRI elements would change from things like: <a href="http://xcri.org/profiles/catalog/1.2/catalog" rel="nofollow">http://xcri.org/profiles/catalog/1.2/catalog</a> To ones like: <a href="http://purl.org/xcri#catalog" rel="nofollow">http://purl.org/xcri#catalog</a> ... and the top level namespace would change to <a href="http://purl.org/xcri" rel="nofollow">http://purl.org/xcri</a> The rationale is that a PURL is a persistent registry id and can point to any page in future, not necessarily on the xcri.org or xcri.co.uk domains. The element URIs aren't critical for XML applications (the top level namespace is the only important one), but are important for other representations, e.g. using RDF.