Relax range of name (and many others)

[philbarker]

OrganizationName has a range of xsd:token. We are trying to use CEDS ontology properties for the PESC Transcript standard, which has to work internationally. Many organizations represent their name in different languages, e.g. French and English in parts of Canada, and it is desirable to be able to use a langString so that the different language variations can be noted and applications can select the appropriate one. In order to accommodate this and any current use of the property where the language is not noted, we suggest the range be set to rdfs:Literal.

The similar considerations apply to many other properties that have xsd:token as their range, such as AddressCity, AddressCountyName, CalendarEventDayName, CourseTitle etc. etc.

[aemnathanclinton]

Should all xsd:token and xsd:string elements be converted to rdfs:Literal to support langString?

[philbarker]

Probably not. Strings and tokens can be alpha-numeric codes that are language independent. These would often be best coded as xsd:token

Also, I think you are using xsd:string for some dates (where xsd:date or schema:date would be better) e.g.

	<rdf:Property rdf:about="http://ceds.ed.gov/terms#P000081">
	<rdfs:label>Diploma or Credential Award Date</rdfs:label>
		<skos:notation>DiplomaOrCredentialAwardDate</skos:notation>
		<schema:domainIncludes rdf:resource="http://ceds.ed.gov/terms#C200006"/>
		<schema:rangeIncludes rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>

[philbarker]

Sorry @aemnathanclinton I misread the question: yes you could change all xsd:token and xsd:string elements to rdfs:Literal.
I'll leave my previous reply as it might be worth making some of them more specific.

[aemnathanclinton]

@philbarker, Looking at the properties you referenced, they are all xsd:string. There are only two properties that are xsd:token, and they are identifiers. Do you still recommend implementing rdfs:literal, or does xsd:string give you what you need?

[philbarker]

As I understand it, PESC transcript is used in Canada so they need to know which data is in English and which in French, hence langstring is better than string.