XCRI Forum: Recent Topics

XCRI Forum: Recent Topics http://www.xcri.org/forum/ XCRI Forum: Recent Topics en Fri, 18 May 2012 04:02:16 +0000 https://profiles.google.com/matt.southall on "Data Definitions Example Problem?" http://www.xcri.org/forum/topic.php?id=197#post-817 Fri, 04 May 2012 12:57:39 +0000 https://profiles.google.com/matt.southall 817@http://www.xcri.org/forum/ Hi, Looking at the document: <a href="http://www.xcri.co.uk/KbLibrary/XCRI_CAP_Data_Definitions3.0.docx" rel="nofollow">www.xcri.co.uk/KbLibrary/XCRI_CAP_Data_Definitions3.0.docx</a> It shows that you can have a course identifier of the format: <dc:identifier xsi:type="http://www.ucas.ac.uk/:UCAScoursecode">V100</dc:identifier> Yet the validator at <a href="http://validator.xcri.co.uk/" rel="nofollow">http://validator.xcri.co.uk/</a> tells me that I cannot have a colon in the xsi:type there: "The attribute 'type' has an invalid value 'http://www.ucas.ac.uk/:UCAScoursecode' according to its schema type 'QName' - The ':' character, hexadecimal value 0x3A, cannot be included in a name. (1 failed instance)" Can anybody tell me which of these is correct? Or perhaps that I've misunderstood something here? Regards, Matt https://profiles.google.com/matt.southall on "OpenID Login Field Too Short" http://www.xcri.org/forum/topic.php?id=196#post-816 Fri, 04 May 2012 12:32:50 +0000 https://profiles.google.com/matt.southall 816@http://www.xcri.org/forum/ Hi, The OpenID login box up top on this forum is slightly too short to fit my OpenID URL: <a href="https://profiles.google.com/matt.southall" rel="nofollow">https://profiles.google.com/matt.southall</a> Luckily, it was exactly 1 character too short, and I managed to fudge it by using http instead of https - not ideal. Suggest raising the limit to something more like 255 characters. Regards, Matt Alan Paull on "Data Definitions and Vocabulary Framework documents" http://www.xcri.org/forum/topic.php?id=195#post-810 Thu, 05 Apr 2012 14:28:47 +0000 Alan Paull 810@http://www.xcri.org/forum/ Dear Colleagues Data Definitions and Vocabularies --------------------------------- The first version controlled release of the Data Definitions document (v3.0) and the Vocabulary Framework document (also v3.0) for the JISC-funded Course Data Programme are now available from the XCRI Knowledge Base at: <a href="http://www.xcri.co.uk/data-definitions-and-vocabulary-framework.html." rel="nofollow">http://www.xcri.co.uk/data-definitions-and-vocabulary-framework.html.</a> The link is a page of the Knowledge Base that explains the purpose of the two documents and provides links for downloading them. Both documents have been provided as Word files (.docx); there are hyperlinks in the document for internal navigation and to external resources. A simplified spreadsheet version of the Data Definitions document is currently in preparation and will be available next week. If you would prefer a different format, please contact me; it's likely that we will be able to accommodate other formats relatively easily and quickly. To give feedback on either of these documents please contact Alan Paull, <a href="mailto:alan@alanpaull.co.uk.">alan@alanpaull.co.uk.</a> Best wishes, and have a good holiday. Alan Paull <a href="mailto:alan@alanpaull.co.uk">alan@alanpaull.co.uk</a> https://profiles.google.com/106151444538427901807/about?hl=en on "StudyMode - sandwich?" http://www.xcri.org/forum/topic.php?id=194#post-808 Tue, 03 Apr 2012 09:04:35 +0000 https://profiles.google.com/106151444538427901807/about?hl=en 808@http://www.xcri.org/forum/ Hi all As described in v.2 of the Data Definitions document, the studyMode element does not mention courses taught on a Sandwich Mode. At the University of Greenwich this is a possible offering. Therefore it will have a separate presentation with the studyMode as: <studyMode identifier="SW">Sandwich</studyMode> I assume this is okay? but are we the only ones doing this? and i will interested to know how other institutions offering a SW mode are handling this. Tavis on "Widgets for small-scale course information syndication" http://www.xcri.org/forum/topic.php?id=82#post-268 Mon, 15 Feb 2010 11:40:59 +0000 Tavis 268@http://www.xcri.org/forum/ Widgets were mentioned in the <a href="http://www.xcri.org/wiki/index.php/XCRI_1.2_Requirements">XCRI-CAP 1.2 Requirements</a>. I suppose organizations might like to publish lightweight widgets (with comprehensive course filtering options) for sites who wanted to publish just a small selection of their courses. One example would be <a href="http://www.fifegingerbread.org.uk/component/content/article/2-news/39-adam-smith-college-new-courses">Fife Gingerbread's page: Adam Smith College New Courses</a>. Of course, you would have to supply something like a user-understandable <code>dc:subject</code> which could be filtered on. https://profiles.google.com/106151444538427901807/about?hl=en on "Designing an 'XCRI' Data Model" http://www.xcri.org/forum/topic.php?id=191#post-777 Thu, 22 Mar 2012 10:40:01 +0000 https://profiles.google.com/106151444538427901807/about?hl=en 777@http://www.xcri.org/forum/ Hi all After a productive seminar with Alan Paull yesterday, I was advised that this forum could be a good place to seek some information. At the University of Greenwich we are in the process of designing a data model within our Student Record System (Banner/ ORACLE) to store Programme level information. The XCRI project has certainly been the catalyst needed to address our issue of disparate programme information and a more centralised approach would make life a lot easier for XCRI :) Alan Paull mentioned that some institutions have taken a similar approach to us and have created a new “XCRI” data model which complements the XCRI-CAP requirements. The question I posed to Alan Paull yesterday was if any institutions on this forum are willing to share their data model, ideas, problems e.t.c that where faced when designing their data structure to the Forum. Any information and ideas would be greatly appreciated whilst we are in our design phase, it’s a given that everyone’s models will vary but I'm sure the common entities will be similar. In regards to the data model, I am also interested in finding out at what granularity these 7 ‘common descriptive elements’ can be stored at and how you have dealt with temporarily. We are always willing to return the favor, and input where we can. We are a BANNER university, currently on Oracle 11g. Mehmet Batmaz <a href="mailto:m.batmaz@gre.ac.uk">m.batmaz@gre.ac.uk</a> http://uclan-dev.myopenid.com/ on "Guidance sought on data mapping" http://www.xcri.org/forum/topic.php?id=188#post-754 Fri, 02 Mar 2012 20:19:03 +0000 http://uclan-dev.myopenid.com/ 754@http://www.xcri.org/forum/ Two course data items that we would generaly include in any marketing info are: ‘School of Study’ : An orgaizational division responsible for the administration of courses and students for a range of related subjets. ‘Professional Body Accreditation’ : Official endorcment of a course from one or more profesional bodies leading to automatic eligability to entry level membership for graduates. I cannot seem to find a ‘natural’ home for these items in the 1.2 data definition. All advise welcome. Clive. http://uclan-dev.myopenid.com/ on "Using the 1.2 validator" http://www.xcri.org/forum/topic.php?id=184#post-731 Sat, 25 Feb 2012 22:05:08 +0000 http://uclan-dev.myopenid.com/ 731@http://www.xcri.org/forum/ Hi my name is Clive, I am a developer at the University of Central Lancashire tasked with developing an XCRI feed for our institution. I am hoping this is the correct forum in which to to raise this type of issue. I have an issue trying to validate a sample file using the 1.2 validator (http://xcricapvalidator.apphb.com/). If I use the "http://purl.org/net/mlo" namespace for the child elements of providor.location then the validator insists they should be in the "http://xcri.org/profiles/1.2/catalog/terms" namespace. ... <mlo:location> <mlo:postcode>PR1 2HE</mlo:postcode> <mlo:address>University of Central Lancashire</mlo:address> <mlo:phone>0172 201201</mlo:phone> </mlo:location> ... XML STRUCTURE EXCEPTION: The element 'location' in namespace 'http://purl.org/net/mlo' has invalid child element 'postcode' in namespace 'http://purl.org/net/mlo'. List of possible elements expected: 'street, town, postcode, address, phone, fax, email, url' in namespace 'http://xcri.org/profiles/1.2/catalog/terms'. (1 failed instance) If I use the "http://xcri.org/profiles/1.2/catalog/terms" namespace the validator reports no XML errors but missing XCRI elements. ... <mlo:location> <xcri12terms:postcode>PR1 2HE</xcri12terms:postcode> <xcri12terms:address>University of Central Lancashire</xcri12terms:address> <xcri12terms:phone>0172 201201</xcri12terms:phone> </mlo:location> ... XCRI STRUCTURE EXCEPTION: An XCRI provider's location must contain one postcode element. (1 failed instance) An XCRI provider's location must contain at least one address element. (1 failed instance) An XCRI provider's location must contain one phone element. (1 failed instance) Also, any attempt to use a venue element in a presentation causes the validator to crash. It would be be really helpful if someone could provide a sample file that includes all the main elements and passes all the 1.2 validator checks. http://qamar-xaman.myopenid.com/ on "Related Courses" http://www.xcri.org/forum/topic.php?id=193#post-785 Tue, 27 Mar 2012 12:11:29 +0000 http://qamar-xaman.myopenid.com/ 785@http://www.xcri.org/forum/ We sort of talked about this ona previous webinar (14 March). Essentially I wanted the ability to link cources to other courses - and there could be a host of reasons why. There were other people interested in this as well. Websites that will aggregate courses will also find it useful. Here are some thoughts on how that and other types of links may be implemented. I think we need something like the following 'relatedElements' complex element that can be added to any of the main types; <relatedElements relatedTo="Course|Provider|Presentation" type="isPartOf|location|prerequisite|"> <ResourceIdentifier>http://...</ResourceIdentifier> <ResourceIdentifier></ResourceIdentifier> <ResourceIdentifier></ResourceIdentifier> </relatedElement> Specific examples... - The following example shows a list of venues where a course is available - note that presentation have a venue element that can link back to a provider, but this is restricted to only the current location of that course offering (not all possible locations). However, here I want to highlight all locations where that course is being taught (or has been or will be taught at some point). This is a contrived example as there are alternative (correct) ways to map this relation - the most common way is through multiple presentations. But I can still see a need for it. <relatedElements relatedTo="Provider" type="location"> <ResourceIdentifier>http://harper-adams/alternative/campus/234567</ResourceIdentifier> </relatedElement> - Course Pre-requisite cources <relatedElements relatedTo="course" type="requirement"> <ResourceIdentifier>http://harper-adams/courses/level1/PHY01</ResourceIdentifier> <ResourceIdentifier>http://harper-adams/courses/level1/BIO01</ResourceIdentifier> <ResourceIdentifier>http://harper-adams/courses/level1/CHE01</ResourceIdentifier> </relatedElement> Does anyone else have any need for any of 'relation' building within Xcri format? Qamar Xaman Harper Adams University College https://www.google.com/accounts/o8/id?id=AItOawmcxfq9NUT2pS0gqg9hO4Fy2yZrLuv9vRY on "Qualifications and Credit Framework (common vocabulary)" http://www.xcri.org/forum/topic.php?id=192#post-781 Mon, 26 Mar 2012 20:50:00 +0000 https://www.google.com/accounts/o8/id?id=AItOawmcxfq9NUT2pS0gqg9hO4Fy2yZrLuv9vRY 781@http://www.xcri.org/forum/ Is anyone planning on categorising qualifications using something based on the QCF? I've started turning a few controlled vocabularies into RDF (including the Researcher Development Framework) at <a href="https://github.com/oucs/xcri-rdf" rel="nofollow">https://github.com/oucs/xcri-rdf</a> , so this shouldn't be too much additional bother. Tavis on "Wiki anti-spam measures" http://www.xcri.org/forum/topic.php?id=190#post-773 Sun, 18 Mar 2012 20:57:02 +0000 Tavis 773@http://www.xcri.org/forum/ Has anyone any ideas about preventing useful pages on the wiki being overwritten by spam machines? The problem seems to be increasing lately (and making it harder to find genuine updates in the feeds). Or will the wiki be moving anyway? Craig Hawker on "Location elements (validation and XSD files)" http://www.xcri.org/forum/topic.php?id=189#post-755 Sun, 04 Mar 2012 11:09:41 +0000 Craig Hawker 755@http://www.xcri.org/forum/ It appears that the current XSD files are causing a problem for some XML tools which are mis-reporting the namespace for the child elements declared within <a href="http://code.google.com/p/xcri-schemas/source/browse/trunk/xsd/mlo_xcri_profile.xsd">mlo_xcri_profile.xsd</a>. The issue seems to be primarily reported by .NET-based XML tools, although there may be others. As confirmed by Alan, <a href="http://www.xcri.org/forum/topic.php?id=176">the child elements should also be within the MLO namespace</a>. This has been highlighted a few times, <a href="http://www.xcri.org/forum/topic.php?id=145">once by me about 11 months ago</a>, <a href="http://www.xcri.org/forum/topic.php?id=184">also by some institutions that are starting to use the validator</a>, as well as by some members of the Course Data Programme using other tools. These tools report the child elements as being within the XCRI-CAP 1.2 Tools namespace, typically, although this seems to change based upon which namespaces are loaded and possibly their order. The issue seems to be caused by the fact that the elements are declared within the extension of <code>locationDType</code>. I propose a small modification to the XSD file whereby the elements are instead declared within the <xs:schema> element and ref-ed within the <code>locationDType</code> extension. I have tested this with the validator code and this seems to resolve the issue for .NET. I have included the full replacement for the file below. Please can the community comment upon these changes before I request that the XSD files are changed within the Google Code repository? I would ask that any issues are raised as quickly as possible as this is a blocking issue for the validator. Craig. <blockquote><?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns="http://purl.org/net/mlo" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:credit="http://purl.org/net/cm" xmlns:xcri="http://xcri.org/profiles/1.2/catalog" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:xhtml="http://www.w3.org/1999/xhtml" targetNamespace="http://purl.org/net/mlo" elementFormDefault="qualified"> <xs:annotation> <xs:documentation> This is the profile of MLO used in XCRI; this schema redefines some of the base types in MLO adding additional attributes and/or specifying child elements defined by other schemas Revised by Alan Paull, 30 October 2011 </xs:documentation> </xs:annotation> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:import namespace="http://purl.org/dc/terms/" schemaLocation="dcterms.xsd"/> <xs:import namespace="http://purl.org/dc/elements/1.1/" schemaLocation="dc.xsd"/> <xs:import namespace="http://purl.org/net/cm" schemaLocation="educationalcredit.xsd" /> <xs:import namespace="http://xcri.org/profiles/1.2/catalog" schemaLocation="xcri_cap_1_2.xsd"/> <xs:import namespace="http://www.w3.org/1999/xhtml" schemaLocation="http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd" /> <xs:include schemaLocation="types.xsd"></xs:include> <xs:redefine schemaLocation="mlo-strict.xsd"> <xs:complexType name="qualificationDType"> <xs:complexContent> <xs:extension base="qualificationDType"> <xs:sequence> <xs:element ref="dc:identifier" minOccurs="0" maxOccurs="unbounded" /> <xs:element ref="dc:title" minOccurs="1" maxOccurs="unbounded" /> <xs:element ref="xcri:abbr" minOccurs="0" maxOccurs="1" /> <xs:element ref="dc:description" minOccurs="0" maxOccurs="unbounded" /> <xs:element ref="dcterms:educationLevel" minOccurs="0" /> <xs:element ref="dc:type" minOccurs="0" maxOccurs="1" /> <xs:element ref="url" minOccurs="0" maxOccurs="1" /> <xs:element ref="xcri:awardedBy" minOccurs="0" maxOccurs="1" /> <xs:element ref="xcri:accreditedBy" minOccurs="0" maxOccurs="1" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="creditDType"> <xs:complexContent> <xs:extension base="creditDType"> <xs:sequence> <xs:element ref="credit:scheme" maxOccurs="unbounded" minOccurs="0" /> <xs:element ref="credit:level" maxOccurs="unbounded" minOccurs="0" /> <xs:element ref="credit:value" maxOccurs="unbounded" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="locationDType"> <xs:complexContent> <xs:extension base="locationDType"> <xs:sequence> <xs:element ref="street" minOccurs="0" /> <xs:element ref="town" minOccurs="0" /> <xs:element ref="postcode" minOccurs="0" /> <xs:element ref="address" minOccurs="0" maxOccurs="unbounded" /> <xs:element ref="phone" minOccurs="0" /> <xs:element ref="fax" minOccurs="0" /> <xs:element ref="email" minOccurs="0" /> <xs:element ref="url" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="startDType" mixed="true"> <xs:complexContent> <xs:extension base="startDType"> <xs:attribute name="dtf" type="dateOrDateTimeDType"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="durationDType" mixed="true"> <xs:complexContent mixed="true"> <xs:extension base="durationDType"> <xs:attribute name="interval"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="prerequisiteDType" mixed="true"> <xs:complexContent> <xs:extension base="prerequisiteDType"> <xs:sequence> <xs:element ref="xhtml:div" minOccurs="0" /> </xs:sequence> <xs:attribute ref="xml:lang" use="optional" /> <xs:attribute name="href" type="xs:anyURI" use="optional" /> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="assessmentDType" mixed="true"> <xs:complexContent> <xs:extension base="assessmentDType"> <xs:sequence> <xs:element ref="xhtml:div" minOccurs="0" /> </xs:sequence> <xs:attribute ref="xml:lang" use="optional" /> <xs:attribute name="href" type="xs:anyURI" use="optional" /> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="objectiveDType" mixed="true"> <xs:complexContent> <xs:extension base="objectiveDType"> <xs:sequence> <xs:element ref="xhtml:div" minOccurs="0" /> </xs:sequence> <xs:attribute ref="xml:lang" use="optional" /> <xs:attribute name="href" type="xs:anyURI" use="optional" /> </xs:extension> </xs:complexContent> </xs:complexType> </xs:redefine> <xs:element name="street" type="xs:string" /> <xs:element name="town" type="xs:string" /> <xs:element name="postcode" type="xs:string" /> <xs:element name="address" type="xs:string" /> <xs:element name="phone" type="xs:string" /> <xs:element name="fax" type="xs:string" /> <xs:element name="email" type="xs:string" /> </xs:schema> </blockquote> Tavis on "XHTML markup guidelines" http://www.xcri.org/forum/topic.php?id=187#post-753 Thu, 01 Mar 2012 23:39:33 +0000 Tavis 753@http://www.xcri.org/forum/ Having just read a World Wide Web Consortium draft on <a href="http://www.w3.org/TR/html-polyglot/#named-entity-references">Polyglot Markup: HTML-Compatible XHTML Documents, section on Named Entity References</a>, and getting <a href="http://www.xcri.org/forum/topic.php?id=185#post-751">notice from Alan Paull that he's writing version 2</a> of the <a href="http://www.xcri.co.uk/h2-mm2-xcriblog/entry/straw-man.html">Data Definitions document</a>, I wonder if we might reconsider our advice on some aspects of XHTML markup. In particular, the special character section: 6) I am entirely happy with UTF-8... 7) If we are using UTF-8, then I think we should feel free to use a reasonable range of Unicode characters. For example, our Marketing team wanted to use <a href="http://en.wikipedia.org/wiki/Dash">en dashes</a> (and probably em dashes too). I agree, they should be used where instead of misusing hyphens. Perhaps this comes under "common punctuation list". 8) Back in the day, the HTML authoring advice used to be to use entities for special characters, but now with Unicode/UCS/UTF-8 pretty much the norm and widely available fonts with many glyphs, <a href="http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509/#IDAPNGO">recent advice</a> appears to be to "Only use escapes for characters in exceptional circumstances". And in those cases, use hexadecimal codes in preference, apparently (except for the five reserved XML entities amp, lt, gt, apos and quot). I would really rather prefer not to use named entities from HTML's Latin set which do not exist in XML, so we can treat the XHTML as XML and make it easier to use custom schema subsets of XHTML (for security, house style and validation reasons). It's still valid XHTML if you use '£' or '&⁠#xA3;' for pound sterling sign, and even better might be <abbr title="Great British Pound sterling (GBP)" class="currency">£</abbr>. On a practical note, we found we could lock down our HTML editor (FCKeditor) to only use numeric entities (&⁠#xa0; instead of &nbsp; then). Note, to make some entities display properly on this page, I have inserted a no-width space after ampersands (I think there's probably an irony here, but it's too late at night). However, I appreciate that there may be advantages to the existing special characters guidance (perhaps it matches content management system output), and experiences may vary. http://uclan-dev.myopenid.com/ on "Duplicate venues causing inflated file size." http://www.xcri.org/forum/topic.php?id=185#post-745 Wed, 29 Feb 2012 11:07:16 +0000 http://uclan-dev.myopenid.com/ 745@http://www.xcri.org/forum/ The UCLan main campus is at Preston but we have another campus at Burnley and another at Westlakes in Cumbria. We are currently offering approximately 100 PG and UG courses that can be studied at the Burnley campus. If we include course presentations for the next two academic sessions then the venue element for Burnley campus is duplicated 200 times. Where the courses are offered in both FT and PT mode this again doubles the number of duplicate venues. I think most people would agree that production of very large XML files is in nobodies best interest. On the other hand wholesale restructuring of the 1.2 schema to normalise the data is a non-starter. What then is the policy regarding providing multiple feeds ? I notice that the OU split their feeds on the basis of PG and UG course. On a related topic: In October this year UCLan will be opening its first overseas campus in Cyprus. UK students will be given the opportunity to study all or part of their course abroad. This is very much a part of our marketing strategy and as such must be prominent in our promotions. Unfortunately the XCRI-CAP 1.2 is somewhat UK centric. How are we to fit the Cypriot equivalent of postcode into a strictly typed and mandatory mlo:postcode element? Kind regards, Clive. University of Central Lancashire Scott Wilson on "BS8581 (aka XCRI CAP) out for public comment" http://www.xcri.org/forum/topic.php?id=186#post-746 Wed, 29 Feb 2012 13:05:24 +0000 Scott Wilson 746@http://www.xcri.org/forum/ Hi everyone, The British Standards version of XCRI-CAP is now available for public review as BS8581, and is in two parts: The specification can be found at: <a href="http://drafts.bsigroup.com/Home/Details/952" rel="nofollow">http://drafts.bsigroup.com/Home/Details/952</a> The code of practice (guidelines) are at: <a href="http://drafts.bsigroup.com/Home/Details/953" rel="nofollow">http://drafts.bsigroup.com/Home/Details/953</a> S 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. Craig Hawker on "Case sensitivity on enumerated values (and vocabularies?)" http://www.xcri.org/forum/topic.php?id=183#post-719 Sun, 19 Feb 2012 14:09:14 +0000 Craig Hawker 719@http://www.xcri.org/forum/ What's the expected case sensitivity of information, particularly where we have specified a list of valid values (e.g. studyMode, attendanceMode, attendancePattern)? I assume that any guidance on the above would also apply for any vocabularies...? My assumption thus far has been to be case-sensitive but I'm cross-referencing a couple of resources and noticing casing differences so perhaps I'm being too literal. Craig. Alan Paull on "Presentation title - can it be inheritable?" http://www.xcri.org/forum/topic.php?id=182#post-716 Thu, 16 Feb 2012 11:59:26 +0000 Alan Paull 716@http://www.xcri.org/forum/ Could we make Presentation title inheritable from Course title? That would make the XML less verbose, and very often the presentation data fails to include a title in any event, so systems would have to go and get the course title. Alan Scott Wilson on "Namespace changes ahead!" http://www.xcri.org/forum/topic.php?id=181#post-712 Wed, 08 Feb 2012 14:15:37 +0000 Scott Wilson 712@http://www.xcri.org/forum/ We've discussed before migrating from the XCRI.org namespace to PURLs: <a href="http://www.xcri.org/forum/topic.php?id=174" rel="nofollow">http://www.xcri.org/forum/topic.php?id=174</a> This is the approach likely to be taken in BS8581, which will supersede XCRI 1.2, probably later this year. The namespace URI will be: <a href="http://purl.org/xcri" rel="nofollow">http://purl.org/xcri</a> ... with element URIs of the form <a href="http://purl.org/xcri#name" rel="nofollow">http://purl.org/xcri#name</a> The question for us is do we: <ol> <li> Issue a new version of XCRI-CAP (1.2.1) now with the new namespace and element URIs? </li> <li> Leave XCRI-CAP 1.2 as-is, and issue some sort of advisory when BS8581 is published about important changes? </li> </ol> Scott Wilson on "Venues in 1.2" http://www.xcri.org/forum/topic.php?id=110#post-364 Fri, 20 Aug 2010 12:07:14 +0000 Scott Wilson 364@http://www.xcri.org/forum/ Another MLO vs XCRI issue. In MLO, there are two ways to identify where a learning opportunity is delivered: 1. Using a Location property (address) 2. Using the OfferedAt association to a Provider. In XCRI 1.1 there was Venue, which was a sort of halfway between a provider and location information. For XCRI 1.2 we initially proposed making Venue an association to Provider (mapping to method 2, above), but have no explicit mapping for method 1. So... the question is what makes the most sense? I can see a semantic distinction in the MLO properties between a location where a course is presented at the provider (e.g. a campus location) versus where a course is offered by a third party (e.g. by an associated college in a regional federation, or by a private training provider) which isn't covered by Venue, which can be used either way. I think the options are: 1. Keep Venue, which contains a Provider and Location element, and use for both same-provider locations and "offeredAt" relationships 2. Replace Venue with Location and OfferedAt. Location contains contact details, OfferedAt contains a Provider and its Location etc 3. As 2, but add a Title and Description to Location as well as the contact info. See <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> for the current draft. 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 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. 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 Alan Paull on "Postal addresses" http://www.xcri.org/forum/topic.php?id=170#post-635 Wed, 17 Aug 2011 13:39:02 +0000 Alan Paull 635@http://www.xcri.org/forum/ This is a thorny problem in XCRI-CAP 1.2, and I would welcome any help on how we can both work within the current XML binding and design a solution for the future. The problem is that a postal address in existing systems typically has from 2 to 6 address lines, ordered for post office use. Dependent on the system, the fields holding these will be variously labelled (for example Address1, Address2, Address3, and so on). However some have internal structures and arbitrary lines may be left blank on output. In addition some may have PO Box numbers, and may or may not include the organisations name as part of the address. Some will have counties, some won't. Postcodes are easy, because they are usually in a separate field. On output into XCRI-CAP 1.2 we store postal addresses in the Location element, and there are specific elements for Street, Town and Postcode. However, we cannot tell the content of the address lines output from a typical system. We can probably identify the Postcode, but it's unlikely we'll be able to identify a Town or Street field accurately. The only information we have is the order in which the fields are output. Many systems nowadays have a field for the house number and postcode, and then derive the rest of the address from a Post Office address lookup. I believe our objective in managing the postal addresses within XCRI-CAP 1.2 is to be able to collect an address and export an address with no loss of data. At the present time that's difficult, because the elements supporting postal addresses - Street, Town and Postcode - are insufficient. Adding in address lines through sequential Address elements is horrible, because XML should not depend on the inline order of the elements. And in addition the Address elements are supposed to contain other types of geo-spatial information, not postal addresses, so we can't even tell if they *are* postal addresses without eyeballing them. Automatic processing of multiple Address elements with no differentiation between them is problematic. We can input separate address lines, but we don't know how many we're going to get, how many are blank and where the blanks are (typically a standard 5 line address format might have 1 or 2 blanks). That means we can't easily output exactly what we've collected. I suggest that in future we would want to support the following requirements in relation to Postal Addresses: * 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 * Input and output of house number + Postcode for Postal Address look-up * Separate identification and storage of Postcode * Input and output of up to 6 address lines, in addition to postcode and house number Craig Hawker 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 Craig Hawker 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. 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 "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. https://plus.google.com/104793707299379214307/posts on "Using JAXB with XCRI-CAP XSD" http://www.xcri.org/forum/topic.php?id=173#post-659 Tue, 01 Nov 2011 08:00:11 +0000 https://plus.google.com/104793707299379214307/posts 659@http://www.xcri.org/forum/ I'm trying to generate a set of Java classes using the XCRI-CAP XSD. I was hoping to use JAXB to be able to do this. However, when I try to parse the schema I get the following error: [ERROR] undefined complex type 'startDType' This is referring to mlo_xcri_profile.xsd. I have the following XSDs in a single directory: dc.xsd dcmitype.xsd dcterms.xsd educationalcredit.xsd mlo-strict.xsd mlo_xcri_profile.xsd temp types.xsd xcri_cap_1_2.xsd xcri_cap_terms_1_2.xsd I am starting with xcri_cap_1_2.xsd. I get a similar message when I try the same thing using XMLBeans <a href="http://xmlbeans.apache.org/" rel="nofollow">http://xmlbeans.apache.org/</a> mlo_xcri_profile.xsd:64:3: error: Redefined complex type startDType not found in mlo-strict.xsd Has anyone had a similar problem or tried to do a similar thing? Thanks, Rob matthewwillard on "Generating classes from XCRI schema - "[ERROR] 'lang' is already defined"" http://www.xcri.org/forum/topic.php?id=49#post-142 Fri, 07 Nov 2008 11:45:39 +0000 matthewwillard 142@http://www.xcri.org/forum/ I am working on a web service application and need to generate Java classes from this schema: <a href="http://www.xcri.org/bindings/xcri_cap_1_1.xsd" rel="nofollow">http://www.xcri.org/bindings/xcri_cap_1_1.xsd</a> For speed, I chose to use NetBeans's JAXB binding wizard. The JAXB compiler's choking with this error: <output> xjc-typedef-target: jaxb-code-generation: Created dir: D:\XCRI NetBeans\build\generated\jaxbCache\XCRICAP Compiling file:/D:/XCRI NetBeans/xml-resources/jaxb/XCRICAP/www.xcri.org/bindings/xcri_cap_1_1.xsd [ERROR] 'lang' is already defined line 113 of <a href="http://www.w3.org/2001/xml.xsd" rel="nofollow">http://www.w3.org/2001/xml.xsd</a> [ERROR] (related to above error) the first definition appears here line 88 of <a href="http://www.w3.org/2001/03/xml.xsd" rel="nofollow">http://www.w3.org/2001/03/xml.xsd</a> [ERROR] 'space' is already defined line 122 of <a href="http://www.w3.org/2001/xml.xsd" rel="nofollow">http://www.w3.org/2001/xml.xsd</a> [ERROR] (related to above error) the first definition appears here line 95 of <a href="http://www.w3.org/2001/03/xml.xsd" rel="nofollow">http://www.w3.org/2001/03/xml.xsd</a> [ERROR] 'base' is already defined line 129 of <a href="http://www.w3.org/2001/xml.xsd" rel="nofollow">http://www.w3.org/2001/xml.xsd</a> [ERROR] (related to above error) the first definition appears here line 104 of <a href="http://www.w3.org/2001/03/xml.xsd" rel="nofollow">http://www.w3.org/2001/03/xml.xsd</a> [ERROR] 'specialAttrs' is already defined line 145 of <a href="http://www.w3.org/2001/xml.xsd" rel="nofollow">http://www.w3.org/2001/xml.xsd</a> [ERROR] (related to above error) the first definition appears here line 111 of <a href="http://www.w3.org/2001/03/xml.xsd" rel="nofollow">http://www.w3.org/2001/03/xml.xsd</a> failure in the XJC task. Use the Ant -verbose switch for more details D:\XCRI NetBeans\nbproject\xml_binding_build.xml:18: unable to parse the schema. Error messages should have been provided BUILD FAILED (total time: 7 seconds) </output> For two W3C schemas to clash would seem to be such a common error that finding the solution ought to be easy, but two days wasted on this has uncovered nothing. The goal is to have an Ant script which uses JAXB to generate classes from that schema. I have tried Castor but run into other problems and for this project I'd rather use JAXB anyway. Eclipse is my usual IDE. Anyone run into the same problem? https://plus.google.com/100435963860845547248 on "XCRI-CAP 1.2 getting started guide" http://www.xcri.org/forum/topic.php?id=172#post-654 Fri, 07 Oct 2011 13:09:06 +0000 https://plus.google.com/100435963860845547248 654@http://www.xcri.org/forum/ Hi I'm project manager for Stage 1 of the Course Data programme at the University of Sussex, so I'm just getting going with XCRI-CAP. Back at the XCRI Exchange in June 2011, there was a group discussion on upgrading to XCRI-CAP 1.2. There is a note that: "XCRI dummies – a usage guide. Current docs aimed at standards bodies, not even developers. Need a guide for next level. Why to use this field, how have others used this field etc." <a href="http://br.inin.jisc-ssbr.net/2011/06/29/br-assembly-xcri/" rel="nofollow">http://br.inin.jisc-ssbr.net/2011/06/29/br-assembly-xcri/</a> Has this guide been written? I've had a look for some entry-level documentation on 1.2, and haven't found it yet. The annotated XCRI-CAP 1.1 feed from the OU is very helpful, it would be great to know if there's a 1.2 version of this out there. Any pointers would be great Also, I am finding a few dead links on the xcri.org site; is it useful to send these to anyone? Many thanks Carol Shergold University of Sussex