OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OSLCCORE-128) oslc:maxSize meaning

David Honey created OSLCCORE-128:

             Summary: oslc:maxSize meaning
                 Key: OSLCCORE-128
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-128
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
          Components: Core
            Reporter: David Honey
            Assignee: James Amsden

The oslc:maxSize property is defined in OSLC Core 3.0 as:

"For datatype properties whose type is xsd:string, oslc:maxSize specifies the maximum number of characters in the defined property value. The absence of oslc:maxSize indicates that either there is no maximum size or that the maximum size is specified some other way."

Does this mean the number of:
1) Unicode characters?
2) Code points?
3) Bytes in some encoding?
It looks like the first is the intended meaning,.

The issue is that many relational databases define VARCHAR(N) as a maximum of N UTF-8 encoded bytes (or a server encoding). 

The spec should be persistence agnostic and allow non-RDF-persistence that have well-defined size constraints, such as VARCHAR(N), to be described. 

The problem with the current definition is that an OSLC server that uses a relational database cannot meaningfully describe the oslc:maxSize of strings because the number of characters depends on whether each character is a 1, 2, 3, or 4 byte encoding - see http://tools.ietf.org/html/rfc3629.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]